Mapping of reference signals to transmission configuration indicator for beam management and reporting

Abstract

Methods, systems, and devices are described for wireless communication. A device can map a reference signal identifier to at least one transmission configuration indicator (TCI) state in a set of one or more TCI states associated with a TCI codepoint according to a rule. The TCI codepoint can include one or more of a downlink TCI state, an uplink TCI state, or a joint TCI state. The device can select the at least one TCI state for the reference signal by switching to or activating the at least one TCI state.

Description

Technical Field

[0001] The following relates to wireless communication, including mapping reference signals to transmit configuration indicators (TCIs) for beam management and reporting. Background Technology

[0002] Wireless communication systems are widely deployed to provide various types of communication content, such as voice, video, packet data, message sending and receiving, and broadcasting. These systems can support communication with multiple users by sharing available system resources (e.g., time, frequency, and power). Examples of such multiple access systems include fourth-generation (4G) systems (such as Long Term Evolution (LTE) systems, LTE-A 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 technologies such as Code Division Multiple Access (CDMA), Time Division Multiple Access (TDMA), Frequency Division Multiple Access (FDMA), Orthogonal FDMA (OFDMA), or Discrete Fourier Transform Extended Orthogonal Frequency Division Multiplexing (DFT-S-OFDM). A wireless multiple access communication system may include one or more base stations, each supporting wireless communication for communication devices, which may be referred to as User Equipment (UE). Summary of the Invention

[0003] The described technology relates to improved methods, systems, devices, and apparatuses that support mapping reference signals to transmit configuration indicators (TCIs) for beam management and reporting.

[0004] A method for wireless communication by a user equipment (UE) is described. The method may include: sending a report to a network entity, the report including a reference signal identifier identifying a reference signal; mapping the reference signal identifier to at least one TCI state from a set of one or more TCI states associated with a TCI code point, wherein the TCI code point includes one or more of a downlink TCI state, an uplink TCI state, or a combined TCI state; and selecting the at least one TCI state for the reference signal by switching to or activating the at least one TCI state.

[0005] A UE for wireless communication is described. The UE may include: one or more memories storing processor-executable code; and one or more processors coupled to the one or more memories. The one or more processors are capable of operating individually or jointly to execute the code to cause the UE to: send a report to a network entity, the report including a reference signal identifier identifying a reference signal; map the reference signal identifier to at least one TCI state from a set of one or more TCI states associated with a TCI code point, wherein the TCI code point includes one or more of a downlink TCI state, an uplink TCI state, or a combined TCI state; and select the at least one TCI state for the reference signal by switching to or activating the at least one TCI state.

[0006] Another UE for wireless communication is described. This UE may include: components for sending a report to a network entity, the report including a reference signal identifier identifying a reference signal; components for mapping the reference signal identifier to at least one TCI state from a set of one or more TCI states associated with a TCI code point, wherein the TCI code point includes one or more of a downlink TCI state, an uplink TCI state, or a combined TCI state; and components for selecting the at least one TCI state for the reference signal by switching to or activating the at least one TCI state.

[0007] A non-transitory computer-readable medium storing code for wireless communication is described. The code may include instructions executable by one or more processors to: send a report to a network entity, the report including a reference signal identifier identifying a reference signal; map the reference signal identifier to at least one TCI state from a set of one or more TCI states associated with a TCI code point, wherein the TCI code point includes one or more of a downlink TCI state, an uplink TCI state, or a combined TCI state; and select the at least one TCI state for the reference signal by switching to or activating the at least one TCI state.

[0008] In some examples of the methods, UEs, and nontransitory computer-readable media described herein, the rule defines the association between the at least one TCI state for the reference signal and the joint TCI state or the downlink TCI state associated with the unified TCI state.

[0009] In some examples of the methods, UEs, and nontransitory computer-readable media described herein, the rule defines the association between the at least one TCI state for the reference signal and one or more of the joint TCI state, the downlink TCI state, or the uplink TCI state, which is associated with a unified TCI state.

[0010] In some examples of the methods, UEs, and nontransitory computer-readable media described herein, the report includes an indication that the reference signal can be associated with the uplink TCI state or the downlink TCI state.

[0011] In some examples of the methods, UEs, and nontransitory computer-readable media described herein, the report includes a set of one or more reference signal identifiers, each of which identifies a corresponding reference signal in the set of one or more reference signals, and the rule defines the association between each corresponding reference signal and the downlink TCI state or the uplink TCI state.

[0012] In some examples of the methods, UEs, and nontransitory computer-readable media described herein, each TCI code point in a set of one or more TCI code points includes a single TCI state.

[0013] In some examples of the methods, UEs, and nontransitory computer-readable media described herein, the rule defines the association between each TCI code point in the group of one or more TCI code points and one or more of the downlink TCI state or the uplink TCI state.

[0014] In some examples of the methods, UEs, and nontransitory computer-readable media described herein, each TCI code point in a group of one or more TCI code points includes a TCI state group, and the TCI state group includes one or more of the downlink TCI state or the uplink TCI state.

[0015] In some examples of the methods, UEs, and nontransitory computer-readable media described herein, the report includes a set of multiple reference signal identifier groups that identify a set of multiple reference signal groups, and the rule defines the association between each reference signal in each of the multiple reference signal groups and the corresponding TCI code point in one or more TCI code points in the set.

[0016] In some examples of the methods, UEs, and nontransitory computer-readable media described herein, the report includes a group of reference signal identifiers that identifies a group of reference signals, the rule defining the association between the group of reference signal identifiers and a corresponding TCI code point in one or more TCI code points of the group, and at least one reference signal identifier in the group of reference signal identifiers includes a dummy reference signal identifier that is at least partially based on the corresponding TCI code point that includes the downlink TCI state or the uplink TCI state.

[0017] In some examples of the methods, UEs, and nontransitory computer-readable media described herein, the report includes an indication of whether the reference signal can be associated with switching to the at least one TCI state.

[0018] In some examples of the methods, UEs, and nontransitory computer-readable media described herein, the report includes a second reference signal identifier that identifies a second reference signal, and the methods, apparatus, and nontransitory computer-readable media may also include operations, features, components, or instructions for performing the following actions: mapping the second reference signal identifier to at least one second TCI state from one or more TCI states associated with the TCI code point according to the rule, wherein the at least one TCI state for the reference signal corresponds to the downlink TCI state or the uplink TCI state, or wherein the at least one TCI state for the reference signal corresponds to the downlink TCI state and the at least one second TCI state for the second reference signal corresponds to the uplink TCI state.

[0019] In some examples of the methods, UEs, and nontransitory computer-readable media described herein, the at least one TCI state includes quasi-co-location (QCL) information, which includes a first QCL type or a second QCL type. The first QCL type may be associated with one or more of Doppler frequency shift, Doppler spread, average delay, or average spread, and the second QCL type may be associated with a spatial filter that is associated with at least one beam for wireless communication.

[0020] In some examples of the methods, UEs, and nontransitory computer-readable media described herein, the reference signal may be associated with the second QCL type, and the at least one TCI state may be based on the reference signal associated with the second QCL type.

[0021] The methods described herein, some examples of UEs and nontransitory computer-readable media may also include operations, features, components or instructions for performing the following actions: selecting at least one TCI state from one or more TCI states in the group of one or more TCI states according to the rule and based on a corresponding TCI state identifier associated with each TCI state in the group of one or more TCI states, wherein at least two TCI states in the group of one or more TCI states may be associated with the second QCL type.

[0022] The methods described herein, UEs, and some examples of non-transitory computer-readable media may also include operations, features, components, or instructions for performing the following actions: applying the reference signal as a QCL-type reference signal regardless of the at least one TCI state.

[0023] In the methods described herein, in some examples of UEs and non-transitory computer-readable media, the synchronization signal block (SSB) may be associated with the QCL type reference signal QCL.

[0024] In some examples of the methods described herein, UEs, and non-transitory computer-readable media, at least one Channel State Information Reference Signal (CSI-RS) may be associated with the QCL reference signal. Attached Figure Description

[0025] Figure 1 and Figure 2 An example is shown of a wireless communication system that maps a reference signal to a transmit configuration indicator (TCI) for beam management and reporting, in accordance with one or more aspects of this disclosure.

[0026] Figure 3 An example of a process flow for mapping a reference signal to a TCI for beam management and reporting, supported by one or more aspects of this disclosure, is shown.

[0027] Figure 4 and Figure 5 A block diagram of an apparatus for mapping a reference signal to a TCI for beam management and reporting, supported by one or more aspects of this disclosure, is shown.

[0028] Figure 6 A block diagram is shown of a communication manager that maps a reference signal to a TCI for beam management and reporting, in accordance with one or more aspects of this disclosure.

[0029] Figure 7 A diagram is shown of a system including a device that supports mapping a reference signal to a TCI for beam management and reporting, according to one or more aspects of this disclosure.

[0030] Figure 8 and Figure 9A block diagram of an apparatus for mapping a reference signal to a TCI for beam management and reporting, supported by one or more aspects of this disclosure, is shown.

[0031] Figure 10 A block diagram is shown of a communication manager that maps a reference signal to a TCI for beam management and reporting, in accordance with one or more aspects of this disclosure.

[0032] Figure 11 A diagram is shown of a system including a device that supports mapping a reference signal to a TCI for beam management and reporting, according to one or more aspects of this disclosure.

[0033] Figure 12 and Figure 13 A flowchart illustrating a method for mapping a reference signal to a TCI for beam management and reporting, supported by one or more aspects of this disclosure, is shown. Detailed Implementation

[0034] In a wireless communication system, one or more of the network entities, base stations, or user equipment (UE) may support beam management in response to beam events. For example, a UE may perform beam measurements on beams in a set of beams used for wireless communication with one or more of the network entities or base stations. Based on the beam measurements, the UE may determine whether the quality of the beams in that set of beams meets (e.g., reaches or falls below) a threshold. For example, one or more of the network entities or base stations may transmit Channel State Information Reference Signals (CSI-RS) on beams in that set of beams, and the UE may receive CSI-RS on one or more beams in that set of beams. In some examples, the UE may determine that the signal strength (e.g., Reference Signal Received Power (RSRP)) of the beams in that set meets an RSRP threshold (e.g., falls below an RSRP threshold). In some other examples, the UE may determine that the signal strength (e.g., Reference Signal Strength Indicator (RSSI)) of the beams in that set meets an RSSI threshold (e.g., falls below an RSSI threshold). In response to (e.g., based at least in part on) determining that the quality of beams in the group of beams meets a threshold, the UE may send a beam report (e.g., a channel state information (CSI) report) to one or more of the network entities or base stations. The beam report may include information associated with beam measurements.

[0035] Based on beam reports, one or more network entities or base stations may switch the Transmit Configuration Indicator (TCI) state associated with wireless communication, or the UE may switch the TCI state associated with wireless communication. Therefore, based on beam reports, one or more network entities or base stations may switch one or more beams in the set of beams used for wireless communication with the UE, or the UE may switch one or more beams in the set of beams used for wireless communication with one or more network entities or base stations. In some cases, one or more network entities or base stations may send a Medium Access Control (MAC-CE) element that can activate or deactivate one or more TCI states, which may be associated with one or more beams in the set of beams of one or more network entities, base stations, or UEs, or combinations thereof. Although MAC-CE provides a signaling mechanism for one or more network entities or base stations to indicate the activation or deactivation of TCI to the UE, including switching one or more TCI states (e.g., beam), the UE may experience increased latency and reduced reliability of wireless communication due to the latency associated with MAC-CE signaling.

[0036] Various aspects of this disclosure relate to supporting beam management without MAC-CE signaling. By eliminating beam management using MAC-CE (e.g., activating or deactivating, including switching one or more TCI states), one or more of the network entities, base stations, or UEs can experience reduced signaling overhead, lower latency, and improved reliability in wireless communication. One or more of the network entities, base stations, or UEs can support beam management (e.g., activating or deactivating, including switching one or more TCI states) without MAC-CE signaling by supporting rule-based mapping of reference signals to TCIs. For example, one or more of the network entities or base stations can receive a report (e.g., a CSI report) including a reference signal identifier (e.g., CSI-RS, etc.) that identifies the reference signal, and the UE can send this report. One or more of the network entities, base stations, or UEs can map the reference signal identifier to a TCI state in a set of one or more TCI states associated with a TCI code point, according to rules. The TCI code point may include a downlink TCI state, an uplink TCI state, or a joint TCI state, as referenced herein. Figure 2 and Figure 3 As described. One or more of the network entities, base stations, or UEs may select a TCI state for a reference signal (e.g., CSI-RS) and switch to or activate the selected TCI state for wireless communication.

[0037] The aspects of this disclosure are first described in the context of a wireless communication system. The aspects of this disclosure are further illustrated and described with reference to apparatus diagrams, system diagrams, and flowcharts relating to mapping reference signals to a TCI for beam management and reporting.

[0038] Figure 1 An example of a wireless communication system 100 is illustrated, which maps a reference signal to a TCI for beam management and reporting in accordance with one or more aspects of this disclosure. The wireless communication system 100 may include one or more devices, such as one or more network devices (e.g., network entity 105), one or more UEs 115, and a core network 130. In some examples, the wireless communication system 100 may be a Long Term Evolution (LTE) network, an Advanced LTE (LTE-A) network, an LTE-A Pro network, a New Radio (NR) network, or a network operating under other systems and radio technologies, including future systems and radio technologies not explicitly mentioned herein.

[0039] Network entity 105 may be distributed across a geographical area to form wireless communication system 100, and may include devices employing different forms or having different capabilities. In various examples, network entity 105 may be referred to as a network element, mobility element, radio access network (RAN) node, or network equipment, etc. In some examples, network entity 105 and UE 115 may wirelessly communicate via communication link 125 (e.g., a radio frequency (RF) access link). For example, network entity 105 may support coverage area 110 (e.g., a geographical coverage area) within which UE 115 and network entity 105 may establish communication link 125. Coverage area 110 may be an example of a geographical area within which network entity 105 and UE 115 may support the transmission of signals according to one or more radio access technologies (RATs).

[0040] UE 115 can be distributed throughout the coverage area 110 of wireless communication system 100, and each UE 115 can be stationary or mobile, or stationary and mobile at different times. UE 115 can be devices in different forms or with different capabilities. Figure 1 Examples of UE 115 are illustrated herein. The UE 115 described herein may be able to support communication with various types of devices in the wireless communication system 100 (e.g., other wireless communication devices, including UE 115 or network entity 105), such as... Figure 1 As shown.

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

[0042] In some examples, network entity 105 may communicate with core network 130, communicate with each other, or both. For example, network entity 105 may communicate with core network 130 via backhaul communication link 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 midhaul interface protocol) or fronthaul communication link 168 (e.g., according to fronthaul interface protocol) or any combination thereof. The backhaul communication link 120, midhaul communication link 162, or fronthaul communication link 168 may be one or more wired links (e.g., electrical links, fiber optic links) or one or more wireless links (e.g., radio links, wireless optical links), etc., or various combinations thereof, or may include one or more wired links (e.g., electrical links, fiber optic links) or one or more wireless links (e.g., radio links, wireless optical links), etc., or various combinations thereof. UE 115 may communicate with the core network 130 via communication link 155.

