Signaling information for custom beams

Abstract

Aspects of the present disclosure generally relate to wireless communications. In some aspects, a first device may receive a plurality of reference signals from a second device based at least in part on a plurality of beams. The first device may transmit an angle of departure (AoD) associated with a reference signal of the plurality of reference signals to the second device. The first device may receive, from the second device, a delta value indicating a difference between the AoD and a beam pointing angle of a custom second device beam. The first device may receive data from the second device using a custom first device beam derived based at least in part on the delta value. Numerous other aspects are described.

Description

TECHNICAL FIELD

[0001] Aspects of the present disclosure generally relate to wireless communication and relate to techniques and apparatus for signaling information for custom beams. BACKGROUND OF THE DISCLOSURE

[0002] Wireless communication systems are widely deployed to provide various telecommunication services such as telephony, video, data, messaging, and broadcast. A typical wireless communication system may employ multiple access techniques that are capable of supporting communication with multiple users by sharing available system resources, such as bandwidth, transmit power, etc. Examples of such multiple access techniques include Code Division Multiple Access (CDMA) systems, Time Division Multiple Access (TDMA) systems, Frequency Division Multiple Access (FDMA) systems, Orthogonal Frequency Division Multiple Access (OFDMA) systems, Single Carrier Frequency Division Multiple Access (SC-FDMA) systems, Time Division Synchronous Code Division Multiple Access (TD-SCDMA) systems, and Long Term Evolution (LTE). LTE / LTE-Advanced is an enhanced set of the Universal Mobile Telecommunication System (UMTS) mobile standards promulgated by the Third Generation Partnership Project (3GPP).

[0003] A wireless network may include one or more network nodes that support communication for wireless communication devices such as user equipment (UE) or multiple UEs. A UE may communicate with a network node via downlink communication and uplink communication. "Downlink" (or "DL") refers to a communication link from a network node to a UE, and "uplink" (or "UL") refers to a communication link from a UE to a network node. Some wireless networks may support device-to-device communication, such as via a local link (e.g., sidelink (SL), Wireless Local Area Network (WLAN) link, and / or Wireless Personal Area Network (WPAN) link, etc.).

[0004] The above multiple access techniques have been adopted in various telecommunication standards to provide a common protocol that enables different UEs to communicate at the urban, national, regional, and / or global levels. New Radio (NR) (which may be referred to as 5G) is an enhanced set of the LTE mobile standards promulgated by 3GPP. NR is designed to better support mobile broadband Internet access by improving spectral efficiency, reducing costs, improving services, leveraging new spectrums, and better integrating with other open standards by using Orthogonal Frequency Division Multiplexing (OFDM) with Cyclic Prefix (CP) (CP-OFDM) on the downlink, CP-OFDM and / or Single Carrier Frequency Division Multiplexing (SC-FDM) (also known as Discrete Fourier Transform Spread OFDM (DFT-s-OFDM)) on the uplink, and supporting beamforming, Multiple-Input Multiple-Output (MIMO) antenna techniques, and carrier aggregation. As the demand for mobile broadband access continues to increase, further improvements to LTE, NR, and other radio access technologies remain useful. SUMMARY OF THE DISCLOSURE

[0005] Some aspects described herein relate to a first device for wireless communication. The first device may include a memory, one or more processors coupled to the memory, and instructions stored in the memory and executable by the one or more processors (e.g., directly, indirectly, after preprocessing, or without preprocessing). The instructions may be executable by the one or more processors to cause the first device to receive a plurality of reference signals from a second device at least in part based on a plurality of beams. The instructions may be executable by the one or more processors to cause the first device to send an angle of departure (AoD) associated with a reference signal among the plurality of reference signals to the second device. The instructions may be executable by the one or more processors to cause the first device to receive an incremental value indicating a difference between the AoD and a beam pointing angle of a customized second device beam from the second device. The instructions may be executable by the one or more processors to cause the first device to receive data from the second device using a customized first device beam derived at least in part based on the incremental value.

[0006] Some aspects described herein relate to a second device for wireless communication. The second device may include a memory, one or more processors coupled to the memory, and instructions stored in the memory and executable by the one or more processors. The instructions may be executable by the one or more processors to cause the second device to send a plurality of reference signals to a first device at least in part based on a plurality of beams. The instructions may be executable by one or more processors to cause the second device to receive an AoD associated with a reference signal among the plurality of reference signals from the first device. The instructions may be executable by one or more processors to cause the second device to send an incremental value indicating a difference between the AoD and a beam pointing angle of a customized second device beam to the first device. The instructions may be executable by one or more processors to cause the second device to send data to the first device using a customized second device beam.

[0007] Some aspects described herein relate to a method of wireless communication performed by an apparatus of a first device. The method may include: receiving a plurality of reference signals from a second device at least in part based on a plurality of beams. The method may include: sending an AoD associated with a reference signal among the plurality of reference signals to the second device. The method may include: receiving an incremental value indicating a difference between the AoD and a beam pointing angle of a customized second device beam from the second device. The method may include: receiving data from the second device using a customized first device beam derived at least in part based on the incremental value.

[0008] Some aspects described herein relate to a method of wireless communication performed by an apparatus of a second device. The method may include: sending a plurality of reference signals to a first device based at least in part on a plurality of beams. The method may include: receiving, from the first device, an AoD associated with a reference signal of the plurality of reference signals. The method may include: sending to the first device an incremental value indicating a difference between the AoD and a beam pointing angle of a custom second device beam. The method may include: sending data to the first device using the custom second device beam.

[0009] Some aspects described herein relate to a non-transitory computer-readable medium storing one or more instructions for wireless communication by a first device. The one or more instructions, when executed by one or more processors of the first device, may cause the first device to receive a plurality of reference signals from a second device based at least in part on a plurality of beams. The one or more instructions, when executed by one or more processors of the first device, may cause the first device to send to the second device an AoD associated with a reference signal of the plurality of reference signals. The one or more instructions, when executed by one or more processors of the first device, may cause the first device to receive from the second device an incremental value indicating a difference between the AoD and a beam pointing angle of a custom second device beam. The one or more instructions, when executed by one or more processors of the first device, may cause the first device to receive data from the second device using a custom first device beam derived at least in part based on the incremental value.

[0010] Some aspects described herein relate to a non-transitory computer-readable medium storing one or more instructions for wireless communication by a second device. The one or more instructions, when executed by one or more processors of the second device, may cause the second device to send a plurality of reference signals to a first device based at least in part on a plurality of beams. The one or more instructions, when executed by one or more processors of the second device, may cause the second device to receive from the first device an AoD associated with a reference signal of the plurality of reference signals. The one or more instructions, when executed by one or more processors of the second device, may cause the second device to send to the first device an incremental value indicating a difference between the AoD and a beam pointing angle of a custom second device beam. The one or more instructions, when executed by one or more processors of the second device, may cause the second device to send data to the first device using the custom second device beam.

[0011] Some aspects described herein relate to a first device for wireless communication. The first device may include components for receiving a plurality of reference signals from a second device based at least in part on a plurality of beams. The first device may include components for sending to the second device an AoD associated with a reference signal among the plurality of reference signals. The first device may include components for receiving from the second device an incremental value indicating a difference between the AoD and a beam pointing angle of a customized second device beam. The first device may include components for receiving data from the second device using a customized first device beam derived at least in part based on the incremental value.

[0012] Some aspects described herein relate to a second device for wireless communication. The second device may include components for sending a plurality of reference signals to a first device based at least in part on a plurality of beams. The second device may include components for receiving from the first device an AoD associated with a reference signal among the plurality of reference signals. The second device may include components for sending to the first device an incremental value indicating a difference between the AoD and a beam pointing angle of a customized second device beam. The second device may include components for sending data to the first device using the customized second device beam.

[0013] Aspects generally include methods, apparatuses, systems, computer program products, non-transitory computer-readable media, user equipment, base stations, network entities, network nodes, wireless communication devices, and / or processing systems as fully described herein with reference to the figures and the specification and as illustrated in the figures and the specification.

[0014] The features and technical advantages of examples in accordance with the present disclosure have been outlined rather broadly above so that the detailed description that follows may be better understood. Additional features and advantages will be described hereinafter. The disclosed concepts and specific examples may be readily utilized as a basis for modifying or designing other structures for carrying out the same purposes of the present disclosure. Such equivalent constructions do not depart from the scope of the appended claims. The characteristics of the concepts disclosed herein, both as to their organization and operation methods, as well as associated advantages, will be better understood by considering the following description in conjunction with the accompanying figures. Each of the figures provided in the accompanying drawings is for the purpose of illustration and description and is not a definition of the limits of the claims.

[0015] Although aspects are described herein by way of illustration of some examples, those skilled in the art will understand that such aspects can be implemented in many different arrangements and scenarios. The techniques described herein can be implemented using different platform types, devices, systems, shapes, sizes, and / or packaging arrangements. For example, some aspects can be implemented via an integrated chip implementation or other non-module component-based devices (e.g., end-user devices, vehicles, communication devices, computing devices, industrial equipment, retail / shopping devices, medical devices, and / or artificial intelligence devices). Aspects can be implemented in chip-level components, modular components, non-modular components, non-chip-level components, device-level components, and / or system-level components. Devices incorporating the described aspects and features can include additional components and features for implementing and practicing the claimed and described aspects. For example, the transmission and reception of wireless signals can include one or more components for analog and digital purposes (e.g., hardware components including antennas, radio frequency (RF) chains, power amplifiers, modulators, buffers, processors, interleavers, adders, and / or summers). The aspects described herein are intended to be practiced in a wide variety of devices, components, systems, distributed arrangements, and / or end-user devices of various sizes, shapes, and configurations. BRIEF DESCRIPTION OF THE DRAWINGS

[0016] To gain a more detailed understanding of the above-described features of the present disclosure, a more specific description of the inventive concept briefly outlined above can be obtained by referring to aspects, some of which are illustrated in the drawings. However, it should be noted that the drawings merely illustrate certain exemplary aspects of the present disclosure and are not considered to be a limitation of its scope, as the specification may admit other equally valid aspects. The same reference numerals in different drawings may identify the same or similar elements.

[0017] Figure 1 is a diagram illustrating an example of a wireless network according to the present disclosure.

[0018] Figure 2 is a diagram illustrating an example of communication between a network node and a user equipment (UE) in a wireless network according to the present disclosure.

[0019] Figure 3 is a diagram illustrating an example of a decomposed base station architecture according to the present disclosure.

[0020] Figure 4 is a diagram illustrating an example of the per-subcarrier hybrid beamforming input-output relationship for the downlink according to the present disclosure.

[0021] Figure 5 is a diagram illustrating an example of a quantization representation of a channel in the angular space according to the present disclosure.

[0022] Figure 6A diagram illustrating an example of a sparse recovery formula for original channel estimation according to the present disclosure.

[0023] Figure 7 A diagram illustrating an example of a sparse recovery formula for original channel estimation according to the present disclosure.

[0024] Figure 8 A diagram illustrating an example of a custom non-codebook-based beam according to the present disclosure.

[0025] Figures 9 to 10 A diagram illustrating an example associated with signaling information for a custom beam according to the present disclosure.

[0026] Figures 11 to 12 A diagram illustrating an example process associated with signaling information for a custom beam according to the present disclosure.

[0027] Figures 13 to 14 A diagram of an example apparatus for wireless communication according to the present disclosure. Detailed Description

