Quasi co-location relationship indication of dormant or deactivated carriers

Abstract

Methods, systems, and devices for wireless communication are described. A user equipment (UE) may receive a carrier indication identifying a first carrier and a second carrier for communication between the UE and a network entity. The UE may receive a first quasi-co-location (QCL) indication using the first carrier. The first QCL indication may identify a first set of QCL information, the first set of QCL information corresponding to a reference signal received using the first carrier. The UE may receive a second QCL indication using the second carrier. The second QCL indication may identify the reference signal and may indicate that the first set of QCL information is associated with signaling received using the second carrier.

Description

[0001] Cross-reference

[0002] This patent application claims the benefit of U.S. Patent Application No. 18 / 064,857, filed Dec. 12, 2022, by ABOTABL et al., entitled "QUASI CO-LOCATION RELATIONSHIP INDICATIONS FOR DORMANT OR DEACTIVATED CARRIERS", which is assigned to the assignee of the present application. Technical Field

[0003] The following relates to wireless communication, including indicating quasi co-location (QCL) relationships for dormant and / or deactivated carriers.

[0004] Description of Related Art

[0005] Wireless communication systems are widely deployed to provide various types of communication content such as voice, video, packet data, messaging, broadcasting, etc. These systems may be capable of supporting communication with multiple users by sharing available system resources (e.g., time, frequency, and power). Examples of such multi-access systems include fourth-generation (4G) systems such as Long-Term Evolution (LTE) systems, LTE-Advanced (LTE-A) systems, or LTE-A Pro systems, and fifth-generation (5G) systems which may be referred to as New Radio (NR) systems. These systems may employ techniques such as Code Division Multiple Access (CDMA), Time Division Multiple Access (TDMA), Frequency Division Multiple Access (FDMA), Orthogonal FDMA (OFDMA), or Discrete Fourier Transform Spread Orthogonal Frequency Division Multiplexing (DFT-S-OFDM). A wireless multi-access communication system may include one or more network entities, each supporting wireless communication of communication devices which may be referred to as User Equipment (UE).

[0006] In some wireless communication systems, operations performed at a network entity may result in increased power consumption and associated costs. To save power, the network entity may support secondary cell (SCell) deactivation and SCell dormancy. In some cases, the network entity may configure the UE with an anchor cell (such as a primary cell) to determine the quality of SCell(s) that can (or may have previously been) deactivated or put into dormancy. For example, the network entity may infer (e.g., determine) the quality of the deactivated or dormant SCell(s) based on measurements performed on reference signals transmitted using an anchor carrier associated with the anchor cell. Additionally or alternatively, the UE may identify parameters to be used for receiving the signaling based on a quasi-colocation (QCL) relationship between signaling transmitted using an SCell carrier associated with the SCell and the reference signal. However, in some cases, the network entity may not be able to indicate the QCL relationship between the signaling and the reference signal to the UE. For example, the network entity may lack a mechanism for indicating one or more QCL relationships between signaling transmitted using carriers associated with different cells, let alone an efficient mechanism. SUMMARY

[0007] The systems, methods, and devices of the present disclosure each have several innovative aspects, none of which is solely responsible for the desired attributes disclosed herein.

[0008] One innovative aspect of the subject matter described in the present disclosure may be implemented in a method for wireless communication. The method may include: receiving a carrier indication that identifies a first carrier and a second carrier for communication between a user equipment (UE) and a network entity; receiving, using the first carrier, a first quasi-colocation (QCL) indication that identifies a first set of QCL information, the first set of QCL information corresponding to a reference signal received using the first carrier; and receiving, using the second carrier, a second QCL indication that identifies the reference signal and indicates that the first set of QCL information is associated with signaling received using the second carrier.

[0009] Another innovative aspect of the subject matter described in this disclosure may be implemented in a device for wireless communication. The device may include: a processor; a memory coupled to the processor; and instructions stored in the memory. The instructions may be executable by the processor to cause the device to: receive a carrier indication that identifies a first carrier and a second carrier for communication between a UE and a network entity; receive, using the first carrier, a first QCL indication that identifies a first set of QCL information, the first set of QCL information corresponding to a reference signal received using the first carrier; and receive, using the second carrier, a second QCL indication that identifies the reference signal and indicates that the first set of QCL information is associated with signaling received using the second carrier.

[0010] Another innovative aspect of the subject matter described in this disclosure may be implemented in a device for wireless communication. The device may include: means for receiving a carrier indication that identifies a first carrier and a second carrier for communication between a UE and a network entity; means for receiving, using the first carrier, a first QCL indication that identifies a first set of QCL information, the first set of QCL information corresponding to a reference signal received using the first carrier; and means for receiving, using the second carrier, a second QCL indication that identifies the reference signal and indicates that the first set of QCL information is associated with signaling received using the second carrier.

[0011] Another innovative aspect of the subject matter described in this disclosure may be implemented in a non-transitory computer-readable medium storing code for wireless communication. The code may include instructions executable by a processor to: receive a carrier indication that identifies a first carrier and a second carrier for communication between a UE and a network entity; receive, using the first carrier, a first QCL indication that identifies a first set of QCL information, the first set of QCL information corresponding to a reference signal received using the first carrier; and receive, using the second carrier, a second QCL indication that identifies the reference signal and indicates that the first set of QCL information is associated with signaling received using the second carrier.

[0012] Another innovative aspect of the subject matter described in this disclosure may be implemented in a method for wireless communication. The method may include: outputting a carrier indication that identifies a first carrier and a second carrier for communication between a UE and a network entity; using the first carrier to output a first QCL indication that identifies a first set of QCL information, the first set of QCL information corresponding to a reference signal output using the first carrier; and using the second carrier to output a second QCL indication that identifies the reference signal and indicates that the first set of QCL information is associated with signaling output using the second carrier.

[0013] Another innovative aspect of the subject matter described in this disclosure may be implemented in a device for wireless communication. The device may include: a processor; a memory coupled to the processor; and instructions stored in the memory. The instructions may be executable by the processor to cause the device to: output a carrier indication that identifies a first carrier and a second carrier for communication between a UE and a network entity; use the first carrier to output a first QCL indication that identifies a first set of QCL information, the first set of QCL information corresponding to a reference signal output using the first carrier; and use the second carrier to output a second QCL indication that identifies the reference signal and indicates that the first set of QCL information is associated with signaling output using the second carrier.

[0014] Another innovative aspect of the subject matter described in this disclosure may be implemented in a device for wireless communication. The device may include: means for outputting a carrier indication that identifies a first carrier and a second carrier for communication between a UE and a network entity; means for using the first carrier to output a first QCL indication that identifies a first set of QCL information, the first set of QCL information corresponding to a reference signal output using the first carrier; and means for using the second carrier to output a second QCL indication that identifies the reference signal and indicates that the first set of QCL information is associated with signaling output using the second carrier.

[0015] Another innovative aspect of the subject matter described in this disclosure can be implemented in a non-transitory computer-readable medium storing code for wireless communication. The code can include instructions that can be executed by a processor to perform the following operations: output a carrier indication that identifies a first carrier and a second carrier for communication between a UE and a network entity; use the first carrier to output a first QCL indication that identifies a first set of QCL information, the first set of QCL information corresponding to a reference signal output using the first carrier; and use the second carrier to output a second QCL indication that identifies the reference signal and indicates that the first set of QCL information is associated with signaling output using the second carrier. BRIEF DESCRIPTION OF THE DRAWINGS

[0016] Figure 1 and Figure 2 each illustrate an example of a wireless communication system supporting quasi-co-location (QCL) relationship indication for a dormant and / or deactivated carrier, in accordance with one or more aspects of the present disclosure.

[0017] Figure 3 illustrates an example of a timing diagram supporting QCL relationship indication for a dormant and / or deactivated carrier, in accordance with one or more aspects of the present disclosure.

[0018] Figure 4 illustrates an example of a process flow supporting QCL relationship indication for a dormant and / or deactivated carrier, in accordance with one or more aspects of the present disclosure.

[0019] Figure 5 and Figure 6 illustrates a block diagram of a device supporting QCL relationship indication for a dormant and / or deactivated carrier, in accordance with one or more aspects of the present disclosure.

[0020] Figure 7 illustrates a block diagram of a communication manager supporting QCL relationship indication for a dormant and / or deactivated carrier, in accordance with one or more aspects of the present disclosure.

[0021] Figure 8 illustrates a diagram of a system including a device supporting QCL relationship indication for a dormant and / or deactivated carrier, in accordance with one or more aspects of the present disclosure.

[0022] Figure 9 and Figure 10 illustrates a block diagram of a device supporting QCL relationship indication for a dormant and / or deactivated carrier, in accordance with one or more aspects of the present disclosure.

[0023] Figure 11 illustrates a block diagram of a communication manager supporting QCL relationship indication for a dormant and / or deactivated carrier, in accordance with one or more aspects of the present disclosure.

[0024] Figure 12 A diagram illustrating a system including a device supporting a QCL relationship indication for carrier sleep and / or deactivation according to one or more aspects of the present disclosure.

[0025] Figures 13 to 16 A flowchart illustrating a method supporting a QCL relationship indication for carrier sleep and / or deactivation according to one or more aspects of the present disclosure. Detailed Description

[0026] In some wireless communication systems, operations performed at a network entity may result in increased energy consumption and associated costs. In some cases, to conserve energy at the network entity, the network entity may support secondary cell (SCell) deactivation, where the network entity deactivates the use of an SCell for wireless communication. For example, the network entity may send control signaling to a user equipment (UE) that instructs the UE to deactivate the use of the SCell. In some cases, the network entity may avoid using a carrier associated with the deactivated SCell for downlink transmission to the UE (e.g., to conserve energy). A carrier associated with a deactivated SCell may be referred to as a deactivated carrier. Additionally or alternatively, the network entity may support SCell sleep, where the network entity activates a sleep mode for a carrier associated with the SCell (e.g., using a sleep bandwidth part (BWP)). A carrier for which the sleep mode is activated may be referred to as a sleeping carrier. Since the network entity may avoid using a deactivated or sleeping carrier to transmit reference signals (or other types of signaling), the network entity may use another carrier associated with another cell to determine the quality of the SCell associated with the deactivated or sleeping carrier. For example, the network entity may configure the UE with an anchor carrier associated with an anchor cell and use the anchor carrier to send reference signals to the UE. In some instances, the network entity may infer (e.g., determine) the quality of the SCell based on measurements performed on the reference signals at the UE. Additionally or alternatively, the UE may identify one or more parameters for receiving the signaling based on, for example, a quasi - co - location (QCL) relationship between signaling sent using the SCell and the reference signals. However, the network entity may not be able to indicate such QCL relationships to the UE, or may not be configured to indicate such QCL relationships to the UE. For example, the network entity may lack a mechanism for indicating QCL relationships between signaling sent using carriers associated with different cells.

[0027] Various aspects generally relate to the indication of the QCL relationship for a dormant and / or deactivated carrier, and more specifically, to a framework for configuring a UE with the QCL relationship between a reference signal transmitted using an anchor cell and signaling transmitted using an SCell. For example, the network entity may configure the UE to use an anchor carrier associated with the anchor cell and an SCell carrier associated with the SCell. In such examples, the network entity and the UE may use the anchor carrier to send a first QCL indication to the UE. The first QCL indication may identify a first set of QCL information, where the first set of QCL information corresponds to a reference signal received or to be received at the UE using the anchor carrier. In some examples, after sending the first QCL indication, during a duration in which the SCell may be active / activated or in a non-dormant mode, the network entity may use the SCell carrier to send a second QCL indication to the UE. The second QCL indication may identify the reference signal received or to be received at the UE using the anchor carrier. Additionally or alternatively, the second QCL indication may indicate to the UE that the first set of QCL information is associated with signaling to be received at the UE using the SCell carrier. That is, the network entity may use the second QCL indication to configure the UE with the QCL relationship between the reference signal transmitted using the anchor cell and the signaling transmitted using the SCell. In some examples, after sending the second QCL indication, the network entity may indicate to the UE to deactivate the SCell or switch the SCell from the non-dormant mode to the dormant mode, such that the network entity may avoid using the SCell for downlink transmission to the UE. In some examples, after using the anchor carrier to transmit the reference signal, the network entity may indicate to the UE to activate the SCell or switch the SCell from the dormant mode to the non-dormant mode, such that the network entity may use the SCell to send the signaling to the UE. In such examples, based on the QCL relationship, the UE may receive the signaling from the network entity according to the first set of QCL information and the reference signal.

[0028] Certain aspects of the subject matter described in this disclosure can achieve one or more of the following potential advantages. The techniques employed by the described communication devices can provide energy savings for the network entity by enabling the network entity to reduce the signaling overhead associated with determining the quality of a dormant or deactivated SCell. For example, the network entity can send a reference signal to the UE by using an anchor carrier associated with a previously dormant or deactivated SCell and determine the quality of the SCell with reduced signaling overhead by configuring the UE with the QCL relationship between the reference signal and the signaling sent using the SCell, rather than relying on the SCell to send such a reference signal (which would require the SCell to be active). In some implementations, the operations performed by the described communication devices can support improvements in the latency and reliability of downlink communication via the previously dormant or deactivated SCell, as well as other possible benefits, by enabling the network entity to use the previously dormant or deactivated SCell to send signaling without first using the previously dormant or deactivated SCell to send a reference signal for determining the quality.

[0029] Aspects of the present disclosure are initially described in the context of a wireless communication system. Aspects of the present disclosure are also described in the context of timing diagrams and process flows. Aspects of the present disclosure are further illustrated by, and described with reference to, apparatus diagrams, system diagrams, and flowcharts related to indicating QCL relationships for dormant and / or deactivated carriers.

[0030] Figure 1 An example of a wireless communication system 100 that supports indicating QCL relationships for dormant and / or deactivated carriers in accordance with one or more aspects of the present disclosure is illustrated. The wireless communication system 100 can include one or more network entities 105, one or more UEs 115, and a core network 130. In some examples, the wireless communication system 100 can be a Long Term Evolution (LTE) network, an LTE-Advanced (LTE-A) network, an LTE-A Pro network, a New Radio (NR) network, or a network operating according to other system and radio technologies, including future system and radio technologies not explicitly mentioned herein.

[0031] The network entity 105 can be dispersed throughout a geographical area to form a wireless communication system 100 and can include devices in different forms or with different capabilities. In various examples, the network entity 105 can be referred to as a network element, a mobility element, a radio access network (RAN) node, or network equipment, among other designations. In some examples, the network entity 105 and the UE 115 can communicate wirelessly via one or more communication links 125 (e.g., radio frequency (RF) access links). For example, the network entity 105 can support a coverage area 110 (e.g., a geographical coverage area), and the UE 115 and the network entity 105 can establish one or more communication links 125 over the coverage area. The coverage area 110 can be an example of a geographical area within which the network entity 105 and the UE 115 can support the conveyance of signals according to one or more radio access technologies (RATs).

[0032] The UEs 115 can be spread throughout the entire coverage area 110 of the wireless communication system 100, and each UE 115 can be stationary, or mobile, or both at different times. The UEs 115 can be devices in different forms or with different capabilities. In Figure 1 some example UEs 115 are illustrated. The UEs 115 can be capable of supporting communication with various types of devices (such as other UEs 115 or network entities 105 as shown Figure 1 ).

[0033] The nodes of the wireless communication system 100 (which can be referred to as network nodes or wireless nodes) can be the network entity 105 (e.g., any network entity), the UE 115 (e.g., any UE), a network controller, a device, an apparatus, a computing system, one or more components, or another suitable processing entity configured to perform any of the techniques described in this disclosure. For example, the node can be the UE 115. As another example, the node can be the network entity 105. As yet another example, a first node can be configured to communicate with a second node or a third node. In one aspect of this example, the first node can be the UE 115, the second node can be the network entity 105, and the third node can be the UE 115. In another aspect of this example, the first node can be the UE 115, the second node can be the network entity 105, and the third node can be the network entity 105. In other aspects of this example, the first node, the second node, and the third node can be different from these examples. Similarly, references to the UE 115, the network entity 105, the device, the apparatus, the computing system, etc. can include the disclosure of the UE 115, the network entity 105, the device, the apparatus, the computing system, etc. as nodes. For example, the disclosure that the UE 115 is configured to receive information from the network entity 105 also discloses that a first node is configured to receive information from a second node.

[0034] In some examples, network entity 105 may communicate with core network 130 or with each other or both. For example, network entity 105 may communicate with core network 130 via one or more backhaul communication links 120 (e.g., according to S1, N2, N3, or other interface protocols). In some examples, network entity 105 may communicate with each other directly (e.g., directly between network entities 105) or indirectly (e.g., via core network 130) via backhaul communication link 120 (e.g., according to X2, Xn, or other interface protocols). In some examples, network entity 105 may communicate with each other via midhaul communication link 162 (e.g., according to a midhaul interface protocol) or fronthaul communication link 168 (e.g., according to a fronthaul interface protocol) or any combination thereof. Backhaul communication link 120, midhaul communication link 162, or fronthaul communication link 168 may be or include one or more wired links (e.g., electrical links, fiber optic links), one or more wireless links (e.g., radio links, wireless optical links), etc., or various combinations thereof. UE 115 may communicate with core network 130 via communication link 155.

