Beam pair prediction and indication

Abstract

Methods, systems, and devices for wireless communication are described. A user equipment (UE) may transmit control signaling indicating parameters of a set of receive beams at the UE. The parameter may be based on an orientation of the UE and a hierarchical beamwidth configuration of the set of received beams. The UE may measure one or more reference signals using a first subset of receive beams of a first beam pair set based on the parameter. The UE may transmit one or more measurement reports for the first subset of receive beams based on measuring the one or more reference signals. In some examples, the network entity may send a message for activating a receive beam at the UE based on the prediction at the network entity and indicate a confidence level for the receive beam.

Description

Technical Field

[0001] The following relates to wireless communications, including beam pair prediction and indication. Background Art

[0002] Wireless communication systems are widely deployed to provide various types of communication content, such as voice, video, packet data, messaging, broadcast, etc. These systems may be able to 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, advanced LTE (LTE-A) systems, or LTE-A Pro systems) and fifth generation (5G) systems (which may be referred to as new radio (NR) systems). These systems may employ techniques such as code division multiple access (CDMA), time division multiple access (TDMA), frequency division multiple access (FDMA), orthogonal FDMA (OFDMA), or discrete Fourier transform spread orthogonal frequency division multiplexing (DFT-S-OFDM). A wireless multiple access communication system may include one or more base stations, each of which supports wireless communication of a communication device, which may be referred to as a user equipment (UE). Summary of the invention

[0003] The described techniques relate to improved methods, systems, devices, and apparatuses that support beam pair prediction and indication. For example, the described techniques provide enhanced predictive beam management. A user equipment (UE) may report receive beam information of the UE, including actual UE rotation and orientation information and hierarchical levels of receive beam width. For example, the UE may report beam pointing directions and beam widths of receive beams of the UE. The UE may measure and report measurements relative to a first number of receive beams or transmit-receive beam pairs. The measured and reported receive beams may be a subset of the total receive beams at the UE. In some examples, the UE may send recommendations for which beams the UE is to report measurements for and which beams should rely on network-side predictions.

[0004] A network entity may activate or indicate a transmit configuration indicator (TCI) state associated with a receive beam or a transmit-receive beam pair that the UE will use to receive a data message at a future time or future time window. For example, the network entity may activate a TCI state associated with a predicted receive beam that the UE will use to receive a downlink shared channel message. In some examples, the network entity may indicate a confidence level for a receive beam or a prediction for a receive beam. In some examples, the UE may perform measurements using a receive beam and report the measurements if the confidence level is below a threshold.

[0005] A method for wireless communication at a UE is described. The method may include: sending control signaling indicating a parameter of a set of receive beams at the UE, the parameter being based on an orientation of the UE and a hierarchical beamwidth configuration of the set of receive beams; measuring one or more reference signals using a first subset of receive beams of a first set of beam pairs based on the parameter; and sending one or more measurement reports for the first subset of receive beams based on measuring the one or more reference signals.

[0006] An apparatus for wireless communication at a UE is described. The apparatus may include a processor, a memory coupled to the processor, and instructions stored in the memory. The instructions may be executable by the processor to cause the apparatus to: send control signaling indicating a parameter of a set of receive beams at the UE, the parameter being based on an orientation of the UE and a hierarchical beamwidth configuration of the set of receive beams; measure one or more reference signals using a first subset of receive beams of a first set of beam pairs based on the parameter; and send one or more measurement reports for the first subset of receive beams based on measuring the one or more reference signals.

[0007] Another apparatus for wireless communication at a UE is described. The apparatus may include: means for sending control signaling indicating a parameter of a set of receive beams at the UE, the parameter being based on an orientation of the UE and a hierarchical beamwidth configuration of the set of receive beams; means for measuring one or more reference signals using a first subset of receive beams of a first set of beam pairs based on the parameter; and means for sending one or more measurement reports for the first subset of receive beams based on measuring the one or more reference signals.

[0008] A non-transitory computer-readable medium storing code for wireless communication at a UE is described. The code may include instructions executable by a processor to: send control signaling indicating a parameter of a set of receive beams at the UE, the parameter based on an orientation of the UE and a hierarchical beamwidth configuration of the set of receive beams; measure one or more reference signals using a first subset of receive beams of a first set of beam pairs based on the parameter; and send one or more measurement reports for the first subset of receive beams based on measuring the one or more reference signals.

[0009] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, sending the control signaling may include operations, features, components, or instructions for sending the control signaling indicating the beam direction of the receive beam set and the beam width of the receive beam set based on the orientation of the UE and the hierarchical beam width configuration.

[0010] Some examples of the methods, apparatus, and non-transitory computer-readable media described herein may also include operations, features, components, or instructions for sending a control message indicating a change in the orientation of the UE via uplink control information, a medium access control (MAC) control element (CE), or both.

[0011] Some examples of the methods, apparatus, and non-transitory computer-readable media described herein may also include operations, features, components, or instructions for sending a message that includes a recommendation for the UE to report measurements for an initial subset of received beams and for a network entity to predict measurements for a second subset of received beams.

[0012] Some examples of the methods, apparatus, and non-transitory computer-readable media described herein may also include operations, features, components, or instructions for receiving a control message from the network entity, the control message instructing the UE to report measurements for the first subset of received beams, wherein the one or more reference signals may be measured based on the control message for the first subset of received beams rather than the initial subset of received beams.

[0013] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, the first subset of receive beams may be the initial subset of receive beams.

[0014] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, sending the message may include operations, features, components, or instructions for sending the message via an uplink control information message, a MAC CE, or a radio resource control (RRC) message.

[0015] Some examples of the methods, apparatus, and non-transitory computer-readable media described herein may also include operations, features, components, or instructions for receiving a message based on one or more measurement reports that activates a TCI state for a receive beam of a beam pair to receive a downlink shared channel message.

[0016] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, receiving the message indicating the TCI state may include operations, features, components, or instructions for receiving the message indicating a confidence level of the receive beam.

[0017] Some examples of the methods, apparatus, and non-transitory computer-readable media described herein may also include operations, features, components, or instructions for: measuring a second one or more reference signals using the receive beam based on the confidence level of the receive beam failing to meet a threshold; and sending a measurement report for the receive beam based on measuring the second one or more reference signals.

[0018] Some examples of the methods, apparatus, and non-transitory computer-readable media described herein may also include operations, features, components, or instructions for receiving control signaling indicating a downlink reference signal confidence level.

[0019] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, the confidence level for the receive beam can be based on a standard deviation of a predicted average reference signal received power for the receive beam.

[0020] In some examples of the methods, apparatus, and non-transitory computer-readable media used herein, the message includes a time window for communicating using the receive beam of the beam pair.

[0021] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, the parameters include at least a first set of parameters for the wide beam set and at least a second set of parameters for the narrow beam set, and one or more narrow beams may be superimposed with the wide beam.

[0022] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, the orientation of the UE may be indicated based on a local coordinate system format or a global coordinate system format, or both.

[0023] A method of wireless communication at a network entity is described. The method may include: receiving control signaling indicating a parameter of a set of receive beams at a UE, the parameter being based on an orientation of the UE and a hierarchical beamwidth configuration of the set of receive beams; transmitting one or more reference signals using a first subset of transmit beams of a first set of beam pairs based on the parameter; and receiving one or more measurement reports for the first subset of receive beams based on the one or more reference signals.

[0024] An apparatus for wireless communication at a network entity is described. The apparatus may include a processor, a memory coupled to the processor, and instructions stored in the memory. The instructions may be executable by the processor to cause the apparatus to: receive control signaling indicating a parameter of a set of receive beams at a UE, the parameter being based on an orientation of the UE and a hierarchical beamwidth configuration of the set of receive beams; transmit one or more reference signals using a first subset of transmit beams of a first set of beam pairs based on the parameter; and receive one or more measurement reports for the first subset of receive beams based on the one or more reference signals.

[0025] Another apparatus for wireless communication at a network entity is described. The apparatus may include: means for receiving control signaling indicating a parameter of a set of receive beams at a UE, the parameter being based on an orientation of the UE and a hierarchical beamwidth configuration of the set of receive beams; means for transmitting one or more reference signals using a first subset of transmit beams of a first set of beam pairs based on the parameter; and means for receiving one or more measurement reports for the first subset of receive beams based on the one or more reference signals.

[0026] A non-transitory computer-readable medium storing code for wireless communication at a network entity is described. The code may include instructions executable by a processor to: receive control signaling indicating a parameter of a set of receive beams at a UE, the parameter being based on an orientation of the UE and a hierarchical beamwidth configuration of the set of receive beams; transmit one or more reference signals using a first subset of transmit beams of a first set of beam pairs based on the parameter; and receive one or more measurement reports for the first subset of receive beams based on the one or more reference signals.

[0027] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, receiving the control signaling may include operations, features, components, or instructions for receiving the control signaling indicating the beam direction of the receive beam set and the beam width of the receive beam set based on the orientation of the UE and the hierarchical beam width configuration.

[0028] Some examples of the methods, apparatus, and non-transitory computer-readable media described herein may also include operations, features, components, or instructions for receiving a control message indicating a change in orientation of the UE via uplink control information, a MAC CE, or both.

[0029] Some examples of the methods, apparatus, and non-transitory computer-readable media described herein may also include operations, features, components, or instructions for receiving a message that includes a recommendation for the UE to report measurements for an initial subset of received beams and for the network entity to predict measurements for a second subset of received beams.

[0030] Some examples of the methods, apparatus, and non-transitory computer-readable media described herein may also include operations, features, components, or instructions for sending a control message to the UE, the control message instructing the UE to report measurements for the first subset of received beams, wherein based on the control message, the one or more measurement reports may be for the first subset of received beams instead of the initial subset of received beams.

[0031] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, the first subset of receive beams may be the initial subset of receive beams.

[0032] Some examples of the methods, apparatus, and non-transitory computer-readable media described herein may also include operations, features, components, or instructions for sending a message based on the one or more measurement reports that activates the TCI state for the receive beam of the beam pair for the UE to receive a downlink shared channel message.

[0033] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, sending the message indicating the TCI state may include operations, features, components, or instructions for sending the message indicating a confidence level of the receive beam.

[0034] Some examples of the methods, apparatuses, and non-transitory computer-readable media described herein may also include operations, features, components, or instructions for receiving a measurement report for the receive beam based on a confidence level of the receive beam failing to satisfy a threshold.

[0035] Some examples of the methods, apparatus, and non-transitory computer-readable media described herein may also include operations, features, components, or instructions for receiving control signaling indicating a downlink reference signal confidence level.

[0036] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, the confidence level for the receive beam can be based on a standard deviation of a predicted average reference signal received power for the receive beam.

[0037] In some examples of the methods, apparatus and non-transitory computer-readable media described herein, the message includes a time window for the UE to communicate using the receive beam of the beam pair.

[0038] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, the parameters include at least a first set of parameters for the wide beam set and at least a second set of parameters for the narrow beam set, and one or more narrow beams may be superimposed with the wide beam. BRIEF DESCRIPTION OF THE DRAWINGS

[0039] Figure 1 An example of a wireless communication system supporting beam pair prediction and indication according to one or more aspects of the present disclosure is illustrated.

[0040] Figure 2 An example of a wireless communication system supporting beam pair prediction and indication according to one or more aspects of the present disclosure is illustrated.

[0041] Figure 3Examples of supporting beam pair prediction and indicated receive beam orientations according to one or more aspects of the present disclosure are illustrated.

[0042] Figure 4 An example of a receive beam superposition configuration supporting beam pair prediction and indication according to one or more aspects of the present disclosure is illustrated.

[0043] Figure 5 An example of a process flow supporting beam pair prediction and indication according to one or more aspects of the present disclosure is illustrated.

[0044] Figure 6 and Figure 7 A block diagram of a device supporting beam pair prediction and indication according to one or more aspects of the present disclosure is shown.

[0045] Figure 8 A block diagram of a communication manager supporting beam pair prediction and indication according to one or more aspects of the present disclosure is shown.

[0046] Fig. 9 A diagram of a system including a device supporting beam pair prediction and indication in accordance with one or more aspects of the present disclosure is shown.

[0047] Fig.10 and Fig.11 A block diagram of a device supporting beam pair prediction and indication according to one or more aspects of the present disclosure is shown.

[0048] Fig.12 A block diagram of a communication manager supporting beam pair prediction and indication according to one or more aspects of the present disclosure is shown.

[0049] Fig.13 A diagram of a system including a device supporting beam pair prediction and indication in accordance with one or more aspects of the present disclosure is shown.

[0050] Figures 14 to 17 A flow chart illustrating a method of supporting beam pair prediction and indication according to one or more aspects of the present disclosure is shown. DETAILED DESCRIPTION

[0051] A user equipment (UE) and a network entity may communicate using a beam pair. For example, the network entity may use a transmit beam of a beam pair to transmit to the UE, and the UE may use a receive beam of the beam pair to receive signaling from the network entity. Some systems may use artificial intelligence (e.g., machine learning) to support predictive beam management. For example, instead of using measurements to identify the transmit beam and receive beam of a beam pair, a network entity or UE may predict the beam quality of a transmit beam or receive beam to identify high-quality transmit beams and receive beams for the beam pair. The UE may use one or more receive beams at the UE to measure a reference signal from the network entity, and send a measurement report to the network entity based on measuring the reference signal using these receive beams. The network entity may predict a beam pair based on measurements reported from the UE, and activate one or more receive beams or beam pairs at the UE based on the predictions and measurements.

[0052] The wireless communication system described herein supports techniques for providing information to the UE to assist in predictive beam management. For example, the UE may indicate orientation information of a receive beam at the UE. The UE may report receive beam information at the UE, such as the number of beams, beam width, and hierarchical beam information (e.g., information associated with the superposition of beams of different beam widths). The UE may report relative beam pointing directions and beam widths based on the orientation information of the UE. For example, the UE may report beam pointing directions based on the rotation of the UE. In some cases, the UE may send signaling indicating updated orientation information of the UE, such as if the orientation of the UE changes, and therefore the direction of the receive beam of the UE changes.