[0028] Aspects of the present disclosure are described more fully hereinafter with reference to the accompanying drawings. However, the present disclosure may be embodied in many different forms and should not be construed as limited to any specific structure or function presented throughout this disclosure. Rather, these aspects are provided so that this disclosure will be thorough and complete, and will convey the full scope of the disclosure to those skilled in the art. Those skilled in the art should understand that the scope of the present disclosure is intended to cover any aspect of the disclosure disclosed herein, whether implemented independently of or in combination with any other aspect of the disclosure. For example, any number of the aspects set forth herein may be used to implement an apparatus or practice a method. Additionally, the scope of the present disclosure is intended to cover such apparatus or methods implemented using other structures, functions, or combinations of structures and functions in addition to or different from the aspects of the disclosure set forth herein. It should be understood that any aspect of the disclosure disclosed herein may be embodied by one or more elements of the claims.

[0029] Several aspects of a telecommunications system will now be presented with reference to various apparatuses and techniques. These apparatuses and techniques will be described in the following detailed description and illustrated in the accompanying drawings by various blocks, modules, components, circuits, steps, processes, algorithms, etc. (collectively referred to as "elements"). These elements may be implemented using hardware, software, or a combination thereof. Whether these elements are implemented as hardware or software depends on the particular application and design constraints imposed on the overall system.

[0030] Although terms that are generally associated with 5G or New Radio (NR) radio access technology (RAT) may be used to describe aspects herein, aspects of the present disclosure may be applicable to other RATs, such as 3G RAT, 4G RAT, and / or post-5G (e.g., 6G) RATs.

[0031] Figure 1 FIG. is an illustration of an example of a wireless network 100 in accordance with the present disclosure. The wireless network 100 may be a 5G (e.g., NR) network and / or a 4G (e.g., Long Term Evolution (LTE)) network, or may include elements of a 5G (e.g., NR) network and / or elements of a 4G (e.g., Long Term Evolution (LTE)) network, and so on. The wireless network 100 may include one or more network nodes 110 (shown as network nodes 110a, network nodes 110b, network nodes 110c, and network nodes 110d), user equipment (UE) 120 or multiple UEs 120 (shown as UEs 120a, UEs 120b, UEs 120c, UEs 120d, and UEs 120e), and / or other entities. The network nodes 110 are network nodes that communicate with the UEs 120. As shown, the network nodes 110 may include one or more network nodes. For example, the network nodes 110 may be aggregated network nodes, which means that the aggregated network nodes are configured to utilize a radio protocol stack that is physically or logically integrated within a single radio access network (RAN) node (e.g., within a single device or unit). As another example, the network nodes 110 may be disaggregated network nodes (sometimes referred to as disaggregated base stations), which means that the network nodes 110 are configured to utilize a protocol stack that is physically or logically distributed among two or more nodes, such as one or more central units (CUs), one or more distributed units (DUs), or one or more radio units (RUs).

[0032] In some examples, network node 110 is or includes a network node (such as a RU) that communicates with UE 120 via a radio access link. In some examples, network node 110 is or includes a network node (such as a DU) that communicates with other network nodes 110 via a fronthaul link or a midhaul link. In some examples, network node 110 is or includes a network node (such as a CU) that communicates with other network nodes 110 via a midhaul link or communicates with a core network via a backhaul link. In some examples, network node 110 (such as an aggregated network node 110 or a disaggregated network node 110) may include multiple network nodes, such as one or more RUs, one or more CUs, and / or one or more DUs. Network node 110 may include, for example, an NR base station, an LTE base station, a Node B, an eNB (e.g., in 4G), a gNB (e.g., in 5G), an access point, a transmit receive point (TRP), a DU, a RU, a CU, a mobility element of the network, a core network node, a network element, network equipment, a RAN node, or a combination thereof. In some examples, network nodes 110 may be interconnected with each other or interconnected to one or more other network nodes 110 in the wireless network 100 via various types of fronthaul, midhaul, and / or backhaul interfaces (such as direct physical connections, air interfaces, or virtual networks, using any suitable transport network).

[0033] In some examples, network node 110 may provide communication coverage for a specific geographical area. In the 3rd Generation Partnership Project (3GPP), depending on the context in which the term is used, the term "cell" may refer to the coverage area of network node 110 and / or the network node subsystem serving that coverage area. Network node 110 may provide communication coverage for a macrocell, a picocell, a femtocell, and / or another type of cell. A macrocell may cover a relatively large geographical area (e.g., with a radius of several kilometers) and may allow unrestricted access by UE 120 having a service subscription. A picocell may cover a relatively small geographical area and may allow unrestricted access by UE 120 having a service subscription. A femtocell may cover a relatively small geographical area (e.g., a home) and may allow restricted access by UE 120 associated with the femtocell (e.g., UE 120 in a Closed Subscriber Group (CSG)). The network node 110 for a macrocell may be referred to as a macro network node. The network node 110 for a picocell may be referred to as a pico network node. The network node 110 for a femtocell may be referred to as a femto network node or a home network node. In Figure 1In the example shown, network node 110a may be a macro network node for macro cell 102a, network node 110b may be a pico network node for pico cell 102b, and network node 110c may be a femto network node for femto cell 102c. A network node may support one or more (e.g., three) cells. In some examples, a cell may not necessarily be stationary, and the geographical area of a cell may move according to the location of a moving network node 110 (e.g., a mobile network node).

[0034] In some aspects, the term "base station" or "network node" may refer to an aggregated base station, a disaggregated base station, an integrated access and backhaul (IAB) node, a relay node, or one or more of their components. For example, in some aspects, the "base station" or "network node" may refer to a CU, a DU, an RU, a near real-time (near RT) RAN intelligent controller (RIC), or a non-real-time (non RT) RIC, or a combination thereof. In some aspects, the term "base station" or "network node" may refer to a single device configured to perform one or more functions, such as those described herein in connection with network node 110. In some aspects, the term "base station" or "network node" may refer to multiple devices configured to perform one or more functions. For example, in some distributed systems, each of multiple different devices (which may be located in the same geographical location or different geographical locations) may be configured to perform at least a portion of a function, or to repeatedly perform at least a portion of the function, and the term "base station" or "network node" may refer to any one or more of these different devices. In some aspects, the term "base station" or "network node" may refer to one or more virtual base stations or one or more virtual base station functions. For example, in some aspects, two or more base station functions may be instantiated on a single device. In some aspects, the term "base station" or "network node" may refer to one base station function among base station functions, rather than another base station function. In this way, a single device may include more than one base station.

[0035] Wireless network 100 may include one or more relay stations. A relay station is a network node that can receive a transmission of data from an upstream node (e.g., network node 110 or UE 120) and transmit the data to a downstream node (e.g., UE 120 or network node 110). A relay station may be a UE 120 capable of relaying transmissions for other UEs 120. In Figure 1 the example shown, network node 110d (e.g., a relay network node) may communicate with network node 110a (e.g., a macro network node) and UE 120d to facilitate communication between network node 110a and UE 120d. A network node that relays communication may be referred to as a relay station, a relay base station, a relay network node, a relay node, a relay, etc.

[0036] The wireless network 100 can be a heterogeneous network that includes different types of network nodes 110, such as macro network nodes, pico network nodes, femto network nodes, relay network nodes, etc. These different types of network nodes 110 can have different transmission power levels, different coverage areas, and / or different impacts on interference in the wireless network 100. For example, a macro network node can have a high transmission power level (e.g., 5 watts to 40 watts), while pico network nodes, femto network nodes, and relay network nodes can have lower transmission power levels (e.g., 0.1 watt to 2 watts).

[0037] The network controller 130 can be coupled to or communicate with a set of network nodes 110 and can provide coordination and control for these network nodes 110. The network controller 130 can communicate with the network nodes 110 via a backhaul communication link or a midhaul communication link. The network nodes 110 can also communicate directly with each other or indirectly via a wireless backhaul communication link or a wired backhaul communication link. In some aspects, the network controller 130 can be a CU or a core network device, or can include a CU or a core network device.

[0038] UEs 120 can be distributed throughout the wireless network 100, and each UE 120 can be stationary or mobile. The UEs 120 can include, for example, access terminals, terminals, mobile stations, and / or subscriber units. A UE 120 can be a cellular phone (e.g., a smart phone), a personal digital assistant (PDA), a wireless modem, a wireless communication device, a handheld device, a laptop computer, a cordless phone, a wireless local loop (WLL) station, a tablet computer, a camera, a gaming device, a netbook, a smartbook, a superbook, a medical device, a biometric device, a wearable device (e.g., a smart watch, smart clothing, smart glasses, a smart wristband, smart jewelry (e.g., a smart ring or a smart bracelet)), an entertainment device (e.g., a music device, a video device, and / or a satellite radio), a vehicle component or sensor, a smart meter / sensor, industrial manufacturing equipment, a global positioning system device, UE functionality of a network node, and / or any other suitable device configured to communicate via a wireless or wired medium.

[0039] Some UEs 120 may be considered machine type communication (MTC) or evolved or enhanced machine type communication (eMTC) UEs. MTC UEs and / or eMTC UEs may include, for example, robots, drones, remote devices, sensors, meters, monitors, and / or location tags, which may communicate with network nodes, another device (e.g., a remote device), or some other entity. Some UEs 120 may be considered Internet of Things (IoT) devices and / or may be implemented as narrowband IoT (NB-IoT) devices. Some UEs 120 may be considered customer premises equipment. The UE 120 may be included inside a housing that houses components of the UE 120, such as processor components and / or memory components. In some examples, the processor components and the memory components may be coupled together. For example, the processor components (e.g., one or more processors) and the memory components (e.g., memory) may be operably coupled, communicatively coupled, electronically coupled, and / or electrically coupled.

[0040] Generally, any number of radio networks 100 may be deployed in a given geographical area. Each radio network 100 may support a specific RAT and may operate on one or more frequencies. The RAT may be referred to as a radio technology, an air interface, etc. The frequency may be referred to as a carrier, a frequency channel, etc. Each frequency in a given geographical area may support a single RAT to avoid interference between radio networks of different RATs. In some cases, an NR or 5G RAT network may be deployed.

[0041] In some examples, two or more UEs 120 (e.g., shown as UE 120a and UE 120e) may communicate directly using one or more sidelink channels (e.g., communicate with each other without using the network node 110 as an intermediate device). For example, the UE 120 may use peer-to-peer (P2P) communication, device-to-device (D2D) communication, vehicle-to-everything (V2X) protocols (e.g., which may include vehicle-to-vehicle (V2V) protocols, vehicle-to-infrastructure (V2I) protocols, or vehicle-to-pedestrian (V2P) protocols), and / or mesh networks to communicate. In such examples, the UE 120 may perform scheduling operations, resource selection operations, and / or other operations described elsewhere herein as being performed by the network node 110.

[0042] Devices of the wireless network 100 can communicate using the electromagnetic spectrum, which can be subdivided into various categories, bands, channels, etc. according to frequency or wavelength. For example, devices of the wireless network 100 can communicate using one or more operating bands. In 5G NR, two initial operating bands have been identified as Frequency Range Designation FR1 (410 MHz – 7.125 GHz) and FR2 (24.25 GHz – 52.6 GHz). It should be understood that although part of FR1 is greater than 6 GHz, in various documents and articles, FR1 is often (interchangeably) referred to as the “sub-6 GHz” band. Regarding FR2, a similar naming issue sometimes occurs, which is usually (interchangeably) referred to as the “millimeter wave” band in documents and articles, although it is different from the extremely high frequency (EHF) band (30 GHz - 300 GHz) identified by the International Telecommunication Union (ITU) as the “millimeter wave” band.