[0043] One or more network entities or network equipment in network entity 105 described herein may include or 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, standalone) base station architecture that may be configured to utilize a protocol stack that is physically or logically integrated within a single network entity (e.g., network entity 105 or a single RAN node, such as base station 140).

[0044] In some examples, network entity 105 may be implemented in a decomposed architecture (e.g., a decomposed base station architecture, a decomposed RAN architecture) that can be configured to utilize protocol stacks physically or logically distributed across multiple network entities (e.g., network entity 105) such as an Integrated Access and 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) such as CU 160, a Distributed Unit (DU) such as DU 165, a Radio Unit (RU) such as RU 170, a RAN Intelligent Controller (RIC) such as RIC 175 (e.g., a near real-time RIC (near RTRIC), a non-real-time RIC (non-RT RIC)), a Service Management and Orchestration (SMO) system such as SMO system 180, or any combination thereof. RU 170 may also be referred to as a radio headend, intelligent radio headend, remote radio headend (RRH), remote radio unit (RRU), or transmit / receive point (TRP). One or more components of network entity 105 in a decomposed RAN architecture may be co-located, or one or more components of network entity 105 may be located in distributed locations (e.g., separate physical locations). In some examples, one or more network entities in network entity 105 of a decomposed RAN architecture may be implemented as virtual units (e.g., virtual CU (VCU), virtual DU (VDU), virtual RU (VRU)).

[0045] The functional splitting among CU 160, DU 165, and RU 170 is flexible and can support different functionalities depending on which functions (e.g., network layer functions, protocol layer functions, baseband functions, RF functions, or any combination thereof) are performed at CU 160, DU 165, or RU 170. For example, a protocol stack functional splitting can be used between CU 160 and DU 165, allowing CU 160 to support one or more layers of the protocol stack, and DU 165 to support one or more different layers of the protocol stack. In some examples, CU 160 can host higher protocol layer (e.g., Layer 3 (L3), Layer 2 (L2)) functionalities and signaling (e.g., Radio Resource Control (RRC), Serving Data Adaptation Protocol (SDAP), Packet Data Convergence Protocol (PDCP)). CU 160 (e.g., one or more CUs) can connect to DU 165 (e.g., one or more DUs) or RU 170 (e.g., one or more RUs) or some combination thereof, and DU 165, RU 170, or both 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) functionality and signaling, and can each be at least partially controlled by CU 160. Additionally or alternatively, a functional split of the protocol stack can be employed between DU 165 and RU 170, such that DU 165 can support one or more layers of the protocol stack, and RU 170 can support one or more different layers of the protocol stack. DU 165 can (e.g., via one or more different RUs, such as RU 170) support one or more different cells. In some cases, functional decomposition between CU 160 and DU 165, or between DU 165 and RU 170, can be performed within the protocol layer (e.g., some functions of the protocol layer can be performed by one of CU 160, DU 165, or RU 170, while other functions of the protocol layer can be performed by a different one of CU 160, DU 165, or RU 170). CU 160 can be further functionally decomposed into CU control plane (CU-CP) functions and CU user plane (CU-UP) functions. CU 160 can be connected to DU 165 via midhaul communication link 162 (e.g., F1, F1-c, F1-u), and DU 165 can be connected to RU 170 via fronthaul communication link 168 (e.g., open fronthaul (FH) interface). In some examples, the midhaul communication link 162 or the fronthaul communication link 168 may be implemented based on the interfaces (e.g., channels) between the layers of the protocol stack, which are supported by corresponding network entities (e.g., one or more network entities in network entity 105) that communicate via such communication links.

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

[0047] When the techniques described herein are applied in the context of a decomposed RAN architecture, one or more components of the decomposed RAN architecture may be configured to support the tests described herein. For example, some operations described as being performed by UE 115 or network entity 105 (e.g., base station 140) may additionally or alternatively be performed by one or more components of the decomposed RAN architecture (e.g., components such as IAB node, DU 165, CU 160, RU 170, RIC 175, SMO system 180).

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

[0049] The UE 115 described herein may be able to communicate with various types of devices, such as the UE 115 which may sometimes operate as a relay, and network entity 105 and network equipment including macro eNBs or gNBs, small cell eNBs or gNBs, or relay base stations, etc. Figure 1 As shown.

[0050] UE 115 and network entity 105 can wirelessly communicate with each other via communication link 125 (e.g., one or more access links) using resources associated with one or more carriers. The term "carrier" can refer to a set of RF spectrum resources having a defined PHY layer structure for supporting communication link 125. For example, a carrier for communication link 125 may include a portion of the RF spectrum band (e.g., a bandwidth portion (BWP)) operating according to one or more PHY layer channels for a given RAT (e.g., LTE, LTE-A, LTE-A Pro, NR). Each PHY layer channel may carry acquisition signaling (e.g., synchronization signals, system information), control signaling coordinating operation for the carrier, user data, or other signaling. Wireless communication system 100 can support communication with UE 115 using carrier aggregation or multi-carrier operation. Depending on the carrier aggregation configuration, UE 115 may be configured with multiple downlink component carriers and one or more uplink component carriers. Carrier aggregation can be used in conjunction with both frequency division duplex (FDD) component carriers and time division duplex (TDD) component carriers. Communication between network entity 105 and other devices can refer to communication between these devices and any part of network entity 105 (e.g., entity, sub-entity). For example, the terms “send,” “receive,” or “communicate” when referring to network entity 105 can refer to any part of the RAN’s network entity 105 (e.g., base station 140, CU 160, DU 165, RU 170) communicating with another device (e.g., directly or via one or more other network entities, such as one or more network entities in network entity 105).

[0051] In some examples, such as in carrier aggregation configurations, a carrier may 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 grating used for discovery by UE 115. A carrier may operate in standalone mode, in which case initial acquisition and connection can be performed by UE 115 via that carrier, or the carrier may operate in non-standalone mode, in which case different carriers (e.g., of the same or different RATs) are used to anchor the connection.

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

[0053] 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 carrier or the “system bandwidth” of the wireless communication system 100. For example, the carrier bandwidth may be one bandwidth in a set of bandwidths for a specific RAT (e.g., 1.4 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., network entity 105, UE 115, or both) may have hardware configurations that support communication using a specific carrier bandwidth, or may be configured to support communication using one carrier bandwidth in a set of carrier bandwidths. In some examples, the wireless communication system 100 may include 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., subband, BWP) or all of the carrier bandwidth.

[0054] The signal waveform transmitted via a carrier may include multiple subcarriers (e.g., using multi-carrier modulation (MCM) techniques, such as orthogonal frequency division multiplexing (OFDM) or discrete Fourier transform extended OFDM (DFT-S-OFDM)). In a system employing MCM, a resource element may refer to a resource of one symbol period (e.g., the duration of one modulation symbol) and one subcarrier, where the symbol period and subcarrier spacing may be inversely related. The number of bits carried by each resource element may 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 high number of resource elements (e.g., in the transmission duration) and a relatively high modulation scheme order correspond to a relatively high communication rate. Wireless communication resources may refer to a combination of RF spectrum resources, temporal resources, and spatial resources (e.g., spatial layers or beams), and the use of multiple spatial resources may increase the data rate or data integrity used for communication with UE 115.

[0055] It can support one or more parameter sets for a carrier, and the parameter sets may include subcarrier spacing ( (and cyclic prefix). A carrier can be divided into one or more BWPs with the same or different sets of parameters. In some examples, UE 115 can be configured to utilize multiple BWPs. In some examples, a single BWP of a carrier can be active at a given time, and the communication of UE 115 can be constrained to one or more active BWPs.

[0056] The time interval for network entity 105 or UE 115 can be expressed as a multiple of a basic time unit, such as the sampling period. seconds, in response This can represent the supported subcarrier spacing, while The supported Discrete Fourier Transform (DFT) size can be represented. Time intervals for communication resources can be organized according to radio frames, each with a specified 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).