[0053] In some examples, the UE may send signaling indicating a recommendation for which beams should be measured by the UE and which beams should have measurements predicted by the network entity. For example, among the receive beams reported at the UE, the UE may recommend that a first portion of the receive beams be measured and reported by the UE, and the UE may recommend that the network entity predict measurements for a second portion of the receive beams. In one example, the UE may recommend that the UE measure and report measurements for wide beams at the UE, and the network entity predict measurements for narrow beams at the UE.

[0054] A network entity may send control signaling to activate a transmit configuration indicator (TCI) state for a predicted receive beam or a predicted transmit and receive beam pair at a UE. In some examples, the network entity may indicate a confidence level for the predicted receive beam or beam pair. For example, the network entity may determine a confidence level for an activated TCI state based on measurements and predictions for a receive beam or beam pair associated with an activated TCI state. The confidence level may, for example, correspond to the likelihood that a receive beam or beam pair will provide quality signaling for downlink signaling. If the confidence level for a receive beam is below a threshold, the UE may perform measurements using the receive beam or beam pair and send a measurement report indicating the measurements to the network entity. By sending the measurement report, the network entity may determine whether the receive beam or beam pair provides communications of sufficient quality. For example, if the reported measurement is below a threshold, the network entity may change the active TCI state or receive beam at the UE, or if the reported measurement meets the threshold, the network entity may maintain the active TCI state or receive beam at the UE.

[0055] First, various aspects of the disclosure are described in the context of a wireless communication system. Various aspects of the disclosure are further illustrated by and described with reference to apparatus diagrams, system diagrams, and flow diagrams related to beam pair prediction and indication.

[0056] Figure 1 An example of a wireless communication system 100 supporting beam pair prediction and indication according to one or more aspects of the present disclosure is illustrated. The wireless communication system 100 may include one or more network entities 105, one or more UEs 115, and a core network 130. In some examples, the wireless communication system 100 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 according to other systems and radio technologies (including future systems and radio technologies not explicitly mentioned herein).

[0057] The network entities 105 may be dispersed throughout a geographic area to form the wireless communication system 100, and may include devices in different forms or with different capabilities. In various examples, the network entities 105 may be referred to as network elements, mobility elements, radio access network (RAN) nodes, or network equipment, among other names. In some examples, the network entities 105 and the UE 115 may communicate wirelessly via one or more communication links 125 (e.g., radio frequency (RF) access links). For example, the network entity 105 may support a coverage area 110 (e.g., a geographic coverage area) within which the UE 115 and the network entity 105 may establish one or more communication links 125. The coverage area 110 may be an example of a geographic area within which the network entity 105 and the UE 115 may support signal communications according to one or more radio access technologies (RATs).

[0058] The UEs 115 may be dispersed throughout the coverage area 110 of the wireless communication system 100, and each UE 115 may be stationary or mobile, or both stationary and mobile at different times. The UEs 115 may be devices in different forms or with different capabilities. Figure 1 Some example UEs 115 are illustrated in FIG. 1. The UEs 115 described herein may be capable of supporting communication with various types of devices, such as Figure 1 Communicate with other UEs 115 or network entities 105) as shown.

[0059] As described herein, a node of the wireless communication system 100 (which may be referred to as a network node or a 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, an apparatus, a device, a computing system, one or more components, or another suitable processing entity configured to perform any of the techniques described herein. For example, the node may be a UE 115. As another example, the node may be a 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 a UE 115, the second node may be a network entity 105, and the third node may be a UE 115. In another aspect of this example, the first node may be a UE 115, the second node may be a network entity 105, and the third node may be a network entity 105. In yet other aspects of this example, the first node, the second node, and the third node may be different relative to these examples. Similarly, references to UE 115, network entity 105, apparatus, device, computing system, etc. may include disclosure of UE 115, network entity 105, apparatus, device, computing system, etc. as nodes. For example, a disclosure that UE 115 is configured to receive information from network entity 105 also discloses that the first node is configured to receive information from a second node.

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

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

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

[0063] The functional split between 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, and any combination thereof) are performed at CU 160, DU 165, or RU 170. For example, a functional split of a protocol stack can be employed between CU 160 and DU 165, such that CU 160 can support one or more layers of a protocol stack and DU 165 can support one or more different layers of a protocol stack. In some examples, CU 160 can host higher protocol layer (e.g., layer 3 (L3), layer 2 (L2)) functionality and signaling (e.g., radio resource control (RRC), service data adaptation protocol (SDAP), packet data convergence protocol (PDCP)). The CU 160 may be connected to one or more DUs 165 or RUs 170, and the one or more DUs 165 or RUs 170 may 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 may each be at least partially controlled by the CU 160. Additionally or alternatively, a functional split of the protocol stack may be employed between the DUs 165 and RUs 170, such that the DUs 165 may support one or more layers of the protocol stack, and the RUs 170 may support one or more different layers of the protocol stack. The DUs 165 may support one or more different cells (e.g., via one or more RUs 170). In some cases, the functional split between CU 160 and DU 165 or between DU 165 and RU 170 may be within the protocol layer (e.g., some functions of the protocol layer may be performed by one of CU 160, DU 165, or RU 170, while other functions of the protocol layer are performed by the other of CU 160, DU 165, or RU 170). CU 160 may be further functionally split into CU control plane (CU-CP) functions and CU user plane (CU-UP) functions. CU 160 may be connected to one or more DUs 165 via midhaul communication links 162 (e.g., F1, F1-c, F1-u), and DU 165 may be connected to one or more RUs 170 via fronthaul communication links 168 (e.g., open fronthaul (FH) interface). In some examples, midhaul communication link 162 or fronthaul communication link 168 may be implemented based on interfaces (eg, channels) between layers of a protocol stack supported by respective network entities 105 that communicate via those communication links.

[0064] In a wireless communication system (e.g., wireless communication system 100), infrastructure and spectrum resources for radio access may support wireless backhaul link capabilities to supplement wired backhaul connections, thereby providing an IAB network architecture (e.g., to a core network 130). In some cases, in an IAB network, one or more network entities 105 (e.g., IAB nodes 104) may be partially controlled by each other. One or more IAB nodes 104 may be referred to as donor entities or IAB donors. One or more DUs 165 or one or more RUs 170 may be controlled in part by one or more CUs 160 associated with a donor network entity 105 (e.g., a donor base station 140). One or more donor network entities 105 (e.g., IAB donors) may communicate with one or more additional network entities 105 (e.g., IAB nodes 104) via supported access and backhaul links (e.g., backhaul communication links 120). The IAB node 104 may include an IAB mobile terminal (IAB-MT) controlled (e.g., scheduled) by a coupled IAB donor's DU 165. The IAB-MT may include an independent set of antennas for relaying communications with the UE 115, or may share the same antennas of the IAB node 104 (e.g., of the RU 170) for access via the DU 165 of the IAB node 104 (e.g., referred to as a virtual IAB-MT (vIAB-MT)). In some examples, the IAB node 104 may include a DU 165 that supports 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., one or more IAB nodes 104 or components of the IAB node 104) may be configured to operate according to the techniques described herein.

[0065] For example, an access network (AN) or RAN may include an access node (e.g., an IAB donor), communications between an IAB node 104, and one or more UEs 115. The IAB donor may facilitate connectivity between the core network 130 and the AN (e.g., via a wired or wireless connection to the core network 130). That is, the IAB donor may refer to a RAN node that has a wired or wireless connection to the core network 130. The IAB donor may include a CU 160 and at least one DU 165 (e.g., and RU 170), in which case the CU 160 may communicate with the core network 130 via an interface (e.g., a backhaul link). The IAB donor and the IAB node 104 may communicate via an F1 interface according to a protocol that defines signaling messages (e.g., an F1 AP protocol). Additionally or alternatively, CU 160 may communicate with the core network via an interface (which may be an example of a portion of a backhaul link) and may communicate with other CUs 160 (e.g., CUs 160 associated with alternative IAB donors) via an Xn-C interface (which may be an example of a portion of a backhaul link).

[0066] An IAB node 104 may refer to a RAN node that provides IAB functionality (e.g., access for UE 115, wireless self-backhaul capabilities, etc.). DU 165 may act as a distributed scheduling node toward child nodes associated with IAB node 104, and IAB-MT may act as a scheduled node toward a parent node associated with IAB node 104. That is, an IAB donor may be referred to as a parent node that communicates with one or more child nodes (e.g., an IAB donor may relay for UE transmissions through one or more other IAB nodes 104). Additionally or alternatively, depending on the relay chain or configuration of the AN, an IAB node 104 may also be referred to as a parent node or child node of other IAB nodes 104. Thus, the IAB-MT entity of the IAB node 104 may provide a Uu interface for the child IAB node 104 to receive signaling from the parent IAB node 104, and a DU interface (eg, DU 165) may provide a Uu interface for the parent IAB node 104 to signal the child IAB node 104 or the UE 115.

[0067] For example, the IAB node 104 may be referred to as a parent node supporting communications for a child IAB node or as a child IAB node associated with an IAB donor, or both. The IAB donor may include a CU 160 having a wired or wireless connection (e.g., backhaul communication link 120) to the core network 130, and may act as a parent node of the IAB node 104. For example, the DU 165 of the IAB donor may relay the transmission to the UE 115 through the IAB node 104, or may directly signal the transmission to the UE 115, or both. The CU 160 of the IAB donor may signal the IAB node 104 via the F1 interface that the communication link is established, and the IAB node 104 may schedule the transmission (e.g., the transmission relayed from the IAB donor to the UE 115) through the DU 165. That is, data may be relayed to and from the IAB node 104 via signaling via the NR Uu interface of the MT to the IAB node 104. Communications with the IAB node 104 may be scheduled by the DU 165 of the IAB donor, and communications with the IAB node 104 may be scheduled by the DU 165 of the IAB node 104 .

[0068] Where the techniques described herein are applied to the context of a decomposed RAN architecture, one or more components of the decomposed RAN architecture may be configured to support beam pair prediction and indication as 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., IAB node 104, DU 165, CU 160, RU 170, RIC 175, SMO 180).

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

[0070] The UE 115 described herein may be capable of communicating with various types of devices, such as other UEs 115, which may sometimes act as relays, as well as network entities 105 and network equipment including macro eNBs or gNBs, small cell eNBs or gNBs, or relay base stations, among other examples. Figure 1 shown.

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

[0072] In some examples (such as in a carrier aggregation configuration), a carrier may also have acquisition signaling or control signaling that coordinates the operation of other carriers. A carrier may be associated with a frequency channel (e.g., an Evolved Universal Mobile Telecommunications System Terrestrial Radio Access (E-UTRA) Absolute RF Channel Number (EARFCN)) and may be identified according to a channel raster for discovery by UE 115. A carrier may operate in a stand-alone mode, in which case initial acquisition and connection may be performed by UE 115 via the carrier, or a carrier may operate in a non-stand-alone mode, in which case the connection is anchored using a different carrier (e.g., a different carrier of the same or different radio access technology).

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

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

[0075] The signal waveform transmitted via the carrier may include multiple subcarriers (e.g., using multi-carrier modulation (MCM) techniques, such as orthogonal frequency division multiplexing (OFDM) or discrete Fourier transform spread OFDM (DFT-S-OFDM)). In a system using MCM techniques, a resource element may refer to a resource of one symbol period (e.g., the duration of one modulation symbol) and one subcarrier, in which case the symbol period and the 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 coding rate of the modulation scheme, or both), so that a relatively high number of resource elements (e.g., in the transmission duration) and a relatively high order modulation scheme may correspond to a relatively high communication rate. Wireless communication resources may refer to a combination of RF spectrum resources, time resources, and spatial resources (e.g., spatial layers, beams), and the use of multiple spatial resources may increase the data rate or data integrity of communications with UE 115.

[0076] One or more parameter sets for a carrier may be supported, and the parameter sets may include subcarrier spacing (Δf) and cyclic prefixes. A carrier may be divided into one or more BWPs with the same or different parameter sets. In some examples, a UE 115 may be configured with multiple BWPs. In some examples, a single BWP for a carrier may be active at a given time, and communications of a UE 115 may be constrained to one or more active BWPs.

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

[0078] 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, the frame may be divided into subframes (e.g., in the time domain), and each subframe may be further 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 added before each symbol period). In some wireless communication systems 100, the time slot may be further divided into a plurality of 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., N f The duration of a symbol period may depend on the subcarrier spacing or the operating band.

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

[0080] Physical channels may be multiplexed according to various techniques in order to communicate using a carrier. Physical control channels and physical data channels may be multiplexed, for example, using one or more of a time division multiplexing (TDM) technique, a frequency division multiplexing (FDM) technique, or a hybrid TDM-FDM technique for signaling via a downlink carrier. A control region (e.g., a control resource set (CORESET)) of a physical control channel may be defined by a set of symbol periods and may extend across a system bandwidth or a subset of a system bandwidth of a carrier. One or more control regions (e.g., CORESETs) may be configured for a set of UEs 115. For example, one or more UEs in UE 115 may monitor or search a control region for control information according to one or more search space sets, and each search space set may include one or more control channel candidates in one or more aggregation levels arranged in a cascaded manner. The aggregation level of a control channel candidate may 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 sets may include a common search space set configured for transmitting control information to multiple UEs 115 , and a UE-specific search space set for transmitting control information to a specific UE 115 .

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

[0082] A macro cell generally covers a relatively large geographic area (e.g., several kilometers in radius) and may allow unrestricted access to UEs 115 that have service subscriptions with a network provider that supports the macro cell. A small cell may be associated with a lower power network entity 105 (e.g., a lower power base station 140) (compared to a macro cell), and the small cell may operate using the same or different (e.g., licensed, unlicensed) frequency band as the macro cell. A small cell may provide unrestricted access to UEs 115 that have service subscriptions with a network provider, or may provide restricted access to UEs 115 associated with a small cell (e.g., UEs 115 in a closed subscriber group (CSG), UEs 115 associated with users in a home or office). A network entity 105 may support one or more cells, and may also use one or more component carriers to support communications via one or more cells.

[0083] In some examples, a carrier may support multiple cells, and different cells may be configured according to different protocol types (e.g., MTC, narrowband IoT (NB-IoT), enhanced mobile broadband (eMBB)) that may provide access to different types of devices.