[0043] Frequencies between FR1 and FR2 are generally referred to as mid-band frequencies. Recent 5G NR research has identified operating bands for these mid-band frequencies as Frequency Range Designation FR3 (7.125 GHz - 24.25 GHz). Bands falling within FR3 can inherit FR1 characteristics and / or FR2 characteristics, and thus can effectively extend the features of FR1 and / or FR2 to mid-band frequencies. In addition, higher bands are currently being explored to extend 5G NR operations beyond 52.6 GHz. For example, three higher operating bands have been identified as Frequency Range Designation FR4a or FR4-1 (52.6 GHz – 71 GHz), FR4 (52.6 GHz – 114.25 GHz), and FR5 (114.25 GHz – 300 GHz). Each of these higher bands falls within the EHF band.

[0044] Considering the above examples, unless otherwise specifically stated, it should be understood that if the term “sub-6 GHz” etc. is used in this document, the term can generally represent frequencies that can be below 6 GHz, can be within FR1, or can include mid-band frequencies. Additionally, unless otherwise specifically stated, it should be understood that if the term “millimeter wave” etc. is used in this document, the term can generally represent frequencies that can include mid-band frequencies, can be within FR2, FR4, FR4-a or FR4-1 and / or FR5, or can be within the EHF band. It is envisioned that the frequencies included in these operating bands (e.g., FR1, FR2, FR3, FR4, FR4-a, FR4-1, and / or FR5) can be modified, and the techniques described herein apply to those modified frequency ranges.

[0045] In some aspects, a first device (e.g., UE 120 or network node 110) may include a communication manager 140. As described in more detail elsewhere herein, the communication manager 140 may receive a plurality of reference signals from a second device based at least in part on a plurality of beams; transmit an angle of departure (AoD) associated with a reference signal among the plurality of reference signals to the second device; receive an incremental value indicating a difference between the AoD and a beam pointing angle of a custom second device beam from the second device; and receive data from the second device using a custom first device beam derived at least in part based on the incremental value. Additionally or alternatively, the communication manager 140 may perform one or more other operations described herein.

[0046] In some aspects, a second device (e.g., network node 110 or UE 120) may include a communication manager 150. As described in more detail elsewhere herein, the communication manager 150 may transmit a plurality of reference signals to a first device based at least in part on a plurality of beams; receive an AoD associated with a reference signal among the plurality of reference signals from the first device; transmit an incremental value indicating a difference between the AoD and a beam pointing angle of a custom second device beam to the first device; and transmit data to the first device using the custom second device beam. Additionally or alternatively, the communication manager 150 may perform one or more other operations described herein.

[0047] As indicated above, Figure 1 is provided as an example. Other examples may differ from what is described with respect to Figure 1 what is described.

[0048] Figure 2 FIG. 200 is a diagram illustrating an example 200 of communication between a network node 110 and a UE 120 in a wireless network 100 in accordance with the present disclosure. The network node 110 may be equipped with a set of antennas 234a through 234t, such as T antennas (T≥1). The UE 120 may be equipped with a set of antennas 252a through 252r, such as R antennas (R≥1). The network node 110 of example 200 includes one or more radio frequency components, such as antennas 234 and a modem 254. In some examples, the network node 110 may include an interface, a communication component, or another component that facilitates communication with the UE 120 or another network node. Some network nodes 110 may not include radio frequency components that facilitate direct communication with the UE 120, such as one or more CUs or one or more DUs.

[0049] At network node 110, transmit processor 220 may receive data destined for UE 120 (or a set of UEs 120) from data source 212. Transmit processor 220 may select one or more modulation and coding schemes (MCSs) for UE 120 based at least in part on one or more channel quality indicators (CQIs) received from UE 120. Network node 110 may process (e.g., encode and modulate) data for UE 120 based at least in part on the MCS selected for UE 120, and may provide data symbols for UE 120. Transmit processor 220 may process system information (e.g., for semi-static resource allocation information (SRPI)) and control information (e.g., CQI requests, grants, and / or upper layer signaling), and may provide overhead symbols and control symbols. Transmit processor 220 may generate reference symbols for reference signals (e.g., cell-specific reference signal (CRS) or demodulation reference signal (DMRS)) and synchronization signals (e.g., primary synchronization signal (PSS) or secondary synchronization signal (SSS)). Transmit (TX) multiple-input multiple-output (MIMO) processor 230 may perform spatial processing (e.g., precoding) on the data symbols, control symbols, overhead symbols, and / or reference symbols, if applicable, and may provide a set of output symbol streams (e.g., T output symbol streams) to a corresponding set of modems 232 (e.g., T modems) (shown as modems 232a through 232t). For example, each output symbol stream may be provided to a modulator component (shown as MOD) of a modem 232. Each modem 232 may process the corresponding output symbol stream (e.g., for OFDM) using the corresponding modulator component to obtain a stream of output samples. Each modem 232 may also process the stream of output samples (e.g., convert to analog, amplify, filter, and / or up-convert) using the corresponding modulator component to obtain a downlink signal. Modems 232a through 232t may transmit a set of downlink signals (e.g., T downlink signals) via a corresponding set of antennas 234 (e.g., T antennas) (shown as antennas 234a through 234t).

[0050] At the UE 120, a set of antennas 252 (shown as antennas 252a through 252r) may receive downlink signals from the network node 110 and / or other network nodes 110 and may provide a set of received signals (e.g., R received signals) to a set of modems 254 (e.g., R modems) (shown as modems 254a through 254r). For example, each received signal may be provided to a demodulator component (shown as DEMOD) of the modem 254. Each modem 254 may use the corresponding demodulator component to condition (e.g., filter, amplify, down-convert, and / or digitize) the received signal to obtain input samples. Each modem 254 may use the demodulator component to further process the input samples (e.g., for OFDM) to obtain received symbols. The MIMO detector 256 may obtain the received symbols from the modems 254, may perform MIMO detection on the received symbols if applicable, and may provide the detected symbols. The receive processor 258 may process (e.g., demodulate and decode) the detected symbols, may provide the decoded data for the UE 120 to the data sink 260, and may provide the decoded control information and system information to the controller / processor 280. The term "controller / processor" may refer to one or more controllers, one or more processors, or a combination thereof. The channel processor may determine reference signal received power (RSRP) parameters, received signal strength indicator (RSSI) parameters, reference signal received quality (RSRQ) parameters, and / or CQI parameters, etc. In some examples, one or more components of the UE 120 may be included in the housing 284.

[0051] The network controller 130 may include a communication unit 294, a controller / processor 290, and a memory 292. The network controller 130 may include, for example, one or more devices in a core network. The network controller 130 may communicate with the network node 110 via the communication unit 294.

[0052] One or more antennas (e.g., antennas 234a through 234t and / or antennas 252a through 252r) may include one or more antenna panels, one or more antenna groups, one or more sets of antenna elements, and / or one or more antenna arrays, etc., or may be included within one or more antenna panels, one or more antenna groups, one or more sets of antenna elements, and / or one or more antenna arrays, etc. The antenna panel, antenna group, set of antenna elements, and / or antenna array may include one or more antenna elements (within a single housing or multiple housings), a set of coplanar antenna elements, a set of non-coplanar antenna elements, and / or one or more antenna elements coupled to one or more transmit and / or receive components (such as Figure 2 one or more components among).

[0053] On the uplink, at the UE 120, the transmit processor 264 may receive and process data from the data source 262 and control information from the controller / processor 280 (e.g., for reports including RSRP, RSSI, RSRQ, and / or CQI). The transmit processor 264 may generate reference symbols for one or more reference signals. The symbols from the transmit processor 264 may be precoded by the TX MIMO processor 266 if applicable, further processed by the modem 254 (e.g., for DFT-s-OFDM or CP-OFDM), and sent to the network node 110. In some examples, the modem 254 of the UE 120 may include a modulator and a demodulator. In some examples, the UE 120 includes a transceiver. The transceiver may include any combination of the antenna 252, the modem 254, the MIMO detector 256, the receive processor 258, the transmit processor 264, and / or the TX MIMO processor 266. The transceiver may be used by a processor (e.g., the controller / processor 280) and the memory 282 to perform aspects of any of the methods described herein (e.g., with reference to Figures 9 to 14 ) for any of the methods described herein.

[0054] At the network node 110, the uplink signals from the UE 120 and / or other UEs may be received by the antenna 234, processed by the modem 232 (e.g., the demodulator component of the modem 232, shown as DEMOD), detected by the MIMO detector 236 if applicable, and further processed by the receive processor 238 to obtain the decoded data and control information transmitted by the UE 120. The receive processor 238 may provide the decoded data to the data sink 239 and the decoded control information to the controller / processor 240. The network node 110 may include a communication unit 244 and may communicate with the network controller 130 via the communication unit 244. The network node 110 may include a scheduler 246 to schedule one or more UEs 120 for downlink communication and / or uplink communication. In some examples, the modem 232 of the network node 110 may include a modulator and a demodulator. In some examples, the network node 110 includes a transceiver. The transceiver may include any combination of the antenna 234, the modem 232, the MIMO detector 236, the receive processor 238, the transmit processor 220, and / or the TX MIMO processor 230. The transceiver may be used by a processor (e.g., the controller / processor 240) and the memory 242 to perform aspects of any of the methods described herein (e.g., with reference to Figures 9 to 14 ) for any of the methods described herein.

[0055] The controller / processor 240 of network node 110, the controller / processor 280 of UE 120, and / or Figure 2 any other components in may perform one or more techniques associated with signaling information for custom beams, as described in more detail elsewhere herein. In some aspects, the first device or the second device described herein is network node 110, included in network node 110, or includes Figure 2 one or more components of network node 110 as shown. In some aspects, the first device or the second device described herein is UE 120, included in UE 120, or includes Figure 2 one or more components of UE 120 as shown. For example, the controller / processor 240 of network node 110, the controller / processor 280 of UE 120, and / or Figure 2 any other components may execute or direct, for example Figure 11 process 1100 of Figure 12 process 1200 of and / or other processes as described herein. Memory 242 and memory 282 may store data and program code for network node 110 and UE 120, respectively. In some examples, memory 242 and / or memory 282 may include non-transitory computer-readable media storing one or more instructions for wireless communication (e.g., code and / or program code). For example, when executed by one or more processors of network node 110 and / or UE 120 (e.g., directly, or after compilation, transformation, and / or interpretation), the one or more instructions may cause the one or more processors, UE 120, and / or network node 110 to execute or direct, for example Figure 11 process 1100 of Figure 12 process 1200 of and / or other processes as described herein. In some examples, executing the instructions may include running the instructions, transforming the instructions, compiling the instructions, and / or interpreting the instructions, etc.

[0056] In some aspects, a first device (e.g., UE 120 or network node 110) includes components for receiving a plurality of reference signals from a second device based at least in part on a plurality of beams; for transmitting to the second device an AoD associated with a reference signal among the plurality of reference signals; for receiving from the second device an incremental value indicating a difference between the AoD and a beam pointing angle of a customized second device beam; and / or for receiving data from the second device using a customized first device beam derived at least in part based on the incremental value. In some aspects, the components for the first device to perform the operations described herein may include one or more of, for example, communication manager 150, transmission processor 220, TX MIMO processor 230, modem 232, antenna 234, MIMO detector 236, receive processor 238, controller / processor 240, memory 242, or scheduler 246. In some aspects, the components for the first device to perform the operations described herein may include one or more of, for example, communication manager 140, antenna 252, modem 254, MIMO detector 256, receive processor 258, transmit processor 264, TX MIMO processor 266, controller / processor 280, or memory 282.