[0057] Each frame may include multiple consecutively numbered subframes or time slots, and each subframe or time slot may have the same duration. In some examples, a frame may (e.g., in the time domain) be divided into subframes, and each subframe may also be divided into a certain number of time slots. Alternatively, each frame may include a variable number of time slots, and the number of time slots may depend on the subcarrier spacing. Each time slot may include a certain number of symbol periods (e.g., depending on the length of the cyclic prefix appended to each symbol period). In some wireless communication systems, such as wireless communication system 100, time slots may be further divided into multiple micro-time slots associated with one or more symbols. Excluding the cyclic prefix, each symbol period may be associated with one or more (e.g., The duration of a symbol period is associated with a (number) sampling period. The duration of a symbol period can depend on the subcarrier spacing or the operating frequency band.

[0058] A subframe, time slot, micro-time slot, or symbol can be the smallest scheduling unit of the wireless communication system 100 (e.g., in the time domain) and can be referred to as a transmission time interval (TTI). In some examples, the duration of the TTI (e.g., the number of symbol periods in the TTI) can be variable. Additionally or alternatively, the smallest scheduling unit of the wireless communication system 100 can be dynamically selected (e.g., in a burst of shortened TTIs (sTTIs)).

[0059] Depending on the technology, carriers can be used to multiplex physical channels for communication. One or more of Time Division Multiplexing (TDM), Frequency Division Multiplexing (FDM), or hybrid TDM-FDM techniques can be used, for example, to multiplex physical control channels and physical data channels for signaling via a downlink carrier. The control region (e.g., control resource set (CORESET)) of the physical control channel can be defined by a set of symbol periods and can extend across the system bandwidth of the carrier or a subset of that bandwidth. One or more control regions (e.g., CORESET) can be configured for a set of UEs 115. For example, one or more UEs in UE 115 can monitor or search for control regions to obtain control information based on one or more search space sets, and each search space set can include one or more control channel candidates in one or more aggregation levels arranged in a concatenated manner. The aggregation level of control channel candidates can refer to the amount of control channel resources (e.g., control channel elements (CCEs)) associated with coded information for a control information format having a given payload size. The search space set may include a common search space set configured to transmit control information to UE 115 (e.g., one or more UEs) or a UE-specific search space set configured to transmit control information to UE 115 (e.g., a particular UE).

[0060] 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 used (e.g., using a carrier) to communicate with network entity 105 and may be associated with an identifier used to distinguish adjacent cells (e.g., Physical Cell Identifier (PCID), Virtual Cell Identifier (VCID)). In some examples, a cell may also refer to a coverage area 110 or a portion of coverage area 110 (e.g., a sector) in which a logical communication entity operates. Depending on various factors such as the capabilities of network entity 105, the range of such cells may be from smaller areas (e.g., structures, subsets of structures) to larger areas. For example, a cell may be a building, a subset of buildings, or external space between or overlapping coverage areas 110, etc., or may include buildings, subsets of buildings, or external space between or overlapping coverage areas, etc.

[0061] Macro cells typically cover a relatively large geographic area (e.g., a radius of several kilometers) and allow unrestricted access to UE 115 that has a service subscription with a network provider supporting the macro cell. In contrast to macro cells, small cells may be associated with network entities 105 operating at lower power (e.g., base station 140 operating at lower power) and may operate using the same or different (e.g., licensed, unlicensed) frequency bands as macro cells. Small cells may provide unrestricted access to UE 115 that has a service subscription with a network provider, or restricted access to UE 115 associated with a small cell (e.g., UE 115 in a Closed Subscriber Group (CSG), UE 115 associated with a user in a home or office). Network entity 105 may support one or more cells and may also use one or more component carriers to support communication via one or more cells.

[0062] In some examples, a carrier can support multiple cells and can be configured with different cells based on different protocol types that can provide access for different types of devices (e.g., MTC, Narrowband IoT (NB-IoT), Enhanced Mobile Broadband (eMBB)).

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

[0064] The wireless communication system 100 can support synchronous or asynchronous operation. For synchronous operation, network entities 105 (e.g., base station 140) can have similar frame timings, and transmissions from different network entities (e.g., different network entities within network entity 105) can be approximately time-aligned. For asynchronous operation, network entities 105 can have different frame timings, and in some examples, transmissions from different network entities (e.g., different network entities within network entity 105) may not be time-aligned. The techniques described herein can be used for both synchronous and asynchronous operation.

[0065] Some UE 115 devices (such as MTC or IoT devices) can be relatively low-cost or low-complexity devices and can provide automated communication between machines (e.g., via machine-to-machine (M2M) communication). M2M communication or MTC can refer to data communication technologies that allow devices to communicate with each other or with network entity 105 (e.g., base station 140) without human intervention. In some examples, M2M communication or MTC may include communication from devices with integrated sensors or instruments to measure or acquire information and relay such information to a central server or application that uses the information or presents it to people interacting with the application. Some UE 115 devices may be designed to collect information or enable automated behavior of machines or other devices. Examples of applications for MTC devices include smart metering, inventory monitoring, water level monitoring, equipment monitoring, healthcare monitoring, wildlife monitoring, weather and geological event monitoring, fleet management and tracking, remote security sensing, physical access control, and transaction-based service charging.

[0066] Some UE 115s can be configured to operate in a power-saving mode, such as half-duplex communication (e.g., a mode that supports unidirectional communication via transmission or reception but does not involve concurrent transmission and reception). In some examples, half-duplex communication can be performed at a reduced peak rate. Other power-saving techniques for UE 115s include entering a power-saving deep sleep mode when not engaged in active communication, operating with limited bandwidth (e.g., according to narrowband communication), or a combination of these techniques. For example, some UE 115s can be configured to operate using a narrowband protocol type associated with a defined portion or range (e.g., a set of subcarriers or resource blocks (RBs)) within a carrier, within a carrier's guard band, or outside a carrier.

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

[0068] In some examples, UE 115 may be configured to support direct communication with other UEs (e.g., one or more UEs in UE 115) via a device-to-device (D2D) communication link (such as 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 in a group performing D2D communication may be within the coverage area 110 of network entity 105 (e.g., base station 140, RU 170), which may support aspects of such D2D communication configured (e.g., scheduled by network entity 105). In some examples, one or more UEs 115 in such a group may be outside the coverage area 110 of network entity 105, or may otherwise be unable or not configured to receive transmissions from network entity 105. In some examples, a group of UEs 115 communicating via D2D communication can support a one-to-many (1:M) system, in which each UE 115 transmits to one or more UEs within the group. In some examples, network entity 105 can facilitate the scheduling of resources used for D2D communication. In some other examples, D2D communication can be performed between UEs 115 without involving network entity 105.

[0069] In some systems, the D2D communication link 135 may be an example of a communication channel (such as a sidelink communication channel) between vehicles (e.g., UE 115). In some examples, vehicles may communicate using vehicle-to-vehicle (V2X) communication, vehicle-to-vehicle (V2V) communication, or some combination of these. Vehicles may signal information related to traffic conditions, signaling, weather, safety, emergencies, or any other information relevant to the V2X system. In some examples, vehicles in a V2X system may communicate with roadside infrastructure (such as roadside units), or communicate with the network via one or more network nodes (e.g., network entity 105, base station 140, RU 170) using vehicle-to-network (V2N) communication, or both.

[0070] Core network 130 provides user authentication, access authorization, tracking, Internet Protocol (IP) connectivity, and other access, routing, or mobility functions. Core network 130 can be an evolved packet core (EPC) or a 5G core (5GC), which may include at least one control plane entity (e.g., a Mobility Management Entity (MME), Access and Mobility Management Function (AMF)) for managing access and mobility, and at least one user plane entity (e.g., a Serving Gateway (S-GW), Packet Data Network (PDN) Gateway (P-GW), or User Plane Function (UPF)) for routing packets or interconnecting to external networks. The control plane entity manages non-access stratum (NAS) functions, such as mobility, authentication, and bearer management of UE 115 served by network entity 105 (e.g., base station 140) associated with core network 130. User IP packets can be delivered through the user plane entity, which provides IP address allocation and other functions. The user plane entity may connect to one or more network operator IP services 150. IP services 150 may include access to the Internet, intranets, IP Multimedia Subsystem (IMS), or packet-switched streaming services.

[0071] Wireless communication system 100 can operate using one or more frequency bands in the range of 300 MHz to 300 GHz. Generally, the area from 300 MHz to 3 GHz is referred to as the Ultra High Frequency (UHF) band or decimeter band because the wavelength range is approximately one decimeter to one meter in length. UHF waves may be blocked or redirected by buildings and environmental features (which may be referred to as clusters), but these waves are sufficient to penetrate structures so that macrocells can provide service to UE 115 located indoors. Compared to communication using smaller frequencies and longer wavelengths 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 ranges (e.g., less than 100 km).

[0072] The wireless communication system 100 can also operate using the ultra-high frequency (SHF) region (also known as the centimeter band) in the range of 3 GHz to 30 GHz or the extremely high frequency (EHF) region (e.g., 30 GHz to 300 GHz) (also known as the millimeter band). In some examples, the wireless communication system 100 can support millimeter-wave (mmW) communication between the UE 115 and network entity 105 (e.g., base station 140, RU 170), and the EHF antennas of the corresponding devices can be smaller and more closely spaced than UHF antennas. In some examples, such techniques facilitate the use of antenna arrays within the device. However, compared to SHF or UHF transmissions, EHF transmissions may experience even greater attenuation and shorter range. The techniques disclosed herein can be adopted across transmissions using one or more different frequency regions, and the frequency band usage specified across these frequency regions may vary by country or regulatory authority.

[0073] Wireless communication system 100 may utilize both licensed and unlicensed RF spectrum bands. For example, wireless communication system 100 may employ licensed assisted access (LAA), LTE-Unlicensed (LTE-U) RAT, or NR technology using unlicensed frequency bands (such as the 5 GHz Industrial, Scientific, and Medical (ISM) band). When operating with unlicensed RF spectrum, devices such as network entity 105 and UE 115 may employ carrier sensing for collision detection and avoidance. In some examples, operation using unlicensed frequency bands may be based on carrier aggregation configurations combined with component carriers operating with licensed frequency bands (e.g., LAA). Operation using unlicensed spectrum may include downlink transmission, uplink transmission, P2P transmission, or D2D transmission, etc.

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

[0075] Network entity 105 or UE 115 may use MIMO communication to leverage multipath signal propagation and improve spectral efficiency by transmitting or receiving multiple signals via different spatial layers. This technique may be referred to as spatial multiplexing. The multiple signals may be transmitted, for example, by a transmitting device via different antennas or different combinations of antennas. Similarly, the multiple signals may be received by a receiving device via different antennas or different combinations of antennas. Each of the multiple signals may be referred to as a separate spatial stream and may carry information associated with the same data stream (e.g., the same codeword) or different data streams (e.g., different codewords). Different spatial layers may be associated with different antenna ports used for channel measurement and reporting. MIMO techniques include: single-user MIMO (SU-MIMO), for which multiple spatial layers are transmitted to the same receiving device; and multi-user MIMO (MU-MIMO), for which multiple spatial layers are transmitted to multiple devices.

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

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

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

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

[0080] A receiving device (e.g., UE 115) may perform reception operations according to multiple reception configurations (e.g., directional listening) when receiving various signals (such as synchronization signals, reference signals, beam selection signals, or other control signals) from a transmitting device (e.g., network entity 105). For example, the receiving device may perform reception according to multiple reception directions by: receiving via different antenna subarrays; processing the received signal according to different antenna subarrays; receiving according to different sets of reception beamforming weights (e.g., different directional listening weight sets) applied to signals received at multiple antenna elements of the antenna array; or processing the received signal according to different sets of reception beamforming weights applied to signals received at multiple antenna elements of the antenna array. Any of these operations may be referred to as “listening” according to different reception configurations or reception directions. In some examples, the receiving device may use a single reception configuration to receive along a single beam direction (e.g., when a data signal is received). A single receiver configuration can be aligned along a beam direction determined based on listening according to different receiver 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).

[0081] The wireless communication system 100 can be a packet-based network operating according to a layered protocol stack. In the user plane, communication at the bearer or PDCP layer can be IP-based. The RLC layer performs packet segmentation and reassembly for transmission via logical channels. The MAC layer performs priority processing and multiplexing of logical channels to transport channels. The MAC layer can also use error detection, error correction, or both to support retransmission to improve link efficiency. In the control plane, the RRC layer provides the establishment, configuration, and maintenance of RRC connections between the UE 115 and network entity 105 or core network 130 that support user plane data radio bearers. The PHY layer maps transport channels to physical channels.

[0082] UE 115 and network entity 105 can support data retransmission to increase the likelihood of successful data reception. Hybrid Automatic Repeat Request (HARQ) feedback is a technique used to increase the likelihood of correctly receiving data via communication links (e.g., communication link 125, D2D communication link 135). HARQ may include a combination of error detection (e.g., using Cyclic Redundancy Check (CRC)), forward error correction (FEC), and retransmission (e.g., Automatic Repeat Request (ARQ)). HARQ can improve throughput at the MAC layer under relatively poor radio conditions (e.g., low signal-to-noise ratio conditions). In some examples, the device may support same-slot HARQ feedback, in which case the device can provide HARQ feedback in a specific time slot for data received via a previous symbol in that time slot. In some other examples, the device may provide HARQ feedback in subsequent time slots or according to a different time interval.

[0083] In the wireless communication system 100, one or more of the network entity 105, base station 140, or UE 115 may support beam management, including activating or switching TCI states without MAC-CE signaling (e.g., a command in MAC-CE indicating TCI activation or TCI switching). For example, UE 115 may send a report to network entity 105 or base station 140 including a reference signal identifier (e.g., CSI index) that identifies a reference signal (e.g., CSI). UE 115 may map the reference signal identifier to at least one of a set of one or more TCI states associated with a TCI code point, according to rules. The TCI code point may include one or more of a downlink TCI state, an uplink TCI state, or a combined TCI state, as described herein.

[0084] Optionally, network entity 105 or base station 140 may also map the reported reference signal identifier to at least one TCI state from a set of one or more TCI states associated with a TCI code point, according to rules. The TCI code point may include one or more of a downlink TCI state, an uplink TCI state, or a combined TCI state, as described herein. UE 115 may select at least one TCI state for the reference signal by switching to or activating at least one TCI state. Optionally, network entity 105 or base station 140 may also select at least one TCI state for the reference signal by switching to or activating at least one TCI state.

[0085] One or more of network entity 105, base station 140, or UE 115 may perform beamforming communication, for example, based on switching to or activating at least one TCI state. Therefore, one or more of network entity 105, base station 140, or UE 115 may perform beam management (e.g., via TCI activation or TCI switching) without requiring MAC-CE signaling (e.g., a command in the MAC-CE indicating TCI activation or TCI switching) from network entity 105 or base station 140.

[0086] Figure 2 An example of a wireless communication system 200 is shown that maps a reference signal to a TCI for beam management and reporting, in accordance with one or more aspects of this disclosure. In some examples, the wireless communication system 200 may implement as referenced herein. Figure 1 The described aspects of the wireless communication system 100, or aspects that may be implemented by these aspects, are as follows. For example, the wireless communication system 200 may include network entity 105-a and UE 115-a, which may be as referenced herein. Figure 1 Examples of network entity 105 and UE 115 are described. Wireless communication system 200 supports 3G, 4G, 5G, or higher radio access technologies.

[0087] Network entity 105-a and UE 115-a can be configured using multiple antennas, which can be used to support beamforming functionality (e.g., beam switching, beam activation, beam deactivation, beam reporting, and beamforming wireless communication). For example, network entity 105-a may be equipped with an antenna array including multiple rows and columns of antenna ports, which network entity 105-a can use to support beamforming for wireless communication with UE 115-a. Additionally or alternatively, UE 115-a may be equipped with an antenna array including multiple rows and columns of antenna ports, which UE 115-a can use to support beamforming for wireless communication with network entity 105-a.

[0088] One or more of network entity 105-a or UE 115-a may use one or more beams 205 of network entity 105-a and one or more beams 210 of UE 115-a to support beamforming wireless communication over one or more frequency ranges. In some examples, one or more of network entity 105-a or UE 115-a may support beamforming wireless communication over a first frequency range (FR1) that spans one or more of a first set of frequencies (e.g., 410MHz to 7125MHz). In some other examples, one or more of network entity 105-a or UE 115-a may support beamforming wireless communication over a second frequency range (FR2) that spans one or more of a second set of frequencies (e.g., 24250MHz to 52600MHz). In some other examples, one or more of network entity 105-a or UE 115-a may support beamforming wireless communication over both FR1 and FR2.

[0089] exist Figure 2 In the example, one or more of network entity 105-a or UE 115-a may support beam management according to the TCI framework. For example, one or more of network entity 105-a or UE 115-a may indicate, through TCI status, at least one beam of one or more beams 205 of network entity 105-a or at least one beam of one or more beams 210 of UE 115-a for a channel (e.g., Physical Downlink Control Channel (PDCCH), Physical Downlink Shared Channel (PDSCH), Physical Uplink Control Channel (PUCCH), Physical Uplink Shared Channel (PUSCH), etc.) or a reference signal (e.g., Channel State Information (CSI) Reference Signal (CSI-RS), Sounding Reference Signal (SRS), etc.). The TCI status may include one or more of reference signal information or quasi-co-location (QCL) information.

[0090] Additionally or alternatively, one or more of network entity 105-a or UE 115-a may support a unified TCI framework. For example, one or more of network entity 105-a or UE 115-a may use a TCI state to indicate one or more beams of a set of one or more beams 205 of network entity 105-a or one or more beams of a set of one or more beams 210 of UE 115-a for multiple channels (e.g., PDCCH, PDSCH, PUCCH, PUSCH) or reference signals (e.g., CSI-RS). This TCI may be referred to as a unified TCI state (or common TCI state), which may apply to multiple channels or multiple signals, or a combination thereof. Therefore, a unified TCI state may apply to multiple channels / signals simultaneously.

[0091] Network entity 105-a may send a configuration including a set of one or more TCI states or a set of one or more TCI state pools, and UE 115-a may receive this configuration. This configuration may be an RRC configuration that indicates the set of one or more TCI states or the set of one or more TCI state pools. In some examples, a TCI state (or TCI state pool) may be specifically applicable to a downlink channel or an uplink channel. In other examples, a TCI state (also referred to as a joint TCI state) may be jointly applicable to multiple downlink channels and uplink channels. In some other examples, a joint TCI state may include a pair of TCI states, where the pair may include a first TCI state specifically applicable to a downlink channel and a second TCI state specifically applicable to an uplink channel.

[0092] TCI states can be associated with a set of one or more parameters that configure the QCL relationship between one or more reference signals associated with a channel (e.g., PDCCH, PDSCH, PUCCH, PUSCH) and the reference signal antenna connection port. The QCL relationship can be based on one or more QCL parameters that define a QCL type. In some examples, the QCL type can be a first QCL type (also referred to as QCL type A), which defines a set of channel characteristics including Doppler shift, Doppler spread, average delay (e.g., the average time of all multipath components of the received signal), and delay spread (e.g., the difference between the arrival time of the earliest multipath signal component and the arrival time of the last multipath component). In some other examples, the QCL type can be a second QCL type (also referred to as QCL type B), which defines a subgroup of the set of channel characteristics, including Doppler shift and Doppler spread. In other examples, the QCL type can be a third QCL type (also referred to as QCL type C), which defines a subgroup of the set of channel characteristics, including Doppler shift and average delay. In some other examples, the QCL type can be a fourth QCL type (also known as QCL type D), which defines the parameters of the spatial filter (e.g., spatial...). Rx parameter).