[0035] One or more of network entities 105 may include or may be referred to as base station 140 (e.g., transceiver base station, radio base station, NR base station, access point, radio transceiver, NodeB, eNodeB (eNB), next generation NodeB, or gigabit NodeB (any of which may be referred to as gNB), 5G NB, next generation eNB (ng-eNB), home NodeB, home eNodeB, or other suitable terms). In some examples, network entity 105 (e.g., base station 140) may be implemented in an aggregated (e.g., monolithic, stand-alone) base station architecture that may be configured to utilize a protocol stack physically or logically integrated within a single network entity 105 (e.g., a single RAN node, such as base station 140).

[0036] In some examples, network entity 105 may be implemented in a split architecture (e.g., split base station architecture, split RAN architecture), which may be configured to utilize a protocol stack physically or logically distributed between two or more network entities 105 (such as an integrated access backhaul (IAB) network, an open RAN (O-RAN) (e.g., a network configuration sponsored by the O-RAN Alliance), or a virtualized RAN (vRAN) (e.g., a cloud RAN (C-RAN))). For example, network entity 105 may include one or more of the following: a central unit (CU) 160, a distributed unit (DU) 165, a radio unit (RU) 170, a RAN intelligent controller (RIC) 175 (e.g., a near-real-time RIC (near-RT RIC), a non-real-time RIC (non-RT RIC)), a service management and orchestration (SMO) 180 system, or any combination thereof. The RU 170 may also be referred to as a radio headend, an intelligent radio headend, a remote radio headend (RRH), a remote radio unit (RRU), or a transmit receive point (TRP). One or more components of network entity 105 in the split RAN architecture may be co-located, or one or more components of network entity 105 may be located at distributed locations (e.g., separate physical locations). In some examples, one or more network entities 105 of the split RAN architecture may be implemented as virtual units (e.g., a virtual CU (VCU), a virtual DU (VDU), a virtual RU (VRU)).

[0037] The functional split between the CU 160, DU 165, and RU 170 is flexible and can support different functions, depending on which functions are performed at the CU 160, DU 165, and RU 170 (e.g., network layer functions, protocol layer functions, baseband functions, RF functions, and any combination thereof). For example, a functional split of the protocol stack can be adopted between the CU 160 and the DU 165 such that the CU 160 can support one or more layers of the protocol stack and the DU 165 can support one or more different layers of the protocol stack. In some examples, the CU 160 can host higher protocol layer (e.g., layer 3 (L3), layer 2 (L2)) functions and signaling (e.g., radio resource control (RRC), service data adaptation protocol (SDAP), packet data convergence protocol (PDCP)). The CU 160 can be connected to one or more DU 165s or RU 170s, and one or more DU 165s or RU 170s can host lower protocol layers, such as layer 1 (L1) (e.g., physical (PHY) layer) or L2 (e.g., radio link control (RLC) layer, medium access control (MAC) layer) functions and signaling, and can each be at least partially controlled by the CU 160. Additionally or alternatively, a functional split of the protocol stack can be adopted between the DU 165 and the RU 170 such that the DU 165 can support one or more layers of the protocol stack and the RU 170 can support one or more different layers of the protocol stack. The DU 165 can support one or more different cells (e.g., via one or more RU 170s). In some cases, the functional split between the CU 160 and the DU 165 or between the DU 165 and the RU 170 can be within a protocol layer (e.g., some functions of a protocol layer can be performed by one of the CU 160, DU 165, or RU 170, while other functions of that protocol layer are performed by another of the CU 160, DU 165, or RU 170). The CU 160 can be further functionally split into a CU control plane (CU-CP) and a CU user plane (CU-UP) function. The CU 160 can be connected to one or more DU 165s via an intermediate transport communication link 162 (e.g., F1, F1-c, F1-u), and the DU 165 can be connected to one or more RU 170s via a fronthaul communication link 168 (e.g., open fronthaul (FH) interface). In some examples, the intermediate transport communication link 162 or the fronthaul communication link 168 can be implemented according to the interfaces (e.g., channels) between the layers of the protocol stack, which are supported by the respective network entities 105 communicating via such communication links.

[0038] In a wireless communication system (e.g., wireless communication system 100), the infrastructure and spectrum resources for radio access can support wireless backhaul link capabilities to supplement a wired backhaul connection, thereby providing an IAB network architecture (e.g., to core network 130). In some cases, in an IAB network, one or more network entities 105 (e.g., IAB nodes 104) can be partially controlled by each other. One or more IAB nodes 104 can be referred to as donor entities or IAB donors. One or more DUs 165 or one or more RUs 170 can be partially controlled by one or more CUs 160 associated with a host network entity 105 (e.g., host base station 140). One or more host network entities 105 (e.g., IAB hosts) can communicate with one or more additional network entities 105 (e.g., IAB nodes 104) via the supported access and backhaul links (e.g., backhaul communication link 120). An IAB node 104 can include an IAB mobile terminal (IAB-MT) controlled (e.g., scheduled) by a DU 165 of a coupled IAB host. The IAB-MT can include a separate antenna set for relaying communication with the UE 115, or can share the same antenna of the IAB node 104 (e.g., of the RU 170) for accessing via the DU 165 of the IAB node 104 (e.g., referred to as a virtual IAB-MT (vIAB-MT)). In some examples, the IAB node 104 can include a DU 165 that supports communication links with additional entities (e.g., IAB nodes 104, UEs 115) within a relay chain or configuration (e.g., downstream) of the access network. In such cases, one or more components of the split RAN architecture (e.g., one or more IAB nodes 104 or components of the IAB node 104) can be configured to operate according to the techniques described in this disclosure.

[0039] In the context of the techniques described in this disclosure being applied to a split RAN architecture, one or more components of the split RAN architecture can be configured to support indication of QCL relationships for dormant and / or deactivated carriers. For example, some operations described as being performed by the UE 115 or network entity 105 (e.g., base station 140) can additionally or alternatively be performed by one or more components of the split RAN architecture (e.g., IAB nodes 104, DUs 165, CUs 160, RUs 170, RIC 175, SMO 180).

[0040] The UE 115 may include or may be referred to as a mobile device, a wireless communication device, a remote device, a handheld device, or a subscriber device, or some other suitable term. In some examples, a "device" may also be referred to as a unit, a station, a terminal, or a client, etc. The UE 115 may also include or may be referred to as a personal electronic device, such as a cellular phone, a personal digital assistant (PDA), a tablet computer, a laptop computer, or a personal computer. In some examples, the UE 115 may include or may be referred to as a wireless local loop (WLL) station, an Internet of Things (IoT) device, an Internet of Everything (IoE) device, or a machine type communication (MTC) device, etc., which may be implemented in various objects such as electrical appliances, vehicles, meters, etc.

[0041] The UE 115 may be capable of communicating with various types of devices, such as other UE 115s that may sometimes act as relays, and network entities 105 and network equipment including macro eNBs or gNBs, small cell eNBs or gNBs, relay base stations, etc., as Figure 1 shown.

[0042] The UE 115 and the network entity 105 may wirelessly communicate with each other via one or more communication links 125 (e.g., access links) using resources associated with one or more carriers. The term "carrier" may refer to a set of RF spectral resources having a defined physical layer structure for supporting the communication link 125. For example, a carrier for the communication link 125 may include a portion (e.g., BWP) of an RF spectral band that operates according to one or more physical layer channels for a given radio access technology (e.g., LTE, LTE-A, LTE-A Pro, NR). Each physical layer channel may carry acquisition signaling (e.g., synchronization signals, system information), control signaling for coordinating carrier operation, user data, or other signaling. The wireless communication system 100 may support communication with the UE 115 using carrier aggregation or multi-carrier operation. According to a carrier aggregation configuration, the UE 115 may be configured to have multiple downlink component carriers and one or more uplink component carriers. Carrier aggregation may be used for both frequency division duplex (FDD) and time division duplex (TDD) component carriers. Communication between the network entity 105 and other devices may refer to communication between a device and any part (e.g., entity, sub-entity) of the network entity 105. For example, in examples where the network entity 105 may be involved, the terms "transmit", "receive", or "communicate" may refer to any part (e.g., directly or via one or more other network entities 105) of the network entity 105 of the RAN (e.g., base station 140, CU 160, DU 165, RU170) communicating with another device.

[0043] In some examples, such as in a carrier aggregation configuration, a carrier may also have acquisition signaling or control signaling that coordinates the operation of other carriers. A carrier may be associated with a frequency channel (e.g., an evolved universal mobile telecommunications system terrestrial radio access (E-UTRA) absolute RF channel number (EARFCN)), and may be identified according to a channel raster for discovery by UE 115. A carrier may operate in an independent mode, in which case initial capture and connection may be performed by UE 115 via the carrier, or a carrier may operate in a non-independent mode, in which case the connection is anchored using a different carrier (e.g., different carriers of the same or different radio access technologies).

[0044] The communication link 125 shown in the wireless communication system 100 may include a downlink transmission (e.g., a forward link transmission) from the network entity 105 to UE 115, an uplink transmission (e.g., a return link transmission) from UE 115 to the network entity 105, or both, and other transmission configurations. A carrier may carry downlink or uplink communication (e.g., in FDD mode), or may be configured to carry both downlink and uplink communication (e.g., in TDD mode).

[0045] A carrier may be associated with a specific bandwidth of the RF spectrum, and in some examples, the carrier bandwidth may be referred to as the "system bandwidth" of the carrier or the wireless communication system 100. For example, the carrier bandwidth may be one of a set of bandwidths for a carrier of a particular radio access technology (e.g., 1.4 megahertz (MHz), 3 MHz, 5 MHz, 10 MHz, 15 MHz, 20 MHz, 40 MHz, or 80 MHz). Devices of the wireless communication system 100 (e.g., the network entity 105, UE 115, or both) may have a hardware configuration that supports communication using a specific carrier bandwidth, or may be capable of being configured to support communication using one of a set of carrier bandwidths. In some examples, the wireless communication system 100 may include a network entity 105 or UE 115 that supports concurrent communication using carriers associated with multiple carrier bandwidths. In some examples, each served UE 115 may be configured to operate using a portion (e.g., a subband, a BWP) or all of the carrier bandwidth.

[0046] The signal waveform transmitted via a carrier can be composed of multiple subcarriers (e.g., using multi-carrier modulation (MCM) techniques such as orthogonal frequency division multiplexing (OFDM) or discrete Fourier transform spread OFDM (DFT-S-OFDM)). In a system adopting MCM techniques, a resource element can refer to the resource of one symbol duration (e.g., the duration of one modulation symbol) and one subcarrier. In this case, the symbol duration and the subcarrier spacing can be inversely related. The number of bits carried by each resource element can depend on the modulation scheme (e.g., the order of the modulation scheme, the decoding rate of the modulation scheme, or both), such that a relatively large number of resource elements (e.g., during the transmission duration) and a relatively high-order modulation scheme can correspond to a relatively high communication rate. Wireless communication resources can refer to a combination of RF spectrum resources, time resources, and space resources (e.g., spatial layers, beams), and the use of multiple space resources can increase the data rate or data integrity for communication with UE 115.

[0047] One or more parameter sets of the carrier can be supported, and the parameter set can include the subcarrier spacing (Δf) and the cyclic prefix. The carrier can be divided into one or more BWPs with the same or different parameter sets. In some examples, UE 115 can be configured with multiple BWPs. In some examples, a single BWP of the carrier can be active at a given time, and the communication of UE 115 can be restricted to one or more active BWPs.

[0048] The time interval for the network entity 105 or UE 115 can be expressed as a multiple of a basic time unit, which can refer to, for example, the sampling duration T s = 1 / (Δf max ·N f ) seconds, where Δf max can represent the supported subcarrier spacing, and N f can represent the supported discrete Fourier transform (DFT) size. The time interval of the communication resources can be organized according to radio frames each having a specific duration (e.g., 10 milliseconds (ms)). Each radio frame can be identified by a system frame number (SFN) (e.g., ranging from 0 to 1023).