[0057] In some aspects, a second device (e.g., network node 110 or UE 120) includes components for transmitting a plurality of reference signals to a first device based at least in part on a plurality of beams; for receiving from the first device an AoD associated with a reference signal among the plurality of reference signals; for transmitting to the first device an incremental value indicating a difference between the AoD and a beam pointing angle of a customized second device beam; and / or for transmitting data to the first device using a customized second device beam. In some aspects, the components for the second device to perform the operations described herein may include one or more of, for example, communication manager 150, transmit processor 220, TX MIMO processor 230, modem 232, antenna 234, MIMO detector 236, receive processor 238, controller / processor 240, memory 242, or scheduler 246. In some aspects, the components for the second device to perform the operations described herein may include one or more of, for example, communication manager 140, antenna 252, modem 254, MIMO detector 256, receive processor 258, transmit processor 264, TX MIMO processor 266, controller / processor 280, or memory 282.

[0058] Although Figure 2The boxes in [ ] are illustrated as separate components, but the functions described above for these boxes can be implemented in a single hardware, software, or combined component, or in various combinations of components. For example, the functions described for the transmit processor 264, receive processor 258, and / or TX MIMO processor 266 can be performed by, or under the control of, the controller / processor 280.

[0059] As indicated above, Figure 2 is provided as an example. Other examples may differ from what is described with respect to Figure 2 what is described.

[0060] The deployment of a communication system such as a 5G NR system can be arranged in various ways using various components or constituent parts. In a 5G NR system or network, network nodes, network entities, mobility elements of the network, RAN nodes, core network nodes, network elements, base stations, or network equipment can be implemented in a converged or decomposed architecture. For example, a base station (such as a Node B (NB), evolved NB (eNB), NR BS, 5G NB, access point (AP), TRP, or cell, etc.) or one or more units (or one or more components) performing base station functionality can be implemented as a converged base station (also referred to as a stand-alone base station or monolithic base station) or a decomposed base station. A "network entity" or "network node" can refer to a decomposed base station or one or more units of a decomposed base station (such as one or more CUs, one or more DUs, one or more RUs, or a combination thereof).

[0061] A converged base station (e.g., a converged network node) can be configured to utilize a radio protocol stack that is physically or logically integrated within a single RAN node (e.g., within a single device or unit). A decomposed base station (e.g., a decomposed network node) can be configured to utilize a protocol stack that is physically or logically distributed among two or more units (such as one or more CUs, one or more DUs, or one or more RUs). In some examples, a CU can be implemented within a network node, and one or more DUs can be co-located with the CU, or alternatively, can be geographically or virtually spread across one or more other network nodes. A DU can be implemented to communicate with one or more RUs. Each of the CU, DU, and RU can also be implemented as a virtual unit, such as a virtual central unit (VCU), virtual distributed unit (VDU), or virtual radio unit (VRU), etc.

[0062] Base station type operations or network designs can consider the aggregation characteristics of base station functionality. For example, a disaggregated base station can be utilized in an IAB network, an open radio access network (O-RAN, such as a network configuration initiated by the O-RAN Alliance), or a virtualized radio access network (vRAN, also known as a cloud radio access network (C-RAN)) to facilitate the scaling of a communication system by separating base station functionality into one or more units that can be individually deployed. A disaggregated base station can include functionality implemented across two or more units at various physical locations, as well as functionality implemented virtually for at least one unit, which can achieve flexibility in network design. Each unit of the disaggregated base station can be configured for wired or wireless communication with at least one other unit of the disaggregated base station.

[0063] Figure 3 FIG. is a diagram illustrating an example disaggregated base station architecture 300 according to the present disclosure. The disaggregated base station architecture 300 can include a CU 310, which can communicate directly with a core network 320 via a backhaul link, or indirectly with the core network 320 through one or more disaggregated control units, such as a near RT RIC 325 via an E2 link, or a non-RT RIC 315 associated with a service management and orchestration (SMO) framework 305, or both. The CU 310 can communicate with one or more DUs 330 via respective midhaul links, such as through an F1 interface. Each DU in the DUs 330 can communicate with one or more RUs 340 via a respective fronthaul link. Each RU in the RUs 340 can communicate with one or more UEs 120 via a respective radio frequency (RF) access link. In some specific implementations, a UE 120 can be served simultaneously by multiple RUs 340.

[0064] Each unit (including the CU 310, DU 330, RU 340) and the near RT RIC 325, non-RT RIC 315, and SMO framework 305 can include one or more interfaces or be coupled to one or more interfaces, which are configured to receive or transmit signals, data, or information (collectively referred to as signals) via a wired or wireless transmission medium. Each unit or an associated processor or controller that provides instructions to one or more communication interfaces of a respective unit can be configured to communicate with one or more other units via the transmission medium. In some examples, each unit can include a wired interface and a wireless interface, the wired interface being configured to receive signals or transmit signals to one or more other units via a wired transmission medium, and the wireless interface can include a receiver, a transmitter, or a transceiver (such as an RF transceiver), the wireless interface being configured to receive signals or transmit signals to one or more other units via a wireless transmission medium or perform both.

[0065] In some aspects, the CU 310 may host one or more higher layer control functions. Such control functions may include Radio Resource Control (RRC) functions, Packet Data Convergence Protocol (PDCP) functions, or Service Data Adaptation Protocol (SDAP) functions, among others. Each control function may be implemented using an interface that is configured to communicate signals with other control functions hosted by the CU 310. The CU 310 may be configured to handle user plane functionality (e.g., Central Unit - User Plane (CU-UP) functionality), control plane functionality (e.g., Central Unit - Control Plane (CU-CP) functionality), or a combination thereof. In some specific implementations, the CU 310 may be logically divided into one or more CU-UP units and one or more CU-CP units. When implemented in an O-RAN configuration, the CU-UP units may communicate bidirectionally with the CU-CP units via an interface such as the E1 interface. As needed, the CU 310 may be implemented to communicate with the DU 330 for network control and signaling.

[0066] Each DU 330 may correspond to a logical unit that includes one or more base station functions for controlling the operation of one or more RUs 340. In some aspects, the DU 330 may host at least part of the Radio Link Control (RLC) layer, the MAC layer, and one or more of the higher Physical (PHY) layers, at least in accordance with a functional split such as the one defined by 3GPP. In some aspects, one or more of the higher PHY layers may be implemented by one or more modules for forward error correction (FEC) encoding and decoding, scrambling, and modulation and demodulation, among other things. In some aspects, the DU 330 may also host one or more lower PHY layers, such as those implemented by one or more modules for fast Fourier transform (FFT), inverse FFT (iFFT), digital beamforming, or physical random access channel (PRACH) extraction and filtering, among other things. Each layer (which may also be referred to as a module) may be implemented using an interface that is configured to communicate signals with other layers (and modules) hosted by the DU 330 or with control functions hosted by the CU 310.

[0067] Each RU 340 can implement lower layer functionality. In some deployments, the RU 340 controlled by the DU 330 can correspond to a logical node that hosts RF processing functions or low PHY layer functions, such as performing FFT, performing iFFT, digital beamforming, or PRACH extraction and filtering, etc., based on a functional split (e.g., the functional split defined by 3GPP) such as a lower layer functional split. In such an architecture, each RU 340 can be operated to handle over-the-air (OTA) communication with one or more UEs 120. In some embodiments, the real-time and non-real-time aspects of the control plane and user plane communication with the RU 340 can be controlled by the corresponding DU 330. In some scenarios, this configuration can enable each DU 330 and CU 310 to be implemented in a cloud-based RAN architecture such as a vRAN architecture.

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

[0069] The non-RT RIC 315 can be configured to include logic functions that implement non-real-time control and optimization of RAN elements and resources, artificial intelligence / machine learning (AI / ML) workflows including model training and updating, or policy-based guidance of applications / features in the near-RT RIC 325. The non-RT RIC 315 can be coupled to or communicate with the near-RT RIC 325 (such as via the A1 interface). The near-RT RIC 325 can be configured to include logic functions that enable near-real-time control and optimization of RAN elements and resources via an interface (such as via the E2 interface) through data collection and actions, which interface connects one or more CUs 310, one or more DUs 330, or both, and the O-eNB to the near-RT RIC 325.

[0070] In some specific implementations, to generate an AI / ML model to be deployed in the near-RT RIC 325, the non-RT RIC 315 can receive parameters or external enrichment information from an external server. Such information can be utilized by the near-RT RIC 325 and can be received from non-network data sources or from network functions at the SMO framework 305 or the non-RT RIC 315. In some examples, the non-RT RIC 315 or the near-RT RIC 325 can be configured to tune RAN behavior or performance. For example, the non-RT RIC 315 can monitor long-term trends and patterns of performance and employ an AI / ML model to perform corrective actions through the SMO framework 305 (such as reconfiguration via the O1 interface) or via the creation of RAN management policies (such as A1 interface policies).

[0071] As indicated above, Figure 3 is provided as an example. Other examples may be different from what is described with respect to Figure 3 what is described.

[0072] Analog beamforming at millimeter wave frequencies can be improved by using compressive sensing / machine learning tools to obtain information about the underlying raw channel. The per-tone hybrid beamforming input-output relationship (y) for the downlink can be defined according to y = AHBPx + n. Here, H indicates the raw channel matrix, which can be represented by N Rx ×N Tx representation. H can vary with core parameters such as the number of clusters and the angle of arrival (AoA), angle of departure (AoD), zenith angle of arrival (ZoA), zenith angle of departure (ZoD), delay, and / or power of each cluster. Additionally, A can indicate the receive (Rx) (analog) beamforming matrix, which can be represented by N RP ×N Rx representation. Additionally, B can indicate the Tx (analog) beamforming matrix, which can be represented by N Tx ×NTP denoted. Additionally, x may indicate a transmitted signal vector, and n may indicate additive white Gaussian noise. Additionally, P may indicate a Tx (digital) precoding matrix, which may be represented by N TP ×N SS denoted. Multiple Tx and Rx beamforming measurements (A i HB j ) may be used to infer some information about the original channel H. This information may be associated with channel AoA / AoD estimation. The information obtained about the original channel H may be used for dynamic codebook adaptation and for creating custom non-codebook-based analog beams, which may improve capacity. Additionally, the information obtained about the original channel H may be used to predict oversampled codebook indices via non-oversampled codebook measurements, which may reduce overhead.

[0073] Figure 4 is a diagram illustrating Example 400 of the per-tone hybrid beamforming input-output relationship for the downlink according to the present disclosure.

[0074] As Figure 4 shown, a receiver (e.g., a UE) may include a digital beamformer that may be associated with an analog beamformer of the receiver. The analog beamformer of the receiver may be associated with an Rx (analog) beamforming matrix (A). The receiver may be associated with multiple Rx beams (e.g., A1 to A N ). Multiple Rx beams may be respectively associated with multiple pointing directions and multiple predefined codebooks. Multiple Rx beams may be associated with multiple codebook-based beams. A transmitter (e.g., a network node) may include a digital precoder (P) that may be associated with an analog beamformer of the transmitter. The analog beamformer of the transmitter may be associated with a Tx (analog) beamforming matrix (B). The transmitter may be associated with multiple Tx beams (e.g., B1 to B M ). Multiple Tx beams may be respectively associated with multiple pointing directions and multiple predefined codebooks. Multiple Tx beams may be associated with multiple codebook-based beams. A channel (H) may exist between the receiver and the transmitter.

[0075] As indicated above, Figure 4 is provided as an example. Other examples may be different from what is described with respect to Figure 4 .