[0093] In the wireless communication system 200, one or more of network entity 105-a or UE 115-a may support beam management in response to beam events. For example, UE 115-a may perform one or more beam measurements on one or more beams in a set of one or more beams 210 used for wireless communication with network entity 105-a. Based on the one or more beam measurements, UE 115-a may determine whether the quality of one or more beams in the set of one or more beams 210 meets (e.g., reaches or falls below) a threshold. For example, network entity 105-a may transmit one or more CSI-RS on one or more beams in a set of one or more beams 205 of network entity 105-a, and UE 115-a may receive one or more CSI-RS on one or more beams in a set of one or more beams 210 of UE 115-a. In some examples, UE 115-a may determine that the signal strength (e.g., Reference Signal Received Power (RSRP)) of at least one beam in a group of one or more beams 210 meets an RSRP threshold (e.g., the RSRP of at least one beam is below the RSRP threshold). In some other examples, UE 115-a may determine that the signal strength (e.g., Reference Signal Strength Indicator (RSSI)) of at least one beam in a group of one or more beams 210 meets an RSSI threshold (e.g., the RSSI of at least one beam is below the RSSI threshold). In response to (e.g., at least in part based on) determining that the quality of one or more beams in a group of one or more beams 210 meets the threshold, UE 115-a may send a beam report (e.g., a CSI report) to network entity 105-a. The beam report may include information associated with one or more beam measurements.

[0094] Based at least in part on beam reports, network entity 105-a may switch the TCI state associated with wireless communication, or UE 115-a may switch the TCI state associated with wireless communication. Therefore, based at least in part on beam reports, network entity 105-a may switch one or more beams from a set of one or more beams 205 used for wireless communication with UE 115-a, or UE 115-a may switch one or more beams from a set of one or more beams 210 used for wireless communication with network entity 105-a. In some cases, network entity 105-a may send a Media Access Control (MAC-CE) element that can activate or deactivate one or more TCI states, which may be associated with one or more beams from a set of one or more beams 205 or a set of one or more beams 210, or a combination thereof. Although MAC-CE provides a signaling mechanism for network entity 105-a and UE 115-a to indicate activation or deactivation, including switching one or more TCI states (e.g., beam), network entity 105-a or UE 115-a may experience increased latency and reduced reliability of wireless communication between network entity 105-a and UE 115-a due to the duration associated with beam reports sent by UE 115-a and MAC-CE sent by network entity 105-a.

[0095] exist Figure 2 In the example, by eliminating beam management using MAC-CE (e.g., activation or deactivation, including switching one or more TCI states), network entity 105-a and UE 115-a can experience reduced signaling overhead, lower latency, and improved reliability in wireless communication between network entity 105-a and UE 115-a. Network entity 105-a and UE 115-a can support beam management (e.g., activation or deactivation, including switching one or more TCI states) without MAC-CE signaling by supporting rule-based mapping of reference signals to TCIs. For example, network entity 105-a may (e.g., from UE 115-a) receive a report 215 including a reference signal identifier 220 that identifies a reference signal (e.g., CSI-RS, etc.). One or more of network entity 105-a or UE 115-a may, according to rules, map the reference signal identifier 220 to a TCI state in a set of one or more TCI states associated with TCI code point 225. TCI code point 225 may include downlink TCI state 230, uplink TCI state 235, or joint TCI state 240, as described herein. One or more of network entity 105-a or UE 115-a may select a TCI state for a reference signal (e.g., CSI-RS) and switch to or activate the selected TCI state.

[0096] TCI handover may include, for example, switching from one TCI state to another during an ongoing wireless communication session between network entity 105-a and UE 115-a. TCI handover may be triggered by various factors, including conditions (e.g., signal strength, interference), quality of service (QoS) requirements, or changes in the mobility of UE 115-a. TCI activation may include activating (e.g., enabling) a TCI state during the initial connection establishment process between network entity 105-a and UE 115-a, or when a change in the TCI state is required based on network conditions.

[0097] This rule can define the association between the TCI state used for the reference signal and either the joint TCI state 240 or the downlink TCI state 230, with the downlink TCI state associated with the unified TCI state. Therefore, for example, when UE 115-a is configured by network entity 105-a using separate unified TCI states, the TCI state to be activated or switched for the reference signal could be either the joint TCI state 240 or the downlink TCI state 230. In this example, the TCI state to be activated or switched for the uplink could be indicated by network entity 105-a (e.g., via DCI or MAC-CE). Alternatively, this rule can define the association between the TCI state used for the reference signal and one or more of the joint TCI state 240, downlink TCI state 230, or uplink TCI state 235, with the downlink TCI state or uplink TCI state associated with the unified TCI state. Therefore, UE 115-a can indicate for each reference signal in report 215 (e.g., CSI report) whether the corresponding reference signal is for downlink TCI state 230 or uplink TCI state 235. For example, report 215 may include indications (e.g., information elements, fields, etc.) of the association between the corresponding reference signal and downlink TCI state 230 or uplink TCI state 235.

[0098] Additionally, when uplink TCI state 235 is applicable, UE 115-a may report multiple reference signal identifiers 220 in report 215 (e.g., CSI report), wherein each reference signal is mapped to either downlink TCI state 230 or uplink TCI state 235 according to a rule (e.g., a reference signal to TCI mapping rule). In some examples, each TCI code point 225 may include a single TCI state. In these examples, rules may define the association between each TCI code point 225 and one or more of the downlink TCI state 230 or uplink TCI state 235. That is, downlink TCI state 230 and uplink TCI state 235 may be mapped to different TCI code points 225. In some other examples, each TCI code point 225 may include a group of TCI states, wherein the group of TCI states includes one or more of the downlink TCI state 230 or uplink TCI state 235. That is, each TCI code point 225 may include one or two TCI states. For example, each TCI code point 225 may have one downlink TCI state 230, one uplink TCI state 235, or one downlink TCI state 230 and one uplink TCI state 235. In some examples, grouping a downlink TCI state 230 and an uplink TCI state 235 into a TCI code point 225 may be based on UE 115-a (e.g., signaling, indication).

[0099] UE 115-a may indicate to network entity 105-a multiple reference signal identifier groups 220 that identify multiple reference signal groups. For example, report 215 may include reference signal identifier groups that identify reference signal groups, and rules may define the association between reference signal identifier groups and corresponding TCI code points 225. For example, a first reference signal may be mapped to a downlink TCI state 230 of a corresponding TCI code point 225, and a second reference signal may be mapped to an uplink TCI state 235 of a corresponding TCI code point 225. In some examples, UE 115-a may indicate in report 215 dummy reference signals (e.g., signals that do not carry data) of reference signal groups, such as if a corresponding TCI code point 225 has a single downlink TCI state 230 or a single uplink TCI state 235. For example, UE 115-a may indicate a dummy reference signal identifier in report 215, which is at least in part based on a corresponding TCI code point 225 including a single downlink TCI state 230 or a single uplink TCI state 235.

[0100] In some examples, UE 115-a may indicate a reference signal used to activate or switch a TCI state. Therefore, report 215 may include an indication of whether the reference signal is associated with switching to at least one TCI state associated with the corresponding TCI code point 225. Additionally or alternatively, UE 115-a may indicate in report 215 (e.g., a CSI report) whether a single reference signal (e.g., a single reference signal identifier 220) or multiple reference signals (e.g., multiple reference signal identifiers 220) are used to activate or switch one or more TCI states.

[0101] In some examples, for a single reference signal, UE 115-a may switch only downlink TCI state 230 or uplink TCI state 235. Alternatively, for multiple reference signals, such as at least two reference signals, at least one TCI state of one of the at least two reference signals corresponds to downlink TCI state 230 and the other of the at least two reference signals corresponds to uplink TCI state 235. Therefore, a first reference signal can be used to switch downlink TCI state 230 and a second reference signal can be used to switch uplink TCI state 235.

[0102] In some cases, UE 115-a may include a reference signal identifier 220 (e.g., reference signal index) and a corresponding metric (e.g., signal strength) to network entity 105-a in report 215. In some cases, network entity 105-a may send signaling (e.g., MAC-CE) to UE 115-a, which may include QCL type A information. Because... Figure 2 In the example, there is no explicit indication (e.g., a MAC-CE indicating TCI activation and / or TCI switching), the rule defines the association between the reference signal identifier 220 (e.g., reference signal index) and the corresponding TCI state, as described above.

[0103] When UE 115-a reports a reference signal identifier 220 (e.g., a reference signal index) associated with a reference signal used by UE 115-a for TCI activation or TCI switching, UE 115-a may determine the appropriate TCI state to activate or switch to for one or more channels or reference signals, as described herein. In some examples, the TCI state may correspond to the state for receiving the reported reference signal identifier 220 (e.g., a reference signal index) associated with the reported reference signal. The TCI state may include QCL information that may identify a first QCL type (e.g., QCL type A) or a second QCL type (e.g., QCL type D). QCL type A may define one or more of Doppler shift, Doppler spread, average delay, or average spread, as described herein. QCL type D may define a spatial filter associated with at least one of a set of one or more beams 210 for wireless communication with network entity 105-a.

[0104] In some other examples, the TCI state may correspond to the state of the reported reference signal identifier 220 (e.g., reference signal index) associated with the reported reference signal configured as a QCL type D reference signal. If multiple such TCI states exist, UE 115-a may select the TCI state based on a rule (e.g., by the lowest TCI identifier). In other examples, the TCI state may correspond to a QCL type D reference signal that is QCL-D with the reported reference signal. If multiple such TCI states exist, UE 115-a may select the TCI state according to a rule (e.g., by the TCI identifier). UE 115-a may apply the reported reference signal identifier 220 (e.g., reference signal index) associated with the reported reference signal as the QCL type D reference signal. In some examples, the synchronization signal block (SSB) may be QCL-C with the QCL type C reference signal. Additionally or alternatively, the periodic CSI-RS may be QCL-C with the reported reference signal (e.g., TRS as a QCL type A reference signal).

[0105] Therefore, in the wireless communication system 200, UE 115-a can send report 215 to network entity 105-a and (e.g., via activating or switching TCI state) perform beam switching without receiving instructions (e.g., MAC-CE) from network entity 105-a.

[0106] Figure 3 An example of a process flow 300 for mapping a reference signal to a TCI for beam management and reporting, supported by one or more aspects of this disclosure, is shown. Process flow 300 enables reference... Figure 1The described wireless communication system 100 includes various aspects. Process flow 300 may include network entity 105-b and UE 115-b, which may be corresponding examples of network entity 105 and UE 115 as described herein. In the following description of process flow 300, operations between network entity 105-b and UE 115-b may be transmitted in a different order than the example order shown, or operations performed by network entity 105-b and UE 115-b may be performed in a different order or at different times. Some operations may also be omitted from process flow 300, and other operations may be added to process flow 300.

[0107] At 305, UE 115-b may send a report to network entity 105-b, which includes a reference signal identifier (e.g., CSI index) that identifies the reference signal (e.g., CSI).

[0108] At 310-a, UE 115-b may, according to rules, map a reference signal identifier to at least one TCI state from a set of one or more TCI states associated with a TCI code point. The TCI code point may include one or more of a downlink TCI state, an uplink TCI state, or a combined TCI state, as described herein. Optionally, at 310-b, network entity 105-b may also, according to rules, map a reported reference signal identifier to at least one TCI state from a set of one or more TCI states associated with a TCI code point. The TCI code point may include one or more of a downlink TCI state, an uplink TCI state, or a combined TCI state, as described herein.

[0109] At 315-a, UE 115-b can select at least one TCI state for the reference signal by switching to at least one TCI state or activating at least one TCI state. Optionally, at 315-b, network entity 105-b can also select at least one TCI state for the reference signal by switching to at least one TCI state or activating at least one TCI state.

[0110] At 320, one or more of network entities 105-b or UE 115-b may perform beamforming communication, for example, by switching to or activating at least one TCI state.

[0111] Therefore, in Figure 3 In the example, one or more of network entity 105-b or UE 115-b (e.g., via TCI activation or TCI switching) perform beam management without the need for MAC-CE signaling from network entity 105-b (e.g., a command in MAC-CE indicating TCI activation or TCI switching).

[0112] Figure 4 A block diagram 400 illustrates a device 405 that supports mapping a reference signal to a TCI for beam management and reporting according to one or more aspects of this disclosure. Device 405 may be an example of various aspects of UE 115 as described herein. Device 405 may include a receiver 410, a transmitter 415, and a communication manager 420. Device 405, or one or more components of device 405 (e.g., receiver 410, transmitter 415, communication manager 420), may include at least one processor that may be coupled to at least one memory to individually or jointly support or implement the described techniques. Each of these components may communicate with each other (e.g., via one or more buses).

[0113] Receiver 410 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 mapping reference signals to TCI for beam management and reporting). Information may be delivered to other components of device 405. Receiver 410 may utilize a single antenna or a collection of antennas.

[0114] Transmitter 415 may provide components for transmitting signals generated by other components of device 405. For example, transmitter 415 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 mapping reference signals to TCI for beam management and reporting). In some examples, transmitter 415 may be co-located with receiver 410 in a transceiver module. Transmitter 415 may utilize a single antenna or a collection of multiple antennas.

[0115] The communication manager 420, receiver 410, transmitter 415, or various combinations or components thereof may be examples of components used to perform various aspects of mapping a reference signal to a TCI for beam management and reporting as described herein. For example, the communication manager 420, receiver 410, transmitter 415, or various combinations or components thereof may be able to perform one or more of the functions described herein.

[0116] In some examples, the communication manager 420, receiver 410, transmitter 415, or various combinations or components thereof may be implemented in hardware (e.g., in communication management circuitry). The hardware may include at least one of the following: a processor, digital signal processor (DSP), central processing unit (CPU), application-specific integrated circuit (ASIC), field-programmable gate array (FPGA) or other programmable logic device, microcontroller, discrete gate or transistor logic component, discrete hardware component, or any combination thereof, configured as or otherwise individually or collectively to support components for performing the functions described herein. In some examples, at least one processor and at least one memory coupled to said at least one processor may be configured to perform one or more of the functions described herein (e.g., instructions stored in at least one memory are executed individually or collectively by one or more processors).