[0084] In some examples, the network entities 105 (e.g., base stations 140, RUs 170) may be mobile and thus provide communication coverage for mobile geographic coverage areas 110. In some examples, different coverage areas 110 associated with different technologies may overlap, but the different coverage areas 110 may be supported by the same network entity 105. In some other examples, overlapping coverage areas 110 associated with different technologies may be supported by different network entities 105. The wireless communication system 100 may include, for example, a heterogeneous network in which different types of network entities 105 provide coverage for respective coverage areas 110 using the same or different radio access technologies.

[0085] The wireless communication system 100 may support synchronous or asynchronous operation. For synchronous operation, the network entities 105 (e.g., base stations 140) may have similar frame timing, and transmissions from different network entities 105 may be approximately aligned in time. For asynchronous operation, the network entities 105 may have different frame timing, and in some examples, transmissions from different network entities 105 may not be aligned in time. The techniques described herein may be used for either synchronous operation or asynchronous operation.

[0086] Some UEs 115, such as MTC or IoT devices, may be low-cost or low-complexity devices and may provide automated communication between machines (e.g., via machine-to-machine (M2M) communication). M2M communication or MTC may refer to data communication technology that allows devices to communicate with each other or with a network entity 105 (e.g., base station 140) without human intervention. In some examples, M2M communication or MTC may include communication from devices that integrate sensors or meters to measure or capture information and relay such information to a central server or application that uses the information or presents the information to a person interacting with the application. Some UEs 115 may be designed to collect information or implement automated behavior of machines or other devices. Examples of applications for MTC devices include: smart metering, inventory monitoring, water level monitoring, equipment monitoring, health care monitoring, field survival monitoring, weather and geographic event monitoring, fleet management and tracking, remote security sensing, physical access control, and transaction-based commercial charging.

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

[0088] The wireless communication system 100 may be configured to support ultra-reliable communication or low-latency communication or various combinations thereof. For example, the wireless communication system 100 may be configured to support ultra-reliable low-latency communication (URLLC). The UE 115 may be designed to support ultra-reliable, low-latency or critical functions. Ultra-reliable communication may include private communication 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 prioritization of services, and such services may be used for public safety or general commercial applications. The terms ultra-reliable, low-latency and ultra-reliable low-latency may be used interchangeably herein.

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

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

[0091] The core network 130 may provide user authentication, access authorization, tracking, Internet Protocol (IP) connectivity, and other access, routing, or mobility functions. The core network 130 may 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), an 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), a packet data network (PDN) gateway (P-GW), or a user plane function (UPF)) for routing packets or interconnecting to an external network. The control plane entity may manage non-access stratum (NAS) functions, such as mobility, authentication, and bearer management of UE 115 served by a network entity 105 (e.g., a base station 140) associated with the core network 130. User IP packets may be delivered through the user plane entity, which may provide IP address allocation and other functions. The user plane entity may be connected to an IP service 150 for one or more network operators. IP services 150 may include access to the Internet, an intranet, an IP Multimedia Subsystem (IMS), or packet-switched streaming services.

[0092] The wireless communication system 100 may operate using one or more frequency bands that may be in the range of 300 megahertz (MHz) to 300 gigahertz (GHz). Generally speaking, the region from 300 MHz to 3 GHz is referred to as the ultra-high frequency (UHF) region or decimeter band because the wavelength ranges from about 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 may be sufficient to penetrate structures so that macro cells provide services to UEs 115 located indoors. Communications using UHF waves may be associated with smaller antennas and shorter ranges (e.g., less than 100 kilometers) than communications using the lower frequencies and longer wavelengths of the high frequency (HF) or very high frequency (VHF) portions of the spectrum below 300 MHz.

[0093] The wireless communication system 100 may also operate using a super high frequency (SHF) region that may be in the range of 3 GHz to 30 GHz (also referred to as a centimeter band) or an extremely high frequency (EHF) region that uses a spectrum (e.g., from 30 GHz to 300 GHz) (also referred to as a millimeter band). In some examples, the wireless communication system 100 may support millimeter wave (mmW) communications between UE 115 and network entity 105 (e.g., base station 140, RU 170), and the EHF antenna of the corresponding device may be smaller and closer than the UHF antenna. In some examples, such technology may facilitate the use of antenna arrays within the device. However, the propagation of EHF transmissions may be affected by greater attenuation and shorter range than SHF or UHF transmissions. The technology disclosed herein may be adopted across transmissions using one or more different frequency regions, and the use of frequency bands specified across these frequency regions may vary by country or regulatory agency.

[0094] The wireless communication system 100 may utilize both licensed RF spectrum bands and unlicensed RF spectrum bands. For example, the wireless communication system 100 may use unlicensed bands (such as the 5 GHz Industrial, Scientific, and Medical (ISM) band) to adopt license assisted access (LAA), LTE unlicensed (LTE-U) radio access technology, or NR technology. When operating using unlicensed RF spectrum bands, devices such as network entity 105 and UE 115 may use carrier sensing for conflict detection and avoidance. In some examples, operations performed using unlicensed bands may be based on carrier aggregation configuration in combination with component carriers (e.g., LAA) that operate using licensed bands. Operations performed using unlicensed spectrum may include downlink transmissions, uplink transmissions, P2P transmissions, or D2D transmissions, and the like.

[0095] The 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 technologies such as transmit diversity, receive diversity, multiple-input multiple-output (MIMO) communication, or beamforming. The antennas of the network entity 105 or UE 115 may be located in one or more antenna arrays or antenna panels, which may support MIMO operations 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, antennas or antenna arrays associated with the network entity 105 may be located at different geographical locations. The network entity 105 may include an antenna array having a set of antenna ports of multiple rows and columns that the network entity 105 can use to support beamforming for communications with the UE 115. Similarly, the UE 115 may include one or more antenna arrays that may support various MIMO or beamforming operations. Additionally or alternatively, the antenna panel may support RF beamforming for signals sent via the antenna ports.

[0096] The network entity 105 or UE 115 may use MIMO communication to utilize multipath signal propagation and improve spectral efficiency by sending or receiving multiple signals via different spatial layers. Such a technology may be referred to as spatial multiplexing. The multiple signals may be sent, 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 for channel measurement and reporting. MIMO technologies include: single-user MIMO (SU-MIMO), in which multiple spatial layers are sent to the same receiving device; and multi-user MIMO (MU-MIMO), in which multiple spatial layers are sent to multiple devices.

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

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

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

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

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

[0102] The wireless communication system 100 may be a packet-based network that operates according to a layered protocol stack. In the user plane, communications at the bearer or PDCP layer may be IP-based. The RLC layer may perform packet segmentation and reassembly to communicate via logical channels. The MAC layer may perform priority handling and multiplexing of logical channels into transport channels. The MAC layer may also implement error detection techniques, error correction techniques, or both to support retransmissions to improve link efficiency. In the control plane, the RRC layer may provide the establishment, configuration, and maintenance of an RRC connection that supports radio bearers of user plane data between the UE 115 and the network entity 105 or the core network 130. The PHY layer may map transport channels to physical channels.

[0103] UE 115 and network entity 105 may support retransmission of data to increase the possibility of successfully receiving data. Hybrid automatic repeat request (HARQ) feedback is a technology for increasing the possibility of correctly receiving data via a communication link (e.g., communication link 125, D2D communication link 135). HARQ may include a combination of error detection (e.g., using a cyclic redundancy check (CRC)), forward error correction (FEC), and retransmission (e.g., automatic repeat request (ARQ)). HARQ can improve the throughput at the MAC layer under 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 may provide HARQ feedback in a specific time slot for data received via a previous symbol in the time slot. In some other examples, the device may provide HARQ feedback in a subsequent time slot or according to some other time interval.

[0104] The wireless communication system 100 may support wireless communication between a UE 115 and a network entity 105 using a beam pair. For example, the network entity 105 may use a transmit beam to transmit to the UE 115, and the UE 115 may use a receive beam to receive signaling from the network entity 105. In some systems, the UE 115 and the network entity 105 may select or be configured with a receive beam of the beam pair based on measuring a plurality of receive beams at the UE 115. For example, the network entity 105 may use a transmit beam to transmit a reference signal to the UE 115, and the UE 115 may use the receive beam of the UE 115 to perform a plurality of measurements to identify the best (e.g., strongest) receive beam for the beam pair.

[0105] For example, the UE 115 may be configured with a reporting number corresponding to the number of SSBs for which the UE 115 is to measure and provide measurements. For example, the UE 115 may report a reference signal received power (RSRP) measurement or a signal-to-interference ratio (SINR) measurement or both (e.g., individually or jointly) for one or more SSBs or one or more CSI-RSs or both. The UE 115 may report measurements of a configured number of signals (e.g., SSBs or CSI-RSs) for each CSI reporting configuration. The UE 115 may report RSRP measurements for the strongest SSB. In some cases, the UE 115 may report RSRP measurements for other SSBs (e.g., the second strongest SSB measurements), in some cases using a lower granularity than the RSRP measurements for the strongest SSB. Additionally or alternatively, the UE 115 may report the SINR of the strongest SSB or CSI-RS. Similarly, in some cases, UE 115 may report SINR measurements for other SSBs or CSI-RS (e.g., the next strongest SSB or CSI-RS measurements), in some cases using a lower granularity than the SINR measurements for the strongest SSB or CSI-RS.

[0106] Some systems may support techniques for predictive beam management. For example, network entity 105 or UE 115 or both may use a machine learning model to predict unmeasured beam quality. In some examples, network entity 105 and UE 115 or both may predict future beam blockages or failures. In some examples, predicting future transmit beam quality may be based on the movement speed or trajectory of UE 115, receive beams configured or supported by UE 115, interference, and other factors.

[0107] In one example, the network entity 105 may perform time domain beam prediction. The network entity 105 may input a time series of layer 1 (L1) RSRP measurements for a set of transmit beams (e.g., of the network entity 105) to a machine learning model. The machine learning model may output predicted L1 RSRP measurements for the transmit beams, predicted candidate beams for an upcoming time period, and future beam blockages or beam failures. In some examples, the L1 RSRP measurements may be reported by the UE 115. Similarly, the network entity 105 may perform receive beam prediction based on the measurements reported by the UE 115.

[0108] The wireless communication system 100 and the wireless communication described herein support techniques for enhanced predictive beam management. For example, the wireless communication system 100 may support a network entity assisted beam pair prediction framework. The UE 115 may report the receive beam information of the UE 115, including the actual UE rotation and orientation information and the hierarchical level of the receive beam width. For example, the UE 115 may report the beam pointing direction and beam width of the receive beam of the UE 115. The UE 115 may measure and report RSRP measurements and SINR measurements relative to a first number of transmit-receive beam pairs. The measured and reported receive beams may be a subset of the total receive beams at the UE 115 based on a recommendation from the UE 115 or a configuration received from the network entity 105, or both.

[0109] The network entity 105 may activate or indicate a TCI state associated with a receive beam or a transmit-receive beam pair that the UE 115 will use to receive a data message at a future time or future time window. For example, the network entity 105 may activate a TCI state associated with a predicted receive beam that the UE 115 will use to receive a downlink shared channel message. In some examples, the network entity 105 may indicate a confidence level for the receive beam or a prediction for the receive beam. In some examples, the UE 115 may perform measurements using the receive beam and report the measurements if the confidence level is below a threshold.

[0110] Figure 2 An example of a wireless communication system 200 supporting beam pair prediction and indication according to one or more aspects of the present disclosure is illustrated. The wireless communication system 200 may include a UE 115-a and a network entity 105-a, which may be as described in reference Figure 1 Corresponding examples of UE 115 and network entity 105 are described. UE 115-a and network entity 105-a can communicate using beamforming signaling. For example, network entity 105-a can use one or more transmit beams 205 (such as transmit beam 205-a, transmit beam 205-b, or transmit beam 205-c) to transmit to UE 115-a. UE 115-a can use one or more receive beams (e.g., one or more narrow receive beams 210 or one or more wide receive beams 215 or both) to receive signaling.

[0111] UE 115-a may send signaling indicating receive beam information 220 to network entity 105-a. Receive beam information 220 may include relative beam pointing directions and beam widths of receive beams at UE 115-a. For example, UE 115-a may report beam pointing directions and beam widths of narrow receive beams 210 (e.g., narrow receive beam 210-a, narrow receive beam 210-b, and narrow receive beam 210-c) and wide receive beam 215 of UE 115-a. Receive beam information 220 may include hierarchical receive beam information, such as information about how to configure antenna panels at UE 115-a and how to support receive beams of different widths at each antenna panel. In some examples, UE 115-a may report receive beam information semi-persistently, such as via RRC signaling. For example, UE 115-a may send an RRC message including receive beam information 220 to network entity 105-a.

[0112] In some examples, receive beam information 220 may include orientation information of UE 115-a or receive beam of UE 115-a, or both. For example, UE 115-a may report the real-time absolute beam pointing direction and beam width of the receive beam of UE 115-a. In some examples, the real-time absolute beam pointing direction may be indicated according to a local coordinate system (LCS) or a global coordinate system (GCS) format. For example, UE 115-a may indicate a narrow receive beam 210-b, as well as the beam width and real-time beam pointing direction of other receive beams at UE 115-a. In some examples, UE 115-a may dynamically indicate receive beam information 220. For example, UE 115-a may send receive beam information 220 via a MAC control element (CE) or uplink control information, or both. In some cases, UE 115-a may update the absolute pointing direction and beamwidth of the receive beam at UE 115-a (e.g., periodically or dynamically).

[0113] In some examples, UE 115-a may semi-persistently indicate receive beam information 220 (e.g., via RRC signaling) and dynamically send updates to the UE orientation. For example, UE 115-a may report a receive beam pointing direction via RRC signaling, and UE 115-a may dynamically update real-time orientation information via MAC CE or uplink control information. In some examples, UE 115-a may report a change to the orientation of UE 115-a, which network entity 105-a may use to determine a new beam pointing direction for the receive beam at UE 115-a. Taking into account the UE orientation, UE 115-a provides an initial report of receive beam information, and UE 115-a may provide updates based on the orientation update.