[0076] A quantized representation of the channel in the angular space may be derived, where the channel may be between a receiver (e.g., a UE) and a transmitter (e.g., a network node). The angular space may be partitioned at the receiver and the transmitter into grids of sizes and respectively, where "azi" indicates azimuth angle and "elev" indicates elevation angle. The grid size values may be and The number of antennas at the receiver can be given by N UEant Represented by, and the number of antennas at the transmitter can be expressed by N NBant The dth quantized channel model is represented by th Delay taps (H d ) can be Indicates that P R A function that indicates the position vector of a receiver antenna element, may indicate the channel gain across the quantized transmit and receive angles and may be associated with the receiver and transmitter element responses, and P T A function that can indicate the position vector of the transmitter antenna element. In addition, P R can be express, can be indicates that, and can be For example, P R can be [8×[16×16]], can be [[16×16]×[64×32]], and Can be: [[64×32]×64]. Channels can be based on Rewritten in vectorized format, where May be associated with a channel sparse dictionary (Ψ).

[0077] Figure 5 is a diagram illustrating an example 500 of a quantized representation of channels in an angular space according to the present disclosure.

[0078] like Figure 5 As shown, a receiver (e.g., a UE) may include a digital beamformer that may be associated with an analog beamformer of the receiver. The analog beamformer of the receiver may be associated with an Rx (analog) beamforming matrix (A). A transmitter (e.g., a network node) may include a digital precoder (P) that may be associated with the analog beamformer of the transmitter. The analog beamformer of the transmitter may be associated with a Tx (analog) beamforming matrix (B). A channel (H) may exist between the receiver and the transmitter. The AoD / ZoD may be quantized to one of four adjacent two-dimensional (2D) grid points, wherein the 2D grid points may be based at least in part on an angular space that is divided into a grid of a specific size at the receiver and the transmitter.

[0079] As indicated above, Figure 5 are provided as examples. Other examples can be found in the Figure 5 The content described is different.

[0080] Figure 6 FIG. 600 illustrates an example 600 of a sparse recovery formula for an original channel estimate according to the present disclosure.

[0081] As shown by reference numeral 602, a receiver (e.g., a UE) may be associated with multiple Rx beams (e.g., A1 to A4) that may include Rx beam A i A transmitter (e.g., a network node) may be associated with multiple Tx beams (e.g., B1 to B i ) that may include Tx beam B N ). As shown by reference numeral 604, a channel impulse response (CIR) of (A i , B i ) may be defined. The d th -th delay tap of the CIR of the i th -th Tx beam and the i th -th Rx beam may be defined as y d,i , where where (sparse dictionary), and Φ i may be a function of the Tx and Rx analog beamforming matrices for the i th -th measurement. As shown by reference numeral 606, a receiver (e.g., a UE) may be associated with multiple Rx beams (e.g., A1 to A4) that may include Rx beam Aj. For example, a transmitter (e.g., a network node) may be associated with multiple Tx beams (B1 to BN) that may include Tx beam Bj. The d th -th delay tap of the CIR of the j th -th Tx beam and the j th -th Rx beam may be defined as y d,j . As shown by reference numeral 608, a CIR of (A j , B j ) may be defined. With respect to the CIR of (A i , B i ) and the CIR of (A j , B j ),

[0082] When considering the CIRs corresponding to M different beam pairs, multiple equations may be stacked to obtain the following equation:

[0083]

[0084] where may be a sparse representation of the channel vector. Given yd and the measurement matrix ΦΨ, orthogonal matching pursuit (OMP) may be used to recover and thus recover Hd.

[0085] Figure 7 FIG. 700 is a diagram illustrating an example 700 of a sparse recovery formula for an original channel estimate according to the present disclosure.

[0086] As Figure 7 shown, a receiver (e.g., a UE) may include a digital beamformer that may be associated with an analog beamformer of the receiver. The analog beamformer of the receiver may be associated with an Rx (analog) beamforming matrix (A). A transmitter (e.g., a network node) may include a digital precoder (P) that may be associated with an analog beamformer of the transmitter. The analog beamformer of the transmitter may be associated with a Tx (analog) beamforming matrix (B). A channel (H) may exist between the receiver and the transmitter. The channel that may be represented by Hd may be derived at least in part based on M different beam pairs. The M different beam pairs may correspond to Rx-Tx beam pairs between the receiver and the transmitter. Given yd and a measurement matrix φψ that may be at least in part based on the M different beam pairs, OMP may be used to recover and thus recover Hd.

[0087] As indicated above, Figure 7 is provided as an example. Other examples may be different from what is described with respect to Figure 7 the content.

[0088] A receiver (e.g., a UE) may determine some information about a transmitter (e.g., a network node) in order to perform the OMP process for sparse recovery. For each transmit antenna s, the receiver may determine (the position vector of Tx antenna element s) such that the receiver may compute the dot product and then compute where may be computed at a quantized set of angles θ n,m,ZoD and φ n,m,AoD . The receiver may compute for multiple Tx antennas s and the quantized set of angles (θ n,m,ZoD and φ n,m,AoD ) in the grid and then the receiver may accumulate the results in . The UE may determine B i (the transmitter array response) of the transmitter codebook beam such that the UE is able to compute

[0089] The receiver can run the OMP process for sparse recovery. The receiver can run OMP on the tap d, and the receiver can run the OMP process for each tap. By exploiting the sparsity of the millimeter-wave channel in the tap domain, the OMP process can be run on several dominant taps. For each tap, in each iteration of the OMP process, the most likely AoA, AoD, ZoA, and / or ZoD can be identified. Through the iterative process, the contribution of the identified angles can be subtracted from the observation vector and the residual can be calculated. The OMP process can be iterated until a point where a specific criterion is met (e.g., the mean square error (MSE) of the residual is less than a threshold) or a fixed number of iterations are performed.

[0090] The receiver can obtain the input y via the OMP process. d The inputs of Φ and Ψ. The receiver can perform initialization via the OMP process such that y′ d = y d . The receiver can set via the OMP process The receiver can determine via the OMP process where the i th th index can correspond to an AoA, AoD, ZoA, and / or ZoD quadruple from the sparse dictionary. The receiver can extract via the OMP process where and a R is associated with the receiver (UE) antenna element response vector, and a T is associated with the transmitter (network node) antenna element response vector. The receiver can calculate via the OMP process The receiver can determine via the OMP process and determine the residual according to . The receiver can determine via the OMP process and the output of x d .

[0091] Figure 8 is a diagram illustrating Example 800 of a custom non-codebook-based beam according to the present disclosure.

[0092] As Figure 8As shown, custom non-codebook-based beams can be created at a receiver (e.g., a UE) and a transmitter (e.g., a network node), where the custom non-codebook-based beams can be customized to the underlying raw channel between the receiver and the transmitter using OMP. The custom non-codebook-based beams can be at least partially based on the strongest signal path between the receiver and the transmitter. In some cases, the receiver and the network node can point their beams in the direction of the strongest cluster. The receiver can send feedback to the network node regarding the estimated AoD, and the network node can use this feedback to create a custom non-codebook-based Tx beam that is customized to the underlying channel. Compared to DFT (codebook-based) beams, the custom non-codebook-based beams can provide better metrics (e.g., better spectral efficiency).

[0093] As indicated above, Figure 8 is provided as an example. Other examples may be different from what is described with respect to Figure 8 what is described.

[0094] Codebook beams can be associated with predefined directions and cannot be customized to the channel. For example, a first device and a second device can communicate with each other using codebook beams, but such codebook beams may not be specifically customized to the channel between the first device and the second device. Non-codebook-based beams can be created to be customized to the channel between the first device and the second device. The first device and / or the second device can signal an indication of the beam aiming direction, which can help create the non-codebook-based beams. However, the inefficiency of signaling the indication of the beam aiming direction can increase the signaling overhead between the first device and the second device.

[0095] In various aspects of the techniques and apparatuses described herein, a first device (e.g., a UE) may receive a plurality of reference signals from a second device (e.g., a network node) at least in part based on a plurality of beams. The first device may send an AoD associated with a reference signal among the plurality of reference signals to the second device. The first device may receive from the second device an incremental value indicating a difference between the AoD and a beam pointing angle of a custom second device beam. The incremental value may be a differential value. The first device may receive data from the second device using a custom first device beam derived at least in part based on the incremental value. The first device may determine the custom first device beam at least in part based on the incremental value, where the incremental value may be at least in part based on the AoD reported by the first device. The first device may determine a beam aiming direction associated with the custom first device beam at least in part based on the incremental value. The second device may use the custom second device beam to send data. The custom second device beam may be associated with the beam aiming direction. Contrary to a transmit-receive beam pair based at least in part on a predefined codebook, the custom first device beam and the custom second device beam may correspond to a custom transmit-receive beam pair, which may improve the data rate over the channel due to using the strongest signal path between the first device and the second device.

[0096] In some aspects, a differential beam aiming line direction angle may be indicated. In a first option, the second device may create a predefined two-dimensional grid and index the grid points. The second device may calculate an angle difference with respect to the nearest grid point on the two-dimensional grid. In a second option, the second device may signal the aiming direction of a second device codebook beam to the first device. The second device may calculate an angle difference with respect to the nearest beam of the second device codebook beam. However, a drawback of these options is that the differential value (e.g., the angle difference) may need to be accompanied by an index of the grid point such that the first device can identify the direction. In other words, the second device may also need to indicate the index of the grid point, which may increase the signaling overhead. Reducing the signaling overhead may be important when dynamic signaling is employed for codebook adaptation purposes.

[0097] In some aspects, the incremental value (or differential value) may be calculated relative to a value (e.g., AoD) that the first UE has estimated and knows, so the second device may only need to indicate the incremental value instead of a reference point (e.g., the index of a grid point), thereby reducing the amount of signaling between the first device and the second device.

[0098] Figure 9 is a diagram illustrating example 900 associated with signaling information for a custom beam according to the present disclosure. As Figure 9As shown, example 900 includes communication between a first device (e.g., UE 120 or network node 110) and a second device (e.g., network node 110 or UE 120). In some aspects, the first device and the second device may be included in a wireless network (such as wireless network 100).

[0099] In some aspects, the first device may be a UE and the second device may be a network node. Alternatively, the first device may be a network node and the second device may be a UE.

[0100] As shown by reference numeral 902, the first device may receive a plurality of reference signals from the second device. The second device may transmit the plurality of reference signals based at least in part on a plurality of Tx beams (e.g., B1 to B N )). The first device may receive the plurality of reference signals based at least in part on a plurality of Rx beams (e.g., A1 to A4). In some aspects, when the first device is a UE and the second device is a network node, the plurality of reference signals may be downlink reference signals. In some aspects, when the first device is a network node and the second device is a UE, the plurality of reference signals may be uplink reference signals.

[0101] As shown by reference numeral 904, the first device may send an AoD associated with a reference signal among the plurality of reference signals to the second device. The first device may determine an AoD associated with a reference signal among the plurality of reference signals. The first device may estimate the channel AoD based at least in part on the plurality of reference signals received from the second device. Additionally or alternatively, the first device may determine an AoA associated with a reference signal among the plurality of reference signals. The first device may estimate the channel AoA based at least in part on the plurality of reference signals received from the second device. The first device may send an AoD and / or an AoA associated with a reference signal among the plurality of reference signals to the second device. In some aspects, the first device may send an indication of a confidence level associated with the AoD and / or the AoA, where the confidence level may be used by the second device for custom beam selection. Thus, the first device may estimate the AoD and / or the AoA, and the first device may report the estimated AoD and / or the AoA to the second device.

[0102] As shown by reference numeral 906, the first device may receive an incremental value indicating the difference between the AoD and the beam pointing angle of the custom beam of the second device from the second device. The first device may receive the incremental value via differential signaling. The incremental value may indicate the azimuth difference between the AoD and the beam pointing angle of the custom beam of the second device. The incremental value may indicate the elevation difference between the AoD and the beam pointing angle of the custom beam of the second device. Thus, the incremental value (Δ) may indicate the azimuth and elevation associated with the custom beam of the second device related to the AoD and / or the AoA reported by the first device.