[0117] Additionally or alternatively, the communication manager 420, receiver 410, transmitter 415, or various combinations or components thereof may be implemented in code executed by at least one processor (e.g., referred to as processor executable code) (e.g., implemented as communication management software or firmware). If implemented in code executed by at least one processor, the functionality of the communication manager 420, receiver 410, transmitter 415, or various combinations or components thereof may be performed by any combination of a general-purpose processor, DSP, CPU, ASIC, FPGA, microcontroller, or these or other programmable logic devices (e.g., configured as or otherwise individually or jointly to support components for performing the functions described in this disclosure).

[0118] In some examples, the communication manager 420 may be configured to use a receiver 410, a transmitter 415, or both, or otherwise cooperate with them to perform various operations (e.g., receiving, acquiring, monitoring, outputting, transmitting). For example, the communication manager 420 may receive information from the receiver 410, transmit information to the transmitter 415, or integrate with the receiver 410, the transmitter 415, or both to acquire information, output information, or perform various other operations as described herein.

[0119] Communication manager 420 may support wireless communication according to examples disclosed herein. For example, communication manager 420 may be capable of, configured to, or operable to support components for sending reports to network entities, the reports including reference signal identifiers that identify reference signals. Communication manager 420 may be capable of, configured to, or operable to support components for mapping reference signal identifiers to at least one of a set of one or more TCI states associated with TCI code points, wherein the TCI code points include one or more of downlink TCI states, uplink TCI states, or joint TCI states. Communication manager 420 may be capable of, configured to, or operable to support components for selecting at least one TCI state for a reference signal by switching to or activating at least one TCI state.

[0120] By including or configuring a communication manager 420 according to an example as described herein, device 405 (e.g., controlling receiver 410, transmitter 415, communication manager 420 or a combination thereof or at least one processor otherwise coupled to them) can support techniques for reducing power consumption.

[0121] Figure 5 A block diagram 500 of a device 505 supporting the mapping of reference signals to TCI for beam management and reporting according to one or more aspects of this disclosure is shown. Device 505 may be an example of aspects of device 405 or UE 115 as described herein. Device 505 may include receiver 510, transmitter 515, and communication manager 520. Device 505 or one or more components of device 505 (e.g., receiver 510, transmitter 515, communication manager 520) may include at least one processor that may be coupled to at least one memory to support the described techniques. Each of these components may communicate with each other (e.g., via one or more buses).

[0122] 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 mapping reference signals to TCI for beam management and reporting). Information may be delivered to other components of device 505. Receiver 510 may utilize a single antenna or a collection of antennas.

[0123] Transmitter 515 may provide components for transmitting signals generated by other components of device 505. For example, 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 mapping reference signals to TCI for beam management and reporting). In some examples, transmitter 515 may be co-located with receiver 510 in a transceiver module. Transmitter 515 may utilize a single antenna or a collection of multiple antennas.

[0124] Device 505 or its various components may be examples of parts used to perform various aspects of mapping a reference signal to a TCI for beam management and reporting as described herein. For example, communication manager 520 may include reporting component 525, mapper component 530, TCI status component 535, or any combination thereof. Communication manager 520 may be examples of aspects of communication manager 420 as described herein. In some examples, communication manager 520 or its various components may be configured to use receiver 510, transmitter 515, or both, or otherwise cooperate with them to perform various operations (e.g., receiving, acquiring, monitoring, outputting, transmitting). For example, communication manager 520 may receive information from receiver 510, transmit information to transmitter 515, or be integrated in combination with receiver 510, transmitter 515, or both to acquire information, output information, or perform various other operations as described herein.

[0125] Communication manager 520 may support wireless communication according to examples disclosed herein. Reporting component 525 is capable of, configured to, or operable to support components for sending reports to network entities, the reports including reference signal identifiers that identify reference signals. Mapper component 530 is capable of, configured to, or operable to support components for mapping reference signal identifiers to at least one of a set of one or more TCI states associated with a TCI code point, wherein the TCI code point includes one or more of downlink TCI states, uplink TCI states, or joint TCI states. TCI state component 535 is capable of, configured to, or operable to support components for selecting at least one TCI state for a reference signal by switching to or activating at least one TCI state.

[0126] Figure 6A block diagram 600 is shown of a communication manager 620 that supports mapping a reference signal to a TCI for beam management and reporting according to one or more aspects of this disclosure. The communication manager 620 may be an example of a communication manager 420, a communication manager 520, or aspects thereof as described herein. The communication manager 620 or its various components may be examples of parts for performing the various aspects of mapping a reference signal to a TCI for beam management and reporting as described herein. For example, the communication manager 620 may include a reporting component 625, a mapper component 630, a TCI status component 635, a reference signal component 640, or any combination thereof. Each of these components, or its components or sub-components (e.g., one or more processors, one or more memories), may communicate directly or indirectly with each other (e.g., via one or more buses).

[0127] The communication manager 620 can support wireless communication according to examples disclosed herein. The reporting component 625 is capable of, configured to, or operable to support components for sending reports to network entities, the reports including reference signal identifiers that identify reference signals. The mapper component 630 is capable of, configured to, or operable to support components for mapping reference signal identifiers to at least one of a set of one or more TCI states associated with a TCI code point, wherein the TCI code point includes one or more of downlink TCI states, uplink TCI states, or joint TCI states. The TCI state component 635 is capable of, configured to, or operable to support components for selecting at least one TCI state for a reference signal by switching to or activating at least one TCI state.

[0128] In some examples, the rule defines the association between at least one TCI state for the reference signal and a joint TCI state or a downlink TCI state, with the downlink TCI state being associated with the unified TCI state.

[0129] In some examples, the rule defines the association between at least one TCI state for the reference signal and one or more of a joint TCI state, a downlink TCI state, or an uplink TCI state, which are associated with a unified TCI state.

[0130] In some examples, the report includes indications of the association between the reference signal and the uplink TCI state or the downlink TCI state.

[0131] In some examples, the report includes a set of one or more reference signal identifiers, each of which identifies a corresponding reference signal within that set of one or more reference signals. In some examples, the rule defines the association between each corresponding reference signal and either the downlink TCI state or the uplink TCI state.

[0132] In some examples, each TCI code point in a set of one or more TCI code points includes a single TCI state.

[0133] In some examples, the rule defines the association between each TCI code point in the group of one or more TCI code points and one or more of the downlink TCI states or uplink TCI states.

[0134] In some examples, each TCI code point in a group of one or more TCI code points includes a TCI state group. In some examples, the TCI state group includes one or more of the downlink TCI states or uplink TCI states.

[0135] In some examples, the report includes a group of multiple reference signal identifiers that identify a set of multiple reference signal groups. In some examples, the rule defines the association between each reference signal in each group of the multiple reference signal groups and the corresponding TCI code point in one or more TCI code points in that group.

[0136] In some examples, the report includes a group of reference signal identifiers that identifies a group of reference signals. In some examples, the rule defines the association between the group of reference signal identifiers and a corresponding TCI code point in one or more TCI code points within that group. In some examples, at least one reference signal identifier in the group of reference signal identifiers includes a dummy reference signal identifier that is at least partially based on a corresponding TCI code point that includes a downlink TCI state or an uplink TCI state.

[0137] In some examples, the report includes an indication of whether the reference signal is associated with switching to at least one TCI state.

[0138] In some examples, the report includes a second reference signal identifier that identifies the second reference signal, and the mapper component 630 is capable of, configured to, or operable to support components for mapping the second reference signal identifier to at least one second TCI state in one or more TCI states associated with the TCI code point, wherein at least one TCI state of the reference signal corresponds to a downlink TCI state or an uplink TCI state, or wherein at least one TCI state of the reference signal corresponds to a downlink TCI state and at least one TCI state of the second reference signal corresponds to an uplink TCI state.

[0139] In some examples, at least one TCI state includes QCL information. In some examples, the QCL information includes a first QCL type or a second QCL type. In some examples, the first QCL type is associated with one or more of Doppler shift, Doppler spread, average delay, or average spread. In some examples, the second QCL type is associated with a spatial filter, which is associated with at least one beam used for wireless communication.

[0140] In some examples, the reference signal is associated with a second QCL type. In some examples, at least one TCI state is based on the reference signal associated with the second QCL type.

[0141] In some examples, TCI state component 635 is capable of, configured to, or operable to support a component for selecting at least one TCI state in one or more TCI states in a group of one or more TCI states based on a rule and on a corresponding TCI state identifier associated with each TCI state in the group of one or more TCI states, wherein at least two TCI states in the group of one or more TCI states are associated with a second QCL type.

[0142] In some examples, the reference signal component 640 is capable of, configured to, or operable to support components for applying the reference signal as a QCL-type reference signal independent of at least one TCI state.

[0143] In some examples, the synchronization signal block is quasi-co-located with the QCL type reference signal.

[0144] In some examples, at least one channel state information reference signal is quasi-co-located with a reference signal.

[0145] Figure 7A diagram of a system 700 including device 705 supporting the mapping of reference signals to TCI for beam management and reporting, according to one or more aspects of this disclosure, is shown. Device 705 may be an example of device 405, device 505, or UE 115 as described herein, or may include components thereof. Device 705 may communicate with one or more other devices (e.g., network entity 105, UE 115, or any combination thereof) (e.g., wirelessly). Device 705 may include components for bidirectional voice and data communication, including components for transmitting and receiving communications, such as a communication manager 720, an input / output (I / O) controller (e.g., I / O controller 710), a transceiver 715, one or more antennas 725, at least one memory 730, code 735, and at least one processor 740. These components may communicate electronically or be coupled in other ways (e.g., operational ground, communication ground, functional ground, electronic ground, electrical ground) via one or more buses (e.g., bus 745).

[0146] I / O controller 710 manages the input and output signals of device 705. I / O controller 710 can also manage peripheral devices not integrated into device 705. In some cases, I / O controller 710 may represent a physical connection or port to an external peripheral device. In some cases, I / O controller 710 may utilize an operating system such as iOS. ® ANDROID ® MS-DOS ® MS-WINDOWS ® OS / 2 ® UNIX ® LINUX ® Or another known operating system. Additionally or alternatively, the I / O controller 710 may represent or interact with a modem, keyboard, mouse, touchscreen, or similar device. In some cases, the I / O controller 710 may be implemented as part of one or more processors, such as at least one processor 740. In some cases, a user may interact with the device 705 via the I / O controller 710 or via hardware components controlled by the I / O controller 710.

[0147] In some cases, device 705 may include a single antenna. However, in other cases, device 705 may have more than one antenna, which may be capable of concurrently transmitting or receiving multiple wireless transmissions. Transceiver 715 may communicate bidirectionally via one or more antennas 725 using a wired or wireless link as described herein. For example, transceiver 715 may represent a wireless transceiver and may communicate bidirectionally with another wireless transceiver. Transceiver 715 may also include a modem for: modulating packets; providing the modulated packets to one or more antennas 725 for transmission; and demodulating packets received from one or more antennas 725. Transceiver 715, or transceiver 715 and one or more antennas 725, may be an example of transmitter 415, transmitter 515, receiver 410, receiver 510, or any combination thereof or component thereof as described herein.

[0148] At least one memory 730 may include random access memory (RAM) and read-only memory (ROM). At least one memory 730 may store computer-readable code, computer-executable code, or processor-executable code, such as code 735. Code 735 may include instructions that, when executed by at least one processor 740, cause device 705 to perform the various functions described herein. Code 735 may be stored in a non-transitory computer-readable medium, such as system memory or another type of memory. In some cases, code 735 may not be directly executable by at least one processor 740, but may cause a computer (e.g., when compiled and executed) to perform the functions described herein. In some cases, at least one memory 730 may include a basic I / O system (BIOS), etc., which controls basic hardware or software operations, such as interaction with peripheral components or devices.

[0149] At least one processor 740 may include one or more intelligent hardware devices (e.g., one or more general-purpose processors, one or more DSPs, one or more CPUs, one or more graphics processing units (GPUs), one or more neural processing units (NPUs) (also referred to as neural network processors or deep learning processors (DLPs)), one or more microcontrollers, one or more ASICs, one or more FPGAs, one or more programmable logic devices, discrete gate or transistor logic, one or more discrete hardware components, or any combination thereof). In some cases, at least one processor 740 may be configured to use a memory controller to operate a memory array. In some other cases, the memory controller may be integrated into at least one processor 740. At least one processor 740 may be configured to execute computer-readable instructions stored in memory (e.g., at least one memory 730) to cause device 705 to perform various functions (e.g., functions or tasks that support mapping reference signals to TCI for beam management and reporting). For example, device 705 or components of device 705 may include at least one processor 740 and at least one memory 730 coupled to or coupled to at least one processor 740, wherein at least one processor 740 and at least one memory 730 are configured to perform the various functions described herein.

[0150] In some examples, at least one processor 740 may include multiple processors, and at least one memory 730 may include multiple memories. One or more of the multiple processors may be coupled to one or more of the multiple memories, which may be configured individually or collectively to perform the various functions described herein. In some examples, at least one processor 740 may be a component of a processing system, which may refer to a system of machines (such as a series of machines), circuits (including, for example, one or both of processor circuitry (which may include at least one processor 740) and memory circuitry (which may include at least one memory 730)) or components that receive or obtain input and process the input to produce, generate, or obtain a set of outputs. The processing system may be configured to perform one or more of the functions described herein. For example, at least one processor 740 or a processing system including at least one processor 740 may be configured, capable of being configured, or operable to cause device 705 to perform one or more of the functions described herein. Furthermore, as described herein, “configured to,” “capable of being configured to,” and “capable of operating to” can be used interchangeably and can be associated with the ability to perform one or more of the functions described herein when executing code 735 (e.g., processor-executable code) stored in at least one memory 730 or otherwise.

[0151] The communication manager 720 may support wireless communication according to examples disclosed herein. For example, the communication manager 720 may be capable of, configured to, or operable to support components for sending reports to network entities, the reports including reference signal identifiers that identify reference signals. The communication manager 720 may be capable of, configured to, or operable to support components for mapping reference signal identifiers to at least one of a set of one or more TCI states associated with TCI code points, wherein the TCI code points include one or more of downlink TCI states, uplink TCI states, or joint TCI states. The communication manager 720 may be capable of, configured to, or operable to support components for selecting at least one TCI state for a reference signal by switching to or activating at least one TCI state.

[0152] By including or configuring a communication manager 720 according to an example as described herein, device 705 can support techniques for improved communication reliability, reduced latency, and reduced power consumption.