[0114] In some examples, UE 115-a may send signaling indicating a recommendation 225 for a set of measured receive beams and a set of predicted receive beams. For example, among the reported receive beams of UE 115-a, UE 115-a may further recommend which beams UE 115-a should measure and which beams should rely on network entity-side predictions. In some examples, UE 115-a may recommend that UE 115-a measure a wide receive beam 215 (e.g., and provide measurements for the wide receive beam), and UE 115-a may recommend that network entity 105-a perform predictions for narrow receive beams 210. UE 115-a may send the recommendation semi-persistently or dynamically or both. For example, UE 115-a may send an RRC message or a MAC CE to semi-persistently indicate the recommendation 225, or UE 115-a may send a MAC CE or an uplink control information message to dynamically indicate the recommendation 225.

[0115] In some cases, the network entity 105-a may change the measurement beam set and the predicted beam set recommended by the UE. For example, the UE 115-a may recommend performing measurements for a first receive beam set, and in response, the network entity 105-a may send a message indicating a second receive beam set. The second receive beam set may be different from the first receive beam set, and the UE 115-a may perform measurements on the receive beams in the second receive beam set (e.g., and report measurements thereon). In some examples, the network entity 105-a may send a message for changing the recommended measurement receive beam and the recommended predicted receive beam via an RRC message, a MAC CE, or a downlink control information message. For example, the network entity 105-a may indicate the update via a configured receive beam identifier associated with the CSI report.

[0116] In some examples, the wireless communication system 200 may support a predefined hierarchical beam width reporting framework. For example, UE 115-a may report a first number of wide receive beams, including detailed beam pointing direction information, orientation information, and beam width information. For each reported wide receive beam, UE 115-a may report detailed beam pointing direction and beam width information for a second number of narrow receive beams. The narrow receive beam may be superimposed with the associated wide receive beam, but with a narrower beam width and a higher beamforming gain.

[0117] For example, the narrow receive beam 210-a, the narrow receive beam 210-b, and the narrow receive beam 210-c may be superimposed with the wide receive beam 215. The UE 115-a may report detailed beam pointing information of the wide receive beam 215, and the UE 115-a may indicate that the narrow receive beam 210 is superimposed with the wide receive beam 215, and provide detailed beam pointing information and beam width information of the superimposed narrow receive beam 210.

[0118] In one example, UE 115-a may have three antenna panels. There may be a first panel on the left side of the device, a second panel on the right side of the device, and a third panel on the top of the device. Each panel may provide three wide receive beams, covering a wide angle but with low beamforming gain. Within each of the three wide receive beams, there may be two intermediate narrow receive beams superimposed with the corresponding wide receive beams, providing increased beamforming gain. Within each of the intermediate narrow receive beams, there may be three refined narrow receive beams superimposed with the corresponding intermediate narrow receive beams, providing the highest beamforming gain. Therefore, each panel may provide a total of 18 receive beams, and UE 115-a may have a total of 54 receive beams.

[0119] In a first example, UE 115-a may report (e.g., via RRC signaling) receive beam information 220 including beam pointing directions and beam width information for all 54 receive beams. UE 115-a may send recommendation 225, recommending that UE 115-a measure and report L1 RSRP or L1 SINR or both for wide receive beams. Recommendation 225 may also recommend that UE 115-a will rely on network entity-side beam pair prediction for receiving downlink shared channel messages via the remaining narrower beams (e.g., medium-level narrow receive beams or refined-level narrow receive beams).

[0120] In a second example, UE 115-a may report (e.g., via RRC signaling) receive beam information 220 including beam pointing directions and beam width information for all 54 receive beams. At a first moment, UE 115-a may further report (e.g., via MAC CE) that UE 115-a recommends measuring and reporting RSRP and SINR measurements for 9 wide receive beams, while reception of downlink shared channel messages via the remaining receive beams will rely on beam pair prediction assisted by the network entity. At a second moment (e.g., after the first moment), UE 115-a may send a second recommendation (e.g., via MAC CE). In the second recommendation, UE 115-a may recommend measuring and reporting RSRP and SINR for both wide receive beams and medium-level narrow receive beams, while reception of downlink shared channels via the remaining receive beams (e.g., refined-level narrow receive beams) will rely on beam pair prediction assisted by the network entity.

[0121] UE 115-a may then perform measurements for a first receive beam set for UE 115-a. For example, based on recommendation 225 or configuration signaling from network entity 105-a, UE 115-a may measure reference signals 230 using a first receive beam set. For example, UE 115-a may measure reference signals 230 using a wide receive beam of UE 115-a to determine an RSRP measurement or an SINR measurement, or both, for the wide receive beam of UE 115-a. UE 115-a may send one or more measurements 240 indicating measurements for the first receive beam set to network entity 105-a. In some examples, an SSB may be an example of a reference signal 230. Additionally or alternatively, a CSI-RS may be an example of a reference signal 230.

[0122] The network entity 105-a may send a message to activate a TCI state associated with a receive beam or a transmit-receive beam pair at the UE 115-a. For example, the network entity 105-a may send a message including a beam activation 235, which may activate a TCI state at the UE 115-a associated with a receive beam at the UE 115-a. The message may activate the TCI state at the UE 115-a, and the UE 115-a may receive a scheduled downlink shared channel message using the associated receive beam. For example, the network entity 105-a may configure and activate a beam pair between a transmit beam 205-b and a narrow receive beam 210-b.

[0123] For example, the network entity 105-a may indicate a predicted receive beam for the UE 115-a to receive downlink shared channel messages during future instances or windows. In some examples, the network entity 105-a may send an enhanced TCI state activation MAC CE, wherein each activated TCI state includes a downlink reference signal for a type D quasi-co-located source and a receive beam associated with the downlink reference signal. In some examples, each activated TCI state may correspond to a predicted time window in which a receive beam may be used to receive downlink shared channel signaling. In some examples, the network entity 105-a may indicate the predicted receive beam via a MAC CE or downlink control information. For example, an active TCI state may be indicated via a downlink grant, such as via downlink control information that schedules a downlink shared channel. The UE 115-a may use the indicated receive beam within the indicated time window according to the activated TCI state to receive signaling via the scheduled downlink shared channel.

[0124] For each indicated receive beam, the network entity 105-a may further indicate a confidence level. For example, the enhanced TCI state activation message may include a confidence level for each activated TCI state. In some examples, the confidence level may be based on indicating a confidence level specific to a beam pair. For example, a confidence level may be associated with a downlink reference signal and a receive beam. In some examples, the confidence level may be based on indicating a downlink reference signal confidence level and a receive beam-specific confidence level, respectively. When quantifying the confidence level range, the range of the downlink reference signal may be greater than the range of the receive beam. For example, a downlink reference signal may have a confidence level between 80% and 100%, and a receive beam may have a confidence level between 50% and 80%. In some examples, the confidence level may be based on the standard deviation of the predicted average RSRP of the beam pair.

[0125] UE 115-a may verify and report the actual measured RSRP for a beam pair or a receive beam with a confidence level below a threshold. For example, if the confidence level of a receive beam associated with an activated TCI state does not meet the threshold, UE 115-a may perform measurements (e.g., RSRP measurements) using the receive beam and report the measurements to network entity 105-a. In some examples, network entity 105-a may preconfigure the threshold. For example, network entity 105-a may set the threshold to 60% so that UE 115-a may report RSRP measurements for receive beams with a confidence level below 60%.

[0126] Upon receiving the TCI state activation message, if the TCI state activation message has a confidence level below a threshold, the UE 115-a may feedback (e.g., send to the network entity 105-a) an actual measured RSRP measurement for the receive beam or beam pair associated with the TCI state activation message. The network entity 105-a may use the actual reported measurement to determine the receive beam for the UE 115-a. For example, if the reported measurement indicates a low RSRP, the network entity 105-a may change the scheduled receive beam for future downlink shared channel transmissions based on the measurement. Alternatively, if the reported measurement indicates a strong RSRP or SINR or both, the network entity 105-a may maintain the receive beam for future downlink shared channel transmissions.

[0127] Figure 3 An example of receiving beam orientations 300 and 301 supporting beam pair prediction and indication according to one or more aspects of the present disclosure is illustrated. The receiving beam orientations 300 and 301 may include UE 115-b, which may be as described in reference Figure 1 and Figure 2 An example of UE 115 is described.

[0128] UE 115-b may include one or more antenna panels, each of which may include multiple receive beams 305. For example, UE 115-b may include three antenna panels, with a first panel on the left side of the device, a second panel on the right side of the device, and a third panel on the top of the device. In some examples, each panel may provide a first number of wide beams, a second number of intermediate narrow beams superimposed with each wide beam, and a third number of refined narrow beams superimposed with each intermediate narrow beam. For example, the first antenna panel may include receive beam 305-a, the second antenna panel may include receive beam 305-b, and the third antenna panel may include receive beam 305-c. Reference Figure 4 The superposition of a wide beam and a narrow or more refined beam is described in more detail.

[0129] UE 115-b may send signaling indicating receive beam information to a network entity. Receive beam information 220 may include relative beam pointing directions and beam widths of receive beam 305 at UE 115-b. For example, UE 115-a may report beam pointing directions and beam widths of receive beam 305-a, receive beam 305-b, and receive beam 305-c. In some examples, receive beam information 220 may include hierarchical receive beam information, such as information about how to configure antenna panels at UE 115-a and how to support receive beams of different widths at each antenna panel.

[0130] In some examples, the receive beam information may include orientation information of UE 115-b or receive beam 305 of UE 115-b, or both. For example, UE 115-b may report the real-time absolute beam pointing direction and beam width of receive beam 305 of UE 115-b. In some examples, the real-time absolute beam pointing direction may be indicated according to an LCS or GCS format.

[0131] For example, UE 115 - b may indicate the beam widths and real-time beam pointing directions of receive beam 305 - a , receive beam 305 - b , and receive beam 305 - c , as well as other receive beams at UE 115 - b in receive beam orientation 300 .

[0132] In some examples, the orientation of UE 115-b may change or be updated. For example, UE 115-b may move within a wireless network. Additionally or alternatively, UE 115-b may be rotated, such as by a user manipulating UE 115-b. These rotations and changes may affect the orientation of receive beam 305 of UE 115-b.

[0133] In some examples, UE 115-b may dynamically indicate receive beam information and orientation information. For example, UE 115-a may dynamically send receive beam information (e.g., via MAC CE or uplink control information or both) to update the absolute pointing direction and beam width of the receive beam at UE 115-b. For example, UE 115-b may send a first message to indicate receive beam information for receive beam orientation 300, and UE 115-b may send a second message to indicate receive beam information for receive beam orientation 301. In some cases, the second message may dynamically update the real-time orientation information of UE 115-b or receive beam 305. For example, UE 115-b may indicate how the beam pointing direction of receive beam 305-a changes between receive beam orientation 300 and receive beam orientation 301.

[0134] Figure 4 An example of a receive beam superposition configuration 400 supporting beam pair prediction and indication according to one or more aspects of the present disclosure is illustrated.

[0135] The UE may have one or more antenna panels, each of which may provide one or more beams (such as receive beams). For example, the antenna panel may provide a first number of wide receive beams 405, thereby covering a wide angle but having a low beamforming gain. For example, the receive beam superposition configuration 400 shows an example of an antenna panel with three wide receive beams 405. Within each of the three wide beams, there may be a second number of intermediate narrow beams superimposed with the corresponding wide beam, thereby providing an increased beamforming gain. For example, the receive beam superposition configuration 400 shows an example of four narrow receive beams 410 (e.g., intermediate narrow beams) superimposed with each corresponding wide receive beam 405. In some examples, there may be a more refined beam corresponding to each narrow receive beam 410, such as a refined level narrow beam. In these examples, one or more refined level beams may be superimposed with each intermediate narrow beam, thereby providing additional beamforming gain. The receive beam superposition configuration 400 is exemplary, and other configurations of antenna panels or receive beams may support or implement the techniques described herein.

[0136] The UE may implement techniques for reporting recommendations for which receive beams will be measured by the UE and which receive beams will rely on network-assisted predictions. For example, the UE may send a message that recommends that the UE provide measurements for a first set of receive beams and that a network entity schedule a downlink shared channel for a second set of receive beams based on network-side predictions.

[0137] In a first example, the UE may report receive beam information for a set of receive beams at the UE, including beam pointing directions and beam width information. The UE may send a signal indicating a recommendation for the UE to report measurements for the wide receive beam 405 (e.g., together with or separately from the receive beam information). The recommendation may also recommend that the UE will rely on network-side beam pair prediction for receiving downlink shared channel messages via narrow beam 410.

[0138] In a second example, the UE may report receive beam information for all receive beams of the UE, including beam pointing directions and beam width information. At a first moment, the UE may further recommend that the UE measure and report measurements for the wide receive beam 405, while downlink shared channel scheduling using the narrow receive beam 410 will rely on network-assisted beam pair prediction. At a second moment (e.g., after the first moment), the UE may send a second recommendation. In the second recommendation, the UE may recommend measuring and reporting RSRP and SINR for both the wide receive beam 405 and the narrow receive beam 410, while downlink shared channel reception via the remaining receive beams (e.g., refined-level narrow beams) will rely on network entity-assisted beam pair prediction.

[0139] Figure 5 An example of a process flow 500 for supporting beam pair prediction and indication according to one or more aspects of the present disclosure is illustrated. The process flow 500 may be implemented by a UE 115-c or a network entity 105-b or both, which may be as described in reference to Figure 1 and Figure 2 1 and 105. In some examples, some procedures or signaling of the process flow 500 may occur in an order different from the order shown. Additionally or alternatively, some procedures or signaling shown may not occur, or some procedures or signaling not shown may occur, or both.