[0103] In some aspects, the second device may select a custom second device beam at least partially based on the AoD and / or AoA indicated by the first device. For example, the second device may select a custom second device beam having a beam pointing angle closest to the AoD and / or AoA indicated by the first device compared to other custom second device beams having other respective beam pointing angles. Due to second device hardware constraints, the second device may not be able to point the custom beam exactly at the AoD and / or AoA estimated by the first device, but the second device may attempt to create a custom second device beam relatively close to the AoD and / or AoA estimated by the first device. The second device may calculate an incremental value after selecting the custom second device beam having the beam pointing angle closest to the AoD and / or AoA indicated by the first device. In some aspects, the incremental value may indicate the difference between the AoD and / or AoA estimated by the first device and the beam pointing angle associated with the beam aiming direction of the custom second device beam.

[0104] In some aspects, the first device may receive the incremental value from the second device via downlink control information (DCI). Alternatively, the first device may receive the incremental value from the second device via a medium access control control element (MAC-CE).

[0105] As shown by reference numeral 908, the first device may receive data from the second device using a custom first device beam derived at least partially based on the incremental value. The second device may transmit data to the first device using the custom second device beam. The custom second device beam may be associated with a beam aiming direction that may correspond to the beam aiming direction associated with the custom first device beam. The first device may derive the custom first device beam at least partially based on the incremental value, which may be at least partially based on the incremental value related to the AoD and / or AoA reported by the first device. The custom second device beam and the custom first device beam may be custom non-codebook-based analog beams. The custom second device beam may be a custom non-codebook-based analog Rx beam, and the custom first device beam may be a custom non-codebook-based analog Tx beam.

[0106] In some aspects, the first device can be a UE, the second device can be a gNB, the custom second device beam can be a custom gNB beam, and the custom first device beam can be a custom UE beam. In this case, the AoD and / or AoA reported by the UE can be at least partially based on downlink reference signals. In some aspects, the first device can be a gNB, the second device can be a UE, the custom second device beam can be a custom UE beam, and the custom first device beam can be a custom gNB beam. In this case, the AoD and / or AoA reported by the gNB can be at least partially based on uplink reference signals.

[0107] In some aspects, the first device may not receive an incremental value from the second device. Instead, the first device can receive an acknowledgement (ACK) that the custom second device beam is sufficiently aligned with the AoD from the second device at least partially based on the incremental value meeting a threshold. In this case, the first device can determine the custom first device beam at least partially based on the AoD and / or AoA reported by the first device, rather than at least partially based on the incremental value.

[0108] In some aspects, if the second device may not be able to create the custom second device beam relatively close to the AoD and / or AoA estimated by the first device (e.g., the second device cannot create a custom beam along the estimated AoD), or the AoD and / or AoA estimated by the first device is closer to a codebook-based beam than a threshold, then the second device can select the beam from the existing codebook that is closest to the AoD and / or AoA estimated by the first device. In other words, in some cases, the beam from the existing codebook can be closer to the estimated AoD and / or estimated AoA compared to any custom beam that can be created by the second device.

[0109] In some aspects, when the first device indicates the AoD and / or AoA to the second device, the first device can also indicate a confidence level associated with the AoD and / or AoA. The second device can determine whether to create a custom second device beam at least partially based on the confidence level. For example, the second device can create a custom second device beam at least partially based on a high confidence level. As another example, the second device can fall back to existing behavior and use its codebook beam at least partially based on a low confidence level.

[0110] In some aspects, the second device (e.g., a network node) can signal a differential line-of-sight direction to the first device (e.g., a UE) for downlink communication from the second device to the first device. In some aspects, the first (e.g., UE) device can signal a differential line-of-sight direction to the second device (e.g., a network node) for uplink communication from the first device to the second device.

[0111] As indicated above, Figure 9 is provided as an example. Other examples may be different from what is Figure 9 described.

[0112] Figure 10 is a diagram illustrating Example 1000 associated with signaling information for a custom beam according to the present disclosure.

[0113] As Figure 10 shown, the angular space between a first device (e.g., a UE) and a second device (e.g., a network node) may be divided to form a two-dimensional grid. The first device may report the AoD associated with a reference signal to the second device. The second device may determine the beam point angle of a custom second device beam. The second device may select the custom second device beam at least in part based on the AoD reported by the first device. For example, the second device may select a custom second device beam that is within a particular distance and / or angle of the AoD reported by the first device. The custom second device beam may not be one of the 32 codebook-based beams associated with the second device, which are shown in relation to the two-dimensional grid. The second device may determine an incremental value (Δ) between the AoD reported by the first device and the beam pointing angle of the custom second device beam. The incremental value may include an azimuth increment (Δφ) relative to the AoD reported by the first device, and the incremental value may include an elevation increment (Δθ) relative to the AoD reported by the first device. In other words, for a second device-side custom beam for transmission (e.g., downlink transmission), the second device may signal the incremental values of the azimuth and elevation relative to the AoD reported by the first device. Compared to signaling the absolute value of the beam pointing angle, differential signaling (e.g., signaling the incremental values) for a custom non-codebook-based beam may reduce overhead and improve accuracy.

[0114] In some aspects, the sign of the incremental value may be at least in part based on the direction relative to the second device panel. For example, moving left relative to the reported AoD may correspond to a positive azimuth difference (Δφ > 0), and vice versa. Additionally, in this example, rising relative to the reported AoD may correspond to a positive elevation gain (Δθ > 0), and vice versa. In some aspects, when the incremental value meets a threshold (e.g., the incremental value is less than the threshold), the second device may send a low-overhead ACK, which may indicate that the custom second device beam (e.g., custom Tx beam) is sufficiently aligned with the channel AoD. In this case, instead of sending the exact incremental value (or exact difference value) to the first device, the second device may send only an ACK to the first device.

[0115] As indicated above, Figure 10 is provided as an example. Other examples may be different from what is Figure 10is different from the described content.

[0116] Figure 11 is a diagram illustrating an example process 1100 performed by a first device, for example, according to the present disclosure. The example process 1100 is an example in which a first device (e.g., UE 120 or network node 110) performs operations associated with signaling information for a custom beam.

[0117] As Figure 11 shown, in some aspects, process 1100 may include receiving a plurality of reference signals from a second device at least in part based on a plurality of beams (block 1110). For example, a first device (e.g., using the receiving component 1302 depicted in Figure 13 ) may receive a plurality of reference signals from a second device at least in part based on a plurality of beams, as described above.

[0118] As Figure 11 further shown, in some aspects, process 1100 may include sending an AoD associated with a reference signal among the plurality of reference signals to the second device (block 1120). For example, a first device (e.g., using the transmitting component 1304 depicted in Figure 13 ) may send an AoD associated with a reference signal among the plurality of reference signals to the second device, as described above.

[0119] As Figure 11 further shown, in some aspects, process 1100 may include receiving an incremental value indicating a difference between the AoD and a beam pointing angle of a custom second device beam from the second device (block 1130). For example, a first device (e.g., using the receiving component 1302 depicted in Figure 13 ) may receive an incremental value indicating a difference between the AoD and a beam pointing angle of a custom second device beam from the second device, as described above.

[0120] As Figure 11 further shown, in some aspects, process 1100 may include receiving data from the second device using a custom first device beam derived at least in part based on the incremental value (block 1140). For example, a first device (e.g., using the receiving component 1302 depicted in Figure 13 ) may receive data from the second device using a custom first device beam derived at least in part based on the incremental value, as described above.

[0121] Process 1100 may include additional aspects, such as any single aspect or any combination of aspects described below and / or in combination with one or more other processes described elsewhere herein.

[0122] In a first aspect, the incremental value indicates the difference in azimuth between the AoD and the beam pointing angle of the customized second device beam.

[0123] In a second aspect, either alone or in combination with the first aspect, the incremental value indicates the difference in elevation between the AoD and the beam pointing angle of the customized second device beam.

[0124] In a third aspect, either alone or in combination with one or more of the first and second aspects, the incremental value is received from the second device via DCI.

[0125] In a fourth aspect, either alone or in combination with one or more of the first to third aspects, the incremental value is received from the second device via MAC-CE.

[0126] In a fifth aspect, either alone or in combination with one or more of the first to fourth aspects, process 1100 includes sending an indication of the confidence level associated with the AoD to the second device, and the customized second device beam is selected at least partially based on the confidence level.

[0127] In a sixth aspect, either alone or in combination with one or more of the first to fifth aspects, process 1100 includes receiving an acknowledgement that the customized second device beam is sufficiently aligned with the AoD from the second device at least partially based on the incremental value meeting a threshold.

[0128] In a seventh aspect, either alone or in combination with one or more of the first to sixth aspects, the customized second device beam and the customized first device beam are customized non-codebook-based analog beams.

[0129] In an eighth aspect, either alone or in combination with one or more of the first to seventh aspects, the first device is a UE and the second device is a network node, and the plurality of reference signals includes downlink reference signals, or the first device is a network node and the second device is a UE, and the plurality of reference signals includes uplink reference signals.

[0130] Although Figure 11 example boxes of process 1100 are shown, in some aspects, process 1100 may include additional boxes, fewer boxes, different boxes, or boxes arranged in a different manner compared to those depicted in Figure 11 Two or more boxes of process 1100 may be executed in parallel additionally or alternatively.

[0131] Figure 12FIG. is an illustration of an example process 1200 performed, for example, by a second device in accordance with the present disclosure. The example process 1200 is an example where the second device (e.g., network node 110 or UE 120) performs operations associated with signaling information for a custom beam.

[0132] As Figure 12 shown, in some aspects, process 1200 may include transmitting a plurality of reference signals to a first device based at least in part on a plurality of beams (block 1210). For example, the second device (e.g., using the Figure 14 transmission component 1404 depicted in ) may transmit a plurality of reference signals to the first device based at least in part on a plurality of beams, as described above.

[0133] As Figure 12 further shown, in some aspects, process 1200 may include receiving an AoD associated with a reference signal among the plurality of reference signals from the first device (block 1220). For example, the second device (e.g., using the Figure 14 receiving component 1402 depicted in ) may receive an AoD associated with a reference signal among the plurality of reference signals from the first device, as described above.

[0134] As Figure 12 further shown, in some aspects, process 1200 may include transmitting an incremental value indicating a difference between the AoD and a beam pointing angle of a custom second device beam to the first device (block 1230). For example, the second device (e.g., using the Figure 14 transmission component 1404 depicted in ) may transmit an incremental value indicating a difference between the AoD and a beam pointing angle of a custom second device beam to the first device, as described above.

[0135] As Figure 12 further shown, in some aspects, process 1200 may include transmitting data to the first device using the custom second device beam (block 1240). For example, the second device (e.g., using the Figure 14 transmission component 1404 depicted in ) may transmit data to the first device using the custom second device beam, as described above.

[0136] Process 1200 may include additional aspects, such as any single aspect described below and / or any combination of aspects described in conjunction with one or more other processes described elsewhere herein.

[0137] In a first aspect, the incremental value indicates one or more of a difference in azimuth between the AoD and a beam pointing angle of a custom second device beam or a difference in elevation between the AoD and a beam pointing angle of a custom second device beam.

[0138] In a second aspect, either alone or in combination with the first aspect, an incremental value is sent to the first device via DCI or via MAC-CE.

[0139] In a third aspect, either alone or in combination with one or more of the first and second aspects, process 1200 includes receiving, from the first device, an indication of a confidence level associated with an AoD, and a custom second device beam is selected at least in part based on the confidence level.