[0153] In some examples, the communication manager 720 may be configured to use or otherwise coordinate with the transceiver 715, one or more antennas 725, or any combination thereof to perform various operations (e.g., receiving, monitoring, transmitting). Although the communication manager 720 is illustrated as a separate component, in some examples, one or more functions described with reference to the communication manager 720 may be supported or executed by at least one processor 740, at least one memory 730, code 735, or any combination thereof. For example, code 735 may include instructions that can be executed by at least one processor 740 to cause device 705 to perform various aspects as described herein, such as mapping a reference signal to a TCI for beam management and reporting, or at least one processor 740 and at least one memory 730 may be otherwise configured to perform or support such operations individually or jointly.

[0154] Figure 8 A block diagram 800 of a device 805 supporting the mapping of reference signals to TCI for beam management and reporting, according to one or more aspects of this disclosure, is shown. Device 805 may be an example of aspects of network entity 105 as described herein. Device 805 may include a receiver 810, a transmitter 815, and a communication manager 820. Device 805, or one or more components of device 805 (e.g., receiver 810, transmitter 815, communication manager 820), may include at least one processor that may be coupled to at least one memory to individually or jointly support or implement the described techniques. Each of these components may communicate with each other (e.g., via one or more buses).

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

[0156] Transmitter 815 may provide components for outputting (e.g., transmitting, providing, conveying, transmitting) information generated by other components of device 805. For example, transmitter 815 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 815 may support outputting information by transmitting signals via one or more antennas. Additionally or alternatively, transmitter 815 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, transmitter 815 and receiver 810 may be co-located in a transceiver, which may include or be coupled to a modem.

[0157] The communication manager 820, receiver 810, transmitter 815, or various combinations or components thereof may be examples of components used to perform various aspects of mapping a reference signal to a TCI for beam management and reporting as described herein. For example, the communication manager 820, receiver 810, transmitter 815, or various combinations or components thereof may be able to perform one or more of the functions described herein.

[0158] In some examples, the communication manager 820, receiver 810, transmitter 815, or various combinations or components thereof may be implemented in hardware (e.g., in communication management circuitry). The hardware may include at least one of a processor, DSP, CPU, ASIC, FPGA, or other programmable logic device, microcontroller, discrete gate or transistor logic unit, discrete hardware component, or any combination thereof, configured as or otherwise individually or collectively to support components for performing the functions described herein. In some examples, at least one processor and at least one memory coupled to said at least one processor may be configured to perform one or more of the functions described herein (e.g., instructions stored in at least one memory are executed individually or collectively by one or more processors).

[0159] Additionally or alternatively, the communication manager 820, receiver 810, transmitter 815, or various combinations or components thereof may be implemented in code executed by at least one processor (e.g., referred to as processor executable code) (e.g., implemented as communication management software or firmware). If implemented in code executed by at least one processor, the functionality of the communication manager 820, receiver 810, transmitter 815, or various combinations or components thereof may be performed by any combination of a general-purpose processor, DSP, CPU, ASIC, FPGA, microcontroller, or these or other programmable logic devices (e.g., configured as or otherwise individually or jointly to support components for performing the functions described in this disclosure).

[0160] In some examples, the communication manager 820 may be configured to use a receiver 810, a transmitter 815, or both, or otherwise cooperate with them to perform various operations (e.g., receiving, acquiring, monitoring, outputting, transmitting). For example, the communication manager 820 may receive information from the receiver 810, transmit information to the transmitter 815, or be integrated with the receiver 810, the transmitter 815, or both to acquire information, output information, or perform various other operations as described herein.

[0161] The communication manager 820 may support wireless communication according to examples disclosed herein. For example, the communication manager 820 may be capable of, configured to, or operable to support components for receiving reports from a UE, the reports including a reference signal identifier identifying a reference signal. The communication manager 820 may be capable of, configured to, or operable to support components for mapping the reference signal identifier to at least one of a set of one or more TCI states associated with a TCI code point, wherein the TCI code point includes one or more of a downlink TCI state, an uplink TCI state, or a combined TCI state. The communication manager 820 may be capable of, configured to, or operable to support components for selecting at least one TCI state for a reference signal by switching to or activating at least one TCI state.

[0162] By including or configuring a communication manager 820 according to an example as described herein, device 805 (e.g., controlling receiver 810, transmitter 815, communication manager 820 or a combination thereof or at least one processor otherwise coupled to them) can support techniques for reducing power consumption.

[0163] Figure 9 A block diagram 900 of a device 905 supporting the mapping of a reference signal to a TCI for beam management and reporting, according to one or more aspects of this disclosure, is shown. Device 905 may be an example of aspects of device 805 or network entity 105 as described herein. Device 905 may include a receiver 910, a transmitter 915, and a communication manager 920. Device 905 or one or more components of device 905 (e.g., receiver 910, transmitter 915, communication manager 920) may include at least one processor that may be coupled to at least one memory to support the described techniques. Each of these components may communicate with each other (e.g., via one or more buses).

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

[0165] Transmitter 915 may provide components for outputting (e.g., transmitting, providing, conveying, transmitting) 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, fiber optic) 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 or be coupled to a modem.

[0166] Device 905 or its various components may be examples of parts used to perform various aspects of mapping a reference signal to a TCI for beam management and reporting as described herein. For example, communication manager 920 may include reporting component 925, mapper component 930, TCI status component 935, or any combination thereof. Communication manager 920 may be examples of aspects of communication manager 820 as described herein. In some examples, communication manager 920 or its various components may be configured to use receiver 910, transmitter 915, or both, or otherwise cooperate with them to perform various operations (e.g., receiving, acquiring, monitoring, outputting, transmitting). For example, communication manager 920 may receive information from receiver 910, transmit information to transmitter 915, or be integrated with receiver 910, transmitter 915, or both to acquire information, output information, or perform various other operations as described herein.

[0167] Communication manager 920 may support wireless communication according to examples disclosed herein. Reporting component 925 is capable of, configured to, or operable to support components for receiving reports from the UE, the reports including a reference signal identifier identifying the reference signal. Mapper component 930 is capable of, configured to, or operable to support components for mapping the reference signal identifier to at least one of a set of one or more TCI states associated with a TCI code point, wherein the TCI code point includes one or more of a downlink TCI state, an uplink TCI state, or a combined TCI state. TCI state component 935 is capable of, configured to, or operable to support components for selecting at least one TCI state for the reference signal by switching to or activating at least one TCI state.

[0168] Figure 10A block diagram 1000 of a communication manager 1020, according to one or more aspects of this disclosure, is shown, which maps a reference signal to a TCI for beam management and reporting. The communication manager 1020 may be an example of a communication manager 820, a communication manager 920, or aspects thereof as described herein. The communication manager 1020 or its various components may be examples of parts for performing the various aspects of mapping a reference signal to a TCI for beam management and reporting as described herein. For example, the communication manager 1020 may include a reporting component 1025, a mapper component 1030, a TCI status component 1035, a reference signal component 1040, or any combination thereof. Each of these components, or its components or sub-components (e.g., one or more processors, one or more memories), may communicate directly or indirectly with each other (e.g., via one or more buses). 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 virtualization component associated with network entity 105, between devices, components, or virtualization components associated with network entity 105), or any combination thereof.

[0169] Communication manager 1020 may support wireless communication according to examples disclosed herein. Reporting component 1025 is capable of, configured to, or operable to support components for receiving reports from the UE, the reports including a reference signal identifier identifying the reference signal. Mapper component 1030 is capable of, configured to, or operable to support components for mapping the reference signal identifier to at least one of a set of one or more TCI states associated with a TCI code point, wherein the TCI code point includes one or more of a downlink TCI state, an uplink TCI state, or a combined TCI state. TCI state component 1035 is capable of, configured to, or operable to support components for selecting at least one TCI state for the reference signal by switching to or activating at least one TCI state.

[0170] In some examples, the rule defines the association between at least one TCI state for the reference signal and a joint TCI state or a downlink TCI state, with the downlink TCI state being associated with the unified TCI state.

[0171] In some examples, the rule defines the association between at least one TCI state for the reference signal and one or more of a joint TCI state, a downlink TCI state, or an uplink TCI state, which are associated with a unified TCI state.

[0172] In some examples, the report includes indications of the association between the reference signal and the uplink TCI state or the downlink TCI state.

[0173] In some examples, the report includes a set of one or more reference signal identifiers, each of which identifies a corresponding reference signal within that set of one or more reference signals. In some examples, the rule defines the association between each corresponding reference signal and either the downlink TCI state or the uplink TCI state.

[0174] In some examples, each TCI code point in a set of one or more TCI code points includes a single TCI state.

[0175] In some examples, the rule defines the association between each TCI code point in the group of one or more TCI code points and one or more of the downlink TCI states or uplink TCI states.

[0176] In some examples, each TCI code point in a group of one or more TCI code points includes a TCI state group. In some examples, the TCI state group includes one or more of the downlink TCI states or uplink TCI states.

[0177] In some examples, the report includes a group of multiple reference signal identifiers that identify a set of multiple reference signal groups. In some examples, the rule defines the association between each reference signal in each group of the multiple reference signal groups and the corresponding TCI code point in one or more TCI code points in that group.

[0178] In some examples, the report includes a group of reference signal identifiers that identifies a group of reference signals. In some examples, the rule defines the association between the group of reference signal identifiers and a corresponding TCI code point in one or more TCI code points within that group. In some examples, at least one reference signal identifier in the group of reference signal identifiers includes a dummy reference signal identifier that is at least partially based on a corresponding TCI code point that includes a downlink TCI state or an uplink TCI state.

[0179] In some examples, the report includes an indication of whether the reference signal is associated with switching to at least one TCI state.

[0180] In some examples, the report includes a second reference signal identifier that identifies the second reference signal, and the mapper component 1030 is capable of, configured to, or operable to support components for mapping the second reference signal identifier to at least one second TCI state in one or more TCI states associated with the TCI code point, wherein at least one TCI state of the reference signal corresponds to a downlink TCI state or an uplink TCI state, or wherein at least one TCI state of the reference signal corresponds to a downlink TCI state and at least one TCI state of the second reference signal corresponds to an uplink TCI state.

[0181] In some examples, at least one TCI state includes QCL information. In some examples, the QCL information includes a first QCL type or a second QCL type. In some examples, the first QCL type is associated with one or more of Doppler shift, Doppler spread, average delay, or average spread. In some examples, the second QCL type is associated with a spatial filter, which is associated with at least one beam used for wireless communication.

[0182] In some examples, the reference signal is associated with a second QCL type. In some examples, at least one TCI state is based on the reference signal associated with the second QCL type.

[0183] In some examples, TCI state component 1035 is capable of, configured to, or operable to support a component for selecting at least one TCI state in one or more TCI states in a group of one or more TCI states based on a rule and on a corresponding TCI state identifier associated with each TCI state in the group of one or more TCI states, wherein at least two TCI states in the group of one or more TCI states are associated with a second QCL type.

[0184] In some examples, the reference signal component 1040 is capable of, configured to, or operable to support components for applying the reference signal as a QCL-type reference signal independent of at least one TCI state.

[0185] In some examples, the synchronization signal block is quasi-co-located with the QCL type reference signal.

[0186] In some examples, at least one channel state information reference signal is quasi-co-located with a reference signal.

[0187] Figure 11A diagram of a system 1100 including device 1105 supporting the mapping of reference signals to TCI for beam management and reporting, according to one or more aspects of this disclosure, is shown. Device 1105 may be an example of device 805, device 905, or network entity 105 as described herein, or may include components thereof. Device 1105 may communicate with other network devices or network equipment, such as network entity 105, UE 115, or any combination thereof. Communication may include communication via one or more wired interfaces, one or more wireless interfaces, or any combination thereof. Device 1105 may include components supporting output and acquisition of communication, such as a communication manager 1120, a transceiver 1110, one or more antennas 1115, at least one memory 1125, code 1130, and at least one processor 1135. These components may communicate electronically or otherwise (e.g., operative ground, communication ground, functional ground, electronic ground, electrical ground) via one or more buses (e.g., bus 1140).

[0188] Transceiver 1110 may support bidirectional communication via a wired link, a wireless link, or both, as described herein. In some examples, transceiver 1110 may include a wired transceiver and be capable of bidirectional communication with another wired transceiver. Additionally or alternatively, in some examples, transceiver 1110 may include a wireless transceiver and be capable of bidirectional communication with another wireless transceiver. In some examples, device 1105 may include one or more antennas 1115 that are capable of (e.g., concurrently) transmitting or receiving wireless transmissions. Transceiver 1110 may also include a modem for modulating signals to provide modulated signals for transmission (e.g., via one or more antennas 1115, via a wired transmitter), for receiving modulated signals (e.g., from one or more antennas 1115, from a wired receiver), and for demodulating signals. In some embodiments, transceiver 1110 may include one or more interfaces, such as one or more interfaces coupled to one or more antennas 1115 configured to support various receive or acquire operations, or one or more interfaces coupled to one or more antennas 1115 configured to support various transmit or output operations, or combinations thereof. In some embodiments, transceiver 1110 may include one or more processors or one or more memory components or be configured to couple to said one or more processors or one or more memory components, said one or more processors or one or more memory components being operable to perform or support operations based on received or acquired information or signals, or to generate information or other signals for transmission or other output, or any combination thereof. In some embodiments, transceiver 1110, or transceiver 1110 and one or more antennas 1115, or transceiver 1110 and one or more antennas 1115 and one or more processors or one or more memory components (e.g., at least one processor 1135, at least one memory 1125, or both) may be included in a chip or chip assembly mounted in device 1105. In some examples, transceiver 1110 may be able to operate to support communication via one or more communication links (e.g., communication link 125, backhaul communication link 120, midhaul communication link 162, fronthaul communication link 168).

[0189] At least one memory 1125 may include RAM, ROM, or any combination thereof. At least one memory 1125 may store computer-readable code, computer-executable code, or processor-executable code, such as code 1130. Code 1130 may include instructions that, when executed by one or more of the at least one processor 1135, cause the device 1105 to perform the various functions described herein. Code 1130 may be stored in a non-transitory computer-readable medium, such as system memory or another type of memory. In some cases, code 1130 may not be directly executable by one of the at least one processor 1135, but may cause a computer (e.g., when compiled and executed) to perform the functions described herein. In some cases, at least one memory 1125 may include a BIOS, etc., which controls basic hardware or software operations, such as interaction with peripheral components or devices. In some examples, at least one processor 1135 may include multiple processors, and at least one memory 1125 may include multiple memories. One or more of a plurality of processors may be coupled to one or more of a plurality of memories, which may be configured individually or collectively to perform the various functions described herein (e.g., as part of a processing system).