[0140] At 505, UE 115-c may send receive beam information to network entity 105-b. For example, UE 115-c may send control signaling indicating parameters of a receive beam set at UE 115-c. The parameters may be based on orientation information of UE-c and a hierarchical beamwidth configuration of the receive beam set. For example, UE 115-c may send control signaling indicating an absolute beam pointing direction and beamwidth of a receive beam at UE 115-c. In some examples, UE 115-c may explicitly report real-time absolute beam pointing direction and beamwidth (e.g., dynamically via uplink control information or MAC CE). Additionally or alternatively, UE 115-c may semi-statically report the receive beam pointing direction (e.g., via RRC signaling), and UE 115-c may also dynamically report real-time orientation information (e.g., via uplink control information or MAC CE). For example, UE 115 - c may indicate a change to the orientation of UE 115 - c or a change to the beam pointing direction of a receive beam of UE 115 - c.

[0141] At 510, UE 115-c may send a message that includes a recommendation for the UE to report measurements for an initial subset of receive beams and for the network entity to predict measurements for a second subset of receive beams. For example, UE 115-c may recommend that UE 115-c report measurements for a first subset of receive beams and recommend using a second subset of receive beams for scheduling to rely on network-side predictions. In some examples, network entity 105-b may change the UE's recommendation. For example, network entity 105-b may configure UE 115-c to provide measurements for a different subset of receive beams or measurements for network entity 105-b to perform predictions when scheduling transmissions using a different subset of receive beams.

[0142] At 515, UE 115-c may receive and measure one or more reference signals using a first subset of receive beams of a first set of beam pairs based on the parameters. For example, UE 115-c may use the first subset of receive beams to perform RSRP measurements or SINR measurements or both. In some examples, the first subset of receive beams may correspond to a recommended subset of receive beams for measuring. At 520, UE 115-c may send one or more measurement reports for the first subset of receive beams based on measuring the one or more reference signals.

[0143] At 525, the network entity 105-b may send a message to activate the TCI state at the UE 115-c. In some examples, the message to activate the TCI state may be an example of an enhanced TCI activation message. For example, the message may activate the TCI state for a receive beam of a beam pair for UE 115-c to receive a downlink shared channel message. In some examples, the message may indicate a downlink reference signal for a type D QCL association and a receive beam associated with the downlink reference signal. In some examples, the message may indicate a predicted time window in which the UE 115-c may use the receive beam to receive a downlink shared channel message. For example, the message may indicate a set of time slots in which the TCI state is activated, which may include scheduled resources or predicted scheduled resources for downlink shared channel messages.

[0144] In some examples, the receive beam used to receive the downlink shared channel message may be a receive beam that depends on a network-side prediction. For example, the network entity 105-b may predict that the receive beam is a strong beam for receiving the downlink shared channel message, or that the receive beam will have a strong RSRP characteristic or SINR characteristic when the downlink shared channel message is sent. In some cases, when the TCI state is activated, the UE 115-c may not have measured the receive beam yet.

[0145] The network entity 105-b may indicate a confidence level for a receive beam or beam pair with a message activating a TCI state. If the confidence level is below or does not meet a threshold, the UE 115-c may perform measurements using the receive beam and send a measurement report for the receive beam to the network entity 105-b. In some examples, the threshold for the measurement may be indicated to the UE 115-c via RRC signaling, MAC CE, or downlink control information. In some examples, the threshold may be preconfigured, such as by being preconfigured for a wireless communication system including the UE 115-c and the network entity 105-b.

[0146] By implementing these techniques, UE 115-c may provide information that improves predicted beam management. For example, where UE 115-c provides orientation information of a receive beam at UE 115-c, network entity 105-b may select an efficient receive beam that points toward a transmit beam of network entity 105-b. Additionally, by indicating a confidence level for the beam, UE 115-c may report measurements for receive beams that do not have a high likelihood of being an efficient beam, which may improve beam reliability for downlink signaling.

[0147] Figure 6A block diagram 600 of a device 605 supporting beam pair prediction and indication according to one or more aspects of the present disclosure is shown. The device 605 may be an example of aspects of the UE 115 as described herein. The device 605 may include a receiver 610, a transmitter 615, and a communication manager 620. The device 605 may also include a processor. Each of these components may communicate with each other (e.g., via one or more buses).

[0148] The receiver 610 may provide means for receiving information (such as packets, user data, control information, or any combination thereof) associated with various information channels (e.g., control channels related to beam pair prediction and indication, data channels, information channels). The information may be communicated to other components of the device 605. The receiver 610 may utilize a single antenna or a collection of multiple antennas.

[0149] The transmitter 615 may provide means for transmitting signals generated by other components of the device 605. For example, the transmitter 615 may transmit information (such as packets, user data, control information, or any combination thereof) associated with various information channels (e.g., control channels related to beam pair prediction and indication, data channels, information channels). In some examples, the transmitter 615 may be co-located with the receiver 610 in a transceiver module. The transmitter 615 may utilize a single antenna or a collection of multiple antennas.

[0150] The communication manager 620, the receiver 610, the transmitter 615, or various combinations thereof, or various components thereof, may be examples of means for performing aspects of beam pair prediction and indication as described herein. For example, the communication manager 620, the receiver 610, the transmitter 615, or various combinations thereof, or components thereof, may support methods for performing one or more of the functions described herein.

[0151] In some examples, the communication manager 620, the receiver 610, the transmitter 615, or various combinations or components thereof may be implemented in hardware (e.g., in a communication management circuit). The hardware may include a processor, a digital signal processor (DSP), a central processing unit (CPU), an application specific integrated circuit (ASIC), a field programmable gate array (FPGA) or other programmable logic device, a microcontroller, discrete gate or transistor logic components, discrete hardware components, or any combination thereof that is configured to or otherwise supports components for performing the functions described herein. In some examples, the processor and a memory coupled to the processor may be configured to perform one or more of the functions described herein (e.g., by executing instructions stored in the memory by the processor).

[0152] Additionally or alternatively, in some examples, the communication manager 620, the receiver 610, the transmitter 615, or various combinations or components thereof may be implemented in code executed by a processor (e.g., as communication management software or firmware). If implemented in code executed by a processor, the functionality of the communication manager 620, the receiver 610, the transmitter 615, or various combinations or components thereof may be performed by a general purpose processor (e.g., configured as or otherwise supporting components for performing the functionality described in the present disclosure), a DSP, a CPU, an ASIC, an FPGA, a microcontroller, or any combination of these or other programmable logic devices.

[0153] In some examples, communication manager 620 may be configured to perform various operations (e.g., receive, obtain, monitor, output, transmit) using or otherwise cooperating with receiver 610, transmitter 615, or both. For example, communication manager 620 may receive information from receiver 610, transmit information to transmitter 615, or be integrated in conjunction with receiver 610, transmitter 615, or both to obtain information, output information, or perform various other operations as described herein.

[0154] According to examples as disclosed herein, the communication manager 620 may support wireless communications at a UE. For example, the communication manager 620 may be configured to or otherwise support components for sending control signaling indicating parameters of a set of receive beams at the UE, the parameters being based on an orientation of the UE and a hierarchical beamwidth configuration of the set of receive beams. The communication manager 620 may be configured to or otherwise support components for measuring one or more reference signals using a first subset of receive beams of a first set of beam pairs based on the parameters. The communication manager 620 may be configured to or otherwise support components for sending one or more measurement reports for the first subset of receive beams based on measuring the one or more reference signals.

[0155] By including or configuring the communication manager 620 according to examples as described herein, the device 605 (e.g., a processor controlling or otherwise coupled with the receiver 610, the transmitter 615, the communication manager 620, or a combination thereof) can support techniques for reducing power consumption by reducing measurement reporting overhead and signaling. Additionally, these techniques can increase beamforming accuracy by improving the reliability of beam predictions.

[0156] Figure 7A block diagram 700 of a device 705 supporting beam pair prediction and indication according to one or more aspects of the present disclosure is shown. The device 705 may be an example of aspects of the device 605 or UE 115 as described herein. The device 705 may include a receiver 710, a transmitter 715, and a communication manager 720. The device 705 may also include a processor. Each of these components may communicate with each other (e.g., via one or more buses).

[0157] The receiver 710 may provide means for receiving information (such as packets, user data, control information, or any combination thereof) associated with various information channels (e.g., control channels related to beam pair prediction and indication, data channels, information channels). The information may be communicated to other components of the device 705. The receiver 710 may utilize a single antenna or a collection of multiple antennas.

[0158] The transmitter 715 may provide means for transmitting signals generated by other components of the device 705. For example, the transmitter 715 may transmit information (such as packets, user data, control information, or any combination thereof) associated with various information channels (e.g., control channels related to beam pair prediction and indication, data channels, information channels). In some examples, the transmitter 715 may be co-located with the receiver 710 in a transceiver module. The transmitter 715 may utilize a single antenna or a collection of multiple antennas.

[0159] The device 705 or its various components may be examples of components for performing various aspects of beam pair prediction and indication as described herein. For example, the communication manager 720 may include a receive beam indication component 725, a receive beam measurement component 730, a measurement reporting component 735, or any combination thereof. The communication manager 720 may be an example of various aspects of the communication manager 620 as described herein. In some examples, the communication manager 720 or its various components may be configured to perform various operations (e.g., receive, obtain, monitor, output, send) using or otherwise cooperating with the receiver 710, the transmitter 715, or both. For example, the communication manager 720 may receive information from the receiver 710, transmit information to the transmitter 715, or be integrated with the receiver 710, the transmitter 715, or both to obtain information, output information, or perform various other operations as described herein.

[0160] According to examples as disclosed herein, the communication manager 720 may support wireless communications at a UE. The receive beam indication component 725 may be configured to or otherwise support means for sending control signaling indicating a parameter of a receive beam set at the UE, the parameter being based on an orientation of the UE and a hierarchical beamwidth configuration of the receive beam set. The receive beam measurement component 730 may be configured to or otherwise support means for measuring one or more reference signals using a first subset of receive beams of a first beam pair set based on the parameter. The measurement reporting component 735 may be configured to or otherwise support means for sending one or more measurement reports for the first subset of receive beams based on measuring the one or more reference signals.

[0161] Figure 8 A block diagram 800 of a communication manager 820 supporting beam pair prediction and indication according to one or more aspects of the present disclosure is shown. The communication manager 820 can be an example of aspects of the communication manager 620, the communication manager 720, or both as described herein. The communication manager 820 or its various components can be examples of components for performing aspects of beam pair prediction and indication as described herein. For example, the communication manager 820 may include a receive beam indication component 825, a receive beam measurement component 830, a measurement reporting component 835, a receive beam recommendation component 840, a beam activation component 845, a beam confidence component 850, or any combination thereof. Each of these components can communicate with each other directly or indirectly (e.g., via one or more buses).

[0162] According to examples as disclosed herein, the communication manager 820 may support wireless communications at a UE. The receive beam indication component 825 may be configured to or otherwise support means for sending control signaling indicating a parameter of a receive beam set at the UE, the parameter being based on an orientation of the UE and a hierarchical beamwidth configuration of the receive beam set. The receive beam measurement component 830 may be configured to or otherwise support means for measuring one or more reference signals using a first subset of receive beams of a first beam pair set based on the parameter. The measurement reporting component 835 may be configured to or otherwise support means for sending one or more measurement reports for the first subset of receive beams based on measuring the one or more reference signals.

[0163] In some examples, to support sending control signaling, the receive beam indication component 825 may be configured as or otherwise support components for sending control signaling indicating the beam direction of a receive beam set and the beam width of a receive beam set based on the UE's orientation and hierarchical beam width configuration.

[0164] In some examples, receive beam indication component 825 may be configured or otherwise support components for sending a control message indicating a change in orientation of the UE via uplink control information, MAC CE, or both.

[0165] In some examples, receive beam recommendation component 840 may be configured as or otherwise support components for sending a message that includes a recommendation for a UE to report measurements for an initial subset of receive beams and for a network entity to predict measurements for a second subset of receive beams.

[0166] In some examples, receive beam recommendation component 840 can be configured to or otherwise support means for receiving a control message from a network entity that instructs the UE to report measurements for a first subset of receive beams, wherein one or more reference signals are measured for the first subset of receive beams instead of an initial subset of receive beams based on the control message. In some examples, the first subset of receive beams is an initial subset of receive beams.

[0167] In some examples, to support sending the message, the receive beam recommendation component 840 may be configured or otherwise support components for sending the message via an uplink control information message, a MAC CE, or an RRC message.

[0168] In some examples, beam activation component 845 may be configured or otherwise support components for receiving a message based on one or more measurement reports that activates a TCI state for a receive beam of a beam pair to receive a downlink shared channel message.

[0169] In some examples, to support receiving messages indicating TCI status, beam confidence component 850 may be configured or otherwise support components for receiving messages indicating a confidence level of a received beam.

[0170] In some examples, beam confidence component 850 can be configured or otherwise support means for measuring a second one or more reference signals using the receive beam based on a confidence level of the receive beam failing to meet a threshold. In some examples, beam confidence component 850 can be configured or otherwise support means for sending a measurement report for the receive beam based on measuring the second one or more reference signals.

[0171] In some examples, beam confidence component 850 may be configured as or otherwise support means for receiving control signaling indicating a downlink reference signal confidence level.

[0172] In some examples, the confidence level for a receive beam is based on a standard deviation of a predicted average reference signal received power for the receive beam.

[0173] In some examples, the message includes a time window for communicating using a receive beam of the beam pair.

[0174] In some examples, the parameters include at least a first set of parameters for the set of wide beams and at least a second set of parameters for the set of narrow beams. In some examples, one or more narrow beams are superimposed with the wide beam.

[0175] In some examples, the orientation of the UE is indicated based on a local coordinate system format, a global coordinate system format, or both.

[0176] Fig. 9 A diagram of a system 900 including a device 905 supporting beam pair prediction and indication according to one or more aspects of the present disclosure is shown. The device 905 may be an example of a device 605, a device 705, or a UE 115 as described herein, or include components thereof. The device 905 may communicate (e.g., wirelessly) with one or more network entities 105, one or more UEs 115, or any combination thereof. The device 905 may include components for two-way voice and data communications, including components for sending and receiving communications, such as a communication manager 920, an input / output (I / O) controller 910, a transceiver 915, an antenna 925, a memory 930, a code 935, and a processor 940. These components may be in electronic communication or otherwise coupled (e.g., operatively, communicatively, functionally, electronically, electrically) via one or more buses (e.g., a bus 945).

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