[0049] Each frame may include a plurality of consecutively numbered sub - frames or time slots, and each sub - frame or time slot may have the same duration. In some examples, a frame may be divided (e.g., in the time domain) into sub - frames, and each sub - frame may be further divided into a plurality of time slots. Alternatively, each frame may include a variable number of time slots, and the number of time slots may depend on the sub - carrier spacing. Each time slot may include a certain number of symbol durations (e.g., depending on the length of the cyclic prefix added before each symbol duration). In some wireless communication systems 100, a time slot may be further divided into a plurality of mini - time slots associated with one or more symbols. Excluding the cyclic prefix, each symbol duration may be associated with one or more (e.g., N f

[0050]

[0051]

[0052] sub - frames, time slots, mini - time slots, or symbols may be the smallest scheduling units (e.g., in the time domain) of the wireless communication system 100 and may be referred to as transmission time intervals (TTIs). In some examples, the TTI duration (e.g., the number of symbol durations in a TTI) may be variable. Additionally or alternatively, the smallest scheduling unit of the wireless communication system 100 may be dynamically selected (e.g., in bursts of shortened TTIs (sTTIs)).

[0051] The network entity 105 may provide communication coverage via one or more cells (e.g., macro cells, small cells, hotspots, or other types of cells or any combination thereof). The term "cell" may refer to a logical communication entity for communicating with the network entity 105 (e.g., using a carrier), and may be associated with an identifier for distinguishing adjacent cells (e.g., physical cell identifier (PCID), virtual cell identifier (VCID), or others). In some examples, a cell may also refer to a coverage area 110 or a portion of the coverage area 110 (e.g., a sector) on which the logical communication entity operates. Depending on various factors (such as the capabilities of the network entity 105), the scope of such cells can range from a smaller area (e.g., a structure, a subset of a structure) to a larger area. For example, a cell may be or may include a building, a subset of a building, or an external space between or overlapping the coverage areas 110, etc.

[0053] Macro cells typically cover a relatively large geographical area (e.g., with a radius of several kilometers) and may allow UEs 115 with a service subscription to the network provider supporting the macro cell to have unconstrained access. Compared with macro cells, small cells may be associated with a lower power network entity 105 (e.g., a lower power base station 140), and small cells may operate using the same or different (e.g., licensed, unlicensed) frequency bands as macro cells. Small cells may provide unconstrained access to UEs 115 with a service subscription to the network provider, or may provide constrained access to UEs 115 associated with the small cell (e.g., UEs 115 in a closed subscriber group (CSG), UEs 115 associated with users in a home or office). The network entity 105 may support one or more cells and may also support communication via the one or more cells using one or more component carriers.

[0054] In some examples, the network entity 105 (e.g., base station 140, RU 170) may be movable and provide communication coverage for a moving coverage area 110. In some examples, different coverage areas 110 associated with different technologies may overlap, but the different coverage areas 110 may be supported by the same network entity 105. In some other examples, overlapping coverage areas 110 associated with different technologies may be supported by different network entities 105. The wireless communication system 100 may include, for example, a heterogeneous network in which different types of network entities 105 provide coverage for various coverage areas 110 using the same or different radio access technologies.

[0055] The wireless communication system 100 can be configured to support ultra-reliable communication or low-latency communication or various combinations thereof. For example, the wireless communication system 100 can be configured to support ultra-reliable low-latency communication (URLLC). The UE 115 can be designed to support ultra-reliable or low-latency or critical functions. Ultra-reliable communication can include private communication or group communication and can be supported by one or more services such as push-to-talk, video, or data. Support for ultra-reliable, low-latency functions can include prioritizing services, and such services can be used for public safety or general commercial applications. The terms ultra-reliable, low-latency, and ultra-reliable low-latency can be used interchangeably herein.

[0056] In some examples, the UE 115 can be configured to communicate directly with other UEs 115 via a device-to-device (D2D) communication link 135 (e.g., according to a peer-to-peer (P2P), D2D, or sidelink protocol). In some examples, one or more UEs 115 performing D2D communication in a group can be within the coverage area 110 of a network entity 105 (e.g., base station 140, RU 170), and the network entity can support aspects of such D2D communication configured (e.g., scheduled) by the network entity 105. In some examples, one or more UEs 115 in such a group can be outside the coverage area 110 of the network entity 105 or can otherwise be unable or not configured to receive transmissions from the network entity 105. In some examples, a group of UEs 115 communicating via D2D communication can support a one-to-many (1:M) system where each UE 115 transmits to each of the other UEs 115 in the group. In some examples, the network entity 105 can facilitate scheduling of resources for D2D communication. In some other examples, D2D communication can be performed between UEs 115 without involving the network entity 105.

[0057] The core network 130 can provide user authentication, access authorization, tracking, Internet Protocol (IP) connectivity, and other access, routing, or mobility functions. The core network 130 can be an evolved packet core (EPC) or a 5G core (5GC), and the EPC or 5GC can include at least one control plane entity that manages access and mobility (e.g., a mobility management entity (MME), an access and mobility management function (AMF)), and at least one user plane entity that routes packets or interconnects to an external network (e.g., a serving gateway (S-GW), a packet data network (PDN) gateway (P-GW), or a user plane function (UPF)). The control plane entity can manage non-access stratum (NAS) functions such as mobility, authentication, and bearer management for a UE 115 served by a network entity 105 (e.g., a base station 140) associated with the core network 130. User IP packets can be transferred through the user plane entity, and the user plane entity can provide IP address allocation and other functions. The user plane entity can be connected to the IP services 150 of one or more network operators. The IP services 150 can include access to the Internet, an intranet, an IP multimedia subsystem (IMS), or packet switched streaming services.

[0058] The wireless communication system 100 can operate using one or more frequency bands in the range of 300 megahertz (MHz) to 300 gigahertz (GHz). Generally, the region from 300 MHz to 3 GHz is known as the ultra-high frequency (UHF) region or the decimeter band because, in terms of length, the wavelength range is approximately one decimeter to one meter. UHF waves can be blocked or redirected by buildings and environmental features (which can be referred to as clutter), but these waves can be sufficient to penetrate structures so that a macro cell can serve a UE 115 located indoors. Compared to communication using smaller frequencies and longer waves in the high frequency (HF) or very high frequency (VHF) portions of the spectrum below 300 MHz, communication using UHF waves can be associated with smaller antennas and shorter distances (e.g., less than 100 kilometers).

[0059] The wireless communication system 100 can utilize both licensed RF spectrum bands and unlicensed RF spectrum bands. For example, the wireless communication system 100 can use an unlicensed band (such as the 5 GHz industrial, scientific, and medical (ISM) band) to employ licensed-assisted access (LAA), LTE-unlicensed (LTE-U) radio access technology, or NR technology. When operating using an unlicensed RF spectrum band, devices such as the network entity 105 and the UE 115 can employ carrier sensing for collision detection and avoidance. In some examples, operation using the unlicensed band can be based on a carrier aggregation configuration combined with a component carrier operating using a licensed band (e.g., LAA). Operations using the unlicensed spectrum can include downlink transmissions, uplink transmissions, peer-to-peer (P2P) transmissions, or device-to-device (D2D) transmissions, etc.

[0060] The network entity 105 (e.g., base station 140, RU 170) or the UE 115 may be equipped with multiple antennas, which may be used to employ techniques such as transmit diversity, receive diversity, multiple-input multiple-output (MIMO) communication, or beamforming. The antennas of the network entity 105 or the UE 115 may be located within one or more antenna arrays or antenna panels, which may support MIMO operation or transmit or receive beamforming. For example, one or more base station antennas or antenna arrays may be co-located at an antenna assembly, such as at an antenna tower. In some examples, the antennas or antenna arrays associated with the network entity 105 may be located at different geographical locations. The network entity 105 may include an antenna array having a set of antenna ports in multiple rows and columns that the network entity 105 may use for beamforming to support communication with the UE 115. Similarly, the UE 115 may include one or more antenna arrays, which may support various MIMO or beamforming operations. Additionally or alternatively, an antenna panel may support RF beamforming for signals transmitted via the antenna ports.

[0061] Beamforming (which may also be referred to as spatial filtering, directional transmission, or directional reception) is a signal processing technique that can be used at a transmitting device or a receiving device (e.g., network entity 105, UE 115) to shape or manipulate an antenna beam (e.g., transmit beam, receive beam) along a spatial path between the transmitting device and the receiving device. Beamforming can be achieved by combining signals conveyed via the antenna elements of an antenna array such that some signals propagating in a particular direction with respect to the antenna array experience constructive interference while other signals experience destructive interference. The adjustment of the signals conveyed via the antenna elements may include the transmitting device or the receiving device applying an amplitude offset, a phase offset, or both to the signals carried via the antenna elements associated with the device. The adjustment associated with each antenna element may be defined by a set of beamforming weights associated with a particular orientation (e.g., for the antenna array of the transmitting device or the receiving device, or for some other orientation).

[0062] The network entity 105 or the UE 115 may use beam scanning techniques as part of the beamforming operation. For example, the network entity 105 (e.g., the base station 140, the RU 170) may use multiple antennas or antenna arrays (e.g., antenna panels) to perform beamforming operations for directional communication with the UE 115. Some signals (e.g., synchronization signals, reference signals, beam selection signals, or other control signals) may be sent by the network entity 105 multiple times in different directions. For example, the network entity 105 may send signals according to different beamforming weight sets associated with different transmission directions. The transmissions along different beam directions may be used to identify the beam directions (e.g., by the transmitting device such as the network entity 105 or by the receiving device such as the UE 115) for later transmission or reception by the network entity 105.

[0063] Some signals (such as data signals associated with a specific receiving device) may be sent by the transmitting device (e.g., the transmitting network entity 105, the transmitting UE 115) along a single beam direction (e.g., the direction associated with the receiving device such as the receiving network entity 105 or the receiving UE 115). In some examples, the beam direction associated with the transmission along a single beam direction may be determined based on the signals transmitted along one or more beam directions. For example, the UE 115 may receive one or more of the signals sent by the network entity 105 in different directions and may report to the network entity 105 an indication of the signal that the UE 115 receives with the highest signal quality or other acceptable signal quality.

[0064] In some examples, transmissions performed by a device (e.g., by network entity 105 or UE 115) may be carried out using multiple beam directions, and the device may use a combination of digital precoding or beamforming to generate a combined beam for transmission (e.g., from network entity 105 to UE 115). UE 115 may report feedback indicating precoding weights for one or more beam directions, and the feedback may correspond to a configured beam set across the system bandwidth or one or more subbands. Network entity 105 may transmit reference signals (e.g., cell-specific reference signal (CRS), channel state information reference signal (CSI-RS)), which may be precoded or non-precoded. UE 115 may provide feedback for beam selection, which may be a precoding matrix indicator (PMI) or codebook-based feedback (e.g., multi-panel type codebook, linear combination type codebook, port selection type codebook). Although these techniques are described with reference to signals transmitted by network entity 105 (e.g., base station 140, RU 170) in one or more directions, UE 115 may use similar techniques for transmitting signals multiple times in different directions (e.g., for identifying beam directions used by UE 115 for subsequent transmission or reception), or for transmitting signals in a single direction (e.g., for sending data to a receiving device).

[0065] A receiving device (e.g., UE 115) may perform receive operations according to multiple receive configurations (e.g., directional listening) when, for example, the receiving device may be receiving various signals (such as synchronization signals, reference signals, beam selection signals, or other control signals) from a receiving device (e.g., network entity 105). For example, the receiving device may perform reception according to multiple receive directions by: receiving via different antenna subarrays, processing the received signals according to different antenna subarrays, receiving according to different receive beamforming weight sets (e.g., different directional listening weight sets) applied to signals received at multiple antenna elements of an antenna array, or processing the received signals according to different receive beamforming weight sets applied to signals received at multiple antenna elements of an antenna array, where any of these may refer to "listening" according to different receive configurations or receive directions. In some examples, the receiving device may use a single receive configuration to receive along a single beam direction (e.g., receive a data signal). The single receive configuration may be aligned along a beam direction determined based on listening according to different receive configuration directions (e.g., a beam direction determined to have the highest signal strength, highest signal-to-noise ratio (SNR), or other acceptable signal quality based on listening according to multiple beam directions).

[0066] In some cases, the wireless communication system 100 may support one or more operations performed at the network entity 105, which may result in increased power consumption. To save power, the network entity 105 may support SCell deactivation and SCell dormancy. In some cases, the network entity 105 may configure the UE 115 with an anchor cell to determine the quality of the SCell associated with the deactivated or dormant carrier. For example, the network entity 105 may infer the quality of the SCell based on measurements performed at the UE 115 on reference signals transmitted using the anchor carrier associated with the anchor cell. Additionally or alternatively, the UE 115 may identify reception parameters to be used for receiving the signaling based on the QCL relationship between the signaling transmitted using a previously deactivated or dormant carrier and the reference signal. However, in some cases, the network entity 105 may not be able to indicate such QCL relationships to the UE 115. For example, the network entity 105 may lack a mechanism for indicating the QCL relationship between the signaling transmitted using carriers associated with different cells (such as the anchor carrier associated with the anchor cell and the previously deactivated or dormant carrier associated with the SCell).

[0067] In some examples, the wireless communication system 100 may support a framework for configuring the UE 115 with the QCL relationship between a reference signal transmitted using an anchor cell and signaling transmitted using an SCell. For example, the UE 115 may receive a carrier indication that identifies a first carrier (e.g., the anchor carrier associated with the anchor cell) and a second carrier (e.g., the SCell carrier associated with the SCell) for communication between the UE 115 and the network entity 105. The UE 115 may use the first carrier to receive a first QCL indication. The first QCL indication may identify a first set of QCL information, where the first set of QCL information corresponds to the reference signal received at the UE 115 using the first carrier. The UE 115 may use the second carrier to receive a second QCL indication. The second QCL indication may identify the reference signal and may indicate that the first set of QCL information may be associated with the signaling received using the second carrier. That is, the network entity 105 may use the second QCL indication to configure the UE 115 with the QCL relationship between the reference signal transmitted using the first carrier and the signaling transmitted using the second carrier. In some examples, by configuring the UE 115 with the QCL relationship between the reference signal transmitted using the first carrier and the signaling transmitted using the second carrier, the network entity 105 may reduce power consumption and improve communication efficiency within the wireless communication system 100, among other benefits.

[0068] Figure 2An example of a wireless communication system 200 that supports QCL relationships indicating carrier dormancy and / or deactivation in accordance with one or more aspects of the present disclosure is illustrated. The wireless communication system 200 may implement one or more aspects of the wireless communication system 100, or may be implemented at the one or more aspects. For example, the wireless communication system 200 may include a UE 215 and a network entity 205, which may be examples of corresponding devices illustrated and described with reference to the accompanying drawings. The UE 215 and the network entity 205 may communicate within a coverage area 210-a or a coverage area 210-b or both, which may be examples of the coverage area 110 illustrated and described with reference to the accompanying drawings. Figure 1 In some examples, the network entity 205 may configure the UE 215 to use one or more carriers to communicate wirelessly with the network entity 205. For example, the network entity 205 may configure the UE 215 with multiple carriers to increase the data capacity of wireless communication within the wireless communication system 200. As illustrated in the example of Figure 1 the network entity 205 may communicate wirelessly with the UE 215 using an anchor carrier 220 and an SCell carrier 221. The anchor carrier 220 may be associated with (e.g., may serve) an anchor cell providing the coverage area 210-a. In some examples, the anchor cell may correspond to a primary cell (PCell). The SCell carrier 221 may be associated with (e.g., may serve) an SCell providing the coverage area 210-b. In some examples, a carrier associated with an SCell (such as the SCell carrier 221) may be referred to as a secondary carrier.

[0069] In some examples, operations performed at the network entity 205 may result in increased energy consumption and increased costs within the wireless communication system 200 (e.g., due to the increased energy consumption). For example, a communication network such as a cellular network may incur relatively high costs due to network energy consumption associated with operating (e.g., running) the cellular network. In some examples, a portion of the network cost (e.g., approximately 23% of the total cost) may be due to the operation of the cellular network. In such examples, a relatively large portion of the network energy consumption (e.g., approximately 50% in 5G) may be due to a RAN such as the network entity 205. In some examples, some network energy saving features (e.g., implemented at a RAN such as the network entity 205) may provide benefits for the adoption and expansion of cellular networks. That is, the wireless communication system 200 (e.g., the network entity 205 and the UE 215) may support network energy saving features (e.g., techniques) in multiple domains such as the time domain, the frequency domain, the spatial domain, or the power domain to reduce the energy consumption at the network entity 205. Figure 2 as illustrated and described with reference to the accompanying drawings.

[0070] In some examples, the UE 215 and the network entity 205 may be examples of corresponding devices illustrated and described with reference to the accompanying drawings. The UE 215 and the network entity 205 may communicate within a coverage area 210-a or a coverage area 210-b or both, which may be examples of the coverage area 110 illustrated and described with reference to the accompanying drawings.

[0071] In some examples, these network energy saving features may include (e.g., consider) energy consumption patterns. For example, some network energy saving features may define network entity energy consumption models (e.g., base station energy consumption model, RAN energy consumption model). In some examples, these network entity energy consumption models may adapt some frameworks of power consumption modeling and evaluation methods (such as the framework of power consumption modeling and evaluation methods for UEs) to network entities (e.g., adapt to the base station side, gNB side). In some examples, such frameworks may include the relative energy consumption of downlink communication and uplink communication performed at the network entity (e.g., considering factors such as power amplifier efficiency, number of transmitting RUs, and base station load), the sleep state of the network entity, the transition time associated with the sleep state of the network entity, and one or more reference parameters or configurations (or both parameters and configurations).

[0072] Additionally or alternatively, these network energy saving features may define evaluation methods and key performance indicators (KPIs). The evaluation method may be for evaluating system-level network energy consumption and energy saving gains, and for evaluating or balancing (or both) (e.g., network entity energy consumption) the impact on network performance, user performance (e.g., spectral efficiency, capacity, user perceived throughput (UPT), latency, handover performance, call drop rate, initial access performance, service level agreement (SLA) guaranteed related KPIs), energy efficiency, UE power consumption, and UE complexity. Additionally or alternatively, the evaluation method may provide multiple KPIs (e.g., avoid focusing on a single KPI), and may reuse some KPIs. In some examples (such as examples where some KPIs may be insufficient), additional (e.g., new) KPIs may be developed. The working group may determine one or more KPIs to be evaluated, and may also determine how to evaluate the one or more KPIs.

[0073] Additionally or alternatively, some network energy saving features may include (e.g., may be studied and identified) techniques for network entity 205 and UE 215 (e.g., on the gNB side and UE side) to improve network energy saving (e.g., with respect to both network entity transmission and network entity reception). In some examples, such techniques may provide increased operational efficiency (e.g., dynamically, semi-statically, or both) and increased granularity (e.g., relatively finer granularity) associated with adapting transmission or reception (or both) using potential support or feedback (e.g., including potential UE assistance information) from UE 215 in one or more of the network energy saving techniques (e.g., in one or more of the time domain, frequency domain, spatial domain, or power domain). In some examples, such techniques may include information exchange or coordination (or both) through one or more network interfaces and may include one or more other techniques (in other words, other techniques for improving network energy saving may not be excluded).

[0074] In some examples, these network energy saving features may include using one or more dormant BWPs. For example, network entity 205 may support network energy saving features, where network entity 205 may configure UE 215 with one or more dormant BWPs. In such examples, network entity 205 and UE 215 may use the dormant BWP according to downlink dormant behavior or uplink dormant behavior or both. In some examples, network entity 205 may configure UE 215 with one or more dormant BWPs for each carrier (or each cell) for communication between UE 215 and network entity 205. For example, network entity 205 may configure UE 215 with a dormant BWP associated with SCell carrier 221. In some examples, network entity 205 may configure UE 215 to use the dormant BWP associated with SCell carrier 221 by activating the dormant BWP at UE 215. That is, network entity 205 may configure the dormant BWP as the active BWP (e.g., active downlink BWP) of the SCell associated with SCell carrier 221. In some examples where the dormant BWP of the SCell is the active BWP, the SCell may be referred to as a dormant SCell, and the associated carrier may be referred to as a dormant carrier. Network entity 205 and UE 215 may use the dormant carrier according to a dormant mode (such as downlink dormant behavior or uplink dormant behavior). For example, network entity 205 and UE 215 may operate according to downlink dormant behavior or uplink dormant behavior (or both) in response to the active BWP being switched to the dormant BWP.

[0075] In some examples, the active BWP associated with the SCell carrier 221 may be switched to a dormant BWP. In such examples, and according to the downlink dormancy behavior, the UE 215 may use the SCell carrier 221 to receive CSI-RS from the network entity 205 and may avoid using the SCell carrier 221 to monitor the Physical Downlink Control Channel (PDCCH). For example, the UE 215 may avoid (e.g., stop) monitoring the PDCCH on the SCell and may continue to perform CSI measurements (e.g., using CSI-RS sent from the network entity 205), automatic gain control (AGC), and beam management, as well as other examples of operations configurable at the UE 215. In some examples, the UE 215 may support periodic and semi-persistent CSI reporting according to the downlink dormancy behavior. Additionally, in some examples, the UE 215 may not support aperiodic CSI reporting according to the downlink dormancy behavior. In some examples, for examples where a scheduled SCell may be in a dormant state (e.g., in a dormant mode), the UE 215 may avoid monitoring the PDCCH of the SCell (e.g., for cross-carrier scheduling). That is, for examples where the active BWP associated with the SCell carrier 221 is a dormant BWP, the UE 215 may avoid using the SCell carrier 221 to monitor the PDCCH.

[0076] In some examples, the UE 215 may be configured to perform beam failure recovery (BRF) and beam failure detection (BFD) on a secondary cell (SCell) where the dormant bandwidth part (BWP) can be the active BWP. That is, the UE 215 may be configured to perform BRF and BFD in the dormant SCell, which may also be referred to as the dormant SCell. In some examples, the UE 215 may be capable of performing SCell BFR. In such examples, a BFR indication (e.g., in the form of a scheduling request) may be transmitted in the serving cell (e.g., in any available serving cell other than the serving cell associated with the dormant BWP). In other words, BFD may be configured and performed in the dormant SCell. In some examples, the transmit configuration indicator (TCI) state of the dormant SCell may be configured in the physical downlink shared channel (PDSCH) configuration of the SCell carrier 221. That is, the network entity 205 may use the PDSCH configuration of the SCell carrier 221 (or the associated SCell) to indicate the TCI state associated with the SCell carrier 221 to the UE 215. In some examples, the UE 215 may use the TCI state to identify the beam to be used at the UE 215 for receiving signaling using the SCell carrier 221. For example, for beam management according to the downlink dormant behavior, the UE 215 may apply the configured TCI state (e.g., to receive a reference signal transmitted using the SCell carrier 221), and may avoid applying other aspects of the PDSCH configuration (e.g., when operating according to the downlink dormant behavior).

[0077] In some examples, timer-based transitions between non-dormant and dormant may not be supported. That is, the network entity 205 and the UE 215 may avoid using timer-based transitions between the non-dormant mode and the dormant mode for the SCell carrier 221. In some examples, a timer, such as the timer indicated using the bwp-InactivityTimer information element (IE), may stop running when the UE 215 enters the dormant mode. That is, in an example where the timer is running and the UE 215 may operate according to the non-dormant mode, the timer may stop in response to the UE 215 transitioning from the non-dormant mode to the dormant mode. For example, the timer may stop in response to the network entity 205 activating the use of the dormant BWP.

[0078] In some examples, based on the uplink sleep behavior, the UE 215 may avoid using the SCell carrier 221 to send sounding reference signals (SRS) to the network entity 205. That is, the UE 215 may not support SRS transmission according to the uplink sleep behavior (e.g., including aperiodic SRS, semi-periodic SRS, and periodic SRS), such as for the case where the active BWP (e.g., the active downlink BWP) can be switched to a dormant BWP. Additionally or alternatively, for the case where the active BWP can be switched to a dormant BWP, the UE 215 may avoid operating according to some uplink behaviors (e.g., may stop performing one or more uplink operations). For example, the UE 215 may stop one or more uplink transmissions, suspend one or more configured uplink grants (e.g., any configured uplink grant type 1), and clear one or more other configured uplink grants associated with the dormant SCell (e.g., any configured uplink grant type 2). That is, in an example where the active BWP associated with the SCell is a dormant BWP, the UE may avoid using the SCell carrier 221 associated with the SCell to perform one or more uplink operations. In such examples, the UE 215 may use another carrier (e.g., the anchor carrier or another carrier associated with a non-dormant SCell) to report measurements performed at the UE using CSI-RS transmitted via the dormant BWP. In some examples, the dormant BWP may correspond to a downlink BWP. For example, the network entity 205 may avoid configuring (e.g., may not define) an uplink dormant BWP at the UE 215. In such examples, the UE 215 may be configured to operate according to the uplink sleep behavior in response to the active downlink BWP being switched to a dormant BWP. In some examples, SCell sleep may not apply to an SCell configured for a physical uplink control channel (PUCCH), which may be referred to as a PUCCH SCell. Additionally, in some instances, the UE 215 may be configured to apply timing advance maintenance behavior to the dormant SCell.

[0079] In some examples, sleep behaviors (such as uplink sleep behavior and downlink sleep behavior) may be configured at network entity 205 and UE 215 for UE power saving (e.g., in the SCell associated with SCell carrier 221). However, according to the downlink sleep behavior (e.g., when operating in the sleep mode), network entity 205 may use the SCell (e.g., SCell carrier 221) to send CSI-RS to UE 215. Additionally, UE 215 may perform measurements (e.g., using the sent CSI-RS) and report the measurements to network entity 205, such that network entity 205 may track the SCell quality (e.g., the quality of the communication channel associated with the SCell) and enable a relatively fast switch from sleep to non-sleep. That is, since network entity 205 may use the SCell to send CSI-RS when operating in the sleep mode, network entity 205 may determine the quality of the sleeping SCell and may dynamically switch from the sleep mode to the non-sleep mode.

[0080] However, to achieve network energy saving, it may be beneficial for network entity 205 to avoid sending CSI-RS while tracking the SCell quality (e.g., maintaining an understanding of the SCell quality). That is, network entity 205 may save energy by tracking the quality of the SCell without using the SCell (e.g., SCell carrier 221) to send CSI-RS or other types of signaling. In some examples, to track the SCell quality, network entity 205 may associate the SCell carrier 221 (e.g., a sleeping or deactivated carrier) with the anchor carrier 220. For example, network entity 205 may configure the SCell associated with SCell carrier 221 with an anchor cell associated with anchor carrier 220, such that measurements of the reference signals sent using anchor carrier 220 (e.g., anchor carrier measurements) may be used at network entity 205 to track the SCell quality. For example, some energy saving techniques may employ carriers where SSB (or system information block (SIB)) is not sent. Such carriers may be referred to as SSB-less carriers or non-anchor carriers, and carriers where SSB (or SIB) is sent may be referred to as anchor carriers. In such examples, a sleeping or deactivated carrier may be an example of a non-anchor carrier.

[0081] In some examples, the network energy saving feature may include one or more features for saving energy in the frequency domain. For example, the network energy saving feature may include using a carrier on which SSB and SIB (such as SIB1) may not be transmitted. That is, the network energy saving feature may include using a carrier without SSB, a carrier without SIB1, and a carrier without SSB / SIB1. Additionally or alternatively, the network energy saving feature may include using group common BWP, network energy saving BWP (NES-BWP), and group communication (GS) handover. In some examples, the network energy saving feature may include bandwidth adaptation. Additionally or alternatively, the network energy saving feature may include dynamic cell activation and deactivation. For example, the network energy saving feature may include one or more cell handover and adaptation techniques, such as SCell activation and deactivation, cell wake-up signaling, PCell handover, and multi-cell and sub-cell adaptation. In some examples of SCell activation and deactivation, the network entity 205 may activate or deactivate the use of the SCell associated with the SCell carrier 221 at the UE 215. For example, the network entity 205 may deactivate the use of the SCell at the UE 215 so that the UE 215 can avoid using the SCell carrier 221 to communicate with the network entity 205.

[0082] In some examples, such as for cell activation and deactivation (e.g., relatively fast cell activation and deactivation), network entity 205 may activate a cell such that UE 215 can use the cell to receive signaling (e.g., PDSCH signaling). In such examples, since the cell was previously deactivated (or in a dormant mode where reference signals may not have been transmitted), UE 215 may use QCL assumptions (e.g., QCL relationships) to determine the parameters for using the cell (e.g., the dynamically activated cell) to receive signaling. For example, UE 215 may use the QCL relationship between the signaling to be received using the dynamically activated cell and the signaling received using another cell. In other words, UE 215 may be configured with two intra-band cells (or inter-band cells), such as cell A and cell B. In some examples, from the perspective of network entity 205, for example, cell A may be active while cell B may be inactive or in a dormant state. In some examples, network entity 205 may use cell A to transmit periodic SSBs or CSI-RSs to UE 215 and other examples of reference signals, and may avoid using cell B. Network entity 205 may dynamically activate cell B (e.g., cell B may be turned on, such as switched from a dormant mode to a non-dormant mode) such that cell B can be used to transmit or receive dynamic signaling. For example, network entity 205 may use cell B to dynamically transmit a tracking reference signal (TRS), CSI-RS, PDCCH, or PDSCH. In such examples, UE 215 may use the QCL relationship between the dynamic signaling and the signaling transmitted using cell A to identify the QCL information and timing reference for the dynamic signaling. That is, the signals transmitted on cell A may be used to determine the QCL information and timing reference for the dynamic transmission on cell B. In some examples, using the signals transmitted on cell A to determine the QCL information and timing reference for the signaling on cell B may reduce the energy consumption at network entity 205. That is, since cell B may be dynamically (e.g., non-periodically) activated, semi-static or periodic transmissions that may consume energy at network entity 205 may occur on cell A (e.g., not on cell B), which may reduce the amount of energy used at the network entity for transmission using cell B. That is, by using cell A for semi-static or periodic transmissions, the network energy consumption of cell B can be reduced.

[0083] As Figure 2As illustrated in the example of, cell A may correspond to an anchor cell associated with the anchor carrier 220, and cell B may correspond to an SCell associated with the SCell carrier 221. That is, in some examples, the SCell carrier 221 may be a dormant or deactivated carrier. In such examples, the network entity 205 may avoid using the SCell carrier 221 to communicate with the UE 215, but may use the anchor carrier 220 to send a reference signal to the UE 215. In some examples, the network entity 205 may dynamically activate the SCell carrier 221 such that the network entity 205 may use the SCell carrier 221 to send signaling to the UE 215. In some examples, to activate the SCell carrier 221, the network entity 205 may send an indication to the UE 215 to activate the SCell associated with the SCell carrier 221 or to switch the active BWP of the SCell from a dormant BWP to another BWP. In some instances, the network entity 205 may use the SCell carrier 221 to send a TRS (e.g., an aperiodic TRS (A-TRS)), a CSI-RS (e.g., an aperiodic CSI-RS (A-CSI-RS)), a PDCCH, or a PDSCH. In such examples, to identify the QCL information and timing reference for the signaling to be sent using the SCell carrier 221, the UE 215 may use the QCL relationship between the signaling to be sent using the SCell carrier 221 and the reference signal sent using the anchor carrier 220. However, in some instances, the UE 215 may not be able to determine such a QCL relationship. For example, the network entity 205 may lack a mechanism for indicating the QCL relationship between the signaling sent to the UE 215 using carriers associated with different cells. That is, in some examples, the network entity 205 may lack a mechanism for indicating the QCL relationship between the reference signal sent using the anchor carrier 220 associated with the anchor cell and the signaling sent using the SCell associated with the SCell carrier 221.

[0084] In some other examples, according to one or more aspects of the present disclosure, the network entity 205 and the UE 215 may support the indication of the QCL relationship for dormant and / or deactivated carriers. For example, the network entity 205 may support a framework for configuring the UE 215 with the QCL relationship between the reference signal 240 sent using the anchor carrier 220 and the signaling 245 sent using the SCell carrier 221. That is, the network entity 205 may configure the UE 215 with the QCL relationship for an activated cell (such as a cell that may have been activated relatively recently and may not have been used for receiving a reference signal (e.g., to determine the quality of the cell)). In some examples, the signaling 245 may include a TRS (e.g., A-TRS), a CSI-RS (e.g., A-CSI-RS), a PDCCH, or a PDSCH. AsFigure 2 As illustrated in the example of, UE 215 may receive a carrier indication 225 from network entity 205. In some examples, the carrier indication 225 may configure UE 215 to use an anchor carrier 220 associated with an anchor cell and a SCell carrier 221 associated with a SCell. For example, the carrier indication 225 may correspond to the configuration of the SCell associated with the SCell carrier 221 and may include an indication (e.g., a pointer) that the SCell may be associated with the anchor carrier 220.

[0085] In some examples, network entity 205 may use the anchor carrier 220 to send a first QCL indication 230 to UE 215. That is, UE 215 may use the anchor carrier 220 to receive the first QCL indication 230. In some examples, the first QCL indication 230 may identify a first set of QCL information to UE 215, and this first set of QCL information corresponds to the reference signal received (or to be received) at UE 215 using the anchor carrier 220. For example, the first QCL indication 230 may correspond to a QCL-Info IE (e.g., sent using the TCI-State IE of the anchor cell or sent together with it), and the first set of QCL information may correspond to one or more fields included in the QCL-Info IE, such as the bwp-Id field, the cell field, the referenceSignal field, and the qcl-Type field, as well as other examples of fields that may be included in the IE. In some examples, the names of the IE and the fields may change based on the specific implementation of one or more devices (e.g., UE 215, network entity 205, or both).

[0086] In some examples, network entity 205 may use SCell carrier 221 to send a second QCL indication 235 to UE 215. That is, UE 215 may use SCell carrier 221 to receive the second QCL indication 235. In some examples, the second QCL indication 235 may identify a reference signal. Additionally or alternatively, the second QCL indication 235 may indicate to UE 215 that a first set of QCL information may be associated with the signaling received (or to be received) at UE 215 using SCell carrier 221 (e.g., a previously dormant or deactivated carrier). That is, network entity 205 may use the second QCL indication 235 to configure UE 215 with a QCL relationship between reference signal 240 transmitted using anchor carrier 220 and signaling 245 transmitted using SCell carrier 221. In some examples, the second QCL indication 235 may correspond to a QCL-Info IE (e.g., transmitted using or together with the TCI-State IE for the SCell). In such examples, network entity 205 may use fields included in the QCL-info IE to indicate reference signal 240. For example, the QCL-info IE may include fields such as the Specific_cell_CSI_RS field or the Specific_cell_ssb field, and the content of the field may identify reference signal 240. For example, the content of the field may include an identifier (ID), such as an index, corresponding to reference signal 240 (or to the SCell associated with reference signal 240). In some examples, the presence of an ID associated with reference signal 240 may indicate that a first set of QCL information corresponding to reference signal 240 may be associated with the signaling to be transmitted using SCell carrier 221.

[0087] In some examples, UE 215 may use a first carrier to receive reference signal 240 and may use a second carrier to receive signaling 245. In such examples, the UE may receive signaling 245 based on the first set of QCL information and reference signal 240. For example, one or more parameters used to receive (and decode) reference signal 240 at UE 215 may also be used to receive (and decode) signaling 245 at UE 215. In such examples, the one or more parameters may be based on the first set of QCL information. In some examples, by configuring UE 215 with a QCL relationship between reference signal 240 and signaling 245, network entity 205 may reduce the energy consumption within wireless communication system 200, as well as other possible benefits.

[0088] Figure 3An example of a timing diagram 300 that illustrates QCL relationship indication supporting carrier sleep and / or deactivation in accordance with one or more aspects of the present disclosure is shown. The timing diagram 300 may implement one or more aspects of the wireless communication system 100 and the wireless communication system 200, or may be implemented at the one or more aspects. For example, the timing diagram 300 may be implemented at a UE or a network entity or both, which may be examples of corresponding devices illustrated and described with reference to these figures. Figure 1 and Figure 2 illustrated and described with reference to these figures.

[0089] In some examples, a network entity may support a framework for configuring a UE with a QCL relationship between a reference signal transmitted using an anchor cell and signaling transmitted using an SCell. For example, the network entity may configure the UE to use an anchor carrier 315 and an SCell carrier 320. In Figure 3 the example, the anchor carrier 315 may be associated with an anchor cell, and the SCell carrier 320 may be associated with an SCell. In some examples, the network entity may use the configuration of the SCell to indicate to the UE to use the anchor carrier 315 and the SCell carrier 320. For example, the configuration of the SCell may include an indication that the anchor carrier 315 may be associated with the SCell carrier 320 (e.g., the anchor carrier of the SCell carrier). In some examples, the anchor carrier 315 may be in an active state 305 for a duration, while the SCell carrier 320 may switch between the active state 305 and an inactive state 310 during the duration. That is, the network entity may dynamically indicate to the UE to use the SCell carrier 320 based on the active state 305 or the inactive state 310.

[0090] For example, a network entity may dynamically activate or deactivate the use of SCell carrier 320 at a UE. In some examples, the network entity may activate or deactivate the use of SCell carrier 320 by respectively activating or deactivating the associated SCell at the UE. For example, the SCell associated with SCell carrier 320 may be dedicated to cell activation and deactivation (e.g., relatively fast cell activation and deactivation). In such examples, the network entity may (e.g., dynamically) send downlink control information (DCI) or a MAC control element (MAC-CE) to activate or deactivate the SCell associated with SCell carrier 320. For example, the DCI or MAC-CE may indicate to the UE to deactivate the use of the SCell associated with SCell carrier 320. In such examples, the UE may use SCell carrier 320 according to the inactive state 310 (e.g., deactivated state). That is, in response to the SCell associated with SCell carrier 320 being deactivated, the UE may avoid using SCell carrier 320 to receive signaling from the network entity. In some examples, the DCI or MAC-CE may indicate to the UE to activate the use of the SCell associated with SCell carrier 320. In such examples, the UE may use SCell carrier 320 according to the active state 305. That is, in response to the SCell associated with SCell carrier 320 being activated, the UE may use SCell carrier 320 to receive signaling (such as signaling 330) from the network entity.

[0091] In some other examples, the network entity may dynamically activate or deactivate the use of the dormant BWP associated with SCell carrier 320 at the UE. For example, the network entity may (e.g., dynamically) send DCI or a MAC CE that indicates to the UE to switch the active BWP associated with SCell carrier 320 to the dormant BWP or another BWP. For example, the DCI or MAC-CE may indicate to the UE to use the dormant BWP associated with SCell carrier 320. In such examples, the UE may use SCell carrier 320 according to the inactive state 310 (e.g., dormant mode). That is, in response to the dormant BWP associated with SCell carrier 320 being activated, the UE may avoid using SCell carrier 320 to receive signaling from the network entity. In some examples, the DCI or MAC-CE may indicate to the UE to use another BWP associated with SCell carrier 320. In such examples, the UE may use SCell carrier 320 according to the active state 305 (e.g., non-dormant mode). That is, in response to another BWP (e.g., non-dormant BWP) associated with SCell carrier 320 being activated, the UE may use SCell carrier 320 to receive signaling (such as signaling 330) from the network entity.

[0092] In some examples, the UE may use the SCell carrier 320 (e.g., a cell that can be dedicated to relatively fast cell activation and deactivation) to receive A-TRS, A-CSI-RS, PDCCH, and / or PDSCH that are quasi-co-located (QCL) with the signals transmitted using the anchor carrier 315. For example, the UE may use the SCell carrier 320 to receive the signaling 330 according to a first set of QCL information that may correspond to the reference signal 325-a (e.g., a reference signal received using the anchor carrier 315). That is, the UE may use the QCL assumption (e.g., QCL relationship) between the reference signal 325-a and the signaling 330 to determine the reception parameters for receiving the signaling 330 (in other words, determine one or more parameters that can be used at the UE to receive or decode the signaling 330).

[0093] In some examples, the QCL relationships and configurations (e.g., the configuration of the SCell and / or the configuration of the anchor cell) can depend on the SCell (e.g., a cell that can be dedicated to relatively fast cell activation and deactivation) and the associated anchor carrier (e.g., anchor carrier 315). That is, the QCL relationships and configurations can change in response to a change in the SCell associated with SCell carrier 320 or the anchor cell associated with anchor carrier 315 or both (e.g., in response to a network entity configuring another cell as the anchor cell of the SCell). In other words, the QCL relationship between signals (such as reference signal 325-a and signal 330) can depend on the respective carriers used to transmit the signals. In some examples, anchor carrier 315 can be an example of an in-band anchor carrier. That is, anchor carrier 315 and SCell carrier 320 can occur within the same RF band. In such examples, the UE can assume QCL type A. That is, the QCL relationship of the in-band anchor carrier can include type A QCL parameters. For example, for QCL type A, the UE can determine (e.g., assume) that the Doppler frequency shift, Doppler spread, mean delay, and / or delay spread associated with reference signal 325-a can also be associated with signal 330. For example, for QCL type A, the UE can determine that signal 330 can be transmitted from the same location as reference signal 325-a or using the same hardware as that reference signal. In some other examples, anchor carrier 315 can correspond to an inter-band anchor carrier. That is, anchor carrier 315 and SCell carrier 320 can occur in different RF bands. In such examples, QCL type C or QCL type D can be assumed. That is, the QCL relationship of the inter-band anchor carrier can include type C QCL parameters or type D QCL parameters. In some examples, for QCL type C, the UE can determine (e.g., assume) that the mean delay and / or delay spread associated with reference signal 325-a can also be associated with signal 330. Additionally, for QCL type D, the UE can determine (e.g., assume) that the spatial reception parameters associated with reference signal 325-a can also be associated with signal 330. For example, for QCL type D, the UE can determine that signal 330 is co-located with reference signal 325-a. In some examples, a first QCL indication can be used to indicate the QCL type to the UE. For example, the first QCL indication can include a field indicating the QCL type, such as the qcl-Type field.

[0094] In some examples, the reference signal 325-a (e.g., the reference signal in the anchor carrier 315) may correspond to a reference signal configured for the anchor carrier 315 or the SCell carrier 320 or both. For example, the reference signal 325-a may be an existing reference signal configured for the anchor carrier 315 or a dedicated reference signal configured in the anchor carrier 315 for the SCell carrier 320 (e.g., a cell that may be dedicated to relatively fast cell activation and deactivation). That is, the reference signal 325-a may correspond to a reference signal that may be used at the UE (e.g., and a network entity) to track the quality of the SCell carrier 320 or both the SCell carrier 320 and the anchor carrier 315. In other words, a first set of QCL information (e.g., a set of one or more QCL parameters) corresponding to the reference signal 325-a may be shared for the reference signal 325-a, the signaling 330, and / or other signaling that may be received using the anchor carrier 315. In some examples, the UE may be configured with a mapping relationship between one or more reference signals (e.g., the reference signal 325) associated with the anchor carrier 315 and one or more signals (e.g., the signaling 330) associated with the SCell carrier 320. In such examples, the UE may use the mapping relationship to identify the reference signal (e.g., and the corresponding QCL information), and the UE may use the reference signal to determine the parameters for receiving the signaling 330.

[0095] In some examples, a network entity may use a first QCL indication to configure the UE with a first set of QCL information, where the first set of QCL information corresponds to the reference signal 325-a. For example, the network entity may send a QCL-Info IE for the anchor carrier 315 to the UE, and the QCL-Info IE may include the first set of QCL information. In some examples, the network entity may use the TCI-State IE (or together with it) to indicate the QCL-Info IE to the UE. In some examples, the network entity may use a second QCL indication (e.g., the QCL-Info IE of the SCell carrier 320) to indicate to the UE that the reference signal 325-a and the corresponding QCL information (e.g., the first set of QCL information) may be associated with the SCell carrier 320. For example, the second QCL indication may include a field that may identify the reference signal 325-a, such as the Specific_cell_CSI_RS field or the Specific_cell_ssb field. For example, the content of the field may include a cell ID that may correspond to the reference signal 325-a (e.g., a reference signal dedicated to the anchor cell). In some examples, in response to receiving the second QCL indication that identifies the reference signal 325-a, the UE may determine that the first set of QCL information may be shared for the reference signal 325-a and the signaling (such as the signaling 330) received using the SCell carrier 320.

[0096] In some examples, such as for a cell that may be dedicated to relatively fast cell activation and deactivation, the network entity may be able to configure the UE with the reference signal and QCL information of that cell. For example, the network entity may be able to configure the UE with the reference signal 325-b of the SCell carrier 320 and the corresponding set of QCL information. That is, the second QCL indication may include a second set of the cell ID and QCL information associated with the reference signal 325-b (e.g., the reference signal dedicated to the SCell), and this second set of QCL information corresponds to the reference signal 325-b. However, in some examples, the UE may not be able to determine whether to use the reference signal 325-a or the reference signal 325-b. That is, in some examples, the UE may not be able to determine the duration during which the UE can use the first set of QCL information provided for the anchor carrier 315 and the duration during which the UE can use the second set of QCL information provided for the SCell carrier 320 (e.g., a cell that may be dedicated to relatively fast cell activation and deactivation and may be referred to as a fast switching cell).

[0097] In some examples, multiple sets of QCL information may be provided to the UE such that one set of QCL information may be based on the anchor carrier configuration and another set of QCL information may be based on the fast switching cell configuration (e.g., the SCell under a relatively fast handover configuration). That is, the UE may be configured with a first set of QCL information and a second set of QCL information. The first set of QCL information may be based on the configuration of the anchor carrier 315, and the second set of QCL information may be based on the configuration of the SCell carrier 320. In some examples (such as examples where multiple sets of QCL information may be provided to the UE), the UE may determine to use the QCL information of the anchor carrier 315 (e.g., in an example where the UE is configured with the QCL information of the anchor carrier 315). That is, in some examples, in response to (e.g., as long as) the first set of QCL information is configured for the anchor carrier 315 at the UE, the UE may determine to use this first set of QCL information.

[0098] In some other examples, such as examples in which multiple sets of QCL information may be provided to a UE, the UE may determine the set of QCL information to use (e.g., which set of QCL information) based on a rule for selecting the QCL information. For example, the UE may receive RRC signaling (e.g., RRC configuration) from a network entity, and the RRC signaling includes an indication associated with the rule for selecting the QCL information. In some examples, the indication may correspond to a tag. For example, the UE may receive RRC signaling from a network entity, and the RRC signaling may include a tag indicating the set of QCL information (e.g., which set) that the UE may use. That is, the UE may determine to use a first set of QCL information or a second set of QCL information based on the tag included in the RRC configuration. In some examples, the rule (e.g., the tag) may identify the relationship between multiple reference signals transmitted using an anchor carrier 315 and a SCell carrier 320. For example, the anchor carrier 315 may be associated with an SSB and a CSI-RS, while the SCell carrier 320 may be associated with an SSB. In such examples, the rule may instruct the UE to use the QCL information corresponding to the CSI-RS, and in response, the UE may determine to use the QCL information corresponding to the CSI-RS associated with the anchor carrier 315. In some other examples, the anchor carrier 315 and the SCell carrier 320 may each be associated with an SSB and a CSI-RS. In such examples, the rule may instruct the UE regarding the QCL information of the reference signal corresponding to the associated default carrier.

[0099] In some examples, such as examples where multiple sets of QCL information are provided to a UE, the UE may determine the set of QCL information to use (e.g., which set) based on an indication included in DCI or a MAC-CE. That is, a network entity may use DCI or a MAC-CE to dynamically indicate to the UE to use a first set of QCL information or a second set of QCL information. In some examples, the DCI or MAC-CE may correspond to the DCI or MAC-CE at a network entity for switching the active BWP at the UE from a dormant BWP associated with the SCell carrier 320 to another BWP (e.g., a non-dormant BWP). Additionally or alternatively, the DCI or MAC-CE may correspond to the DCI or MAC-CE at a network entity for activating the SCell associated with the SCell carrier 320. For example, a network entity may send DCI or a MAC-CE to the UE to trigger the UE to activate the SCell associated with the SCell carrier 320 (e.g., to trigger the UE to switch from using the SCell carrier 320 according to the inactive state 310 to using the SCell carrier according to the active state 305). That is, the DCI or MAC-CE may correspond to an activation DCI or an activation MAC-CE (e.g., a DCI or MAC-CE for activating the SCell under fast handover). In such examples, the activation DCI or activation MAC-CE may (e.g., dynamically) indicate the set of QCL information available for the UE to use. For example, the activation DCI or activation MAC-CE may include bits (e.g., additional bits) indicating (e.g., pointing to) which set of QCL information is available for use at the UE (e.g., to determine the parameters for receiving the signaling 330). That is, the activation DCI or activation MAC-CE may include bits indicating a first set of QCL information or a second set of QCL information.

[0100] Additionally or alternatively, in some examples, the activation DCI or activation MAC-CE may include bits indicating the reference signal 325-a or the reference signal 325-b. In such examples, the UE may determine to use the first set of QCL information or the second set of QCL information based on whether the bit indicates the reference signal 325-a or the reference signal 325-b. For example, in an example where the bit indicates the reference signal 325-a (or indicates the anchor carrier 315), the UE may determine to use the first set of QCL information. Alternatively, in an example where the bit indicates the reference signal 325-b (or indicates the SCell carrier 320), the UE may determine to use the second set of QCL information. In some examples, by configuring the UE to use the first set of QCL information or the second set of QCL information, the network entity may reduce the latency associated with wireless communication between the UE and the network entity, as well as other possible benefits.

[0101] Figure 4An example of a process flow 400 for supporting QCL relationship indication of dormant and / or deactivated carriers according to one or more aspects of the present disclosure is illustrated. The process flow 400 may implement or be implemented to achieve or facilitate aspects of the wireless communication system 100, the wireless communication system 200, and the timing diagram 300. For example, the process flow 400 may include example operations associated with the network entity 405 and the UE 415, which may be as described by Figures 1 to 3 Examples of corresponding devices described with reference to these figures are illustrated. Operations performed at the network entity 405 or the UE 415 or both may support improvements to communications between the network entity 405 and the UE 415, among other benefits. In the following description of the process flow 400, the operations performed at the network entity 405 and the UE 415 may be performed in an order different from the example order shown. Additionally, the operations performed at the network entity 405 and the UE 415 may occur at different times. Some operations may be combined, and some operations may be omitted. Figure 4 In the example of , the network entity 405 and the UE 415 may support a framework for configuring the UE with a QCL relationship between a reference signal sent using an anchor cell and signaling sent using an SCell.

[0102] At 420, UE 415 may receive a carrier indication from network entity 405. In some examples, the carrier indication may be such as indicated by Figure 2 and Figure 3 Examples of carrier indications described with reference to these figures are illustrated. For example, the carrier indication may identify a first carrier and a second carrier for communication between a UE 415 and a network entity 405. In some examples, the second carrier may correspond to an SCell carrier associated with the SCell. Additionally, in some examples, the carrier indication may be included in the configuration of the SCell. In some examples, the carrier indication may correspond to an indication identifying the first carrier as an anchor carrier (e.g., identified as an anchor carrier for the second carrier).

[0103] At 425, UE 415 may receive a first QCL indication via the first carrier. In some examples, the first QCL indication may be as indicated by Figure 2 and Figure 3 Examples of first QCL indications are illustrated and described with reference to these figures.For example, the first QCL indication may identify a first set of QCL information (eg, a first set of one or more parameters) corresponding to a reference signal received using a first carrier.

[0104] At 430, UE 415 may receive a second QCL indication via a second carrier. In some examples, the second QCL indication may be a Figure 2 and Figure 3Example of a second QCL indication illustrated and described with reference to these figures. For example, the second QCL indication may identify a reference signal and may indicate that a first set of QCL information is associated with signaling received using a second carrier. In some examples, the second QCL indication may use one or more fields to identify the reference signal. For example, the second QCL indication may include a Specific_cell_CSI_RS field or a Specific_cell_ssb field that may identify the reference signal. In such examples, the UE may determine that the QCL information (e.g., the first set of QCL information) associated with the reference signal is common to the reference signal and the signaling received (or to be received) using the second carrier. That is, the second QCL indication may indicate to the UE 415 the QCL relationship between a reference signal that may be received at the UE 415 via a first carrier and signaling that may be received at the UE 415 via a second carrier.

[0105] For example, at 435, the UE 415 may receive a reference signal via a first carrier. In some examples, the reference signal may be an example of a reference signal illustrated and described with reference to these figures. For example, the reference signal may correspond to a CSI-RS. Figure 2 and Figure 3 For example, the reference signal may be an example of a reference signal illustrated and described with reference to these figures. For example, the reference signal may correspond to a CSI-RS.

[0106] In some examples, at 440, the UE 415 may receive signaling via a second carrier. For example, the UE 415 may receive the signaling based on the first set of QCL information and the reference signal received at 435. In some examples, based on the first set of QCL information and the reference signal, the UE 415 may identify one or more reception parameters for receiving (and decoding) the signaling via the second carrier. For example, based on the first set of QCL information, the UE may identify a reception beam for receiving the signaling using the second carrier. In some examples, by receiving the signaling via the second carrier according to the first set of QCL information and the reference signal, the UE 415 may reduce the latency associated with wireless communication using the second carrier, as well as other possible benefits.

[0107] Figure 5 Block diagram of a device 505 supporting QCL relationship indication for a dormant and / or deactivated carrier, in accordance with one or more aspects of the present disclosure. The device 505 may be an example of aspects of a UE. The device 505 may include a receiver 510, a transmitter 515, and a communication manager 520. The communication manager 520 may be implemented at least in part by one or both of a modem and a processor. Each of these components may communicate with each other (e.g., via one or more buses).

[0108] The receiver 510 may provide components for receiving information (such as packets, user data, control information, or any combination thereof) associated with various information channels (e.g., control channels, data channels, information channels related to the indication of the QCL relationship of a dormant and / or deactivated carrier). The information may be passed to other components of the device 505. The receiver 510 may utilize a single antenna or an array of multiple antennas.

[0109] The transmitter 515 may provide components for transmitting signals generated by other components of the device 505. For example, the transmitter 515 may transmit information (such as packets, user data, control information, or any combination thereof) associated with various information channels (e.g., control channels, data channels, information channels related to the indication of the QCL relationship of a dormant and / or deactivated carrier). In some examples, the transmitter 515 may be co-located with the receiver 510 in a transceiver. The transmitter 515 may utilize a single antenna or an array of multiple antennas.

[0110] The communication manager 520, the receiver 510, the transmitter 515, or various combinations thereof or their various components may be examples of components for performing various aspects of the indication of the QCL relationship of a dormant and / or deactivated carrier. For example, the communication manager 520, the receiver 510, the transmitter 515, or various combinations or components thereof may support methods for performing one or more functions.

[0111] In some examples, the communication manager 520 may be configured to use or otherwise cooperate with the receiver 510, the transmitter 515, or both to perform various operations (e.g., receive, obtain, monitor, output, transmit). For example, the communication manager 520 may receive information from the receiver 510, convey information to the transmitter 515, or be integrated with the receiver 510, the transmitter 515, or both to obtain information, output information, or perform various other operations.

[0112] According to examples disclosed herein, the communication manager 520 may support wireless communication at a UE (e.g., device 505). For example, the communication manager 520 may be configured as or otherwise support a component for receiving a carrier indication that identifies a first carrier and a second carrier for communication between the UE and a network entity. The communication manager 520 may be configured as or otherwise support a component for receiving a first QCL indication using the first carrier, the first QCL indication identifying a first set of QCL information, the first set of QCL information corresponding to a reference signal received using the first carrier. The communication manager 520 may be configured as or otherwise support a component for receiving a second QCL indication using the second carrier, the second QCL indication identifying the reference signal and indicating that the first set of QCL information is associated with signaling received using the second carrier.

[0113] By including or configuring a communication manager 520 according to some examples, a device 505 (e.g., a processor that controls or otherwise couples to a receiver 510, a transmitter 515, a communication manager 520, or a combination thereof) may support techniques for reducing power consumption and more efficiently utilizing communication resources.

[0114] Figure 6 A block diagram of a device 605 that illustrates support for a QCL relationship indication for a dormant and / or deactivated carrier in accordance with one or more aspects of the present disclosure is shown. The device 605 may be an example of aspects of the device 505 or the UE 115. The device 605 may include a receiver 610, a transmitter 615, and a communication manager 620. The communication manager 620 may be implemented at least in part by one or both of a modem and a processor. Each of these components may communicate with one another (e.g., via one or more buses).

[0115] The receiver 610 may provide components for receiving information (such as packets, user data, control information, or any combination thereof) associated with various information channels (e.g., control channels, data channels, information channels associated with a QCL relationship indication for a dormant and / or deactivated carrier). The information may be passed to other components of the device 605. The receiver 610 may utilize a single antenna or an array of multiple antennas.

[0116] The transmitter 615 may provide components for transmitting signals generated by other components of the device 605. For example, the transmitter 615 may transmit information (such as packets, user data, control information, or any combination thereof) associated with various information channels (e.g., control channels, data channels, information channels associated with a QCL relationship indication for a dormant and / or deactivated carrier). In some examples, the transmitter 615 may be co-located with the receiver 610 in a transceiver. The transmitter 615 may utilize a single antenna or an array of multiple antennas.

[0117] The device 605 or its various components may be examples of components for performing various aspects of a QCL relationship indication for a dormant and / or deactivated carrier. For example, the communication manager 620 may include a carrier component 625, a first QCL indication component 630, a second QCL indication component 635, or any combination thereof. In some examples, the communication manager 620 or its various components may be configured to use or otherwise cooperate with the receiver 610, the transmitter 615, or both to perform various operations (e.g., receive, obtain, monitor, output, transmit). For example, the communication manager 620 may receive information from the receiver 610, convey information to the transmitter 615, or be integrated with the receiver 610, the transmitter 615, or both to obtain information, output information, or perform various other operations.

[0118] According to an example disclosed herein, communication manager 620 may support wireless communication at a UE (e.g., device 605). Carrier component 625 may be configured as or otherwise support a component for receiving a carrier indication that identifies a first carrier and a second carrier for communication between the UE and a network entity. First QCL indication component 630 may be configured as or otherwise support a component for receiving a first QCL indication using the first carrier, the first QCL indication identifying a first set of QCL information, the first set of QCL information corresponding to a reference signal received using the first carrier. Second QCL indication component 635 may be configured as or otherwise support a component for receiving a second QCL indication using the second carrier, the second QCL indication identifying the reference signal and indicating that the first set of QCL information is associated with signaling received using the second carrier.

[0119] Figure 7 A block diagram illustrating a communication manager 720 that supports indication of QCL relationships for dormant and / or deactivated carriers, in accordance with one or more aspects of the present disclosure. Communication manager 720 may be an example of aspects of communication manager 520, communication manager 620, or both. Communication manager 720 or its various components may be examples of components for performing various aspects of indication of QCL relationships for dormant and / or deactivated carriers. For example, communication manager 720 may include carrier component 725, first QCL indication component 730, second QCL indication component 735, reference signal component 740, QCL information component 745, anchor carrier indication component 750, rule indication component 755, cell indication component 760, or any combination thereof. Each of these components may communicate directly or indirectly with each other (e.g., via one or more buses).

[0120] According to an example disclosed herein, communication manager 720 may support wireless communication at a UE. Carrier component 725 may be configured as or otherwise support a component for receiving a carrier indication that identifies a first carrier and a second carrier for communication between the UE and a network entity. First QCL indication component 730 may be configured as or otherwise support a component for receiving a first QCL indication using the first carrier, the first QCL indication identifying a first set of QCL information, the first set of QCL information corresponding to a reference signal received using the first carrier. Second QCL indication component 735 may be configured as or otherwise support a component for receiving a second QCL indication using the second carrier, the second QCL indication identifying the reference signal and indicating that the first set of QCL information is associated with signaling received using the second carrier.

[0121] In some examples, the reference signal component 740 may be configured as or otherwise support components for receiving the reference signal using the first carrier. In some examples, the QCL information component 745 may be configured as or otherwise support components for receiving the signaling using the second carrier based on the first set of QCL information and the reference signal.

[0122] In some examples, the first set of QCL information identifies a set of QCL parameters that are common to the reference signal and the signaling. In some examples, the set of QCL parameters is further common to a second signaling received using the first carrier.

[0123] In some examples, the anchor carrier indication component 750 may be configured as or otherwise support components for receiving an indication that the first carrier is an anchor carrier using the second carrier. In some examples, the second QCL indication is associated with the first carrier being the anchor carrier.

[0124] In some examples, the second QCL indication identifies a second set of QCL information, the second set of QCL information corresponding to a second reference signal received using the second carrier, and the QCL information component 745 may be configured as or otherwise support components for receiving the signaling using the second carrier based on the first set of QCL information or the second set of QCL information.

[0125] In some examples, the rule indication component 755 may be configured as or otherwise support components for receiving an indication associated with a rule for selecting QCL information using the second carrier. In some examples, receiving the signaling based on the first set of QCL information or the second set of QCL information is associated with the rule.

[0126] In some examples, the cell indication component 760 may be configured as or otherwise support components for receiving a first indication using the second carrier, the first indication identifying a cell associated with the second carrier to be activated at the UE. In some examples, the reference signal component 740 may be configured as or otherwise support components for receiving a second indication using the second carrier, the second indication identifying the reference signal or the second reference signal.

[0127] In some examples, the first set of QCL information identifies a first QCL type associated with an in-band anchor carrier or a second QCL type associated with an inter-band anchor carrier. In some examples, the signaling includes a TRS, a CSI-RS, a PDCCH signal, or a PDSCH signal.

[0128] Figure 8FIG. illustrates a system of device 805 including a QCL relationship indication supporting dormant and / or deactivated carriers in accordance with one or more aspects of the present disclosure. Device 805 may be an example of, or include components of, device 505, device 605, or UE 115. Device 805 may communicate with one or more network entities 105, one or more UEs 115, or any combination thereof (e.g., wirelessly). Device 805 may include components for two-way voice and data communication, including components for sending and receiving communications, such as communication manager 820, input / output (I / O) controller 810, transceiver 815, antenna 825, memory 830, code 835, and processor 840. These components may be electronically communicated or otherwise (e.g., operatively, communicatively, functionally, electronically, electrically) coupled via one or more buses (e.g., bus 845).

[0129] I / O controller 810 may manage input and output signals of device 805. I / O controller 810 may also manage peripheral devices not integrated into device 805. In some cases, I / O controller 810 may represent a physical connection or port to an external peripheral device. In some cases, I / O controller 810 may utilize an operating system, such as or another known operating system. Additionally or alternatively, I / O controller 810 may represent, or interact with, a modem, keyboard, mouse, touch screen, or similar device. In some cases, I / O controller 810 may be implemented as part of a processor (such as processor 840). In some cases, a user may interact with device 805 via I / O controller 810 or via hardware components controlled by I / O controller 810.

[0130] In some cases, device 805 may include a single antenna 825. However, in some other cases, device 805 may have more than one antenna 825, which may be capable of concurrently sending or receiving multiple wireless transmissions. Transceiver 815 may communicate bi-directionally via one or more antennas 825, wired or wireless links. For example, transceiver 815 may represent a wireless transceiver and may communicate bi-directionally with another wireless transceiver. Transceiver 815 may also include a modem for modulating packets for providing the modulated packets to one or more antennas 825 for transmission and for demodulating packets received from one or more antennas 825. Transceiver 815, or transceiver 815 and one or more antennas 825, may be examples of, or include components of, transmitter 515, transmitter 615, receiver 510, receiver 610, or any combination thereof.

[0131] Memory 830 may include random access memory (RAM) and read only memory (ROM). Memory 830 may store computer-readable, computer-executable code 835 including instructions that, in an example where the instructions are executable by processor 840, cause device 805 to perform various functions. Code 835 may be stored in a non-transitory computer-readable medium (such as system memory) or another type of memory. In some cases, code 835 may not be directly executable by processor 840, but may cause a computer (such as in an example where code 835 may be compiled and executed) to perform functions. In some cases, memory 830 may also include a basic input / output system (BIOS) and the like, which may control basic hardware or software operations, such as interactions with peripheral components or devices.

[0132] Processor 840 may include intelligent hardware devices (such as a general-purpose processor, DSP, CPU, microcontroller, ASIC, FPGA, programmable logic device, discrete gate or transistor logic component, discrete hardware component, or any combination thereof). In some cases, processor 840 may be configured to operate a memory array using a memory controller. In some other cases, the memory controller may be integrated into processor 840. Processor 840 may be configured to execute computer-readable instructions stored in a memory (such as memory 830) to cause device 805 to perform various functions (such as functions or tasks supporting indication of QCL relationships for hibernation and / or deactivation of carriers). For example, device 805 or components of device 805 may include processor 840 and memory 830 coupled to or coupled with processor 840, and processor 840 and memory 830 are configured to perform various functions.

[0133] According to examples disclosed herein, communication manager 820 may support wireless communication at a UE (such as device 805). For example, communication manager 820 may be configured as or otherwise support a component for receiving a carrier indication that identifies a first carrier and a second carrier for communication between the UE and a network entity. Communication manager 820 may be configured as or otherwise support a component for receiving a first QCL indication using the first carrier, the first QCL indication identifying a first set of QCL information, the first set of QCL information corresponding to a reference signal received using the first carrier. Communication manager 820 may be configured as or otherwise support a component for receiving a second QCL indication using the second carrier, the second QCL indication identifying the reference signal and indicating that the first set of QCL information is associated with signaling received using the second carrier.

[0134] By including or configuring a communication manager 820 according to some examples, the device 805 may support techniques for reducing latency, reducing power consumption, and more efficiently utilizing communication resources.

[0135] In some examples, the communication manager 820 may be configured to perform various operations (e.g., receive, monitor, transmit) using or otherwise in cooperation with the transceiver 815, one or more antennas 825, or any combination thereof. Although the communication manager 820 is illustrated as a separate component, in some examples, one or more of the functions described with reference to the communication manager 820 may be supported or performed by the processor 840, the memory 830, the code 835, or any combination thereof. For example, the code 835 may include instructions that can be executed by the processor 840 to cause the device 805 to perform various aspects of the QCL relationship indication for dormant and / or deactivated carriers, or the processor 840 and the memory 830 may otherwise be configured to perform or support such operations.

[0136] Figure 9 A block diagram of a device 905 supporting QCL relationship indication for dormant and / or deactivated carriers in accordance with one or more aspects of the present disclosure is illustrated. The device 905 may be an example of aspects of the network entity 105. The device 905 may include a receiver 910, a transmitter 915, and a communication manager 920. The communication manager 920 may be implemented at least in part by one or both of a modem and a processor. Each of these components may communicate with one another (e.g., via one or more buses).

[0137] The receiver 910 may provide components for obtaining (e.g., receiving, determining, identifying) information associated with various channels (e.g., control channels, data channels, information channels, channels associated with a protocol stack) such as user data, control information, or any combination thereof (e.g., I / Q samples, symbols, packets, protocol data units, service data units). The information may be passed to other components of the device 905. In some examples, the receiver 910 may support obtaining information by receiving signals via one or more antennas. Additionally or alternatively, the receiver 910 may support obtaining information by receiving signals via one or more wired (e.g., electrical, fiber optic) interfaces, wireless interfaces, or any combination thereof.

[0138] Transmitter 915 may provide components for outputting (e.g., transmitting, providing, conveying, delivering) information generated by other components of device 905. For example, transmitter 915 may output information associated with various channels (e.g., control channels, data channels, information channels, channels associated with a protocol stack) such as user data, control information, or any combination thereof (e.g., I / Q samples, symbols, packets, protocol data units, service data units). In some examples, transmitter 915 may support outputting information by transmitting signals via one or more antennas. Additionally or alternatively, transmitter 915 may support outputting information by transmitting signals via one or more wired (e.g., electrical, optical fiber) interfaces, wireless interfaces, or any combination thereof. In some examples, transmitter 915 and receiver 910 may be co-located in a transceiver, which may include a modem or be coupled to a modem.

[0139] Communication manager 920, receiver 910, transmitter 915, or various combinations thereof or their various components may be examples of components for performing various aspects of QCL relationship indication for performing carrier sleep and / or deactivation. For example, communication manager 920, receiver 910, transmitter 915, or various combinations or components thereof may support methods for performing one or more functions.

[0140] In some examples, communication manager 920 may be configured to use or otherwise cooperate with receiver 910, transmitter 915, or both to perform various operations (e.g., receive, obtain, monitor, output, transmit). For example, communication manager 920 may receive information from receiver 910, convey information to transmitter 915, or be integrated with receiver 910, transmitter 915, or both to obtain information, output information, or perform various other operations.

[0141] According to examples disclosed herein, communication manager 920 may support wireless communication at a network entity (e.g., device 905). For example, communication manager 920 may be configured as or otherwise support a component for outputting a carrier indication that identifies a first carrier and a second carrier for communication between a UE and the network entity. Communication manager 920 may be configured as or otherwise support a component for using the first carrier to output a first QCL indication that identifies a first set of QCL information, the first set of QCL information corresponding to a reference signal output using the first carrier. Communication manager 920 may be configured as or otherwise support a component for using the second carrier to output a second QCL indication that identifies the reference signal and indicates that the first set of QCL information is associated with signaling output using the second carrier.

[0142] By including or configuring a communication manager 920 according to some examples, a device 905 (e.g., a processor that controls or otherwise couples to a receiver 910, a transmitter 915, a communication manager 920, or a combination thereof) may support techniques for reducing power consumption and more efficiently utilizing communication resources.

[0143] Figure 10 FIG. illustrates a block diagram of a device 1005 supporting QCL relationship indication for carrier sleep and / or deactivation according to one or more aspects of the present disclosure. The device 1005 may be an example of aspects of the device 905 or the network entity 105. The device 1005 may include a receiver 1010, a transmitter 1015, and a communication manager 1020. The communication manager 1020 may be implemented at least in part by one or both of a modem and a processor. Each of these components may communicate with one another (e.g., via one or more buses).

[0144] The receiver 1010 may provide components for obtaining (e.g., receiving, determining, identifying) information associated with various channels (e.g., control channels, data channels, information channels, channels associated with a protocol stack) such as user data, control information, or any combination thereof (e.g., I / Q samples, symbols, packets, protocol data units, service data units). The information may be passed to other components of the device 1005. In some examples, the receiver 1010 may support obtaining information by receiving signals via one or more antennas. Additionally or alternatively, the receiver 1010 may support obtaining information by receiving signals via one or more wired (e.g., electrical, fiber optic) interfaces, wireless interfaces, or any combination thereof.

[0145] The transmitter 1015 may provide components for outputting (e.g., transmitting, providing, conveying, delivering) information generated by other components of the device 1005. For example, the transmitter 1015 may output information associated with various channels (e.g., control channels, data channels, information channels, channels associated with a protocol stack) such as user data, control information, or any combination thereof (e.g., I / Q samples, symbols, packets, protocol data units, service data units). In some examples, the transmitter 1015 may support outputting information by transmitting signals via one or more antennas. Additionally or alternatively, the transmitter 1015 may support outputting information by transmitting signals via one or more wired (e.g., electrical, fiber optic) interfaces, wireless interfaces, or any combination thereof. In some examples, the transmitter 1015 and the receiver 1010 may be co-located in a transceiver that may include a modem or be coupled to a modem.

[0146] Device 1005 or its various components can be examples of components for performing various aspects of QCL relationship indication for hibernating and / or deactivating carriers. For example, communication manager 1020 can include carrier indication component 1025, first carrier component 1030, second carrier component 1035, or any combination thereof. In some examples, communication manager 1020 or its various components can be configured to perform various operations (e.g., receive, obtain, monitor, output, transmit) using or otherwise in cooperation with receiver 1010, transmitter 1015, or both. For example, communication manager 1020 can receive information from receiver 1010, convey information to transmitter 1015, or be integrated with receiver 1010, transmitter 1015, or both to obtain information, output information, or perform various other operations.

[0147] According to examples as disclosed herein, communication manager 1020 can support wireless communication at a network entity (e.g., device 1005). Carrier indication component 1025 can be configured as or otherwise support a component for outputting a carrier indication that identifies a first carrier and a second carrier for communication between a UE and the network entity. First carrier component 1030 can be configured as or otherwise support a component for outputting a first QCL indication using the first carrier, the first QCL indication identifying a first set of QCL information, the first set of QCL information corresponding to a reference signal output using the first carrier. Second carrier component 1035 can be configured as or otherwise support a component for outputting a second QCL indication using the second carrier, the second QCL indication identifying the reference signal and indicating that the first set of QCL information is associated with signaling output using the second carrier.

[0148] Figure 11A block diagram of a communication manager 1120 that illustrates a QCL relationship indication that supports carrier sleep and / or deactivation in accordance with one or more aspects of the present disclosure. The communication manager 1120 may be an example of aspects of the communication manager 920, the communication manager 1020, or both. The communication manager 1120 or its various components may be examples of components for performing various aspects of a QCL relationship indication that supports carrier sleep and / or deactivation. For example, the communication manager 1120 may include a carrier indication component 1125, a first carrier component 1130, a second carrier component 1135, an anchor carrier component 1140, a rules component 1145, a cell activation component 1150, or any combination thereof. Each of these components may communicate directly or indirectly with each other (e.g., via one or more buses), which communication may include communication within a protocol layer of a protocol stack, communication associated with a logical channel of the protocol stack (e.g., between protocol layers of the protocol stack, within a device, component, or virtualized component associated with the network entity 105, between devices, components, or virtualized components associated with the network entity 105), or any combination thereof.

[0149] In accordance with an example as disclosed herein, the communication manager 1120 may support wireless communication at a network entity. The carrier indication component 1125 may be configured as or otherwise support a component for outputting a carrier indication that identifies a first carrier and a second carrier for communication between a UE and the network entity. The first carrier component 1130 may be configured as or otherwise support a component for outputting a first QCL indication using the first carrier, the first QCL indication identifying a first set of QCL information, the first set of QCL information corresponding to a reference signal output using the first carrier. The second carrier component 1135 may be configured as or otherwise support a component for outputting a second QCL indication using the second carrier, the second QCL indication identifying the reference signal and indicating that the first set of QCL information is associated with signaling output using the second carrier.

[0150] In some examples, the first carrier component 1130 may be configured as or otherwise support a component for outputting the reference signal using the first carrier. In some examples, the second carrier component 1135 may be configured as or otherwise support a component for outputting the signaling using the second carrier in accordance with the first set of QCL information and the reference signal.

[0151] In some examples, the first set of QCL information identifies a set of QCL parameters that are common to the reference signal and the signaling. In some examples, the set of QCL parameters is further common to a second signaling output using the first carrier.

[0152] In some examples, the anchor carrier component 1140 may be configured as or otherwise support a component for using the second carrier to output an indication that the first carrier is the anchor carrier. In some examples, the second QCL indication is associated with the first carrier being the anchor carrier.

[0153] In some examples, the second QCL indication identifies a second set of QCL information, the second set of QCL information corresponding to a second reference signal output using the second carrier, and the second carrier component 1135 may be configured as or otherwise support a component for using the second carrier to output the signaling based on the first set of QCL information or the second set of QCL information.

[0154] In some examples, the rule component 1145 may be configured as or otherwise support a component for using the second carrier to output an indication associated with a rule for selecting QCL information. In some examples, outputting the signaling based on the first set of QCL information or the second set of QCL information is associated with the rule.

[0155] In some examples, the cell activation component 1150 may be configured as or otherwise support a component for using the second carrier to output a first indication that identifies a cell associated with the second carrier to be activated at the UE. In some examples, the second carrier component 1135 may be configured as or otherwise support a component for using the second carrier to output a second indication that identifies the reference signal or the second reference signal.

[0156] In some examples, the first set of QCL information identifies a first QCL type associated with an in-band anchor carrier or a second QCL type associated with an inter-band anchor carrier. In some examples, the signaling includes a TRS, a CSI-RS, a PDCCH signal, or a PDSCH signal.

[0157] Figure 12Illustrated is a diagram of a system including device 1205 that supports QCL relationship indication for carrier sleep and / or deactivation, in accordance with one or more aspects of the present disclosure. Device 1205 may be an example of device 905, device 1005, or network entity 105, or include components thereof. Device 1205 may communicate with one or more network entities 105, one or more UEs 115, or any combination thereof, which communication may include communication via one or more wired interfaces, via one or more wireless interfaces, or any combination thereof. Device 1205 may include components that support outputting and obtaining communication, such as communication manager 1220, transceiver 1210, antenna 1215, memory 1225, code 1230, and processor 1235. These components may communicate electronically or otherwise (e.g., operatively, communicatively, functionally, electronically, electrically) couple via one or more buses (e.g., bus 1240).

[0158] The transceiver 1210 may support bidirectional communication via a wired link, a wireless link, or both. In some examples, the transceiver 1210 may include a wired transceiver and may communicate bidirectionally with another wired transceiver. Additionally or alternatively, in some examples, the transceiver 1210 may include a wireless transceiver and may communicate bidirectionally with another wireless transceiver. In some examples, the device 1205 may include one or more antennas 1215, which may be capable of (e.g., concurrently) sending or receiving wireless transmissions. The transceiver 1210 may also include a modem for modulating a signal (e.g., via one or more antennas 1215, via a wired transmitter) to provide the modulated signal for transmission, for receiving the modulated signal (e.g., from one or more antennas 1215, from a wired receiver), and for demodulating the signal. In some implementations, the transceiver 1210 may include one or more interfaces, such as one or more interfaces coupled to one or more antennas 1215 configured to support various receiving or obtaining operations, or one or more interfaces coupled to one or more antennas 1215 configured to support various sending or outputting operations, or a combination thereof. In some implementations, the transceiver 1210 may include or be configured to be coupled to one or more processors or memory components, which are operable to perform or support operations based on received or obtained information or signals, or to generate information or other signals for transmission or other output, or any combination thereof. In some implementations, the transceiver 1210, or the transceiver 1210 and one or more antennas 1215, or the transceiver 1210 and one or more antennas 1215 and one or more processors or memory components (e.g., processor 1235, or memory 1225, or both) may be included in a chip or chip assembly installed in the device 1205. In some examples, the transceiver may be operable to support communications via one or more communication links (eg, communication link 125, backhaul communication link 120, midhaul communication link 162, fronthaul communication link 168).

[0159] The memory 1225 may include RAM and ROM. The memory 1225 may store computer-readable, computer-executable code 1230 including instructions that, in an example where the instructions are executable by the processor 1235, cause the device 1205 to perform various functions. The code 1230 may be stored in a non-transitory computer-readable medium (such as system memory) or another type of memory. In some cases, the code 1230 may not be directly executable by the processor 1235 but may cause a computer (such as in an example where the code 1230 may be compiled and executed) to perform functions. In some cases, the memory 1225 may also contain a BIOS or the like that may control basic hardware or software operations, such as interactions with peripheral components or devices.

[0160] Processor 1235 may include intelligent hardware devices (e.g., general-purpose processors, DSPs, ASICs, CPUs, FPGAs, microcontrollers, programmable logic devices, discrete gate or transistor logic, discrete hardware components, or any combination thereof). In some cases, processor 1235 may be configured to operate a memory array using a memory controller. In some other cases, the memory controller may be integrated into processor 1235. Processor 1235 may be configured to execute computer-readable instructions stored in a memory (e.g., memory 1225) to cause device 1205 to perform various functions (e.g., functions or tasks supporting QCL relationship indication for hibernation and / or deactivation of carriers). For example, device 1205 or components of device 1205 may include processor 1235 and memory 1225 coupled to processor 1235, and processor 1235 and memory 1225 are configured to perform various functions. Processor 1235 may be an example of a cloud computing platform (e.g., one or more physical nodes and supporting software such as an operating system, virtual machine, or container instance) that may host functions (e.g., by executing code 1230) to perform the functions of device 1205. Processor 1235 may be any one or more suitable processors capable of executing scripts or instructions of one or more software programs stored in device 1205 (such as within memory 1225). In some specific implementations, processor 1235 may be a component of a processing system. A processing system generally may refer to a system or series of machines or components that receive inputs and process these inputs to produce a set of outputs (which may be passed to other systems or components such as device 1205). For example, the processing system of device 1205 may refer to a system including various other components or sub-components of device 1205 (such as processor 1235, or transceiver 1210, or communication manager 1220, or a combination of other components or components of device 1205). The processing system of device 1205 may interface with other components of device 1205 and may process information (such as inputs or signals) received from other components or output information to other components. For example, a chip or modem of device 1205 may include a processing system and one or more interfaces for outputting information or for obtaining information or both. One or more interfaces may be implemented as or otherwise include a first interface configured to output information and a second interface configured to obtain information or the same interface configured to output information and obtain information, as well as other specific implementations. In some specific implementations, one or more interfaces may refer to an interface between the processing system of a chip or modem and a transmitter such that device 1205 may transmit information output from the chip or modem. Additionally or alternatively, in some specific implementations, one or more interfaces may refer to an interface between the processing system of a chip or modem and a receiver such that device 1205 may obtain information or signal inputs, and the information may be passed to the processing system.One of ordinary skill in the art will readily recognize that the first interface may also receive information or signal inputs, and the second interface may also output information or signal outputs.

[0161] In some examples, bus 1240 may support communication within a protocol layer of a protocol stack (e.g., within the protocol layer). In some examples, bus 1240 may support communication associated with a logical channel of a protocol stack (e.g., between protocol layers of the protocol stack), which may include communication performed within components of device 1205, or communication performed between different components of device 1205 that may be co-located or located at different locations (e.g., device 1205 may refer to a system in which one or more of communication manager 1220, transceiver 1210, memory 1225, code 1230, and processor 1235 may be located in one of different components or divided between different components).

[0162] In some examples, communication manager 1220 may manage (e.g., via one or more wired or wireless backhaul links) aspects of communication with core network 130. For example, communication manager 1220 may manage the delivery of data communication for client devices such as one or more UEs 115. In some examples, communication manager 1220 may manage communication with other network entities 105 and may include a controller or scheduler for coordinating with other network entities 105 to control communication with UEs 115. In some examples, communication manager 1220 may support the X2 interface within the LTE / LTE-A wireless communication network technology to provide communication between network entities 105.

[0163] According to examples disclosed herein, communication manager 1220 may support wireless communication at a network entity (e.g., device 1205). For example, communication manager 1220 may be configured as or otherwise support a component for outputting a carrier indication that identifies a first carrier and a second carrier for communication between a UE and the network entity. Communication manager 1220 may be configured as or otherwise support a component for outputting a first QCL indication using the first carrier, the first QCL indication identifying a first set of QCL information, the first set of QCL information corresponding to a reference signal output using the first carrier. Communication manager 1220 may be configured as or otherwise support a component for outputting a second QCL indication using the second carrier, the second QCL indication identifying the reference signal and indicating that the first set of QCL information is associated with signaling output using the second carrier.

[0164] By including or configuring communication manager 1220 according to some examples, device 1205 may support techniques for reducing latency, reducing power consumption, and more efficiently utilizing communication resources.

[0165] In some examples, the communication manager 1220 may be configured to perform various operations (e.g., receive, obtain, monitor, output, transmit) using or otherwise in cooperation with the transceiver 1210, one or more antennas 1215 (e.g., such as applicable examples of the antenna 1215), or any combination thereof. Although the communication manager 1220 is illustrated as a separate component, in some examples, one or more of the functions described with reference to the communication manager 1220 may be supported or performed by the transceiver 1210, the processor 1235, the memory 1225, the code 1230, or any combination thereof. For example, the code 1230 may include instructions that can be executed by the processor 1235 to cause the device 1205 to perform various aspects of the QCL relationship indication for carrier sleep and / or deactivation, or the processor 1235 and the memory 1225 may otherwise be configured to perform or support such operations.

[0166] Figure 13 A flowchart illustrating a method 1300 for supporting QCL relationship indication for carrier sleep and / or deactivation in accordance with one or more aspects of the present disclosure is illustrated. The operations of the method 1300 may be implemented by a UE or components thereof. For example, the operations of the method 1300 may be performed by a UE 115 as described with reference to Figures 1 to 8 In some examples, the UE may execute an instruction set to control functional elements of the UE to perform the described functions. Additionally or alternatively, the UE may use dedicated hardware to perform aspects of the described functions.

[0167] At 1305, the method may include: receiving a carrier indication that identifies a first carrier and a second carrier for communication between the UE and a network entity. The operation of 1305 may be performed in accordance with examples disclosed herein. In some examples, aspects of the operation of 1305 may be performed by a carrier component 725 as described with reference to Figure 7 At 1310, the method may include: using the first carrier to receive a first QCL indication that identifies a first set of QCL information, the first set of QCL information corresponding to a reference signal received using the first carrier. The operation of 1310 may be performed in accordance with examples disclosed herein. In some examples, aspects of the operation of 1310 may be performed by a first QCL indication component 730 as described with reference to

[0168] Figure 7

[0169] ​​At 1315, the method may include: receiving, using the second carrier, a second QCL indication that identifies the reference signal and indicates that the first set of QCL information is associated with signaling received using the second carrier. The operations at 1315 may be performed in accordance with the examples disclosed herein. In some examples, aspects of the operations at 1315 may be performed by a second QCL indication component 735 as described with reference to Figure 7 as described.

[0170] Figure 14 FIG. illustrates a flowchart of a method 1400 for supporting QCL relationship indication for a dormant and / or deactivated carrier in accordance with one or more aspects of the present disclosure. The operations of method 1400 may be implemented by a UE or components thereof. For example, the operations of method 1400 may be performed by a UE 115 as described with reference to Figures 1 to 8 as described. In some examples, the UE may execute an instruction set to control functional elements of the UE to perform the described functions. Additionally or alternatively, the UE may use dedicated hardware to perform aspects of the described functions.

[0171] At 1405, the method may include: receiving a carrier indication that identifies a first carrier and a second carrier for communication between the UE and a network entity. The operations at 1405 may be performed in accordance with the examples disclosed herein. In some examples, aspects of the operations at 1405 may be performed by a carrier component 725 as described with reference to Figure 7 as described.

[0172] At 1410, the method may include: receiving, using the first carrier, a first QCL indication that identifies a first set of QCL information, the first set of QCL information corresponding to a reference signal received using the first carrier. The operations at 1410 may be performed in accordance with the examples disclosed herein. In some examples, aspects of the operations at 1410 may be performed by a first QCL indication component 730 as described with reference to Figure 7 as described.

[0173] At 1415, the method may include: receiving, using the second carrier, a second QCL indication that identifies the reference signal and indicates that the first set of QCL information is associated with signaling received using the second carrier. The operations at 1415 may be performed in accordance with the examples disclosed herein. In some examples, aspects of the operations at 1415 may be performed by a second QCL indication component 735 as described with reference to Figure 7 as described.

[0174] At 1420, the method may include: receiving the reference signal using the first carrier. The operations at 1420 may be performed in accordance with the examples disclosed herein. In some examples, aspects of the operations at 1420 may be performed by a reference toFigure 7 performed by the described reference signal component 740.

[0175] At 1425, the method may include: receiving the signaling using the second carrier based on the first set of QCL information and the reference signal. The operation at 1425 may be performed in accordance with the examples disclosed herein. In some examples, aspects of the operation at 1425 may be performed by a QCL information component 745 as described in reference Figure 7 to.

[0176] Figure 15 FIG. illustrates a flow chart of a method 1500 that supports indication of QCL relationships for carrier dormancy and / or deactivation according to one or more aspects of the present disclosure. The operations of method 1500 may be implemented by a network entity or its components. For example, the operations of method 1500 may be performed by a network entity as described in reference Figures 1 to 4 and Figures 9 to 12 to. In some examples, the network entity may execute an instruction set to control functional elements of the network entity to perform the described functions. Additionally or alternatively, the network entity may use dedicated hardware to perform aspects of the described functions.

[0177] At 1505, the method may include: outputting a carrier indication that identifies a first carrier and a second carrier for communication between a UE and a network entity. The operation at 1505 may be performed in accordance with the examples disclosed herein. In some examples, aspects of the operation at 1505 may be performed by a carrier indication component 1125 as described in reference Figure 11 to.

[0178] At 1510, the method may include: outputting a first QCL indication using the first carrier, the first QCL indication identifying a first set of QCL information, the first set of QCL information corresponding to a reference signal output using the first carrier. The operation at 1510 may be performed in accordance with the examples disclosed herein. In some examples, aspects of the operation at 1510 may be performed by a first carrier component 1130 as described in reference Figure 11 to.

[0179] At 1515, the method may include: outputting a second QCL indication using the second carrier, the second QCL indication identifying the reference signal and indicating that the first set of QCL information is associated with signaling output using the second carrier. The operation at 1515 may be performed in accordance with the examples disclosed herein. In some examples, aspects of the operation at 1515 may be performed by a second carrier component 1135 as described in reference Figure 11 to.

[0180] Figure 16A flowchart illustrating a method 1600 for supporting dormant and / or deactivated carrier QCL indication in accordance with one or more aspects of the present disclosure is shown. Operations of method 1600 may be implemented by a network entity or its components. For example, operations of method 1600 may be performed by a network entity as described with reference to Figures 1 to 4 and Figures 9 to 12 . In some examples, the network entity may execute an instruction set to control functional elements of the network entity to perform the described functions. Additionally or alternatively, the network entity may use dedicated hardware to perform aspects of the described functions.

[0181] At 1605, the method may include: outputting a carrier indication that identifies a first carrier and a second carrier for communication between a UE and a network entity. The operation of 1605 may be performed in accordance with examples as disclosed herein. In some examples, aspects of the operation of 1605 may be performed by a carrier indication component 1125 as described with reference to Figure 11 .

[0182] At 1610, the method may include: using the first carrier to output a first QCL indication that identifies a first set of QCL information, the first set of QCL information corresponding to a reference signal output using the first carrier. The operation of 1610 may be performed in accordance with examples as disclosed herein. In some examples, aspects of the operation of 1610 may be performed by a first carrier component 1130 as described with reference to Figure 11 .

[0183] At 1615, the method may include: using the second carrier to output a second QCL indication that identifies the reference signal and indicates that the first set of QCL information is associated with signaling output using the second carrier. The operation of 1615 may be performed in accordance with examples as disclosed herein. In some examples, aspects of the operation of 1615 may be performed by a second carrier component 1135 as described with reference to Figure 11 .

[0184] At 1620, the method may include: using the first carrier to output the reference signal. The operation of 1620 may be performed in accordance with examples as disclosed herein. In some examples, aspects of the operation of 1620 may be performed by a first carrier component 1130 as described with reference to Figure 11 .

[0185] At 1625, the method may include: using the second carrier to output the signaling based on the first set of QCL information and the reference signal. The operation of 1625 may be performed in accordance with examples as disclosed herein. In some examples, aspects of the operation of 1625 may be performed by a second carrier component 1135 as described with reference to Figure 11 .

[0186] An overview of various aspects of the present disclosure is provided below:

[0187] Aspect 1: A method for wireless communication at a UE, the method comprising: receiving a carrier indication that identifies a first carrier and a second carrier for communication between the UE and a network entity; using the first carrier to receive a first QCL indication that identifies a first set of QCL information, the first set of QCL information corresponding to a reference signal received using the first carrier; and using the second carrier to receive a second QCL indication that identifies the reference signal and indicates that the first set of QCL information is associated with signaling received using the second carrier.

[0188] Aspect 2: The method according to aspect 1, the method further comprising: using the first carrier to receive the reference signal; and using the second carrier to receive the signaling based on the first set of QCL information and the reference signal.

[0189] Aspect 3: The method according to aspect 2, wherein the first set of QCL information identifies a set of QCL parameters that are common to the reference signal and the signaling.

[0190] Aspect 4: The method according to aspect 3, wherein the set of QCL parameters is further common to a second signaling received using the first carrier.

[0191] Aspect 5: The method according to any one of aspects 1 to 4, the method further comprising: using the second carrier to receive an indication that the first carrier is an anchor carrier, wherein the second QCL indication is associated with the first carrier being the anchor carrier.

[0192] Aspect 6: The method according to any one of aspects 1 to 5, wherein the second QCL indication identifies a second set of QCL information, the second set of QCL information corresponding to a second reference signal received using the second carrier, the method further comprising: using the second carrier to receive the signaling based on the first set of QCL information or the second set of QCL information.

[0193] Aspect 7: The method according to aspect 6, the method further comprising: using the second carrier to receive an indication associated with a rule for selecting QCL information, wherein receiving the signaling based on the first set of QCL information or the second set of QCL information is associated with the rule.

[0194] Aspect 8: The method according to aspect 6, the method further comprising: using the second carrier to receive a first indication, the first indication identifying a cell associated with the second carrier to be activated at the UE.

[0195] Aspect 9: The method according to aspect 8, the method further comprising: using the second carrier to receive a second indication, the second indication identifying the reference signal or the second reference signal.

[0196] Aspect 10: The method according to any one of aspects 1 to 9, wherein the first set of QCL information identifies a first QCL type associated with an in-band anchor carrier or a second QCL type associated with an inter-band anchor carrier.

[0197] Aspect 11: The method according to any one of aspects 1 to 10, wherein the signaling comprises a TRS, a CSI-RS, a PDCCH signal, or a PDSCH signal.

[0198] Aspect 12: A method for wireless communication at a network entity, the method comprising: outputting a carrier indication, the carrier indication identifying a first carrier and a second carrier for communication between a UE and the network entity; using the first carrier to output a first QCL indication, the first QCL indication identifying a first set of QCL information, the first set of QCL information corresponding to a reference signal output using the first carrier; and using the second carrier to output a second QCL indication, the second QCL indication identifying the reference signal and indicating that the first set of QCL information is associated with signaling output using the second carrier.

[0199] Aspect 13: The method according to aspect 12, the method further comprising: using the first carrier to output the reference signal; and using the second carrier to output the signaling according to the first set of QCL information and the reference signal.

[0200] Aspect 14: The method according to aspect 13, wherein the first set of QCL information identifies a set of QCL parameters common to the reference signal and the signaling.

[0201] Aspect 15: The method according to aspect 14, wherein the set of QCL parameters is further common to a second signaling output using the first carrier.

[0202] Aspect 16: The method according to any one of aspects 12 to 15, the method further comprising: using the second carrier to output an indication that the first carrier is an anchor carrier, wherein the second QCL indication is associated with the first carrier being used as the anchor carrier.

[0203] Aspect 17: The method according to any one of Aspects 12 to 16, wherein the second QCL indication identifies a second set of QCL information, and the second set of QCL information corresponds to a second reference signal output using the second carrier. The method further includes: using the second carrier to output the signaling according to the first set of QCL information or the second set of QCL information.

[0204] Aspect 18: The method according to Aspect 17, the method further includes: using the second carrier to output an indication associated with a rule for selecting QCL information, wherein outputting the signaling according to the first set of QCL information or the second set of QCL information is associated with the rule.

[0205] Aspect 19: The method according to Aspect 17, the method further includes: using the second carrier to output a first indication that identifies a cell associated with the second carrier to be activated at the UE.

[0206] Aspect 20: The method according to Aspect 19, the method further includes: using the second carrier to output a second indication that identifies the reference signal or the second reference signal.

[0207] Aspect 21: The method according to any one of Aspects 12 to 20, wherein the first set of QCL information identifies a first QCL type associated with an in-band anchor carrier or a second QCL type associated with an inter-band anchor carrier.

[0208] Aspect 22: The method according to any one of Aspects 12 to 21, wherein the signaling includes a TRS, a CSI-RS, a PDCCH signal, or a PDSCH signal.

[0209] Aspect 23: An apparatus for wireless communication at a UE, the apparatus includes: a processor; and a memory coupled to the processor and storing instructions that can be executed by the processor to cause the apparatus to perform the method according to any one of Aspects 1 to 11.

[0210] Aspect 24: An apparatus for wireless communication at a UE, the apparatus includes at least one component for performing the method according to any one of Aspects 1 to 11.

[0211] Aspect 25: A non-transitory computer-readable medium storing code for wireless communication at a UE, the code includes instructions that can be executed by a processor to perform the method according to any one of Aspects 1 to 11.

[0212] Aspect 26: An apparatus for wireless communication at a network entity, the apparatus comprising: a processor; and a memory coupled to the processor and storing instructions executable by the processor to cause the apparatus to perform the method according to any one of Aspects 12 to 22.

[0213] Aspect 27: An apparatus for wireless communication at a network entity, the apparatus comprising at least one component for performing the method according to any one of Aspects 12 to 22.

[0214] Aspect 28: A non-transitory computer-readable medium storing code for wireless communication at a network entity, the code comprising instructions executable by a processor to perform the method according to any one of Aspects 12 to 22.

[0215] It should be noted that the methods described in this disclosure describe possible specific implementations, and the operations and steps can be rearranged or otherwise modified and other specific implementations are also possible. In addition, aspects from two or more methods can be combined.

[0216] Although aspects of LTE, LTE-A, LTE-A Pro, or NR systems may be described for illustrative purposes and the terms LTE, LTE-A, LTE-A Pro, or NR may be used in most of the description, the techniques described in this disclosure are also applicable to networks other than LTE, LTE-A, LTE-A Pro, or NR networks. For example, the described techniques may be applicable to various other wireless communication systems such as Ultra Mobile Broadband (UMB), Institute of Electrical and Electronics Engineers (IEEE) 802.11 (Wi-Fi), IEEE 802.16 (WiMAX), IEEE 802.20, Flash-OFDM, and other systems and radio technologies not explicitly mentioned herein.

[0217] The information and signals described in this disclosure can be represented using any of a variety of different technologies and methods. For example, data, instructions, commands, information, signals, bits, symbols, and chips mentioned throughout the specification can be represented by voltage, current, electromagnetic waves, magnetic fields or magnetic particles, optical fields or optical particles, or any combination thereof.

[0218] The various illustrative blocks and components described in connection with the disclosure herein may be implemented or performed using a general purpose processor, a DSP, an ASIC, a CPU, an FPGA or other programmable logic device, discrete gate or transistor logic, discrete hardware components, or any combination thereof designed to perform the functions described in this disclosure. A general purpose processor may be a microprocessor, but in the alternative, the processor may be any processor, controller, microcontroller, or state machine. The processor may also be implemented as a combination of computing devices (e.g., a combination of a DSP and a microprocessor, multiple microprocessors, one or more microprocessors in conjunction with a DSP core, or any other such configuration).

[0219] The functions described in this disclosure may be implemented using hardware, software executed by a processor, firmware, or any combination thereof. If implemented using software executed by a processor, the functions may be stored as one or more instructions or code on a computer-readable medium or transmitted using one or more instructions or code on a computer-readable medium. Other examples and specific implementations are within the scope of this disclosure and the appended claims. For example, due to the nature of software, the functions described in this disclosure may be implemented using software executed by a processor, hardware, firmware, hardwiring, or any combination of these items. The features implementing the functions may also be physically located at different positions, including being distributed such that portions of the functions are implemented at different physical locations.

[0220] A computer-readable medium includes both a non-transitory computer storage medium and a communication medium, where the communication medium includes any medium that facilitates transfer of a computer program from one location to another. The non-transitory storage medium can be any available medium that can be accessed by a general or special purpose computer. By way of example, and not limitation, non-transitory computer-readable media can include RAM, ROM, electrically erasable programmable ROM (EEPROM), flash memory, compact disc read only memory (CD-ROM) or other optical disc storage, magnetic disk storage or other magnetic storage devices, or any other non-transitory medium that can be used to carry or store desired program code portions in the form of instructions or data structures and that can be accessed by a general or special purpose computer or a general or special purpose processor. Also, any connection is properly termed a computer-readable medium. For example, if software is transmitted using coaxial cable, fiber optic cable, twisted pair, digital subscriber line (DSL), or wireless technologies such as infrared, radio, and microwave, then the coaxial cable, fiber optic cable, twisted pair, DSL, or wireless technologies such as infrared, radio, and microwave are included in the definition of computer-readable medium. As used herein, disk and disc include CD, laser disc, optical disc, digital versatile disc (DVD), floppy disk, and Blu-ray disc. A disk can magnetically reproduce data, and a disc can optically reproduce data using a laser. Combinations of the above are also included within the scope of computer-readable media.

[0221] As used herein, and as included in the claims, the term “or” as used in a list of items (e.g., a list of items followed by a phrase such as “at least one of” or “one or more of”) in a claim indicates an inclusive list, such that for example, a list of at least one of A, B, or C represents A or B or C or AB or AC or BC or ABC (in other words, A and B and C). Additionally, as used herein, the phrase “based on” should not be construed as a reference to a closed set of conditions. For example, an example step described as “based on condition A” can be based on both condition A and condition B without departing from the scope of the present disclosure. In other words, as used herein, the phrase “based on” should be interpreted in the same manner as the phrase “at least partially based on”.

[0222] The term “determine” encompasses a variety of actions and “determine” can include calculating, computing, processing, deriving, investigating, looking up (such as looking up in a table, database, or other data structure), ascertaining, and the like. Additionally, “determine” can include receiving (e.g., receiving information), accessing (e.g., accessing data stored in a memory), and the like. Additionally, “determine” can include parsing, obtaining, selecting, choosing, establishing, and other such like actions.

[0223] In the accompanying drawings, like components or features may have the same reference numerals. Additionally, various components of the same type can be distinguished by adding a dash and a second numeral for distinguishing between like components after the reference numeral. If only the first reference numeral is used in the specification, the description can apply to any one of the like components having the same first reference numeral, regardless of the second reference numeral or any other subsequent reference numerals.

[0224] The description set forth herein in conjunction with the drawings describes exemplary configurations and does not represent all examples that can be implemented or that are within the scope of the claims. The term "exemplary" as used herein means "serving as an example, instance, or illustration" and not "preferred" or "advantageous over other examples." The detailed description includes specific details for providing an understanding of the described techniques. However, the techniques can be practiced without these specific details. In some instances, well-known structures and devices are shown in block diagram form to avoid obscuring the concepts of the described examples.

[0225] The present description is provided to enable a person of ordinary skill in the art to make or use the present disclosure. Various modifications to the present disclosure will be readily apparent to those of ordinary skill in the art, and the general principles defined herein can be applied to other variations without departing from the scope of the present disclosure. The present disclosure is not limited to the examples and designs described herein, but is to be accorded the widest scope consistent with the principles and novel features disclosed herein.

Claims

1. A method for wireless communication at a user equipment (UE), the method comprising: Receiving a carrier indication that identifies a first carrier and a second carrier for communication between the UE and a network entity; Using the first carrier to receive a first quasi - co - location indication that identifies a first set of quasi - co - location information, the first set of quasi - co - location information corresponding to a reference signal received using the first carrier; And Using the second carrier to receive a second quasi - co - location indication that identifies the reference signal and indicates that the first set of quasi - co - location information is associated with signaling received using the second carrier.

2. The method according to claim 1, the method further comprising: Using the first carrier to receive the reference signal; And Using the second carrier to receive the signaling based on the first set of quasi - co - location information and the reference signal.

3. The method according to claim 2, wherein the first set of quasi - co - location information identifies a set of quasi - co - location parameters that are common to the reference signal and the signaling.

4. The method according to claim 3, wherein the set of quasi - co - location parameters is further common to a second signaling received using the first carrier.

5. The method according to claim 1, the method further comprising: Using the second carrier to receive an indication that the first carrier is an anchor carrier, wherein the second quasi - co - location indication is associated with the first carrier being the anchor carrier.

6. The method according to claim 1, wherein the second quasi co-location indication identifies a second set of quasi co-location information, the second set of quasi co-location information corresponding to a second reference signal received using the second carrier, and the method further comprises: Using the second carrier to receive the signaling according to the first set of quasi - co - location information or a second set of quasi - co - location information.

7. The method according to claim 6, the method further comprising: Using the second carrier to receive an indication associated with a rule for selecting quasi - co - location information, wherein receiving the signaling according to the first set of quasi - co - location information or the second set of quasi - co - location information is associated with the rule.

8. The method according to claim 6, the method further comprising: Using the second carrier to receive a first indication that identifies a cell associated with the second carrier to be activated at the UE.

9. The method according to claim 8, the method further comprising: Using the second carrier to receive a second indication that identifies the reference signal or a second reference signal.

10. The method according to claim 1, wherein the first set of quasi - co - location information identifies a first quasi - co - location type associated with an in - band anchor carrier or a second quasi - co - location type associated with an inter - band anchor carrier.

11. The method according to claim 1, wherein the signaling comprises a tracking reference signal, a channel state information reference signal, a physical downlink control channel signal, or a physical downlink shared channel signal.

12. A method for wireless communication at a network entity, the method comprising: Outputting a carrier indication that identifies a first carrier and a second carrier for communication between a user equipment (UE) and the network entity; Using the first carrier to output a first quasi - co - location indication that identifies a first set of quasi - co - location information, the first set of quasi - co - location information corresponding to a reference signal output using the first carrier; And Use the second carrier to output a second quasi - co - location indication, where the second quasi - co - location indication identifies the reference signal and indicates that the first set of quasi - co - location information is associated with the signaling output using the second carrier.

13. The method according to claim 12, the method further comprising: Use the first carrier to output the reference signal; And According to the first set of quasi - co - location information and the reference signal, use the second carrier to output the signaling.

14. The method according to claim 13, wherein the first set of quasi - co - location information identifies a set of quasi - co - location parameters that are common to the reference signal and the signaling.

15. The method according to claim 14, wherein the set of quasi - co - location parameters is further common to a second signaling output using the first carrier.

16. The method according to claim 12, the method further comprising: Use the second carrier to output an indication that the first carrier is an anchor carrier, where the second quasi - co - location indication is associated with the first carrier being the anchor carrier.

17. The method according to claim 12, wherein the second quasi co-location indication identifies a second set of quasi co-location information, the second set of quasi co-location information corresponding to a second reference signal output using the second carrier, and the method further comprises: Output the signaling using the second carrier according to the first set of quasi - co - location information or the second set of quasi - co - location information.

18. The method according to claim 17, the method further comprising: Use the second carrier to output an indication associated with a rule for selecting quasi - co - location information, where outputting the signaling according to the first set of quasi - co - location information or the second set of quasi - co - location information is associated with the rule.

19. The method according to claim 17, the method further comprising: Use the second carrier to output a first indication that identifies a cell associated with the second carrier to be activated at the UE.

20. The method according to claim 19, wherein the method further comprises: Use the second carrier to output a second indication that identifies the reference signal or the second reference signal.

21. The method according to claim 12, wherein the first set of quasi - co - location information identifies a first quasi - co - location type associated with an in - band anchor carrier or a second quasi - co - location type associated with an inter - band anchor carrier.

22. The method according to claim 12, wherein the signaling includes a tracking reference signal, a channel state information reference signal, a physical downlink control channel signal, or a physical downlink shared channel signal.

23. An apparatus for wireless communication at a user equipment (UE), the apparatus comprising: A processor; And A memory coupled to the processor and storing instructions that can be executed by the processor to cause the apparatus to: Receive a carrier indication that identifies a first carrier and a second carrier for communication between the UE and a network entity; Use the first carrier to receive a first quasi - co - location indication that identifies a first set of quasi - co - location information, where the first set of quasi - co - location information corresponds to a reference signal received using the first carrier; And Use the second carrier to receive a second quasi - co - location indication that identifies the reference signal and indicates that the first set of quasi - co - location information is associated with the signaling received using the second carrier.

24. The apparatus according to claim 23, wherein the instructions can be further executed by the processor to cause the apparatus to: Use the first carrier to receive the reference signal; and Receive the signaling using the second carrier according to the first set of the quasi - co - location information and the reference signal.

25. The apparatus according to claim 23, wherein the instructions can be further executed by the processor to cause the apparatus to: receive an indication that the first carrier is an anchor carrier using the second carrier, wherein the second quasi - co - location indication is associated with the first carrier being the anchor carrier.

26. The apparatus according to claim 23, wherein the second quasi - co - location indication identifies a second set of quasi - co - location information, the second set of quasi - co - location information corresponding to a second reference signal received using the second carrier, and the instructions can be further executed by the processor to cause the apparatus to: receive the signaling using the second carrier according to the first set of quasi - co - location information or the second set of quasi - co - location information.

27. An apparatus for wireless communication at a network entity, the apparatus comprising: a processor; and a memory coupled to the processor and storing instructions that can be executed by the processor to cause the apparatus to: output a carrier indication that identifies a first carrier and a second carrier for communication between a user equipment (UE) and the network entity; output a first quasi - co - location indication using the first carrier, the first quasi - co - location indication identifying a first set of quasi - co - location information, the first set of quasi - co - location information corresponding to a reference signal output using the first carrier; and output a second quasi - co - location indication using the second carrier, the second quasi - co - location indication identifying the reference signal and indicating that the first set of quasi - co - location information is associated with the signaling output using the second carrier.

28. The apparatus according to claim 27, wherein the instructions can be further executed by the processor to cause the apparatus to: output the reference signal using the first carrier; and output the signaling using the second carrier according to the first set of quasi - co - location information and the reference signal.

29. The apparatus according to claim 27, wherein the instructions can be further executed by the processor to cause the apparatus to: output an indication that the first carrier is an anchor carrier using the second carrier, wherein the second quasi - co - location indication is associated with the first carrier being the anchor carrier.

30. The apparatus according to claim 27, wherein the second quasi - co - location indication identifies a second set of quasi - co - location information, the second set of quasi - co - location information corresponding to a second reference signal output using the second carrier, and the instructions can be further executed by the processor to cause the apparatus to: output the signaling using the second carrier according to the first set of quasi - co - location information or the second set of quasi - co - location information.

Images