[0190] At least one processor 1135 may include one or more intelligent hardware devices (e.g., one or more general-purpose processors, one or more DSPs, one or more CPUs, one or more graphics processing units (GPUs), one or more neural processing units (NPUs) (also referred to as neural network processors or deep learning processors (DLPs)), one or more microcontrollers, one or more ASICs, one or more FPGAs, one or more programmable logic devices, discrete gate or transistor logic, one or more discrete hardware components, or any combination thereof). In some cases, at least one processor 1135 may be configured to use a memory controller to operate a memory array. In some other cases, the memory controller may be integrated into one or more processors in at least one processor 1135. At least one processor 1135 may be configured to execute computer-readable instructions stored in memory (e.g., one or more memories in at least one memory 1125) to cause device 1105 to perform various functions (e.g., functions or tasks that support mapping reference signals to TCI for beam management and reporting). For example, device 1105 or components of device 1105 may include at least one processor 1135 and at least one memory 1125 coupled to one or more processors in at least processor 1135, wherein at least processor 1135 and at least one memory 1125 are configured to perform the various functions described herein. At least processor 1135 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 (e.g., by executing code 1130) host functions for performing the functions of device 1105. At least processor 1135 may be any one or more suitable processors capable of executing scripts or instructions of one or more software programs stored in device 1105 (such as within one or more memories in at least one memory 1125).

[0191] In some examples, at least one processor 1135 may include multiple processors, and at least one memory 1125 may include multiple memories. One or more of the multiple processors may be coupled to one or more of the multiple memories, which may be configured individually or collectively to perform the various functions described herein. In some examples, at least one processor 1135 may be a component of a processing system, which may refer to a system of machines (such as a series of machines), circuitry (including, for example, one or both of processor circuitry (which may include at least one processor 1135) and memory circuitry (which may include at least one memory 1125)) or components that receive or receive input and process the input to produce, generate, or obtain a set of outputs. The processing system may be configured to perform one or more of the functions described herein. For example, at least one processor 1135 or a processing system including at least one processor 1135 may be configured, configured to, or operable to cause device 1105 to perform one or more of the functions described herein. Furthermore, as described herein, “configured to,” “capable of being configured to,” and “capable of operating to” can be used interchangeably and can be associated with the ability to perform one or more of the functions described herein when executing code stored in at least one memory 1125 or otherwise.

[0192] In some examples, bus 1140 may support communication at the protocol layer of the protocol stack (e.g., within a protocol layer). In some examples, bus 1140 may support communication associated with logical channels of the protocol stack (e.g., between protocol layers of the protocol stack), which may include communication performed within components of device 1105, or communication performed between different components of device 1105 that are co-addressable or may be located in different locations (e.g., where device 1105 may refer to a system in which one or more of communication manager 1120, transceiver 1110, at least one memory 1125, code 1130 and at least one processor 1135 may be located in one component of different components or partitioned between different components).

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

[0194] The communication manager 1120 may support wireless communication according to examples disclosed herein. For example, the communication manager 1120 may be capable of, configured to, or operable to support components for receiving reports from a UE, the reports including a reference signal identifier identifying a reference signal. The communication manager 1120 may be capable of, configured to, or operable to support components for mapping the reference signal identifier to at least one of a set of one or more TCI states associated with a TCI code point, wherein the TCI code point includes one or more of a downlink TCI state, an uplink TCI state, or a combined TCI state. The communication manager 1120 may be capable of, configured to, or operable to support components for selecting at least one TCI state for a reference signal by switching to or activating at least one TCI state.

[0195] By including or configuring a communication manager 1120 according to an example as described herein, device 1105 can support techniques for improved communication reliability, reduced latency, and reduced power consumption.

[0196] In some examples, the communication manager 1120 may be configured to use or otherwise coordinate with the transceiver 1110, one or more antennas 1115 (e.g., where applicable), or any combination thereof to perform various operations (e.g., receiving, acquiring, monitoring, outputting, transmitting). Although the communication manager 1120 is illustrated as a separate component, in some examples, one or more functions described with reference to the communication manager 1120 may be supported or performed by the transceiver 1110, one or more processors in at least one processor 1135, one or more memories in at least one memory 1125, code 1130, or any combination thereof (e.g., by a processing system including at least a portion of at least one processor 1135, at least one memory 1125, code 1130, or any combination thereof). For example, code 1130 may include instructions that can be executed by at least one processor 1135 to cause the device 1105 to perform various aspects of mapping a reference signal to a TCI for beam management and reporting as described herein, or at least one processor 1135 and at least one memory 1125 may be otherwise configured to perform or support such operations individually or jointly.

[0197] Figure 12 A flowchart illustrating method 1200 for mapping a reference signal to a TCI for beam management and reporting, supported by one or more aspects of this disclosure, is shown. Operation of method 1200 may be implemented by a UE or its components as described herein. For example, operation of method 1200 may be implemented by a UE as described herein. Figures 1 to 7The UE 115 described herein is used to perform this function. In some examples, the UE can execute a set of instructions to control the functional elements of the UE to perform the described function. Additionally or alternatively, the UE may use dedicated hardware to perform aspects of the described function.

[0198] At 1205, the method may include sending a report to a network entity, the report including a reference signal identifier that identifies the reference signal. The operation of 1205 may be performed according to the examples disclosed herein. In some examples, aspects of the operation of 1205 may be determined by, as in reference... Figure 6 The report component 625 described is used to perform this.

[0199] At 1210, the method may include mapping a reference signal identifier to at least one of a set of one or more TCI states associated with a TCI code point, according to a rule, wherein the TCI code point includes one or more of a downlink TCI state, an uplink TCI state, or a combined TCI state. The operation of 1210 may be performed according to examples as disclosed herein. In some examples, aspects of the operation of 1210 may be determined by reference... Figure 6 The described mapper component 630 is executed.

[0200] At 1215, the method may include selecting at least one TCI state for the reference signal by switching to or activating at least one TCI state. The operation of 1215 may be performed according to examples as disclosed herein. In some examples, aspects of the operation of 1215 may be determined by, as in the reference... Figure 6 The TCI state component 635 described is executed.

[0201] Figure 13 A flowchart illustrating method 1300 for mapping a reference signal to a TCI for beam management and reporting, supported by one or more aspects of this disclosure, is shown. Operation of method 1300 may be implemented by a network entity or its components as described herein. For example, operation of method 1300 may be implemented by a network entity or its components as described herein. Figures 1 to 3 as well as Figures 8 to 11 The network entity described is used to perform this function. In some examples, the network entity may execute a set of instructions to control the functional elements of the network entity to perform the described function. Additionally or alternatively, the network entity may use dedicated hardware to perform aspects of the described function.

[0202] At 1305, the method may include receiving a report from the UE, the report including a reference signal identifier identifying the reference signal. Operation of 1305 may be performed according to examples as disclosed herein. In some examples, aspects of operation of 1305 may be determined by reference... Figure 10 The report component 1025 described is used to perform this.

[0203] At 1310, the method may include mapping a reference signal identifier to at least one of a set of one or more TCI states associated with a TCI code point, according to a rule, wherein the TCI code point includes one or more of a downlink TCI state, an uplink TCI state, or a combined TCI state. The operation of 1310 may be performed according to examples as disclosed herein. In some examples, aspects of the operation of 1310 may be determined by reference... Figure 10 The described mapper component 1030 is executed.

[0204] At 1315, the method may include selecting at least one TCI state for the reference signal by switching to or activating at least one TCI state. The operation of 1315 may be performed according to examples as disclosed herein. In some examples, aspects of the operation of 1315 may be determined by, as in the reference... Figure 10 The TCI state component 1035 described is executed.

[0205] It should be noted that the methods described herein describe possible specific implementations. Operations and steps can be rearranged or otherwise modified, and other specific implementations are possible. Furthermore, aspects from two or more of these methods can be combined.

[0206] The following provides an overview of the various aspects of this disclosure: Aspect 1: A method for wireless communication at a UE, the method comprising: sending a report to a network entity, the report including a reference signal identifier identifying a reference signal; mapping the reference signal identifier to at least one of a set of one or more TCI states associated with a TCI code point, wherein the TCI code point includes one or more of a downlink TCI state, an uplink TCI state, or a combined TCI state; and selecting the at least one TCI state for the reference signal by switching to or activating the at least one TCI state.

[0207] Aspect 2: According to the method of aspect 1, wherein the rule defines the correlation between the at least one TCI state of the reference signal and the joint TCI state or the downlink TCI state, the downlink TCI state being associated with the unified TCI state.

[0208] Aspect 3: The method according to any one of Aspects 1 to 2, wherein the rule defines the association between the at least one TCI state for the reference signal and one or more of the joint TCI state, the downlink TCI state, or the uplink TCI state, which is associated with a unified TCI state.

[0209] Aspect 4: The method according to any one of Aspects 1 to 3, wherein the report includes an indication of the association between the reference signal and the uplink TCI state or the downlink TCI state.

[0210] Aspect 5: The method according to any one of Aspects 1 to 4, wherein the report includes a set of one or more reference signal identifiers, each of the set of one or more reference signal identifiers identifying a corresponding reference signal in the set of one or more reference signals, and the rule defines the association between each corresponding reference signal and the downlink TCI state or the uplink TCI state.

[0211] Aspect 6: The method according to any one of aspects 1 to 5, wherein each TCI code point in a group of one or more TCI code points includes a single TCI state.

[0212] Aspect 7: According to the method of aspect 6, wherein the rule defines the association between each TCI code point in the set of one or more TCI code points and one or more of the downlink TCI state or the uplink TCI state.

[0213] Aspect 8: The method according to any one of Aspects 1 to 7, wherein each TCI code point in a group of one or more TCI code points includes a TCI state group, and the TCI state group includes one or more of the downlink TCI state or the uplink TCI state.

[0214] Aspect 9: According to the method of aspect 8, wherein the report includes a plurality of reference signal identifier groups that identify a plurality of reference signal groups, and the rule defines the association between each reference signal in each of the plurality of reference signal groups and a corresponding TCI code point in the set of one or more TCI code points.

[0215] Aspect 10: The method according to any one of Aspects 8 to 9, wherein the report includes a group of reference signal identifiers that identifies a group of reference signals, the rule defines the association between the group of reference signal identifiers and a corresponding TCI code point in the group of one or more TCI code points, and at least one reference signal identifier in the group of reference signal identifiers includes a dummy reference signal identifier, the dummy reference signal identifier being based at least in part on the corresponding TCI code point that includes the downlink TCI state or the uplink TCI state.

[0216] Aspect 11: The method according to any one of Aspects 1 to 10, wherein the report includes an indication of whether the reference signal is associated with switching to the at least one TCI state.

[0217] Aspect 12: The method according to any one of Aspects 1 to 11, wherein the report includes a second reference signal identifier identifying a second reference signal, the method further comprising: mapping the second reference signal identifier to at least one second TCI state in one or more TCI states associated with the TCI code point according to the rule, wherein the at least one TCI state for the reference signal corresponds to the downlink TCI state or the uplink TCI state, or wherein the at least one TCI state for the reference signal corresponds to the downlink TCI state and the at least one second TCI state for the second reference signal corresponds to the uplink TCI state.

[0218] Aspect 13: The method according to any one of Aspects 1 to 12, wherein the at least one TCI state includes QCL information, the QCL information including a first QCL type or a second QCL type, the first QCL type being associated with one or more of Doppler frequency shift, Doppler spread, average delay or average spread, and the second QCL type being associated with a spatial filter, the spatial filter being associated with at least one beam for wireless communication.

[0219] Aspect 14: According to the method of aspect 13, wherein the reference signal is associated with the second QCL type, and the at least one TCI state is based at least in part on the reference signal associated with the second QCL type.

[0220] Aspect 15: The method according to aspect 14, the method further comprising: selecting the at least one TCI state in the set of one or more TCI states according to the rule and at least in part based on a corresponding TCI state identifier associated with each TCI state in the set of one or more TCI states, wherein at least two TCI states in the set of one or more TCI states are associated with the second QCL type.

[0221] Aspect 16: The method according to any one of aspects 1 to 15, the method further comprising: applying the reference signal as a QCL type reference signal independent of the at least one TCI state.

[0222] Aspect 17: The method according to aspect 16, wherein the SSB is a reference signal QCL of the QCL type.

[0223] Aspect 18: The method according to any one of Aspects 16 to 17, wherein at least one CSI-RS is associated with the reference signal QCL.

[0224] Aspect 19: A UE for wireless communication, the UE comprising: one or more memories storing processor-executable code; and one or more processors coupled to the one or more memories and capable of operating individually or jointly to execute the code to cause the UE to perform a method according to any one of Aspects 1 to 18.

[0225] Aspect 20: A UE for wireless communication, the UE comprising at least one component for performing a method according to any one of aspects 1 to 18.

[0226] Aspect 21: A non-transitory computer-readable medium storing code for wireless communication, the code including instructions executable by one or more processors to perform the method according to any one of aspects 1 to 18.

[0227] While 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 herein are also applicable to networks outside of LTE, LTE-A, LTE-A Pro, or NR networks. For example, the techniques described are applicable to a variety of other wireless communication systems, such as Ultra Mobile Broadband (UMB), IEEE 802.11 (Wi-Fi), IEEE 802.16 (WiMAX), IEEE 802.20, Flash-OFDM, and other systems and radio technologies not explicitly mentioned herein.

[0228] The information and signals described herein can be represented using any of a variety of different techniques and skills. For example, data, instructions, commands, information, signals, bits, symbols, and chips mentioned throughout the description can be represented by voltage, current, electromagnetic waves, magnetic fields or magnetic particles, light fields or optical particles, or any combination thereof.