[0178] In some cases, the device 905 may include a single antenna 925. However, in some other cases, the device 905 may have more than one antenna 925, which can send or receive multiple wireless transmissions concurrently. The transceiver 915 can communicate bidirectionally via one or more antennas 925, wired or wireless links, as described herein. For example, the transceiver 915 may represent a wireless transceiver and can communicate bidirectionally with another wireless transceiver. The transceiver 915 may also include a modem for: modulating packets; providing the modulated packets to one or more antennas 925 for transmission; and demodulating packets received from one or more antennas 925. The transceiver 915 or the transceiver 915 and one or more antennas 925 can be examples of transmitters 615, transmitters 715, receivers 610, receivers 710, or any combination thereof or components thereof as described herein.

[0179] The memory 930 may include random access memory (RAM) and read-only memory (ROM). The memory 930 may store computer-readable, computer-executable code 935 including instructions that, when executed by the processor 940, cause the device 905 to perform various functions described herein. The code 935 may be stored in a non-transitory computer-readable medium such as a system memory or another type of memory. In some cases, the code 935 may not be directly executable by the processor 940, but may (e.g., when compiled and executed) cause the computer to perform the functions described herein. In some cases, the memory 930 may also include, among other things, a basic I / O system (BIOS) that may control basic hardware or software operations, such as interaction with peripheral components or devices.

[0180] The processor 940 may include an intelligent hardware device (e.g., a general-purpose processor, a DSP, a CPU, a microcontroller, an ASIC, an FPGA, a programmable logic device, a discrete gate or transistor logic component, a discrete hardware component, or any combination thereof). In some cases, the processor 940 may be configured to operate a memory array using a memory controller. In some other cases, the memory controller may be integrated into the processor 940. The processor 940 may be configured to execute computer-readable instructions stored in a memory (e.g., a memory 930) to enable the device 905 to perform various functions (e.g., functions or tasks that support beam pair prediction and indication). For example, the device 905 or a component of the device 905 may include a processor 940 and a memory 930 coupled to or coupled to the processor 940, and the processor 940 and the memory 930 are configured to perform the various functions described herein.

[0181] According to examples as disclosed herein, the communication manager 920 may support wireless communications at a UE. For example, the communication manager 920 may be configured to or otherwise support components for sending control signaling indicating parameters of a set of receive beams at the UE, the parameters being based on an orientation of the UE and a hierarchical beamwidth configuration of the set of receive beams. The communication manager 920 may be configured to or otherwise support components for measuring one or more reference signals using a first subset of receive beams of a first set of beam pairs based on the parameters. The communication manager 920 may be configured to or otherwise support components for sending one or more measurement reports for the first subset of receive beams based on measuring the one or more reference signals.

[0182] By including or configuring a communication manager 920 according to examples described herein, the device 905 can support techniques for reducing power consumption by reducing measurement reporting overhead and signaling. Additionally, these techniques can increase beamforming accuracy by improving the reliability of beam predictions.

[0183] In some examples, the communication manager 920 may be configured to perform various operations (e.g., receive, monitor, transmit) using or otherwise cooperating with the transceiver 915, one or more antennas 925, or any combination thereof. Although the communication manager 920 is illustrated as a separate component, in some examples, one or more functions described with reference to the communication manager 920 may be supported or performed by the processor 940, the memory 930, the code 935, or any combination thereof. For example, the code 935 may include instructions that are executable by the processor 940 to cause the device 905 to perform various aspects of beam pair prediction and indication as described herein, or the processor 940 and the memory 930 may be otherwise configured to perform or support such operations.

[0184] Fig.10 A block diagram 1000 of a device 1005 supporting beam pair prediction and indication according to one or more aspects of the present disclosure is shown. The device 1005 may be an example of aspects of the network entity 105 as described herein. The device 1005 may include a receiver 1010, a transmitter 1015, and a communication manager 1020. The device 1005 may also include a processor. Each of these components may communicate with each other (e.g., via one or more buses).

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

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

[0187] The communication manager 1020, the receiver 1010, the transmitter 1015, or various combinations thereof, or various components thereof, may be examples of means for performing aspects of beam pair prediction and indication as described herein. For example, the communication manager 1020, the receiver 1010, the transmitter 1015, or various combinations thereof, or components thereof, may support methods for performing one or more of the functions described herein.

[0188] In some examples, the communication manager 1020, the receiver 1010, the transmitter 1015, or various combinations or components thereof may be implemented in hardware (e.g., in a communication management circuit). The hardware may include a processor, a DSP, a CPU, an ASIC, an FPGA or other programmable logic device, a microcontroller, discrete gate or transistor logic components, discrete hardware components, or any combination thereof that is configured as or otherwise supports components for performing the functions described in the present disclosure. In some examples, a processor and a memory coupled to the processor may be configured to perform one or more of the functions described herein (e.g., by executing instructions stored in the memory by the processor).

[0189] Additionally or alternatively, in some examples, the communication manager 1020, the receiver 1010, the transmitter 1015, or various combinations or components thereof may be implemented in code executed by a processor (e.g., as communication management software or firmware). If implemented in code executed by a processor, the functionality of the communication manager 1020, the receiver 1010, the transmitter 1015, or various combinations or components thereof may be performed by a general purpose processor (e.g., configured as or otherwise supporting components for performing the functionality described in the present disclosure), a DSP, a CPU, an ASIC, an FPGA, a microcontroller, or any combination of these or other programmable logic devices.

[0190] In some examples, communication manager 1020 may be configured to perform various operations (e.g., receive, obtain, monitor, output, transmit) using or otherwise cooperating with receiver 1010, transmitter 1015, or both. For example, communication manager 1020 may receive information from receiver 1010, transmit information to transmitter 1015, or be integrated in conjunction with receiver 1010, transmitter 1015, or both to obtain information, output information, or perform various other operations as described herein.

[0191] According to examples as disclosed herein, the communication manager 1020 may support wireless communications at a network entity. For example, the communication manager 1020 may be configured to or otherwise support components for receiving control signaling indicating parameters of a set of receive beams at a UE, the parameters being based on an orientation of the UE and a hierarchical beamwidth configuration of the set of receive beams. The communication manager 1020 may be configured to or otherwise support components for transmitting one or more reference signals using a first subset of transmit beams of a first set of beam pairs based on the parameters. The communication manager 1020 may be configured to or otherwise support components for receiving one or more measurement reports for the first subset of receive beams based on the one or more reference signals.

[0192] By including or configuring the communication manager 1020 according to the examples described herein, the device 1005 (e.g., a processor controlling or otherwise coupled with the receiver 1010, the transmitter 1015, the communication manager 1020, or a combination thereof) can support techniques for reducing power consumption by reducing measurement reporting overhead and signaling. Additionally, these techniques can increase beamforming accuracy by improving the reliability of beam predictions.

[0193] Fig.11A block diagram 1100 of a device 1105 supporting beam pair prediction and indication according to one or more aspects of the present disclosure is shown. The device 1105 may be an example of aspects of the device 1005 or network entity 105 as described herein. The device 1105 may include a receiver 1110, a transmitter 1115, and a communication manager 1120. The device 1105 may also include a processor. Each of these components may communicate with each other (e.g., via one or more buses).

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

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

[0196] The device 1105 or its various components may be examples of components for performing various aspects of beam pair prediction and indication as described herein. For example, the communication manager 1120 may include a receive beam indication component 1125, a reference signal transmission component 1130, a receive beam measurement component 1135, or any combination thereof. The communication manager 1120 may be an example of various aspects of the communication manager 1020 as described herein. In some examples, the communication manager 1120 or its various components may be configured to use or otherwise cooperate with the receiver 1110, the transmitter 1115, or both to perform various operations (e.g., receive, obtain, monitor, output, transmit). For example, the communication manager 1120 may receive information from the receiver 1110, transmit information to the transmitter 1115, or be integrated with the receiver 1110, the transmitter 1115, or both to obtain information, output information, or perform various other operations as described herein.

[0197] According to examples as disclosed herein, the communication manager 1120 may support wireless communications at a network entity. The receive beam indication component 1125 may be configured to or otherwise support means for receiving control signaling indicating a parameter of a receive beam set at a UE, the parameter being based on an orientation of the UE and a hierarchical beamwidth configuration of the receive beam set. The reference signal transmission component 1130 may be configured to or otherwise support means for transmitting one or more reference signals using a first subset of transmit beams of a first beam pair set based on the parameter. The receive beam measurement component 1135 may be configured to or otherwise support means for receiving one or more measurement reports for the first subset of receive beams based on the one or more reference signals.

[0198] Fig.12A block diagram 1200 of a communication manager 1220 supporting beam pair prediction and indication according to one or more aspects of the present disclosure is shown. The communication manager 1220 can be an example of aspects of the communication manager 1020, the communication manager 1120, or both as described herein. The communication manager 1220 or its various components can be examples of means for performing aspects of beam pair prediction and indication as described herein. For example, the communication manager 1220 can include a receive beam indication component 1225, a reference signal transmission component 1230, a receive beam measurement component 1235, a receive beam recommendation component 1240, a receive beam activation component 1245, a confidence level component 1250, or any combination thereof. Each of these components may communicate directly or indirectly with each other (e.g., via one or more buses), which communication may include communication within a protocol layer of a protocol stack, communication associated with a logical channel of a protocol stack (e.g., between protocol layers of a protocol stack, within a device, component, or virtualized component associated with the network entity 105, between devices, components, or virtualized components associated with the network entity 105), or any combination thereof.

[0199] According to examples as disclosed herein, the communication manager 1220 may support wireless communications at a network entity. The receive beam indication component 1225 may be configured to or otherwise support components for receiving control signaling indicating a parameter of a receive beam set at a UE, the parameter being based on an orientation of the UE and a hierarchical beamwidth configuration of the receive beam set. The reference signal transmission component 1230 may be configured to or otherwise support components for transmitting one or more reference signals using a first subset of transmit beams of a first beam pair set based on the parameter. The receive beam measurement component 1235 may be configured to or otherwise support components for receiving one or more measurement reports for the first subset of receive beams based on the one or more reference signals.

[0200] In some examples, to support receiving control signaling, receive beam indication component 1225 may be configured as or otherwise support components for receiving control signaling indicating a beam direction of a receive beam set and a beam width of a receive beam set based on an orientation of the UE and a hierarchical beam width configuration.

[0201] In some examples, receive beam indication component 1225 may be configured or otherwise support components for receiving a control message indicating a change in orientation of the UE via uplink control information, MAC CE, or both.

[0202] In some examples, receive beam recommendation component 1240 may be configured as or otherwise support components for receiving a message that includes a recommendation for a UE to report measurements for an initial subset of receive beams and for a network entity to predict measurements for a second subset of receive beams.

[0203] In some examples, receive beam recommendation component 1240 may be configured to or otherwise support components for sending a control message to a UE instructing the UE to report measurements for a first subset of receive beams, wherein based on the control message, one or more measurements are reported for the first subset of receive beams rather than an initial subset of receive beams.

[0204] In some examples, the first subset of receive beams is an initial subset of receive beams.

[0205] In some examples, receive beam activation component 1245 may be configured as or otherwise support components for sending a message based on one or more measurement reports that activates the TCI state for a receive beam for a beam pair for the UE to receive a downlink shared channel message.

[0206] In some examples, to support sending a message indicating a TCI status, confidence level component 1250 may be configured or otherwise support components for sending a message indicating a confidence level of a received beam.

[0207] In some examples, confidence level component 1250 may be configured or otherwise support means for receiving a measurement report for a receive beam based on a confidence level for the receive beam failing to satisfy a threshold.

[0208] In some examples, confidence level component 1250 may be configured as or otherwise support means for receiving control signaling indicating a downlink reference signal confidence level.

[0209] In some examples, the confidence level for a receive beam is based on a standard deviation of a predicted average reference signal received power for the receive beam.

[0210] In some examples, the message includes a time window for the UE to communicate using a receive beam of the beam pair.

[0211] In some examples, the parameters include at least a first set of parameters for the set of wide beams and at least a second set of parameters for the set of narrow beams. In some examples, one or more narrow beams are superimposed with the wide beam.

[0212] Fig.13A diagram of a system 1300 including a device 1305 supporting beam pair prediction and indication according to one or more aspects of the present disclosure is shown. The device 1305 may be an example of a device 1005, a device 1105, or a network entity 105 as described herein, or include components thereof. The device 1305 may communicate with one or more network entities 105, one or more UEs 115, or any combination thereof, which communication may include communication through one or more wired interfaces, through one or more wireless interfaces, or any combination thereof. The device 1305 may include components that support output and acquisition of communications, such as a communication manager 1320, a transceiver 1310, an antenna 1315, a memory 1325, a code 1330, and a processor 1335. These components may be in electronic communication or otherwise coupled (e.g., operatively, communicatively, functionally, electronically, electrically) via one or more buses (e.g., bus 1340).

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

[0214] Memory 1325 may include RAM and ROM. Memory 1325 may store computer-readable, computer-executable code 1330 including instructions that, when executed by processor 1335, cause device 1305 to perform various functions described herein. Code 1330 may be stored in a non-transitory computer-readable medium such as system memory or another type of memory. In some cases, code 1330 may not be directly executable by processor 1335, but may (e.g., when compiled and executed) cause a computer to perform the functions described herein. In some cases, memory 1325 may also contain, among other things, a BIOS that may control basic hardware or software operations, such as interaction with peripheral components or devices.