[0140] In a fourth aspect, either alone or in combination with one or more of the first to third aspects, process 1200 includes sending, to the first device, an acknowledgement that the custom second device beam is sufficiently aligned with the AoD at least in part based on the incremental value meeting a threshold.

[0141] In a fifth aspect, either alone or in combination with one or more of the first to fourth aspects, the first device is a UE and the second device is a network node, and the plurality of reference signals includes a downlink reference signal, or the first device is a network node and the second device is a UE, and the plurality of reference signals includes an uplink reference signal.

[0142] Although Figure 12 example blocks of process 1200 are shown, in some aspects, process 1200 may include additional blocks, fewer blocks, different blocks, or blocks arranged in a different manner compared to those depicted in Figure 12 Two or more of the blocks of process 1200 may be performed in parallel. Additionally or alternatively,

[0143] Figure 13 is a diagram of an example apparatus 1300 for wireless communication in accordance with the present disclosure. Apparatus 1300 may be the first device, or the first device may include apparatus 1300. In some aspects, apparatus 1300 includes a receiving component 1302 and a transmitting component 1304, which may communicate with each other (e.g., via one or more buses and / or one or more other components). As shown, apparatus 1300 may communicate with another device 1306 (such as a UE, a base station, or another wireless communication device) using receiving component 1302 and transmitting component 1304.

[0144] In some aspects, apparatus 1300 may be configured to perform one or more of the operations described herein in connection with Figures 9 to 10 Additionally or alternatively, apparatus 1300 may be configured to perform one or more of the processes described herein, such as Figure 11 process 1100. In some aspects, apparatus 1300 and / or Figure 13 one or more of the components shown may include one or more modules, circuits, and / or units associated with Figure 2One or more components of the first device described. Additionally or alternatively, Figure 13 One or more of the components shown may be implemented in combination with Figure 2 One or more components described. Additionally or alternatively, one or more components in a set of components may be at least partially implemented as software stored in a memory. For example, a component (or a portion of a component) may be implemented as instructions or code stored in a non-transitory computer-readable medium and executable by a controller or processor to perform the functions or operations of the component.

[0145] The receiving component 1302 may receive a communication from the device 1306, such as a reference signal, control information, data communication, or a combination thereof. The receiving component 1302 may provide the received communication to one or more other components of the device 1300. In some aspects, the receiving component 1302 may perform signal processing on the received communication (such as filtering, amplifying, demodulating, analog-to-digital conversion, demultiplexing, deinterleaving, demapping, equalizing, interference cancellation, or decoding, etc.), and may provide the processed signal to one or more other components of the device 1300. In some aspects, the receiving component 1302 may include one or more antennas, modems, demodulators, MIMO detectors, receiving processors, controller / processors, memories, or combinations thereof of the first device described in combination with Figure 2 One or more of the first device.

[0146] The transmitting component 1304 may transmit a communication to the device 1306, such as a reference signal, control information, data communication, or a combination thereof. In some aspects, one or more other components of the device 1300 may generate a communication and may provide the generated communication to the transmitting component 1304 for transmission to the device 1306. In some aspects, the transmitting component 1304 may perform signal processing on the generated communication (such as filtering, amplifying, modulating, digital-to-analog conversion, multiplexing, interleaving, mapping, or encoding, etc.), and may transmit the processed signal to the device 1306. In some aspects, the transmitting component 1304 may include one or more antennas, modems, modulators, transmit MIMO processors, transmit processors, controller / processors, memories, or combinations thereof of the first device described in combination with Figure 2 One or more of the first device. In some aspects, the transmitting component 1304 may be co-located with the receiving component 1302 in a transceiver.

[0147] The receiving component 1302 may receive a plurality of reference signals from a second device based at least in part on a plurality of beams. The transmitting component 1304 may transmit an AoD associated with a reference signal among the plurality of reference signals to the second device. The receiving component 1302 may receive from the second device an incremental value indicating a difference between the AoD and a beam pointing angle of a custom second device beam. The receiving component 1302 may receive data from the second device using a custom first device beam derived at least in part based on the incremental value.

[0148] The transmitting component 1304 may transmit to the second device an indication of a confidence level associated with the AoD, wherein the custom second device beam is selected at least in part based on the confidence level. The receiving component 1302 may receive from the second device an acknowledgement that the custom second device beam is sufficiently aligned with the AoD based at least in part on the incremental value meeting a threshold.

[0149] Figure 13 The number and arrangement of the components shown are provided as an example. In fact, there may be additional components, fewer components, different components, or components arranged in a different manner compared to Figure 13 those shown. Additionally, Figure 13 two or more of the components shown may be implemented within a single component, or Figure 13 a single component shown may be implemented as multiple distributed components. Additionally or alternatively, Figure 13 a set of the (one or more) components shown may perform one or more functions described as being performed by Figure 13 another set of the components shown.

[0150] Figure 14 is a diagram of an example apparatus 1400 for wireless communication in accordance with the present disclosure. The apparatus 1400 may be a second device, or the second device may include the apparatus 1400. In some aspects, the apparatus 1400 includes a receiving component 1402 and a transmitting component 1404, which may communicate with each other (e.g., via one or more buses and / or one or more other components). As shown, the apparatus 1400 may communicate with another device 1406 (such as a UE, a base station, or another wireless communication device) using the receiving component 1402 and the transmitting component 1404.

[0151] In some aspects, the apparatus 1400 may be configured to perform one or more operations described herein in connection with Figures 9 to 10 Additionally or alternatively, the apparatus 1400 may be configured to perform one or more processes described herein, such as Figure 12 process 1200. In some aspects, the apparatus 1400 and / or Figure 14 one or more of the components shown therein may include circuitry associated with Figure 2One or more components of the second device described. Additionally or alternatively, Figure 14 One or more of the components shown may be implemented in combination with Figure 2 One or more components described. Additionally or alternatively, one or more components in a set of components may be at least partially implemented as software stored in a memory. For example, a component (or a part of a component) may be implemented as instructions or code stored in a non-transitory computer-readable medium and executable by a controller or a processor to perform the functions or operations of the component.

[0152] The receiving component 1402 may receive communications from the device 1406, such as reference signals, control information, data communications, or combinations thereof. The receiving component 1402 may provide the received communications to one or more other components of the device 1400. In some aspects, the receiving component 1402 may perform signal processing on the received communications (such as filtering, amplifying, demodulating, analog-to-digital conversion, demultiplexing, deinterleaving, demapping, equalizing, interference cancellation, or decoding, etc.), and may provide the processed signals to one or more other components of the device 1400. In some aspects, the receiving component 1402 may include one or more antennas, modems, demodulators, MIMO detectors, receiving processors, controller / processors, memories, or combinations thereof of the second device described in combination with Figure 2 One or more of the second device.

[0153] The transmitting component 1404 may transmit communications to the device 1406, such as reference signals, control information, data communications, or combinations thereof. In some aspects, one or more other components of the device 1400 may generate communications and may provide the generated communications to the transmitting component 1404 for transmission to the device 1406. In some aspects, the transmitting component 1404 may perform signal processing on the generated communications (such as filtering, amplifying, modulating, digital-to-analog conversion, multiplexing, interleaving, mapping, or encoding, etc.), and may transmit the processed signals to the device 1406. In some aspects, the transmitting component 1404 may include one or more antennas, modems, modulators, transmit MIMO processors, transmit processors, controller / processors, memories, or combinations thereof of the second device described in combination with Figure 2 One or more of the second device. In some aspects, the transmitting component 1404 may be co-located with the receiving component 1402 in a transceiver.

[0154] The transmitting component 1404 may transmit a plurality of reference signals to the first device at least partially based on a plurality of beams. The receiving component 1402 may receive an AoD associated with a reference signal among the plurality of reference signals from the first device. The transmitting component 1404 may transmit an incremental value indicating a difference between the AoD and a beam pointing angle of a custom second device beam to the first device. The transmitting component 1404 may transmit data to the first device using the custom second device beam.

[0155] The receiving component 1402 may receive an indication of a confidence level associated with an AoD from a first device, and a custom second device beam may be selected at least in part based on the confidence level. The transmitting component 1404 may send an acknowledgement to the first device that the custom second device beam is sufficiently aligned with the AoD at least in part based on the incremental value meeting a threshold.

[0156] Figure 14 The number and arrangement of the illustrated components are provided as an example. In fact, there may be additional components, fewer components, different components, or components arranged in a different manner compared to Figure 14 the components shown. Additionally, Figure 14 two or more of the illustrated components may be implemented within a single component, or Figure 14 a single illustrated component may be implemented as multiple distributed components. Additionally or alternatively, Figure 14 a set of the illustrated (one or more) components may perform one or more functions described as being performed by Figure 14 another set of the illustrated components.

[0157] An overview of some aspects of the present disclosure is provided below:

[0158] Aspect 1: A method of wireless communication performed by an apparatus of a first device, the method comprising: receiving a plurality of reference signals from a second device at least in part based on a plurality of beams; sending an angle of departure (AoD) associated with a reference signal among the plurality of reference signals to the second device; receiving an incremental value indicating a difference between the AoD and a beam pointing angle of a custom second device beam from the second device; and receiving data from the second device using a custom first device beam derived at least in part based on the incremental value.

[0159] Aspect 2: The method according to aspect 1, wherein the incremental value indicates an azimuth difference between the AoD and the beam pointing angle of the custom second device beam.

[0160] Aspect 3: The method according to any one of aspects 1 to 2, wherein the incremental value indicates an elevation difference between the AoD and the beam pointing angle of the custom second device beam.

[0161] Aspect 4: The method according to any one of aspects 1 to 3, wherein the incremental value is received from the second device via downlink control information.

[0162] Aspect 5: The method according to any one of aspects 1 to 4, wherein the incremental value is received from the second device via a media access control control element (MAC-CE).

[0163] Aspect 6: The method according to any one of Aspects 1 to 5, the method further comprising: sending an indication of a confidence level associated with the AoD to the second device, wherein the custom second device beam is selected at least in part based on the confidence level.

[0164] Aspect 7: The method according to any one of Aspects 1 to 6, the method further comprising: receiving, from the second device, confirmation that the custom second device beam is sufficiently aligned with the AoD at least in part based on the increment value satisfying a threshold.

[0165] Aspect 8: The method according to any one of Aspects 1 to 7, wherein the custom second device beam and the custom first device beam are custom non-codebook-based analog beams.

[0166] Aspect 9: The method according to any one of Aspects 1 to 8, wherein: the first device is a user equipment (UE) and the second device is a network node, and the plurality of reference signals include downlink reference signals; or the first device is the network node and the second device is the UE, and the plurality of reference signals include uplink reference signals.

[0167] Aspect 10: A method of wireless communication performed by an apparatus of a second device, the method comprising: sending a plurality of reference signals to a first device at least in part based on a plurality of beams; receiving, from the first device, an angle of departure (AoD) associated with a reference signal among the plurality of reference signals; sending an increment value indicating a difference between the AoD and a beam pointing angle of a custom second device beam to the first device; and sending data to the first device using the custom second device beam.

[0168] Aspect 11: The method according to Aspect 10, wherein the increment value indicates one or more of the following: a difference in azimuth angle between the AoD and the beam pointing angle of the custom second device beam; or a difference in elevation angle between the AoD and the beam pointing angle of the custom second device beam.

[0169] Aspect 12: The method according to any one of Aspects 10 to 11, wherein the increment value is sent to the first device via downlink control information or via a medium access control control element (MAC-CE).

[0170] Aspect 13: The method according to any one of Aspects 10 to 12, the method further comprising: receiving, from the first device, an indication of a confidence level associated with the AoD, wherein the custom second device beam is selected at least in part based on the confidence level.