[0229] The various exemplary blocks and components described herein can be implemented or performed using general-purpose processors, DSPs, ASICs, CPUs, graphics processing units (GPUs), neural processing units (NPUs), FPGAs or other programmable logic devices, discrete gate or transistor logic units, discrete hardware components, or any combination thereof that are designed to perform the functions described herein. A general-purpose processor may be a microprocessor, but in alternatives, a processor may be any processor, controller, microcontroller, or state machine. A processor may also be implemented as a combination of computing devices (e.g., a combination of a DSP and a microprocessor, multiple microprocessors, one or more microprocessors combined with a DSP core, or any other such configuration). Any function or operation described herein that can be performed by a processor may be performed by multiple processors capable of performing the described function or operation individually or jointly.

[0230] The functions described herein can be implemented using hardware, software executed by a processor, firmware, or any combination thereof. When implemented using software executed by a processor, the functions can 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 herein can be implemented using software executed by a processor, hardware, firmware, hardwiring, or any combination of these. Features implementing the functions can also be physically located in various locations, including various portions distributed such that the functions are implemented in different physical locations.

[0231] Computer-readable media includes both non-transitory computer storage media and communication media, encompassing any medium that facilitates the transfer of a computer program from one location to another. Non-transitory storage media can be any available medium accessible by a general-purpose or special-purpose computer. By way of example, and not limitation, non-transitory computer-readable media may include RAM, ROM, electrically erasable programmable ROM (EEPROM), flash memory, compressed optical disc (CD) ROM or other optical disc storage devices, magnetic disk storage devices or other magnetic storage devices, or any other non-transitory medium that can be used to carry or store desired program code components in the form of instructions or data structures, and accessible by a general-purpose or special-purpose computer or a general-purpose or special-purpose processor. Furthermore, any connection is appropriately referred to as computer-readable media. For example, if software is transmitted from a website, server, or other remote source using coaxial cable, fiber optic cable, twisted pair, digital subscriber line (DSL), or wireless technologies such as infrared, radio, and microwave, then coaxial cable, fiber optic cable, twisted pair, DSL, or wireless technologies such as infrared, radio, and microwave are included within the definition of computer-readable media. As used herein, disks and optical discs include CDs, laser discs, optical discs, digital multifunction discs (DVDs), floppy disks, and Blu-ray discs. Disks can magnetically reproduce data, and optical discs can optically reproduce data using lasers. Combinations of the above are also included within the scope of computer-readable media. Any function or operation described herein that can be performed by memory can be performed by multiple memories capable of performing the described function or operation individually or jointly.

[0232] As used herein, the word "or" in a list of items (e.g., a list of items accompanied by phrases such as "at least one of" or "one or more of") in the claims indicates an inclusive list, such that a list of at least one of, for example, A, B, or C means A or B or C or AB or AC or BC or ABC (i.e., A and B and C). Furthermore, 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" could be based on both condition A and condition B without departing from the scope of this 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".

[0233] As used herein, including in claims, the article “a” preceding a noun is open-ended and is understood to refer to “at least one” or “one or more” of those nouns. Therefore, the terms “a,” “at least one,” “one or more,” and “at least one of one or more” are interchangeable. For example, where a claim enumerates “components” performing one or more functions, each of the individual functions may be performed by a single component or by any combination of multiple components. Thus, the term “component” having a characteristic or performing a function may refer to “at least one of one or more components” having a particular characteristic or performing a particular function. Subsequent references to a component introduced with the article “a” using the terms “the” or “the” can refer to any or all of the one or more components. For example, a component introduced with the article “a” can be understood to mean “one or more components,” and subsequent reference to “the component” in a claim can be understood as equivalent to referring to “at least one of the one or more components.” Similarly, subsequent references to a component introduced with the terms “the” or “the” as “one or more components” can refer to any or all of the one or more components. For example, reference to "the one or more components" in the subsequent claims can be understood as equivalent to reference to "at least one of the one or more components".

[0234] The term "determine" encompasses a wide range of actions, and therefore, "determine" can include calculation, computation, processing, derivation, investigation, lookup (such as by searching in a table, database, or other data structure), identification, and similar actions. Furthermore, "determine" can include receiving (e.g., receiving information), accessing (e.g., accessing data stored in memory), and so on. Moreover, "determine" can include parsing, obtaining, selecting, choosing, creating, and other similar actions.

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

[0236] The description herein, illustrated with reference to the accompanying drawings, describes an example configuration and does not represent all achievable examples or those within the scope of the claims. The term "example" as used herein means "serving as an example, instance, or illustration," not "preferred" or "advantageous over other examples." The detailed description includes specific details used to provide an understanding of the described techniques. However, these techniques can be practiced without these specific details. In some of the drawings, known structures and devices are shown in block diagram form to avoid obscuring the concept of the described examples.

[0237] The description herein is provided to enable those skilled in the art to implement or use this disclosure. Various modifications to this disclosure will be apparent to those skilled in the art, and the general principles defined herein may be applied to other variations without departing from the scope of this disclosure. Therefore, this disclosure is not limited to the examples and designs described herein, but should be granted the widest scope consistent with the principles and novel features disclosed herein.

Claims

1. A user equipment (UE), the user equipment (UE) comprising: One or more memories, wherein the one or more memories store processor-executable code; and One or more processors, coupled to one or more memories and capable of operating individually or jointly to execute the code to enable the UE: Send a report to the network entity, the report including a reference signal identifier that identifies the reference signal; The reference signal identifier is mapped to at least one of a set of one or more transmission configuration indicator states associated with a transmission configuration indicator code point, according to the rules; wherein the transmission configuration indicator code point includes one or more of a downlink transmission configuration indicator state, an uplink transmission configuration indicator state, or a combined transmission configuration indicator state; and The at least one transmit configuration indicator state for the reference signal is selected by switching to or activating the at least one transmit configuration indicator state.

2. The UE of claim 1, wherein the rule defines the association between the at least one transmission configuration indicator state for the reference signal and the joint transmission configuration indicator state or the downlink transmission configuration indicator state, the downlink transmission configuration indicator state being associated with the unified transmission configuration indicator state.

3. The UE of claim 1, wherein the rule defines the association between the at least one transmission configuration indicator state for the reference signal and one or more of the joint transmission configuration indicator state, the downlink transmission configuration indicator state, or the uplink transmission configuration indicator state, which is associated with the unified transmission configuration indicator state.

4. The UE of claim 1, wherein the report includes an indication of the association between the reference signal and the uplink transmission configuration indicator state or the downlink transmission configuration indicator state.

5. The UE of claim 1, wherein the report includes a set of one or more reference signal identifiers, each of the set of one or more reference signal identifiers identifying a corresponding reference signal in the set of one or more reference signals, and wherein the rule defines the association between each corresponding reference signal and the downlink transmission configuration indicator state or the uplink transmission configuration indicator state.

6. The UE of claim 1, wherein each of the group of one or more transmission configuration indicator code points includes a single transmission configuration indicator state.

7. The UE of claim 6, wherein the rule defines the association between each of the set of one or more transmission configuration indicator code points and one or more of the downlink transmission configuration indicator state or the uplink transmission configuration indicator state.

8. The UE of claim 1, wherein each of the group of one or more transmission configuration indicator code points includes a transmission configuration indicator state group, and wherein the transmission configuration indicator state group includes one or more of the downlink transmission configuration indicator state or the uplink transmission configuration indicator state.

9. The UE of claim 8, wherein the report includes a plurality of reference signal identifier groups identifying a plurality of reference signal groups, and wherein the rule defines the association between each reference signal in each of the plurality of reference signal groups and a corresponding transmission configuration indicator code point in the set of one or more transmission configuration indicator code points.

10. The UE of claim 8, wherein the report includes a group of reference signal identifiers that identifies a group of reference signals, wherein the rule defines the association between the group of reference signal identifiers and a corresponding transmission configuration indicator code point in the group of one or more transmission configuration indicator code points, and wherein at least one reference signal identifier in the group of reference signal identifiers includes a dummy reference signal identifier, the dummy reference signal identifier being at least partially based on the corresponding transmission configuration indicator code point that includes the downlink transmission configuration indicator state or the uplink transmission configuration indicator state.

11. The UE of claim 1, wherein the report includes an indication of whether the reference signal is associated with switching to the state of the at least one transmit configuration indicator.

12. The UE of claim 1, wherein the report includes a second reference signal identifier identifying the second reference signal, and the one or more processors are further capable of operating individually or jointly to execute the code to cause the UE to: According to the rules, the second reference signal identifier is mapped to at least one second transmission configuration indicator state from the set of one or more transmission configuration indicator states associated with the transmission configuration indicator code point. Wherein the at least one transmission configuration indicator state for the reference signal corresponds to the downlink transmission configuration indicator state or the uplink transmission configuration indicator state, or The at least one transmission configuration indicator state for the reference signal corresponds to the downlink transmission configuration indicator state, and the at least one second transmission configuration indicator state for the second reference signal corresponds to the uplink transmission configuration indicator state.

13. The UE of claim 1, wherein the at least one transmit configuration indicator state includes quasi-co-location information, wherein the quasi-co-location information includes a first quasi-co-location type or a second quasi-co-location type, wherein the first quasi-co-location type is associated with one or more of Doppler frequency shift, Doppler spread, average delay, or average spread, and wherein the second quasi-co-location type is associated with a spatial filter, wherein the spatial filter is associated with at least one beam for wireless communication.

14. The UE of claim 13, wherein the reference signal is associated with the second quasi-co-address type, and wherein the state of the at least one transmit configuration indicator is based at least in part on the reference signal associated with the second quasi-co-address type.

15. The UE of claim 14, wherein the one or more processors are further capable of operating individually or jointly to execute the code to cause the UE to: The at least one transmission configuration indicator state in the set of one or more transmission configuration indicator states is selected according to the rules and at least in part based on the corresponding transmission configuration indicator state identifier associated with each transmission configuration indicator state in the set of one or more transmission configuration indicator states, wherein at least two transmission configuration indicator states in the set of one or more transmission configuration indicator states are associated with the second quasi-colocation type.

16. The UE of claim 1, wherein the one or more processors are further capable of operating individually or jointly to execute the code to cause the UE to: The reference signal is used as a quasi-co-location type reference signal and is independent of the state of the at least one transmit configuration indicator.

17. The UE of claim 16, wherein the synchronization signal block is quasi-co-located with the quasi-co-located type reference signal.

18. The UE of claim 16, wherein at least one channel state information reference signal is quasi-co-located with the reference signal.

19. A network entity, the network entity comprising: One or more memories, wherein the one or more memories store processor-executable code; and One or more processors, coupled to one or more memories and capable of operating individually or jointly to execute the code to enable the network entity: Receive a report from the user equipment (UE), the report including a reference signal identifier that identifies the reference signal; The reference signal identifier is mapped to at least one of a set of one or more transmission configuration indicator states associated with a transmission configuration indicator code point, according to the rules; wherein the transmission configuration indicator code point includes one or more of a downlink transmission configuration indicator state, an uplink transmission configuration indicator state, or a combined transmission configuration indicator state; and The at least one transmit configuration indicator state for the reference signal is selected by switching to or activating the at least one transmit configuration indicator state.

20. The network entity of claim 19, wherein the rule defines the association between the at least one transmission configuration indicator state for the reference signal and the joint transmission configuration indicator state or the downlink transmission configuration indicator state, the downlink transmission configuration indicator state being associated with the unified transmission configuration indicator state.

21. The network entity of claim 19, wherein the rule defines the association between the at least one transmission configuration indicator state for the reference signal and one or more of the joint transmission configuration indicator state, the downlink transmission configuration indicator state, or the uplink transmission configuration indicator state, which is associated with the unified transmission configuration indicator state.

22. The network entity of claim 19, wherein the report includes an indication of the association between the reference signal and the uplink transmission configuration indicator state or the downlink transmission configuration indicator state.

23. The network entity of claim 19, wherein the report includes a set of one or more reference signal identifiers, each of the set of one or more reference signal identifiers identifying a corresponding reference signal in the set of one or more reference signals, and wherein the rule defines the association between each corresponding reference signal and the downlink transmission configuration indicator state or the uplink transmission configuration indicator state.

24. The network entity of claim 19, wherein each of the group of one or more transmit configuration indicator code points includes a single transmit configuration indicator state.

25. The network entity of claim 24, wherein the rule defines the association between each of the set of one or more transmission configuration indicator code points and one or more of the downlink transmission configuration indicator state or the uplink transmission configuration indicator state.

26. The network entity of claim 19, wherein each of one or more transmit configuration indicator code points in a group includes a transmit configuration indicator state group, and wherein the transmit configuration indicator state group includes one or more of the downlink transmit configuration indicator state or the uplink transmit configuration indicator state.

27. The network entity of claim 26, wherein the report includes a plurality of reference signal identifier groups that identify a plurality of reference signal groups, and wherein the rule defines the association between each reference signal in each of the plurality of reference signal groups and a corresponding transmission configuration indicator code point in the set of one or more transmission configuration indicator code points.

28. The network entity of claim 26, wherein the report includes a group of reference signal identifiers that identifies a group of reference signals, wherein the rule defines the association between the group of reference signal identifiers and a corresponding transmission configuration indicator code point in the group of one or more transmission configuration indicator code points, and wherein at least one reference signal identifier in the group of reference signal identifiers includes a dummy reference signal identifier, the dummy reference signal identifier being based at least in part on the corresponding transmission configuration indicator code point that includes the downlink transmission configuration indicator state or the uplink transmission configuration indicator state.

29. A method for conducting wireless communication at a user equipment (UE), the method comprising: Send a report to the network entity, the report including a reference signal identifier that identifies the reference signal; The reference signal identifier is mapped to at least one of a set of one or more transmission configuration indicator states associated with a transmission configuration indicator code point, according to the rules; wherein the transmission configuration indicator code point includes one or more of a downlink transmission configuration indicator state, an uplink transmission configuration indicator state, or a combined transmission configuration indicator state; and The at least one transmit configuration indicator state for the reference signal is selected by switching to or activating the at least one transmit configuration indicator state.

30. A method for conducting wireless communication at a network entity, the method comprising: Receive a report from the user equipment (UE), the report including a reference signal identifier that identifies the reference signal; The reference signal identifier is mapped to at least one of a set of one or more transmission configuration indicator states associated with a transmission configuration indicator code point, according to the rules; wherein the transmission configuration indicator code point includes one or more of a downlink transmission configuration indicator state, an uplink transmission configuration indicator state, or a combined transmission configuration indicator state; and The at least one transmit configuration indicator state for the reference signal is selected by switching to or activating the at least one transmit configuration indicator state.

Images