[0215] The processor 1335 may include an intelligent hardware device (e.g., a general-purpose processor, a DSP, an ASIC, a CPU, an FPGA, a microcontroller, a programmable logic device, a discrete gate or transistor logic component, a discrete hardware component, or any combination thereof). In some cases, the processor 1335 may be configured to operate a memory array using a memory controller. In some other cases, the memory controller may be integrated into the processor 1335. The processor 1335 may be configured to execute computer-readable instructions stored in a memory (e.g., a memory 1325) to enable the device 1305 to perform various functions (e.g., functions or tasks that support beam pair prediction and indication). For example, the device 1305 or a component of the device 1305 may include a processor 1335 and a memory 1325 coupled to the processor 1335, and the processor 1335 and the memory 1325 are configured to perform various functions described herein. The processor 1335 may be an example of a cloud computing platform (e.g., one or more physical nodes and supporting software such as an operating system, a virtual machine, or a container instance), which may host functions for performing functions of the device 1305 (e.g., by executing code 1330). The processor 1335 may be any one or more suitable processors capable of executing scripts or instructions of one or more software programs stored in the device 1305 (such as in the memory 1325). In some specific implementations, the processor 1335 may be a component of a processing system. A processing system may generally refer to a system or a series of machines or components that receive inputs and process these inputs to produce an output set (which may be delivered to other systems or components of the device 1305, for example). For example, the processing system of the device 1305 may refer to a system including various other components or subcomponents of the device 1305, such as the processor 1335, or the transceiver 1310, or the communication manager 1320, or other components or combinations of components of the device 1305. The processing system of the device 1305 may interface with other components of the device 1305, and may process information (such as input or signals) received from other components, or output information to other components. For example, a chip or modem of the device 1305 may include a processing system and one or more interfaces for outputting information or for obtaining information or both. One or more interfaces may be implemented as or otherwise include a first interface configured to output information and a second interface configured to obtain information, or the same interface configured to output information and obtain information, as well as other specific implementations. In some specific implementations, one or more interfaces may refer to an interface between a processing system of a chip or modem and a transmitter, so that the device 1305 can send information output from the chip or modem. Additionally or alternatively, in some specific implementations, one or more interfaces may refer to an interface between a processing system of a chip or modem and a receiver, so that the device 1305 can obtain information or signal input, and the information can be passed to the processing system.One of ordinary skill in the art will readily recognize that the first interface may also obtain information or signal input, and the second interface may also output information or signal output.

[0216] In some examples, bus 1340 may support communication of a protocol layer of a protocol stack (e.g., within a protocol layer). In some examples, bus 1340 may support communication associated with a logical channel of a protocol stack (e.g., between protocol layers of a protocol stack), which may include communication performed within a component of device 1305 or communication performed between different components of device 1305 that may be co-located or located in different locations (e.g., where device 1305 may refer to a system in which one or more of communication manager 1320, transceiver 1310, memory 1325, code 1330, and processor 1335 may be located in one of the different components or divided between the different components).

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

[0218] According to examples as disclosed herein, the communication manager 1320 may support wireless communications at a network entity. For example, the communication manager 1320 may be configured to or otherwise support components for receiving control signaling indicating parameters of a set of receive beams at a UE, the parameters being based on an orientation of the UE and a hierarchical beamwidth configuration of the set of receive beams. The communication manager 1320 may be configured to or otherwise support components for transmitting one or more reference signals using a first subset of transmit beams of a first set of beam pairs based on the parameters. The communication manager 1320 may be configured to or otherwise support components for receiving one or more measurement reports for the first subset of receive beams based on the one or more reference signals.

[0219] By including or configuring a communication manager 1320 according to examples described herein, the device 1305 can support techniques for reducing power consumption by reducing measurement reporting overhead and signaling. Additionally, these techniques can increase beamforming accuracy by improving the reliability of beam predictions.

[0220] In some examples, the communication manager 1320 may be configured to perform various operations (e.g., receive, obtain, monitor, output, transmit) using or otherwise cooperating with the transceiver 1310, one or more antennas 1315 (e.g., where applicable), or any combination thereof. Although the communication manager 1320 is illustrated as a separate component, in some examples, one or more functions described with reference to the communication manager 1320 may be supported or performed by the transceiver 1310, the processor 1335, the memory 1325, the code 1330, or any combination thereof. For example, the code 1330 may include instructions that are executable by the processor 1335 to cause the device 1305 to perform various aspects of beam pair prediction and indication as described herein, or the processor 1335 and the memory 1325 may be otherwise configured to perform or support such operations.

[0221] Fig.14 1400 is a flowchart illustrating a method 1400 for supporting beam pair prediction and indication according to one or more aspects of the present disclosure. The operations of the method 1400 may be implemented by a UE or a component thereof as described herein. For example, the operations of the method 1400 may be implemented by a UE or a component thereof as described in reference to Figures 1 to 9 The described UE 115 may be performed. In some examples, the UE may execute an instruction set to control the functional elements of the UE to perform the described functions. Additionally or alternatively, the UE may use dedicated hardware to perform various aspects of the described functions.

[0222] At 1405, the method may include sending control signaling indicating a parameter of a receive beam set at the UE, the parameter being based on an orientation of the UE and a hierarchical beamwidth configuration of the receive beam set. The operations of 1405 may be performed according to examples as disclosed herein. In some examples, aspects of the operations of 1405 may be performed as described in reference to Figure 8 The receive beam indication component 825 described above is executed.

[0223] At 1410, the method may include measuring one or more reference signals using a first subset of receive beams of a first set of beam pairs based on a parameter. The operations of 1410 may be performed according to examples as disclosed herein. In some examples, aspects of the operations of 1410 may be performed by Figure 8 The receive beam measurement component 830 described above is performed.

[0224] At 1415, the method may include sending one or more measurement reports for the first subset of receive beams based on measuring the one or more reference signals. The operations of 1415 may be performed according to examples as disclosed herein. In some examples, aspects of the operations of 1415 may be performed by Figure 8 The described measurement reporting component 835 is performed.

[0225] Fig.15 1 is a flowchart illustrating a method 1500 for supporting beam pair prediction and indication according to one or more aspects of the present disclosure. The operations of the method 1500 may be implemented by a UE or a component thereof as described herein. For example, the operations of the method 1500 may be implemented by a UE or a component thereof as described in reference to Figures 1 to 9 The described UE 115 may be performed. In some examples, the UE may execute an instruction set to control the functional elements of the UE to perform the described functions. Additionally or alternatively, the UE may use dedicated hardware to perform various aspects of the described functions.

[0226] At 1505, the method may include sending control signaling indicating a parameter of a receive beam set at the UE, the parameter being based on an orientation of the UE and a hierarchical beamwidth configuration of the receive beam set. The operations of 1505 may be performed according to examples as disclosed herein. In some examples, aspects of the operations of 1505 may be performed as described in reference to Figure 8 The receive beam indication component 825 described above is executed.

[0227] At 1510, the method may include sending a message including a recommendation for the UE to report measurements for an initial subset of receive beams and for the network entity to predict measurements for a second subset of receive beams. The operations of 1510 may be performed according to examples as disclosed herein. In some examples, aspects of the operations of 1510 may be performed as described in reference to Figure 8 The receive beam recommendation component 840 described above is performed.

[0228] At 1515, the method may include measuring one or more reference signals using a first subset of receive beams of a first set of beam pairs based on the parameter. The operations of 1515 may be performed according to examples as disclosed herein. In some examples, aspects of the operations of 1515 may be performed by Figure 8 The receive beam measurement component 830 described above is performed.

[0229] At 1520, the method may include sending one or more measurement reports for a first subset of receive beams based on measuring one or more reference signals. The operations of 1520 may be performed according to examples as disclosed herein. In some examples, aspects of the operations of 1520 may be performed by Figure 8 The described measurement reporting component 835 is performed.

[0230] Fig.16 1600 is a flowchart illustrating a method 1600 for supporting beam pair prediction and indication according to one or more aspects of the present disclosure. The operations of the method 1600 may be implemented by a UE or a component thereof as described herein. For example, the operations of the method 1600 may be implemented by a UE or a component thereof as described in reference to Figures 1 to 9The described UE 115 may be performed. In some examples, the UE may execute an instruction set to control the functional elements of the UE to perform the described functions. Additionally or alternatively, the UE may use dedicated hardware to perform various aspects of the described functions.

[0231] At 1605, the method may include sending control signaling indicating a parameter of a receive beam set at the UE, the parameter being based on an orientation of the UE and a hierarchical beamwidth configuration of the receive beam set. The operations of 1605 may be performed according to examples as disclosed herein. In some examples, aspects of the operations of 1605 may be performed as described in reference to Figure 8 The receive beam indication component 825 described above is executed.

[0232] At 1610, the method may include measuring one or more reference signals using a first subset of receive beams of a first set of beam pairs based on a parameter. The operations of 1610 may be performed according to examples as disclosed herein. In some examples, aspects of the operations of 1610 may be performed by Figure 8 The receive beam measurement component 830 described above is performed.

[0233] At 1615, the method may include sending one or more measurement reports for the first subset of receive beams based on measuring the one or more reference signals. The operations of 1615 may be performed according to examples as disclosed herein. In some examples, aspects of the operations of 1615 may be performed by Figure 8 The described measurement reporting component 835 is performed.

[0234] At 1620, the method may include receiving a message based on one or more measurement reports, the message activating a TCI state for a receive beam of a beam pair to receive a downlink shared channel message indicating a confidence level of the receive beam. The operations of 1620 may be performed according to examples as disclosed herein. In some examples, aspects of the operations of 1620 may be performed as described in reference to Figure 8 The beam activation component 845 is used to perform the above.

[0235] Fig.17 1700 is a flowchart illustrating a method 1700 for supporting beam pair prediction and indication according to one or more aspects of the present disclosure. The operations of the method 1700 may be implemented by a network entity or a component thereof as described herein. For example, the operations of the method 1700 may be implemented by a network entity or a component thereof as described in reference to Figures 1 to 5 as well as Figures 10 to 13 In some examples, the network entity may execute an instruction set to control the functional elements of the network entity to perform the described functions. Additionally or alternatively, the network entity may use dedicated hardware to perform various aspects of the described functions.

[0236] At 1705, the method may include receiving control signaling indicating parameters of a receive beam set at the UE, the parameters being based on an orientation of the UE and a hierarchical beamwidth configuration of the receive beam set. The operations of 1705 may be performed according to examples as disclosed herein. In some examples, aspects of the operations of 1705 may be performed as described in reference to Fig.12 The receive beam indication component 1225 described above is executed.

[0237] At 1710, the method may include transmitting one or more reference signals using a first subset of transmit beams of a first set of beam pairs based on a parameter. The operations of 1710 may be performed according to examples as disclosed herein. In some examples, aspects of the operations of 1710 may be performed by Fig.12 The reference signal sending component 1230 executes.

[0238] At 1715, the method may include receiving one or more measurement reports for a first subset of receive beams based on one or more reference signals. The operations of 1715 may be performed according to examples as disclosed herein. In some examples, aspects of the operations of 1715 may be performed by Fig.12 The receive beam measurement component 1235 described above is performed.

[0239] The following provides an overview of various aspects of the disclosure:

[0240] Aspect 1: A method for performing wireless communications at a UE, the method comprising: sending control signaling indicating parameters of a receive beam set at the UE, the parameters being based at least in part on an orientation of the UE and a hierarchical beamwidth configuration of the receive beam set; measuring one or more reference signals using a first subset of receive beams of a first beam pair set based at least in part on the parameters; and sending one or more measurement reports for the first subset of receive beams based at least in part on measuring the one or more reference signals.

[0241] Aspect 2: The method according to aspect 1, wherein sending the control signaling includes: sending the control signaling indicating the beam direction of the receive beam set and the beamwidth of the receive beam set based at least in part on the orientation of the UE and the hierarchical beamwidth configuration.

[0242] Aspect 3: According to any one of aspects 1 to 2, the method further includes: sending a control message indicating the change of the orientation of the UE via uplink control information, a medium access control control element, or both.

[0243] Aspect 4: According to the method described in any one of Aspects 1 to 3, the method also includes: sending a message, the message including a recommendation for the UE to report measurements for an initial subset of received beams and a network entity to predict measurements for a second subset of received beams.

[0244] Aspect 5: According to the method described in Aspect 4, the method also includes: receiving a control message from the network entity, the control message instructing the UE to report measurements for the first subset of received beams, wherein the one or more reference signals are measured at least in part based on the control message for the first subset of received beams rather than the initial subset of received beams.

[0245] Aspect 6: The method according to any one of aspects 4 to 5, wherein the first subset of receive beams is the initial subset of receive beams.

[0246] Aspect 7: The method according to any one of aspects 4 to 6, wherein sending the message comprises: sending the message via an uplink control information message, a medium access control element, or a radio resource control message.

[0247] Aspect 8: According to the method described in any one of Aspects 1 to 7, the method also includes: receiving a message based at least in part on the one or more measurement reports, wherein the message activates a transmit configuration indicator (TCI) state for a receiving beam of the beam pair to receive a downlink shared channel message.

[0248] Aspect 9: The method according to aspect 8, wherein receiving the message indicating the TCI state includes: receiving the message indicating the confidence level of the receive beam.

[0249] Aspect 10: According to the method described in Aspect 9, the method also includes: using the received beam to measure a second one or more reference signals based at least in part on the confidence level of the received beam failing to meet a threshold; and sending a measurement report for the received beam based at least in part on measuring the second one or more reference signals.

[0250] Aspect 11: According to the method according to any one of aspects 9 to 10, the method further includes: receiving control signaling indicating a downlink reference signal confidence level.

[0251] Aspect 12: The method according to any one of aspects 9 to 11, wherein the confidence level of the receive beam is based at least in part on a standard deviation of a predicted average reference signal received power of the receive beam.

[0252] Aspect 13: The method according to any one of aspects 8 to 12, wherein the message includes a time window for communicating using the receive beam of the beam pair.

[0253] Aspect 14: The method according to any one of aspects 1 to 13, wherein the parameters include at least a first parameter set of a wide beam set and at least a second parameter set of a narrow beam set, and one or more narrow beams are superimposed with the wide beam.

[0254] Aspect 15: The method according to any one of aspects 1 to 14, wherein the orientation of the UE is indicated at least in part based on a local coordinate system format or a global coordinate system format or both.

[0255] Aspect 16: A method for wireless communication at a network entity, the method comprising: receiving control signaling indicating parameters of a receive beam set at a UE, the parameters being based at least in part on an orientation of the UE and a hierarchical beamwidth configuration of the receive beam set; sending one or more reference signals using a first subset of transmit beams of a first beam pair set based at least in part on the parameters; and receiving one or more measurement reports for the first subset of receive beams based at least in part on the one or more reference signals.