[0171] Aspect 14: The method according to any one of aspects 10 to 13, the method further comprising: sending, to the first device, a confirmation that the custom second device beam is sufficiently aligned with the AoD, at least in part based on the incremental value satisfying a threshold.

[0172] Aspect 15: The method according to any one of aspects 10 to 14, wherein: the first device is a user equipment (UE) and the second device is a network node, and the plurality of reference signals include downlink reference signals; or the first device is the network node and the second device is the UE, and the plurality of reference signals include uplink reference signals.

[0173] Aspect 16: An apparatus for wireless communication at a device, 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 the method according to one or more of aspects 1 to 9.

[0174] Aspect 17: A device for wireless communication, the device comprising: a memory; and one or more processors coupled to the memory, the one or more processors configured to perform the method according to one or more of aspects 1 to 9.

[0175] Aspect 18: An apparatus for wireless communication, the apparatus comprising: at least one component for performing the method according to one or more of aspects 1 to 9.

[0176] Aspect 19: A non-transitory computer-readable medium storing code for wireless communication, the code comprising instructions executable by a processor to perform the method according to one or more of aspects 1 to 9.

[0177] Aspect 20: A non-transitory computer-readable medium storing an instruction set for wireless communication, the instruction set comprising one or more instructions that, when executed by one or more processors of a device, cause the device to perform the method according to one or more of aspects 1 to 9.

[0178] Aspect 21: An apparatus for wireless communication at a device, 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 the method according to one or more of aspects 10 to 15.

[0179] Aspect 22: A device for wireless communication, the device comprising: a memory; and one or more processors coupled to the memory, the one or more processors being configured to execute the method according to one or more of Aspects 10 to 15.

[0180] Aspect 23: A device for wireless communication, the device comprising: at least one component for executing the method according to one or more of Aspects 10 to 15.

[0181] Aspect 24: A non-transitory computer-readable medium storing code for wireless communication, the code comprising instructions that can be executed by a processor to execute the method according to one or more of Aspects 10 to 15.

[0182] Aspect 25: A non-transitory computer-readable medium storing an instruction set for wireless communication, the instruction set comprising one or more instructions that, when executed by one or more processors of a device, cause the device to execute the method according to one or more of Aspects 10 to 15.

[0183] The foregoing disclosure provides illustration and description, but is not intended to be exhaustive or to limit the aspects to the precise forms disclosed. Modifications and variations may be made in accordance with the above disclosure, or may be obtained from practice of the aspects.

[0184] As used herein, the term "component" is intended to be broadly construed as a combination of hardware and / or hardware and software. Whether referred to as software, firmware, middleware, microcode, hardware description language, or other name, "software" should be broadly construed to mean instructions, instruction sets, code, code segments, program code, programs, subprograms, software modules, applications, software applications, software packages, routines, subroutines, objects, executable files, executing threads, processes, and / or functions, etc. As used herein, a "processor" is implemented in a combination of hardware and / or hardware and software. It will be apparent that the systems and / or methods described herein can be implemented in different forms of hardware and / or hardware and software combinations. The actual specific control hardware or software code used to implement these systems and / or methods does not limit the aspects. Accordingly, the operation and behavior of the systems and / or methods are not described herein with reference to specific software code, as those skilled in the art will understand that the software and hardware can be designed at least in part based on the description herein to implement the systems and / or methods.

[0185] As used herein, depending on the context, "meeting a threshold" may refer to a value greater than the threshold, greater than or equal to the threshold, less than the threshold, less than or equal to the threshold, equal to the threshold, not equal to the threshold, etc.

[0186] Although specific combinations of features are recited in the claims and / or disclosed in the specification, these combinations are not intended to limit the disclosure of the various aspects. Many of these features may be combined in ways not specifically recited in the claims and / or not disclosed in the specification. The disclosure of the various aspects includes each dependent claim in combination with every other claim in the set of claims. As used herein, the phrase referring to a list of items “at least one of” refers to any combination of those items (including a single member). By way of example, “at least one of a, b, or c” is intended to cover a, b, c, a + b, a + c, b + c, and a + b + c, as well as any combination with multiple of the same element (e.g., a + a, a + a + a, a + a + b, a + a + c, a + b + b, a + c + c, b + b, b + b + b, b + b + c, c + c, and c + c + c, or any other ordering of a, b, and c).

[0187] None of the elements, acts, or instructions used herein should be construed as critical or essential unless explicitly stated as such. Additionally, as used herein, the article “a” is intended to include one or more items and may be used interchangeably with “one or more.” Additionally, as used herein, the article “the” is intended to include the one or more items referred to in connection with the article “the” and may be used interchangeably with “one or more.” Additionally, as used herein, the terms “set” and “group” are intended to include one or more items and may be used interchangeably with “one or more.” If only one item is intended to be referred to, the phrase “only one” or similar language will be used. Additionally, as used herein, the terms “having,” “possessing,” “with,” etc. are intended to be open-ended terms that do not limit the elements they modify (e.g., an element “with” A may also have B). Additionally, the phrase “based on” is intended to mean “at least partially based on” unless otherwise explicitly stated. Additionally, as used herein, the term “or” when used in a series is intended to be open-ended and may be used interchangeably with “and / or” unless otherwise explicitly stated (e.g., if used in conjunction with “either” or “only one”).

Claims

1. A first device for wireless communication, the first device comprising: a memory; and one or more processors coupled to the memory, the memory including instructions executable by the one or more processors to cause the first device to perform the following operations: receive a plurality of reference signals from a second device based at least in part on a plurality of beams; send to the second device a departure angle of departure (AoD) associated with a reference signal among the plurality of reference signals; receive from the second device an increment value indicating a difference between the AoD and a beam pointing angle of a custom second device beam; and receive data from the second device using a custom first device beam derived at least in part based on the increment value.

2. The first device according to claim 1, wherein the increment value indicates a difference in azimuth angle between the AoD and the beam pointing angle of the custom second device beam.

3. The first device according to claim 1, wherein the increment value indicates a difference in elevation angle between the AoD and the beam pointing angle of the custom second device beam.

4. The first device according to claim 1, wherein the instructions are further executable by the one or more processors to cause the first device to: receive the increment value from the second device via downlink control information.

5. The first device according to claim 1, wherein the instructions are further executable by the one or more processors to cause the first device to: receive the increment value from the second device via a medium access control control element (MAC-CE).

6. The first device according to claim 1, wherein the instructions are further executable by the one or more processors to cause the first device to: send to the second device an indication of a confidence level associated with the AoD, wherein the custom second device beam is selected at least in part based on the confidence level.

7. The first device according to claim 1, wherein the instructions are further executable by the one or more processors to cause the first device to: receive from the second device a confirmation that the custom second device beam is sufficiently aligned with the AoD based at least in part on the increment value meeting a threshold.

8. The first device according to claim 1, wherein the custom second device beam and the custom first device beam are custom non-codebook-based analog beams.

9. According to the first device of claim 1, wherein: the first device is a user equipment (UE) and the second device is a network node, and the plurality of reference signals includes downlink reference signals; or the first device is the network node and the second device is the UE, and the plurality of reference signals includes uplink reference signals.

10. A second device for wireless communication, the second device comprising: a memory; and One or more processors, the one or more processors being coupled to the memory, the memory including instructions executable by the one or more processors to cause the second device to perform the following: Transmit a plurality of reference signals to a first device at least in part based on a plurality of beams; Receive from the first device an angle of departure (AoD) associated with a reference signal among the plurality of reference signals; Transmit to the first device an incremental value indicating a difference between the AoD and a beam pointing angle of a custom second device beam; And Transmit data to the first device using the custom second device beam.

11. The second device according to claim 10, wherein the incremental value indicates one or more of the following: A difference in azimuth angle between the AoD and the beam pointing angle of the custom second device beam; or A difference in elevation angle between the AoD and the beam pointing angle of the custom second device beam.

12. The second device according to claim 10, wherein the instructions are further executable by the one or more processors to cause the second device to: Transmit the incremental value to the first device via downlink control information or via a media access control control element (MAC-CE).

13. The second device according to claim 10, wherein the instructions are further executable by the one or more processors to cause the second device to: Receive from the first device an indication of a confidence level associated with the AoD, wherein the custom second device beam is selected at least in part based on the confidence level.

14. The second device according to claim 10, wherein the instructions are further executable by the one or more processors to cause the second device to: Transmit to the first device an acknowledgement that the custom second device beam is sufficiently aligned with the AoD at least in part based on the incremental value satisfying a threshold.

15. The second device according to claim 10, wherein: The first device is a user equipment (UE) and the second device is a network node, and the plurality of reference signals include downlink reference signals; Or The first device is the network node and the second device is the UE, and the plurality of reference signals include uplink reference signals.

16. A method of wireless communication performed by an apparatus of a first device, the method comprising: Receive a plurality of reference signals from a second device at least in part based on a plurality of beams; Transmit to the second device an angle of departure (AoD) associated with a reference signal among the plurality of reference signals; Receive from the second device an incremental value indicating a difference between the AoD and a beam pointing angle of a custom second device beam; And Receive data from the second device using a custom first device beam derived at least in part based on the incremental value.

17. The method according to claim 16, wherein the incremental value indicates a difference in azimuth angle between the AoD and the beam pointing angle of the custom second device beam.

18. The method according to claim 16, wherein the incremental value indicates a difference in elevation angle between the AoD and the beam pointing angle of the custom second device beam.

19. The method according to claim 16, wherein the incremental value is received from the second device via downlink control information.

20. The method according to claim 16, wherein the incremental value is received from the second device via a medium access control control element (MAC-CE).

21. The method according to claim 16, the method further comprising: sending an indication of a confidence level associated with the AoD to the second device, wherein the custom second device beam is selected at least in part based on the confidence level.

22. The method according to claim 16, the method further comprising: receiving from the second device an acknowledgement that the custom second device beam is sufficiently aligned with the AoD, at least in part based on the incremental value satisfying a threshold.

23. The method according to claim 16, wherein the custom second device beam and the custom first device beam are custom non-codebook-based analog beams.

24. The method according to claim 16, wherein: the first device is a user equipment (UE) and the second device is a network node, and the plurality of reference signals include downlink reference signals; or the first device is the network node and the second device is the UE, and the plurality of reference signals include uplink reference signals.

25. A method of wireless communication performed by an apparatus of a second device, the method comprising: transmitting a plurality of reference signals to a first device at least in part based on a plurality of beams; receiving from the first device an angle of departure (AoD) associated with a reference signal among the plurality of reference signals; transmitting to the first device an incremental value indicating a difference between the AoD and the beam pointing angle of a custom second device beam; and transmitting data to the first device using the custom second device beam.

26. The method according to claim 25, wherein the incremental value indicates one or more of the following: a difference in azimuth angle between the AoD and the beam pointing angle of the custom second device beam; or a difference in elevation angle between the AoD and the beam pointing angle of the custom second device beam.

27. The method according to claim 25, wherein the incremental value is transmitted to the first device via downlink control information or via a medium access control control element (MAC-CE).

28. The method according to claim 25, the method further comprising: receiving from the first device an indication of a confidence level associated with the AoD, wherein the custom second device beam is selected at least in part based on the confidence level.

29. The method according to claim 25, the method further comprising: transmitting to the first device an acknowledgement that the custom second device beam is sufficiently aligned with the AoD, at least in part based on the incremental value satisfying a threshold.

30. The method according to claim 25, wherein: the first device is a user equipment (UE) and the second device is a network node, and the plurality of reference signals include downlink reference signals; or the first device is the network node and the second device is the UE, and the plurality of reference signals include uplink reference signals.

Images