[0256] Aspect 17: A method according to aspect 16, wherein receiving the control signaling includes: receiving the control signaling indicating the beam direction of the receive beam set and the beamwidth of the receive beam set based at least in part on the orientation of the UE and the hierarchical beamwidth configuration.

[0257] Aspect 18: The method according to any one of aspects 16 to 17, the method further comprising: receiving a control message indicating a change in the orientation of the UE via uplink control information, a medium access control control element, or both.

[0258] Aspect 19: According to the method described in any one of Aspects 16 to 18, the method also includes: receiving a message, the message including a recommendation for the UE to report measurements for an initial subset of received beams and for the network entity to predict measurements for a second subset of received beams.

[0259] Aspect 20: According to the method according to Aspect 19, the method also includes: sending a control message to the UE, the control message instructing the UE to report measurements for the first subset of received beams, wherein at least in part based on the control message, the one or more measurement reports are for the first subset of received beams instead of the initial subset of received beams.

[0260] Aspect 21: The method according to any one of aspects 19 to 20, wherein the first subset of receive beams is the initial subset of receive beams.

[0261] Aspect 22: According to the method described in any one of Aspects 16 to 21, the method also includes: sending a message based at least in part on the one or more measurement reports, wherein the message activates a transmit configuration indicator (TCI) state for a receiving beam of the beam pair for the UE to receive a downlink shared channel message.

[0262] Aspect 23: The method according to Aspect 22, wherein sending the message indicating the TCI status includes: sending the message indicating the confidence level of the receive beam.

[0263] Aspect 24: The method according to aspect 23, the method also includes: receiving a measurement report for the receive beam based at least in part on the confidence level of the receive beam failing to meet a threshold.

[0264] Aspect 25: According to the method according to any one of aspects 23 to 24, the method further includes: receiving control signaling indicating a downlink reference signal confidence level.

[0265] Aspect 26: The method according to any one of aspects 23 to 25, wherein the confidence level of the receive beam is based at least in part on a standard deviation of a predicted average reference signal received power of the receive beam.

[0266] Aspect 27: A method according to any one of aspects 22 to 26, wherein the message includes a time window for the UE to communicate using the receive beam of the beam pair.

[0267] Aspect 28: The method according to any one of aspects 16 to 27, wherein the parameters include at least a first parameter set of a wide beam set and at least a second parameter set of a narrow beam set, and one or more narrow beams are superimposed with the wide beam.

[0268] Aspect 29: An apparatus for performing wireless communications at a UE, the apparatus comprising: a processor; a memory coupled to the processor; and instructions stored in the memory and executable by the processor to cause the apparatus to perform a method according to any one of Aspects 1 to 15.

[0269] Aspect 30: An apparatus for wireless communication at a UE, the apparatus comprising at least one component for performing a method according to any one of aspects 1 to 15.

[0270] Aspect 31: A non-transitory computer-readable medium storing a code for wireless communication at a UE, the code comprising instructions executable by a processor to perform the method according to any one of aspects 1 to 15.

[0271] Aspect 32: An apparatus for wireless communication at a network entity, the apparatus comprising: a processor; a memory coupled to the processor; and instructions stored in the memory and executable by the processor to cause the apparatus to perform a method according to any one of Aspects 16 to 28.

[0272] Aspect 33: An apparatus for wireless communication at a network entity, the apparatus comprising at least one component for performing a method according to any one of aspects 16 to 28.

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

[0274] It should be noted that the methods described herein describe possible implementations, and that the various operations and steps may be rearranged or otherwise modified and that other implementations are possible. Furthermore, aspects from two or more methods may be combined.

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

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

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

[0278] The functions described herein may be implemented using hardware, software executed by a processor, firmware, or any combination thereof. If implemented using software executed by a processor, the functions may be stored as one or more instructions or codes of a computer-readable medium, or sent using one or more instructions or codes of 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 may be implemented using software executed by a processor, hardware, firmware, hard wiring, or a combination of any of these items. Features that implement the functions may also be physically located at different locations, including being distributed so that the various parts of the functions are implemented at different physical locations.

[0279] Computer-readable medium includes both non-transient computer storage medium and communication medium, and it includes any medium that facilitates computer program to be transmitted from one position to another position.Non-transient storage medium can be any available medium that can be accessed by general or special-purpose computer.By way of example and not limitation, non-transient computer-readable medium can include RAM, ROM, electrically erasable programmable ROM (EEPROM), flash memory, compact disc (CD) ROM or other optical disc storage device, disk storage device or other magnetic storage device, or can be used for carrying or storing desired program code parts and any other non-transient medium that can be accessed by general or special-purpose computer or general or special-purpose processor in the form of instruction or data structure.In addition, any connection is appropriately referred to as computer-readable medium.For example, if software is sent from website, server or other remote source using coaxial cable, fiber optic cable, twisted pair, digital subscriber line (DSL) or wireless technology such as infrared, radio and microwave, then coaxial cable, fiber optic cable, twisted pair, DSL or wireless technology such as infrared, radio and microwave are included in the definition of computer-readable medium. As used herein, disk and disc include CD, laser disc, optical disc, digital versatile disc (DVD), floppy disk and Blu-ray disc. Disks can reproduce data magnetically, while discs can reproduce data optically using lasers. Combinations of the above are also included within the scope of computer readable media.

[0280] As used herein (including in the claims), "or" used in a list of items (e.g., a list of items introduced by a phrase such as "at least one of..." or "one or more of...") indicates an inclusive list, so that, for example, a list of at least one of 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). In addition, as used herein, the phrase "based on" should not be interpreted as a reference to a closed set of conditions. For example, an example step described as "based on condition A" may be based on both condition A and condition B without departing from the scope of the present disclosure. In other words, as used herein, the phrase "based on" should be interpreted in the same manner as the phrase "based at least in part on".

[0281] The term "determining" encompasses a wide variety of actions, and thus, "determining" may include calculating, computing, processing, deriving, investigating, looking up (such as via looking up in a table, database or other data structure), ascertaining, etc. Furthermore, "determining" may include receiving (e.g., receiving information), accessing (e.g., accessing data stored in a memory), etc. Furthermore, "determining" may include parsing, retrieving, selecting, choosing, establishing, and other such similar actions.

[0282] In the drawings, similar components or features may have the same reference label. In addition, components of the same type may be distinguished by following the reference label with a dash and a second label to distinguish between similar components. If only the first reference label is used in the specification, the description may apply to any of the similar components having the same first reference label, regardless of the second reference label or other subsequent reference labels.

[0283] The descriptions set forth herein in conjunction with the accompanying drawings describe example configurations and do not represent all examples that may be implemented or within the scope of the claims. The term "example" as used herein means "used as an example, instance, or illustration," rather than "preferred" or "advantageous over other examples." The specific embodiments include specific details to provide an understanding of the described techniques. However, these techniques may be practiced without these specific details. In some cases, known structures and devices are shown in block diagram form to avoid obscuring the concepts of the described examples.

[0284] The description herein is provided to enable one of ordinary skill in the art to implement or use the present disclosure. Various modifications to the present disclosure will be apparent to one of ordinary skill in the art, and the general principles defined herein may be applied to other variations without departing from the scope of the present disclosure. Thus, the present 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. An apparatus for wireless communication at a user equipment (UE), the apparatus comprising: processor; a memory coupled to the processor; and instructions stored in the memory and executable by the processor to cause the apparatus to: sending control signaling indicating parameters of a set of receive beams at the UE, the parameters being based at least in part on an orientation of the UE and a hierarchical beamwidth configuration of the set of receive beams; measuring one or more reference signals using a first subset of receive beams of a first set of beam pairs based at least in part on the parameters; as well as One or more measurement reports are sent for the first subset of receive beams based at least in part on measuring the one or more reference signals.

2. The apparatus of claim 1 , wherein the instructions for sending the control signaling are executable by the processor to cause the apparatus to: The control signaling indicating the beam directions of the set of receive beams and the beamwidths of the set of receive beams is sent based at least in part on the orientation of the UE and the hierarchical beamwidth configuration.

3. The apparatus of claim 1 , wherein the instructions are further executable by the processor to cause the apparatus to: A control message indicating the change in the orientation of the UE is sent via uplink control information, a medium access control control element, or both.

4. The apparatus of claim 1, wherein the instructions are further executable by the processor to cause the apparatus to: A message is sent, the message including a recommendation for the UE to report measurements for an initial subset of receive beams and for a network entity to predict measurements for a second subset of receive beams.

5. The apparatus of claim 4, wherein the instructions are further executable by the processor to cause the apparatus to: A control message is received from the network entity, the control message instructing the UE to report measurements for the first subset of received beams, wherein the one or more reference signals are measured for the first subset of received beams instead of the initial subset of received beams based at least in part on the control message. The apparatus of claim 4 , wherein the first subset of receive beams is the initial subset of receive beams.

7. The apparatus of claim 4, wherein the instructions for sending the message are executable by the processor to cause the apparatus to: The message is sent via an uplink control information message, a medium access control element, or a radio resource control message.

8. The apparatus of claim 1, wherein the instructions are further executable by the processor to cause the apparatus to: A message is received based at least in part on the one or more measurement reports, the message activating a transmit configuration indicator (TCI) state for a receive beam of the beam pair to receive a downlink shared channel message.

9. The apparatus of claim 8, wherein the instructions for receiving the message indicating the TCI status are executable by the processor to cause the apparatus to: The message indicating a confidence level of the receive beam is received.

10. The apparatus of claim 9, wherein the instructions are further executable by the processor to cause the apparatus to: Based at least in part on the confidence level for the receive beam failing to satisfy a threshold, measuring a second one or more reference signals using the receive beam; and A measurement report is sent for the receive beam based at least in part on measuring the second one or more reference signals.

11. The apparatus of claim 9, wherein the instructions are further executable by the processor to cause the apparatus to: Control signaling indicating a downlink reference signal confidence level is received.

12. The apparatus of claim 9, wherein the confidence level for the receive beam is based at least in part on a standard deviation of a predicted mean reference signal received power for the receive beam.

13. The apparatus of claim 8, wherein the message comprises a time window for communicating using the receive beam of the beam pair.

14. The device according to claim 1, wherein: The parameters include at least a first set of parameters for a set of wide beams and at least a second set of parameters for a set of narrow beams, wherein one or more narrow beams are superimposed with the wide beam.

15. The apparatus of claim 1, wherein the orientation of the UE is indicated based at least in part on a local coordinate system format or a global coordinate system format, or both.

16. An apparatus for wireless communication at a network entity, the apparatus comprising: processor; a memory coupled to the processor; and instructions stored in the memory and executable by the processor to cause the apparatus to: receiving control signaling indicating parameters of a set of receive beams at a user equipment (UE), the parameters being based at least in part on an orientation of the UE and a hierarchical beamwidth configuration of the set of receive beams; transmitting one or more reference signals using a first subset of transmit beams of a first set of beam pairs based at least in part on the parameters; as well as One or more measurement reports are received for a first subset of receive beams based at least in part on the one or more reference signals.

17. The apparatus of claim 16, wherein the instructions for receiving the control signaling are executable by the processor to cause the apparatus to: The control signaling indicating a beam direction of the set of receive beams and a beamwidth of the set of receive beams is received based at least in part on the orientation of the UE and the hierarchical beamwidth configuration.

18. The apparatus of claim 16, wherein the instructions are further executable by the processor to cause the apparatus to: A control message indicating a change in the orientation of the UE is received via uplink control information, a medium access control control element, or both.

19. The apparatus of claim 16, wherein the instructions are further executable by the processor to cause the apparatus to: A message is received, the message comprising a recommendation for the UE to report measurements for an initial subset of receive beams and for the network entity to predict measurements for a second subset of receive beams.

20. The apparatus of claim 19, wherein the instructions are further executable by the processor to cause the apparatus to: A control message is sent to the UE, the control message instructing the UE to report measurements for the first subset of received beams, wherein at least in part based on the control message, the one or more measurement reports are for the first subset of received beams instead of the initial subset of received beams.

21. The apparatus of claim 19, wherein the first subset of receive beams is the initial subset of receive beams.

22. The apparatus of claim 16, wherein the instructions are further executable by the processor to cause the apparatus to: A message is sent based at least in part on the one or more measurement reports, the message activating a transmit configuration indicator (TCI) state for a receive beam of a beam pair for the UE to receive a downlink shared channel message.

23. The apparatus of claim 22, wherein the instructions for sending the message indicating the TCI status are executable by the processor to cause the apparatus to: The message is sent indicating a confidence level of the receive beam.

24. The apparatus of claim 23, wherein the instructions are further executable by the processor to cause the apparatus to: A measurement report is received for the receive beam based at least in part on a confidence level for the receive beam failing to satisfy a threshold.

25. The apparatus of claim 23, wherein the instructions are further executable by the processor to cause the apparatus to: Control signaling indicating a downlink reference signal confidence level is received.

26. The apparatus of claim 23, wherein the confidence level for the receive beam is based at least in part on a standard deviation of a predicted mean reference signal received power for the receive beam.

27. The apparatus of claim 22, wherein the message comprises a time window for the UE to communicate using the receive beam of the beam pair.

28. The apparatus of claim 16, wherein: The parameters include at least a first set of parameters for a set of wide beams and at least a second set of parameters for a set of narrow beams, wherein one or more narrow beams are superimposed with the wide beam.

29. A method for wireless communication at a user equipment (UE), the method comprising: sending control signaling indicating parameters of a set of receive beams at the UE, the parameters being based at least in part on an orientation of the UE and a hierarchical beamwidth configuration of the set of receive beams; measuring one or more reference signals using a first subset of receive beams of a first set of beam pairs based at least in part on the parameters; as well as One or more measurement reports are sent for the first subset of receive beams based at least in part on measuring the one or more reference signals.

30. A method for wireless communication at a network entity, the method comprising: receiving control signaling indicating parameters of a set of receive beams at a user equipment (UE), the parameters being based at least in part on an orientation of the UE and a hierarchical beamwidth configuration of the set of receive beams; transmitting one or more reference signals using a first subset of transmit beams of a first set of beam pairs based at least in part on the parameters; as well as One or more measurement reports are received for a first subset of receive beams based at least in part on the one or more reference signals.

Images