The wireless network 100 may be a heterogeneous network that includes network nodes 110 of different types, such as macro network nodes, pico network nodes, femto network nodes, relay network nodes, or the like. These different types of network nodes 110 may have different transmit power levels, different coverage areas, and/or different impacts on interference in the wireless network 100. For example, macro network nodes may have a high transmit power level (e.g., 5 to 40 watts) whereas pico network nodes, femto network nodes, and relay network nodes may have lower transmit power levels (e.g., 0.1 to 2 watts).

A network controller 130 may couple to or communicate with a set of network nodes 110 and may provide coordination and control for these network nodes 110. The network controller 130 may communicate with the network nodes 110 via a backhaul communication link or a midhaul communication link. The network nodes 110 may communicate with one another directly or indirectly via a wireless or wireline backhaul communication link. In some aspects, the network controller 130 may be a CU or a core network device, or may include a CU or a core network device.

The UEs 120 may be dispersed throughout the wireless network 100, and each UE 120 may be stationary or mobile. A UE 120 may include, for example, an access terminal, a terminal, a mobile station, and/or a subscriber unit. A UE 120 may 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, a camera, a gaming device, a netbook, a smartbook, an ultrabook, 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 vehicular component or sensor, a smart meter/sensor, industrial manufacturing equipment, a global positioning system device, a UE function of a network node, and/or any other suitable device that is configured to communicate via a wireless or wired medium.

Some UEs 120 may be considered machine-type communication (MTC) or evolved or enhanced machine-type communication (eMTC) UEs. An MTC UE and/or an eMTC UE may include, for example, a robot, a drone, a remote device, a sensor, a meter, a monitor, and/or a location tag, that may communicate with a network node, 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 NB-IoT (narrowband IoT) devices. Some UEs 120 may be considered a Customer Premises Equipment. A 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., a memory) may be operatively coupled, communicatively coupled, electronically coupled, and/or electrically coupled.

In general, any number of wireless networks 100 may be deployed in a given geographic area. Each wireless network 100 may support a particular RAT and may operate on one or more frequencies. A RAT may be referred to as a radio technology, an air interface, or the like. A frequency may be referred to as a carrier, a frequency channel, or the like. Each frequency may support a single RAT in a given geographic area in order to avoid interference between wireless networks of different RATs. In some cases, NR or 5G RAT networks may be deployed.

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., without using a network node 110 as an intermediary to communicate with one another). For example, the UEs 120 may communicate using peer-to-peer (P2P) communications, device-to-device (D2D) communications, a vehicle-to-everything (V2X) protocol (e.g., which may include a vehicle-to-vehicle (V2V) protocol, a vehicle-to-infrastructure (V2I) protocol, or a vehicle-to-pedestrian (V2P) protocol), and/or a mesh network. In such examples, a UE 120 may perform scheduling operations, resource selection operations, and/or other operations described elsewhere herein as being performed by the network node 110.

Devices of the wireless network 100 may communicate using the electromagnetic spectrum, which may be subdivided by frequency or wavelength into various classes, bands, channels, or the like. For example, devices of the wireless network 100 may communicate using one or more operating bands. In 5G NR, two initial operating bands have been identified as frequency range designations FR1 (410 MHz-7.125 GHz) and FR2 (24.25 GHz-52.6 GHz). It should be understood that although a portion of FR1 is greater than 6 GHz, FR1 is often referred to (interchangeably) as a “Sub-6 GHz” band in various documents and articles. A similar nomenclature issue sometimes occurs with regard to FR2, which is often referred to (interchangeably) as a “millimeter wave” band in documents and articles, despite being different from the extremely high frequency (EHF) band (30 GHz-300 GHz) which is identified by the International Telecommunications Union (ITU) as a “millimeter wave” band.

The frequencies between FR1 and FR2 are often referred to as mid-band frequencies. Recent 5G NR studies have identified an operating band for these mid-band frequencies as frequency range designation FR3 (7.125 GHz-24.25 GHz). Frequency bands falling within FR3 may inherit FR1 characteristics and/or FR2 characteristics, and thus may effectively extend features of FR1 and/or FR2 into mid-band frequencies. In addition, higher frequency bands are currently being explored to extend 5G NR operation beyond 52.6 GHz. For example, three higher operating bands have been identified as frequency range designations 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 frequency bands falls within the EHF band.

With the above examples in mind, unless specifically stated otherwise, it should be understood that the term “sub-6 GHz” or the like, if used herein, may broadly represent frequencies that may be less than 6 GHz, may be within FR1, or may include mid-band frequencies. Further, unless specifically stated otherwise, it should be understood that the term “millimeter wave” or the like, if used herein, may broadly represent frequencies that may include mid-band frequencies, may be within FR2, FR4, FR4-a or FR4-1, and/or FR5, or may be within the EHF band. It is contemplated that the frequencies included in these operating bands (e.g., FR1, FR2, FR3, FR4, FR4-a, FR4-1, and/or FR5) may be modified, and techniques described herein are applicable to those modified frequency ranges.

In some aspects, a UE (e.g., UE 120) may include a communication manager 140. As described in more detail elsewhere herein, the communication manager 140 may receive, during a beam management procedure, multiple sets of channel state information reference signals (CSI-RSs), wherein each set of CSI-RSs is associated with a same network node transmit beam; receive multiple CSI-RSs, wherein one CSI-RS of the multiple CSI-RSs is associated with one set of CSI-RSs of the multiple sets of CSI-RSs, and wherein a beam associated with the one CSI-RS corresponds to a beam associated with the one set of CSI-RSs; and transmit multiple channel quality indicator (CQI) reports based at least in part on the multiple CSI-RSs, wherein one CQI report of the multiple CQI reports is based at least in part on the one CSI-RS of the multiple CSI-RSs. Additionally, or alternatively, the communication manager 140 may perform one or more other operations described herein.

In some aspects, a network node (e.g., network node 110) may include a communication manager 150. As described in more detail elsewhere herein, the communication manager 150 may transmit, during a beam management procedure, multiple sets of CSI-RSs, wherein each set of CSI-RSs is associated with a same network node transmit beam; transmit multiple CSI-RSs, wherein one CSI-RS of the multiple CSI-RSs is associated with one set of CSI-RSs of the multiple sets of CSI-RSs, and wherein a beam associated with the one CSI-RS corresponds to a beam associated with the one set of CSI-RSs; and receive multiple CQI reports based at least in part on the multiple CSI-RSs, wherein one CQI report of the multiple CQI reports is based at least in part on the one CSI-RS of the multiple CSI-RSs. Additionally, or alternatively, the communication manager 150 may perform one or more other operations described herein.

As indicated above, FIG. 1 is provided as an example. Other examples may differ from what is described with regard to FIG. 1.

FIG. 2 is a diagram illustrating an example 200 of a network node 110 in communication with 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 232. In some examples, a 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.

At the network node 110, a transmit processor 220 may receive data, from a data source 212, intended for the UE 120 (or a set of UEs 120). The transmit processor 220 may select one or more modulation and coding schemes (MCSs) for the UE 120 based at least in part on one or more channel quality indicators (CQIs) received from that UE 120. The network node 110 may process (e.g., encode and modulate) the data for the UE 120 based at least in part on the MCS(s) selected for the UE 120 and may provide data symbols for the UE 120. The transmit processor 220 may process system information (e.g., for semi-static resource partitioning information (SRPI)) and control information (e.g., CQI requests, grants, and/or upper layer signaling) and provide overhead symbols and control symbols. The transmit processor 220 may generate reference symbols for reference signals (e.g., a cell-specific reference signal (CRS) or a demodulation reference signal (DMRS)) and synchronization signals (e.g., a primary synchronization signal (PSS) or a secondary synchronization signal (SSS)). A transmit (Tx) multiple-input multiple-output (MIMO) processor 230 may perform spatial processing (e.g., precoding) on the data symbols, the control symbols, the overhead symbols, and/or the 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 use a respective modulator component to process a respective output symbol stream (e.g., for OFDM) to obtain an output sample stream. Each modem 232 may further use a respective modulator component to process (e.g., convert to analog, amplify, filter, and/or upconvert) the output sample stream to obtain a downlink signal. The 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.

At the UE 120, a set of antennas 252 (shown as antennas 252a through 252r) may receive the 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 a modem 254. Each modem 254 may use a respective demodulator component to condition (e.g., filter, amplify, downconvert, and/or digitize) a received signal to obtain input samples. Each modem 254 may use a demodulator component to further process the input samples (e.g., for OFDM) to obtain received symbols. A MIMO detector 256 may obtain received symbols from the modems 254, may perform MIMO detection on the received symbols if applicable, and may provide detected symbols. A receive processor 258 may process (e.g., demodulate and decode) the detected symbols, may provide decoded data for the UE 120 to a data sink 260, and may provide decoded control information and system information to a controller/processor 280. The term “controller/processor” may refer to one or more controllers, one or more processors, or a combination thereof. A channel processor may determine a reference signal received power (RSRP) parameter, a received signal strength indicator (RSSI) parameter, a reference signal received quality (RSRQ) parameter, and/or a CQI parameter, among other examples. In some examples, one or more components of the UE 120 may be included in a housing 284.

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.

One or more antennas (e.g., antennas 234a through 234t and/or antennas 252a through 252r) may include, 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, among other examples. An antenna panel, an antenna group, a set of antenna elements, and/or an 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 transmission and/or reception components, such as one or more components of FIG. 2.

On the uplink, at the UE 120, a transmit processor 264 may receive and process data from a data source 262 and control information (e.g., for reports that include RSRP, RSSI, RSRQ, and/or CQI) from the controller/processor 280. 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 a Tx MIMO processor 266 if applicable, further processed by the modems 254 (e.g., for DFT-s-OFDM or CP-OFDM), and transmitted 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(s) 252, the modem(s) 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 FIGS. 5-11).

At the network node 110, the uplink signals from UE 120 and/or other UEs may be received by the antennas 234, processed by the modem 232 (e.g., a demodulator component, shown as DEMOD, of the modem 232), detected by a MIMO detector 236 if applicable, and further processed by a receive processor 238 to obtain decoded data and control information sent by the UE 120. The receive processor 238 may provide the decoded data to a data sink 239 and provide 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 and/or uplink communications. 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(s) 234, the modem(s) 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 FIGS. 5-11).

The controller/processor 240 of the network node 110, the controller/processor 280 of the UE 120, and/or any other component(s) of FIG. 2 may perform one or more techniques associated with beam management using multiple sets of CSI-RSs and CQI reporting, as described in more detail elsewhere herein. For example, the controller/processor 240 of the network node 110, the controller/processor 280 of the UE 120, and/or any other component(s) of FIG. 2 may perform or direct operations of, for example, process 800 of FIG. 8, process 900 of FIG. 9, and/or other processes as described herein. The memory 242 and the memory 282 may store data and program codes for the network node 110 and the UE 120, respectively. In some examples, the memory 242 and/or the memory 282 may include a non-transitory computer-readable medium storing one or more instructions (e.g., code and/or program code) for wireless communication. For example, the one or more instructions, when executed (e.g., directly, or after compiling, converting, and/or interpreting) by one or more processors of the network node 110 and/or the UE 120, may cause the one or more processors, the UE 120, and/or the network node 110 to perform or direct operations of, for example, process 800 of FIG. 8, process 900 of FIG. 9, and/or other processes as described herein. In some examples, executing instructions may include running the instructions, converting the instructions, compiling the instructions, and/or interpreting the instructions, among other examples.

In some aspects, a UE (e.g., UE 120) includes means for receiving, during a beam management procedure, multiple sets of CSI-RSs, wherein each set of CSI-RSs is associated with a same network node transmit beam; means for receiving multiple CSI-RSs, wherein one CSI-RS of the multiple CSI-RSs is associated with one set of CSI-RSs of the multiple sets of CSI-RSs, and wherein a beam associated with the one CSI-RS corresponds to a beam associated with the one set of CSI-RSs; and/or means for transmitting multiple CQI reports based at least in part on the multiple CSI-RSs, wherein one CQI report of the multiple CQI reports is based at least in part on the one CSI-RS of the multiple CSI-RSs. The means for the UE to perform operations described herein may include, for example, one or more of 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.

In some aspects, a network node (e.g., network node 110) includes means for transmitting, during a beam management procedure, multiple sets of CSI-RSs, wherein each set of CSI-RSs is associated with a same network node transmit beam; means for transmitting multiple CSI-RSs, wherein one CSI-RS of the multiple CSI-RSs is associated with one set of CSI-RSs of the multiple sets of CSI-RSs, and wherein a beam associated with the one CSI-RS corresponds to a beam associated with the one set of CSI-RSs; and/or means for receiving multiple CQI reports based at least in part on the multiple CSI-RSs, wherein one CQI report of the multiple CQI reports is based at least in part on the one CSI-RS of the multiple CSI-RSs. The means for the network node to perform operations described herein may include, for example, one or more of 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.

While blocks in FIG. 2 are illustrated as distinct components, the functions described above with respect to the blocks may be implemented in a single hardware, software, or combination component or in various combinations of components. For example, the functions described with respect to the transmit processor 264, the receive processor 258, and/or the Tx MIMO processor 266 may be performed by or under the control of the controller/processor 280.

As indicated above, FIG. 2 is provided as an example. Other examples may differ from what is described with regard to FIG. 2.

Deployment of communication systems, such as 5G NR systems, may be arranged in multiple manners with various components or constituent parts. In a 5G NR system, or network, a network node, a network entity, a mobility element of a network, a RAN node, a core network node, a network element, a base station, or a network equipment may be implemented in an aggregated or disaggregated architecture. For example, a base station (such as a Node B (NB), an evolved NB (eNB), an NR base station, a 5G NB, an access point (AP), a TRP, or a cell, among other examples), or one or more units (or one or more components) performing base station functionality, may be implemented as an aggregated base station (also known as a standalone base station or a monolithic base station) or a disaggregated base station. “Network entity” or “network node” may refer to a disaggregated base station, or to one or more units of a disaggregated base station (such as one or more CUs, one or more DUs, one or more RUs, or a combination thereof).

An aggregated base station (e.g., an aggregated network node) may 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 disaggregated base station (e.g., a disaggregated network node) may 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 may be implemented within a network node, and one or more DUs may be co-located with the CU, or alternatively, may be geographically or virtually distributed throughout one or multiple other network nodes. The DUs may be implemented to communicate with one or more RUs. Each of the CU, DU, and RU also can be implemented as virtual units, such as a virtual central unit (VCU), a virtual distributed unit (VDU), or a virtual radio unit (VRU), among other examples.

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

FIG. 3 is a diagram illustrating an example disaggregated base station architecture 300, in accordance with the present disclosure. The disaggregated base station architecture 300 may include a CU 310 that 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). A CU 310 may communicate with one or more DUs 330 via respective midhaul links, such as through F1 interfaces. Each of the DUs 330 may communicate with one or more RUs 340 via respective fronthaul links. Each of the RUs 340 may communicate with one or more UEs 120 via respective radio frequency (RF) access links. In some implementations, a UE 120 may be simultaneously served by multiple RUs 340.

Each of the units, including the CUs 310, the DUs 330, the RUs 340, as well as the Near-RT RICs 325, the Non-RT RICs 315, and the SMO Framework 305, may include one or more interfaces or be coupled with one or more interfaces configured to receive or transmit signals, data, or information (collectively, signals) via a wired or wireless transmission medium. Each of the units, or an associated processor or controller providing instructions to one or multiple communication interfaces of the respective unit, can be configured to communicate with one or more of the other units via the transmission medium. In some examples, each of the units can include a wired interface, configured to receive or transmit signals over a wired transmission medium to one or more of the other units, and a wireless interface, which may include a receiver, a transmitter or transceiver (such as an RF transceiver), configured to receive or transmit signals, or both, over a wireless transmission medium to one or more of the other units.

In some aspects, the CU 310 may host one or more higher layer control functions. Such control functions can include radio resource control (RRC) functions, packet data convergence protocol (PDCP) functions, or service data adaptation protocol (SDAP) functions, among other examples. Each control function can be implemented with an interface configured to communicate signals with other control functions hosted by the CU 310. The CU 310 may be configured to handle user plane functionality (for example, Central Unit-User Plane (CU-UP) functionality), control plane functionality (for example, Central Unit-Control Plane (CU-CP) functionality), or a combination thereof. In some implementations, the CU 310 can be logically split into one or more CU-UP units and one or more CU-CP units. A CU-UP unit can communicate bidirectionally with a CU-CP unit via an interface, such as the E1 interface when implemented in an O-RAN configuration. The CU 310 can be implemented to communicate with a DU 330, as necessary, for network control and signaling.

Each DU 330 may correspond to a logical unit that includes one or more base station functions to control the operation of one or more RUs 340. In some aspects, the DU 330 may host one or more of a radio link control (RLC) layer, a medium access control (MAC) layer, and one or more high physical (PHY) layers depending, at least in part, on a functional split, such as a functional split defined by the 3GPP. In some aspects, the one or more high 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 examples. In some aspects, the DU 330 may further host one or more low PHY layers, such as implemented by one or more modules for a fast Fourier transform (FFT), an inverse FFT (iFFT), digital beamforming, or physical random access channel (PRACH) extraction and filtering, among other examples. Each layer (which also may be referred to as a module) can be implemented with an interface configured to communicate signals with other layers (and modules) hosted by the DU 330, or with the control functions hosted by the CU 310.

Each RU 340 may implement lower-layer functionality. In some deployments, an RU 340, controlled by a DU 330, may correspond to a logical node that hosts RF processing functions or low-PHY layer functions, such as performing an FFT, performing an iFFT, digital beamforming, or PRACH extraction and filtering, among other examples, based on a functional split (for example, a functional split defined by the 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 implementations, real-time and non-real-time aspects of control and user plane communication with the RU(s) 340 can be controlled by the corresponding DU 330. In some scenarios, this configuration can enable each DU 330 and the CU 310 to be implemented in a cloud-based RAN architecture, such as a vRAN architecture.

The SMO Framework 305 may be configured to support RAN deployment and provisioning of non-virtualized and virtualized network elements. For non-virtualized network elements, the SMO Framework 305 may be configured to support the deployment of dedicated physical resources for RAN coverage requirements, which may be managed via an operations and maintenance interface (such as an O1 interface). For virtualized network elements, the SMO Framework 305 may be configured to interact with a cloud computing platform (such as an open cloud (O-Cloud) platform 390) to perform network element life cycle management (such as to instantiate virtualized network elements) via a cloud computing platform interface (such as an O2 interface). Such virtualized network elements can include, but are not limited to, CUs 310, DUs 330, RUs 340, non-RT RICs 315, and Near-RT RICs 325. In some implementations, the SMO Framework 305 can communicate with a hardware aspect of a 4G RAN, such as an open eNB (O-eNB) 311, via an O1 interface. Additionally, in some implementations, the SMO Framework 305 can communicate directly with each of one or more RUs 340 via a respective O1 interface. The SMO Framework 305 also may include a Non-RT RIC 315 configured to support functionality of the SMO Framework 305.

The Non-RT RIC 315 may be configured to include a logical function that enables non-real-time control and optimization of RAN elements and resources, Artificial Intelligence/Machine Learning (AI/ML) workflows including model training and updates, or policy-based guidance of applications/features in the Near-RT RIC 325. The Non-RT RIC 315 may be coupled to or communicate with (such as via an A1 interface) the Near-RT RIC 325. The Near-RT RIC 325 may be configured to include a logical function that enables near-real-time control and optimization of RAN elements and resources via data collection and actions over an interface (such as via an E2 interface) connecting one or more CUs 310, one or more DUs 330, or both, as well as an O-eNB, with the Near-RT RIC 325.

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

As indicated above, FIG. 3 is provided as an example. Other examples may differ from what is described with regard to FIG. 3.

FIG. 4 is a diagram illustrating examples 400, 410, and 420 of channel state information reference signal (CSI-RS) beam management procedures, in accordance with the present disclosure. As shown in FIG. 4, examples 400, 410, and 420 include a UE 120 in communication with a network node 110 in a wireless network (e.g., wireless network 100). However, the devices shown in FIG. 4 are provided as examples, and the wireless network may support communication and beam management between other devices (e.g., between a UE 120 and a network node 110 or TRP, between a mobile termination node and a control node, between an IAB child node and an IAB parent node, and/or between a scheduled node and a scheduling node). In some aspects, the UE 120 and the network node 110 may be in a connected state (e.g., an RRC connected state).

As shown in FIG. 4, example 400 may include a network node 110 (e.g., one or more network node devices such as an RU, a DU, and/or a CU, among other examples) and a UE 120 communicating to perform beam management using CSI-RSs. Example 400 depicts a first beam management procedure (e.g., P1 CSI-RS beam management). The first beam management procedure may be referred to as a beam selection procedure, an initial beam acquisition procedure, a beam sweeping procedure, a cell search procedure, and/or a beam search procedure. As shown in FIG. 4 and example 400, CSI-RSs may be configured to be transmitted from the network node 110 to the UE 120. The CSI-RSs may be configured to be periodic (e.g., using RRC signaling).

The first beam management procedure may include the network node 110 performing beam sweeping over multiple Tx beams. The network node 110 may transmit a CSI-RS using each transmit beam for beam management. To enable the UE 120 to perform receive (Rx) beam sweeping, the network node may use a transmit beam to transmit (e.g., with repetitions) each CSI-RS at multiple times within the same RS resource set so that the UE 120 can sweep through receive beams in multiple transmission instances. For example, if the network node 110 has a set of N transmit beams and the UE 120 has a set of M receive beams, the CSI-RS may be transmitted on each of the N transmit beams M times so that the UE 120 may receive M instances of the CSI-RS per transmit beam. In other words, for each transmit beam of the network node 110, the UE 120 may perform beam sweeping through the receive beams of the UE 120. As a result, the first beam management procedure may enable the UE 120 to measure a CSI-RS on different transmit beams using different receive beams to support selection of network node 110 transmit beams/UE 120 receive beam(s) beam pair(s). The UE 120 may report the measurements to the network node 110 to enable the network node 110 to select one or more beam pair(s) for communication between the network node 110 and the UE 120. While example 400 has been described in connection with CSI-RSs, the first beam management process may also use synchronization signal blocks (SSBs) for beam management in a similar manner as described above.

As shown in FIG. 4, example 410 may include a network node 110 and a UE 120 communicating to perform beam management using CSI-RSs. Example 410 depicts a second beam management procedure (e.g., P2 CSI-RS beam management). The second beam management procedure may be referred to as a beam refinement procedure, a network node beam refinement procedure, a TRP beam refinement procedure, and/or a transmit beam refinement procedure. As shown in FIG. 4 and example 410, CSI-RSs may be configured to be transmitted from the network node 110 to the UE 120. The CSI-RSs may be configured to be aperiodic (e.g., using DCI). The second beam management procedure may include the network node 110 performing beam sweeping over one or more transmit beams. The one or more transmit beams may be a subset of all transmit beams associated with the network node 110 (e.g., determined based at least in part on measurements reported by the UE 120 in connection with the first beam management procedure). The network node 110 may transmit a CSI-RS using each transmit beam of the one or more transmit beams for beam management. The UE 120 may measure each CSI-RS using a single (e.g., a same) receive beam (e.g., determined based at least in part on measurements performed in connection with the first beam management procedure). The second beam management procedure may enable the network node 110 to select a best transmit beam based at least in part on measurements of the CSI-RSs (e.g., measured by the UE 120 using the single receive beam) reported by the UE 120.

As shown in FIG. 4, example 420 depicts a third beam management procedure (e.g., P3 CSI-RS beam management). The third beam management procedure may be referred to as a beam refinement procedure, a UE beam refinement procedure, and/or a receive beam refinement procedure. As shown in FIG. 4 and example 420, one or more CSI-RSs may be configured to be transmitted from the network node 110 to the UE 120. The CSI-RSs may be configured to be aperiodic (e.g., using DCI). The third beam management process may include the network node 110 transmitting the one or more CSI-RSs using a single transmit beam (e.g., determined based at least in part on measurements reported by the UE 120 in connection with the first beam management procedure and/or the second beam management procedure). To enable the UE 120 to perform receive beam sweeping, the network node may use a transmit beam to transmit (e.g., with repetitions) CSI-RS at multiple times within the same RS resource set so that UE 120 can sweep through one or more receive beams in multiple transmission instances. The one or more receive beams may be a subset of all receive beams associated with the UE 120 (e.g., determined based at least in part on measurements performed in connection with the first beam management procedure and/or the second beam management procedure). The third beam management procedure may enable the network node 110 and/or the UE 120 to select a best receive beam based at least in part on reported measurements received from the UE 120 (e.g., of the CSI-RS of the transmit beam using the one or more receive beams).

As indicated above, FIG. 4 is provided as an example of beam management procedures. Other examples of beam management procedures may differ from what is described with respect to FIG. 4. For example, the UE 120 and the network node 110 may perform the third beam management procedure before performing the second beam management procedure, and/or the UE 120 and the network node 110 may perform a similar beam management procedure to select a UE transmit beam.

A mmWave propagation may be different from a sub-6 GHz propagation. The mmWave propagation may be associated with a higher pathloss as compared to the sub-6 GHz propagation. The mmWave propagation may be associated with new types of mobility introduced by UE translational/rotational motions, as compared to the sub-6 GHz propagation. The mmWave propagation may be associated with cluster jumps and blockers, as compared to the sub-6 GHz propagation. Due to such differences, beam management may be needed for mmWave systems. The beam management may involve beamforming to overcome relatively large pathloss. The beam management may involve establishing and maintaining a beam pair link (BPL) between a UE and a network node. The beam management may involve mobility management.

Beam management may involve a P1 procedure, a P2 procedure, and a P3 procedure. The P1 procedure may involve establishing an initial BPL between the UE and the network node. The P2 procedure may involve a network node beam refinement. The P3 procedure may involve a UE beam refinement. The network node may be associated with refined beams in accordance with: gNB[i], i=1, 2, . . . , K. The UE may be associated with beams in accordance with: UEb[j], j=1, 2, . . . , L.

In a typical beam management, during the P1 procedure, the network node may determine a suitable beam pair, which may include a network node Tx beam (e.g., a gNB Tx beam) and a UE Rx beam. The P1 procedure may be an SSB-based procedure or a CSI-RS-based procedure. During the P1 procedure, the UE may report, to the network node, a best network node beam.

During the P2 procedure, the network node may transmit a set of CSI-RSs, using one or two ports, and using different network node Tx beams. The UE Rx beam may be fixed when different CSI-RSs have the same quasi-co-location (QCL) source, or the UE Rx beam may vary when different CSI-RSs have different QCL sources. The P2 procedure may be associated with a network node beam refinement. During the P2 procedure, the network node may select a best network node beam based at least in part on a measurement reporting from the UE. The best network node beam and UE beam pair may be denoted by (gNB[i], UEb[j]). The network node may select the best network node beam, which may be based at least in part on the best UE beam acquired from the P1 procedure.

During the P3 procedure, the network node may transmit a set of CSI-RSs, using one or two ports, and using the same network node Tx beam. The network node Tx beam may be fixed. The P3 procedure may be associated with a UE beam refinement. During the P3 procedure, the network node may transmit a sequence of CSI-RSs using the same network node Tx beam, where the same network node Tx beam may be based at least in part on a selected refined beam (e.g., the best network node beam from the P2 procedure). The UE may train its Rx beam using the P3 procedure. A best UE beam for gNB[i] may be denoted by UEb[j 1].

In some cases, a selected beam pair (gNB[i], UEb[j 1]) may not globally be the best among a plurality of network node and UE beam pairs, which may be denoted by (gNB[i], UEb[j]), i=1, . . . , K, j=1, . . . , L. Some beam pairs may be better than the selected beam pair, but the network node and/or the UE may not have a mechanism for identifying such beam pairs. Further, the network node beam refinement may primarily be determined at the network node, and the UE beam refinement may primarily be determined at the UE, which may cause the selected beam pair to not necessarily be the best among the plurality of network node and UE beam pairs.

The 3GPP Technical Specification (TS) does not rigidly define P1, P2, and P3 beam management procedures for the UE and the network node. The 3GPP TS does not constrain the ordering or number of P2 and P3 sessions for a given SSB measurement timing configuration (SMTC), and does not preclude the existence of a joint P2/P3 session. In a typical P1, P2, and P3 procedure, in the P1 procedure, the network node may broadcast reference signals using a coarse beam codebook, and then the UE may perform an autonomous beam scan and refinement to establish the initial BPL. In the P2 procedure, the network node may offer a subset of a refined beam codebook. The UE may measure these network node beams with its UE beam selected from the P1 procedure. The network node may then select its best P2 beam based at least in part on a UE report. In the P3 procedure, the network node may transmit the selected P2 refined beam multiple times, such that the UE may further refine its beam. P3 sessions typically follow P3 sessions in a sequential fashion. The BPL obtained from the typical P1, P2, and P3 procedure may not be the optimal BPL. The sequential nature of the P2/P3 procedures may result in a local optimization, and in the P3 procedure, the UE does not have the opportunity to refine its beam against a plurality of beams (e.g., all beams) in a network node refined beam codebook.

In various aspects of techniques and apparatuses described herein, a UE may receive, from a network node and during a beam management procedure, multiple sets of CSI-RSs. Each set of CSI-RSs may be associated with a same network node transmit beam. The UE may receive the multiple sets of CSI-RSs during multiple P3 procedures of the beam management procedure. The UE may receive, from the network node, multiple CSI-RSs. One CSI-RS of the multiple CSI-RSs may be associated with one set of CSI-RSs of the multiple sets of CSI-RSs. A beam associated with the one CSI-RS may correspond to a beam associated with the one set of CSI-RSs. The UE may transmit, to the network node, multiple CQI reports based at least in part on the multiple CSI-RSs. One CQI report of the multiple CQI reports may be based at least in part on the one CSI-RS of the multiple CSI-RSs. The network node may select a best network node beam based at least in part on the multiple CQI reports. In some aspects, the multiple sets of CSI-RSs corresponding to the multiple P3 procedures, the multiple CSI-RSs, and the multiple CQI reports may allow for a joint beam management between the UE and the network node, which may increase a likelihood that a best beam pair is selected among a plurality of network node and UE beam pairs. Further, the network node may use CQI to select the network node beam, which may better match a downlink performance.

In some aspects, a joint P2-P3 network node and UE beam refinement may be achieved through multiple P3 sessions, where each P3 session may be followed with a CQI report through a CSI-RS (e.g., channel state information (CSI)) that has the same network node beam that is utilized in the P3 session. The CQI may be filtered by either the UE or the network node. The network node may use the CQI to determine the best network node beam, and the network node may indicate the best network node beam to the UE via a beam indication signaling. The UE may select the best UE beam based at least in part on the indicated best network node beam. In some aspects, the UE beam refinement in the P3 procedure may be based at least in part on the top beams in the P2 report, or may be determined adaptively around a current network node serving beam without the P2 report. The P2 and P3 reference signals may be associated with one port (1-port) or two ports (2-port). The UE may determine the best UE beam for the P3 procedure based at least in part on an RSRP, a signal-to-interference-plus-noise ratio (SINR), and/or a spectral efficiency. A P2 session frequency may not be constrained by a P3 session frequency. For example, fewer P2 sessions than P3 sessions may be used, or vice versa. In some cases, the P2 sessions may be skipped entirely. Further, the order of the P2 procedure, the P3 procedure, and the CSI-RSs (e.g., CSI) may be arbitrary. For example, multiple CSI-RSs (e.g., CSIs) may be employed per P3 session. As another example, multiple P3 sessions may be employed per P2 session. As a result, an approximately global joint optimization of network node and UE BPLs may be allowed. Further, the use of CQI to select the network node beam may be allowed, which may improve a downlink performance.

FIG. 5 is a diagram illustrating an example 500 associated with beam management using multiple sets of CSI-RSs and CQI reporting, in accordance with the present disclosure. As shown in FIG. 5, example 500 includes communication between a UE (e.g., UE 120) and a network node (e.g., network node 110). In some aspects, the UE and the network node may be included in a wireless network, such as wireless network 100.

As shown by reference number 502, the UE may receive, from the network node and during a beam management procedure, multiple sets of CSI-RSs. Each set of CSI-RSs may be associated with a same network node transmit beam (e.g., a same gNB transmit beam). The multiple sets of CSI-RSs may be associated with multiple P3 procedures of the beam management procedure. For example, during each P3 procedure, the UE may receive a set of CSI-RSs from the network node. In other words, during the same beam management procedure, the UE may receive the multiple sets of CSI-RSs, where each set of CSI-RSs may be associated with one P3 procedure of the multiple P3 procedures.

As shown by reference number 504, the UE may receive, from the network node, multiple CSI-RSs. One CSI-RS of the multiple CSI-RSs may be associated with one set of CSI-RSs of the multiple sets of CSI-RSs. A beam associated with the one CSI-RS may correspond to a beam associated with the one set of CSI-RSs. In other words, the network node may transmit the CSI-RS to the UE, and the same beam used to transmit the set of CSI-RSs may be used to transmit the CSI-RS. The UE may receive the multiple CSI-RSs using multiple beams, which may be based at least in part on the UE beam selection during the multiple P3 procedures.

As an example, the network node may transmit, during a first P3 procedure, a first set of CSI-RSs. The network node may transmit, a first CSI-RS using the same beam as that of the first set of CSI-RS. The network node may transmit, during a second P3 procedure, a second set of CSI-RSs. The network node may transmit, a second CSI-RS using the same beam as that of the second set of CSI-RS. The network node may transmit, during a third P3 procedure, a third set of CSI-RSs. The network node may transmit, a third CSI-RS using the same beam as that of the third set of CSI-RS.

As shown by reference number 506, the UE may transmit, to the network node, multiple CQI reports based at least in part on the multiple CSI-RSs. One CQI report of the multiple CQI reports may be based at least in part on the one CSI-RS of the multiple CSI-RSs. In other words, a particular CQI report may correspond to a particular CSI-RS received from the network node.

In some aspects, each CQI report may be for a single CSI-RS, were the single CSI-RS may be based at least in part on a set of CSI-RSs (e.g., P3 procedure). In other words, each P3 procedure may be associated with a set of CSI-RSs. Each CSI-RS that follows the P3 procedure may be a single CSI-RS. Each CQI report may be for the single CSI-RS.

As shown by reference number 508, the network node may select a best network node beam based at least in part on the multiple CQI reports. In other words, the best network node beam may be based at least in part on the multiple CQI reports. The network node may select the best network node beam after receiving the multiple CQI reports from the multiple CSI-RSs, where the multiple CSI-RSs may be associated with different refined beams.

In some aspects, an ordering associated with the multiple sets of CSI-RSs, the multiple CSI-RSs, and the multiple CQI reports may be based at least in part on a predefined ordering scheme. For example, the predefined ordering scheme may involve an ordering of a single set of CSI-RSs, followed by a single CSI-RS, and followed by a single CQI report. Alternatively, the predefined ordering scheme may involve an ordering of consecutive sets of CSI-RSs, followed by a single CSI-RS, and followed by a single CQI report.

In some aspects, prior to the multiple sets of CSI-RSs being received, the UE may receive an SSB from the network node. The UE may receive the SSB during a P1 procedure of the beam management procedure. In some aspects, prior to the multiple sets of CSI-RSs being received, the UE may receive, from the network node, a plurality of CSI-RSs associated with a P2 procedure of the beam management procedure. The plurality of CSI-RSs may be associated with different beams. The UE may transmit, to the network node, a measurement report (e.g., a P2 measurement report) indicating top beams. The measurement report may be a layer 1 (L1) measurement report. After the UE transmits the measurement report, the UE may receive the multiple sets of CSI-RSs and the multiple CSI-RSs from the network node.

In some aspects, a quantity associated with the top beams may correspond to a quantity associated with the multiple sets of CSI-RSs. For example, when the UE reports three top beams to the network node, the UE may receive three sets of CSI-RSs from the network node. Further, the UE may receive three CSI-RSs from the network node, which may be based at least in part on the three sets of CSI-RSs, respectively. Further, the UE may transmit three CQI reports to the network node, which may be based at least in part on the three CSI-RSs, respectively.

In some aspects, the UE may receive, from the network node and after the multiple CQI reports are transmitted, a beam switch indication. For example, the UE may receive, from the network node, a MAC-CE that indicates the beam switch indication. The beam switch indication may cause the UE to switch to another beam, which may be based at least in part on the multiple CQI reports. In some aspects, the multiple sets of CSI-RSs, the multiple CSI-RSs, and the multiple CQI reports may enable a joint network node and UE beam refinement (e.g., an approximately global joint optimization of a network node and UE beam refinement). Further, the multiple CQI reports may be used for selection of a network node beam, which may enable the network node to better match a downlink performance.

In some aspects, during the P2 procedure, the UE may report up to X top beams to the network node (e.g., top X network node beams). For example, the UE may report the top four measurements (e.g., RSRP measurements and/or SINR measurements) associated with a resource set during the P2 procedure. Each of the top four measurements may be associated with a certain beam. After receiving an indication of the X top beams, the network node may perform a P3 procedure for each of the X top beams or for a portion of the X top beams. For example, when the UE reports four top beams during the P2 procedure, the network node may perform up to four P3 procedures, where one P3 procedure may be for each reported beam. The UE may use an RSRP measurement or a spectral efficiency to select a best UE beam from the P3 procedure. In some aspects, each P3 procedure may be followed with a CSI-RS using the same best UE beam, which may allow the UE to transmit a CQI report based at least in part on the CSI-RS that uses the best UE beam. The UE may report the quality of the best UE beam by effectively using CQI as the metric, where the CQI may be derived based at least in part on the spectral efficiency. After receiving the CQI from multiple CSI-RSs of different refined beams, the network node may select the best network node refined beam using CQI as the metric. In some cases, the order of different P3 procedures and CSI-RSs may be arbitrary.

In some aspects, in a joint P2/P3 beam management, each P2 report provided by the UE may contain the top X network node beams. After receiving the top X network node beams, the network node may grant a P3 session for each P2 beam or a subset of P2 beams. For example, the network node may allocate up to four P3 sessions, where each P3 session may be for each reported P2 beam. The network node may choose to down select the P2 beams from a codebook adaptively based at least in part on other peripheral information, such as codebook structure. For example, the network node may employ a set tracking algorithm, in which the network node may choose the candidate P2 beams around the current P2 serving beam. For each P3 session, the UE may scan a subset of its codebook to further refine its own beam. The UE may use either spectral efficiency or RSRP as a beam selection metric. Each P3 session may be followed by a CSI-RS (e.g., CSI) using the same network node beam utilized in the previous P3 session to allow the UE to perform a CSI report, which may effectively allow the UE to report the quality of the selected network node and UE BPL using CQI as a metric, and where the CQI may be derived based at least in part on the spectral efficiency. After receiving multiple CQI reports from the UE, the network node may select the best P2 beam using the CQI as the metric. With the help of the P2 beam indication, the order of P3/CSI-RS sessions may be arbitrary.

As indicated above, FIG. 5 is provided as an example. Other examples may differ from what is described with regard to FIG. 5.

FIG. 6 is a diagram illustrating an example 600 associated with beam management using multiple sets of CSI-RSs and CQI reporting, in accordance with the present disclosure.

As shown by reference number 602, a network node may transmit, to a UE, an SSB during a P1 procedure of a beam management procedure. As shown by reference number 604, the network node may transmit, to the UE, a plurality of CSI-RSs during a P2 procedure of the beam management procedure. The plurality of CSI-RSs may be associated with different beams. As shown by reference number 606, the UE may transmit, to the network node, a measurement report (e.g., a P2 report), which may be based at least in part on measurements associated with the plurality of CSI-RSs.

As shown by reference number 608, the network node may transmit, to the UE, a first set of CSI-RSs using the same beam during a first P3 procedure of the beam management procedure. As shown by reference number 610, the network node may transmit, to the UE, a first CSI-RS using the same beam as used to transmit the first set of CSI-RSs. As shown by reference number 612, the network node may receive, from the UE, a first CQI report, which may be based at least in part on the first CSI-RS.

As shown by reference number 614, the network node may transmit, to the UE, a second set of CSI-RSs using the same beam during a second P3 procedure of the beam management procedure. As shown by reference number 616, the network node may transmit, to the UE, a second CSI-RS using the same beam as used to transmit the second set of CSI-RSs. As shown by reference number 618, the network node may receive, from the UE, a second CQI report, which may be based at least in part on the second CSI-RS.

As shown by reference number 620, the network node may transmit, to the UE, a third set of CSI-RSs using the same beam during a third P3 procedure of the beam management procedure. As shown by reference number 622, the network node may transmit, to the UE, a third CSI-RS using the same beam as used to transmit the third set of CSI-RSs. As shown by reference number 624, the network node may receive, from the UE, a third CQI report, which may be based at least in part on the third CSI-RS.

In some aspects, beams may be different between the first P3 procedure, the second P3 procedure, and the third P3 procedure. Beams may be different between the first CSI-RS, the second CSI-RS, and the third CSI-RS. The first P3 procedure and the first CSI-RS may be associated with the same beams (e.g., first beams). The second P3 procedure and the second CSI-RS may be associated with the same beams (e.g., second beams). The third P3 procedure and the third CSI-RS may be associated with the same beams (e.g., third beams).

As shown by reference number 626, the network node may transmit, to the UE, a MAC-CE beam switch indication, which may be based at least in part on the first CQI report, the second CQI report, and the third CQI report. In other words, the network node may indicate a beam switching based at least in part on multiple CQI reports received from the UE. The network node may perform a downlink transmission, via a PDxCH, based at least in part on the beam switching. “PDxCH” may refer to a physical downlink shared channel (PDSCH) or a physical downlink control channel (PDCCH). The downlink transmission may occur after the beam switching (e.g., 3 ms after the beam switching).

In some aspects, in a joint P2-P3-CSI-RS for beam decision, the UE may transmit a P2 measurement/report to the network node, which may indicate up to four refined beams. The P2 procedure may be skipped when a number of refined beams under each SSB is less than four, or when the network node is otherwise able to limit the number of refined beams to be tracked. For example, the network node may choose to pick only the P2 beams that are neighbors of the current serving P2 beam. The P2 procedure may be allocated less frequently as compared to the P3 procedure, for example, when the UE is associated with low mobility. Multiple CSI-RS for beam management (e.g., during the P3 procedure) and CSI-RS for CSI pairs on the reported refined beams may be transmitted for a global optimization of beam selection. The CSI-RS for CSI may be associated with CQI reporting. Resources for multiple sets of CSI-RSs (associated with the P3 procedures) may be distributed across frames to save resources. In other words, P3/CSI-RS resources may be either back-to-back for quick turnaround or distributed across frames to save resources. The network node may use CQI reports to determine which beam is best (e.g., which network node beam is best), and the network node may perform a downlink transmission using the selected beam.

As indicated above, FIG. 6 is provided as an example. Other examples may differ from what is described with regard to FIG. 6.

FIG. 7 is a diagram illustrating an example 700 associated with beam management using multiple sets of CSI-RSs and CQI reporting, in accordance with the present disclosure.

As shown by reference number 702, a network node may transmit, to a UE, an SSB during a P1 procedure of a beam management procedure. As shown by reference number 704, the network node may transmit, to the UE, a plurality of CSI-RSs during a P2 procedure of the beam management procedure. The plurality of CSI-RSs may be associated with different beams. As shown by reference number 706, the UE may transmit, to the network node, a measurement report (e.g., a P2 report), which may be based at least in part on measurements associated with the plurality of CSI-RSs.

As shown by reference number 708, the network node may transmit, to the UE, a first set of CSI-RSs using the same beam during a first P3 procedure of the beam management procedure. As shown by reference number 710, the network node may transmit, to the UE, a second set of CSI-RSs using the same beam during a second P3 procedure of the beam management procedure. As shown by reference number 712, the network node may transmit, to the UE, a third set of CSI-RSs using the same beam during a third P3 procedure of the beam management procedure. The network node may transmit the first set of CSI-RSs, the second set of CSI-RSs, and the third set of CSI-RSs in a back-to-back or consecutive manner.

As shown by reference number 714, the network node may transmit, to the UE, a first CSI-RS using the same beam as used to transmit the first set of CSI-RSs. As shown by reference number 716, the network node may receive, from the UE, a first CQI report, which may be based at least in part on the first CSI-RS. As shown by reference number 718, the network node may transmit, to the UE, a second CSI-RS using the same beam as used to transmit the second set of CSI-RSs. As shown by reference number 720, the network node may receive, from the UE, a second CQI report, which may be based at least in part on the second CSI-RS. As shown by reference number 722, the network node may transmit, to the UE, a third CSI-RS using the same beam as used to transmit the third set of CSI-RSs. As shown by reference number 724, the network node may receive, from the UE, a third CQI report, which may be based at least in part on the third CSI-RS.

In some aspects, the network node may repeat CSI-RS transmissions to the UE, and the network node may receive additional CQI reports based at least in part on the repeated CSI-RS transmissions. As shown by reference number 726, the network node may transmit, to the UE, a repetition of the first CSI-RS. As shown by reference number 728, the network node may receive, from the UE, an additional CQI report, which may be based at least in part on the repetition of the first CSI-RS. As shown by reference number 730, the network node may transmit, to the UE, a repetition of the second CSI-RS. As shown by reference number 732, the network node may receive, from the UE, an additional CQI report, which may be based at least in part on the repetition of the second CSI-RS. As shown by reference number 734, the network node may transmit, to the UE, a repetition of the third CSI-RS. As shown by reference number 736, the network node may receive, from the UE, an additional CQI report, which may be based at least in part on the repetition of the third CSI-RS. In some aspects, the network node may transmit repetitions of CSI-RSs using the same beams that were previously used for transmitting the CSI-RSs, respectively.

As shown by reference number 738, the network node may transmit, to the UE, a MAC-CE beam switch indication, which may be based at least in part on the first CQI report, the second CQI report, and the third CQI report. In other words, the network node may indicate a beam switching based at least in part on multiple CQI reports received from the UE. The network node may perform a downlink transmission, via a PDxCH, based at least in part on the beam switching.

In some aspects, resources for multiple sets of CSI-RSs (associated with the P3 procedures) may be back-to-back to enable a quick turnaround. In other words, the multiple sets of CSI-RSs (associated with the P3 procedures) for different refined beams may be transmitted to the UE in a back-to-back manner. In some aspects, the multiple sets of CSI-RSs may be transmitted back-to-back, and may be followed by respective CSI-RSs, which may also be transmitted back-to-back. In some aspects, for each candidate refined beam associated with a P3 procedure, the network node may transmit multiple CSI-RSs to the UE. The multiple CSI-RSs may include repeated CSI-RSs. In some aspects, the UE may perform a filtering on the CQI over the same pair of network node and UE beams before performing a CQI reporting. For example, the UE may transmit filtered CQI to the network node for each CSI-RS of CSI type. In some cases, the network node may perform a filtering on reported CQIs before selecting a network node refined beam, where the filtering may be on the reported CQIs of the same network node transmit beam.

As indicated above, FIG. 7 is provided as an example. Other examples may differ from what is described with regard to FIG. 7.

FIG. 8 is a diagram illustrating an example process 800 performed, for example, by a UE, in accordance with the present disclosure. Example process 800 is an example where the UE (e.g., UE 120) performs operations associated with beam management using multiple sets of CSI-RSs and CQI reporting.

As shown in FIG. 8, in some aspects, process 800 may include receiving, during a beam management procedure, multiple sets of CSI-RSs, wherein each set of CSI-RSs is associated with a same network node transmit beam (block 810). For example, the UE (e.g., using reception component 1002, depicted in FIG. 10) may receive, during a beam management procedure, multiple sets of CSI-RSs, wherein each set of CSI-RSs is associated with a same network node transmit beam, as described above.

As further shown in FIG. 8, in some aspects, process 800 may include receiving multiple CSI-RSs, wherein one CSI-RS of the multiple CSI-RSs is associated with one set of CSI-RSs of the multiple sets of CSI-RSs, and wherein a beam associated with the one CSI-RS corresponds to a beam associated with the one set of CSI-RSs (block 820). For example, the UE (e.g., using reception component 1002, depicted in FIG. 10) may receive multiple CSI-RSs, wherein one CSI-RS of the multiple CSI-RSs is associated with one set of CSI-RSs of the multiple sets of CSI-RSs, and wherein a beam associated with the one CSI-RS corresponds to a beam associated with the one set of CSI-RSs, as described above.

As further shown in FIG. 8, in some aspects, process 800 may include transmitting multiple CQI reports based at least in part on the multiple CSI-RSs, wherein one CQI report of the multiple CQI reports is based at least in part on the one CSI-RS of the multiple CSI-RSs (block 830). For example, the UE (e.g., using transmission component 1004, depicted in FIG. 10) may transmit multiple CQI reports based at least in part on the multiple CSI-RSs, wherein one CQI report of the multiple CQI reports is based at least in part on the one CSI-RS of the multiple CSI-RSs, as described above.

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

In a first aspect, the multiple sets of CSI-RSs are associated with multiple P3 procedures of the beam management procedure.

In a second aspect, alone or in combination with the first aspect, a best network node beam is based at least in part on the multiple CQI reports.

In a third aspect, alone or in combination with one or more of the first and second aspects, an ordering associated with the multiple sets of CSI-RSs, the multiple CSI-RSs, and the multiple CQI reports is based at least in part on a predefined ordering scheme.

In a fourth aspect, alone or in combination with one or more of the first through third aspects, the predefined ordering scheme involves an ordering of a single set of CSI-RSs, followed by a single CSI-RS, and followed by a single CQI report.

In a fifth aspect, alone or in combination with one or more of the first through fourth aspects, the predefined ordering scheme involves an ordering of consecutive sets of CSI-RSs, followed by a single CSI-RS, and followed by a single CQI report.

In a sixth aspect, alone or in combination with one or more of the first through fifth aspects, process 800 includes receiving, prior to receiving the multiple sets of CSI-RSs, a plurality of CSI-RSs associated with a P2 procedure of the beam management procedure, and transmitting a P2 measurement report indicating top beams.

In a seventh aspect, alone or in combination with one or more of the first through sixth aspects, process 800 includes receiving, after the multiple CQI reports are transmitted, a beam switch indication.

In an eighth aspect, alone or in combination with one or more of the first through seventh aspects, the multiple sets of CSI-RSs, the multiple CSI-RSs, and the multiple CQI reports enable a joint network node and UE beam refinement.

Although FIG. 8 shows example blocks of process 800, in some aspects, process 800 may include additional blocks, fewer blocks, different blocks, or differently arranged blocks than those depicted in FIG. 8. Additionally, or alternatively, two or more of the blocks of process 800 may be performed in parallel.

FIG. 9 is a diagram illustrating an example process 900 performed, for example, by a network node, in accordance with the present disclosure. Example process 900 is an example where the network node (e.g., network node 110) performs operations associated with beam management using multiple sets of CSI-RSs and CQI reporting.

As shown in FIG. 9, in some aspects, process 900 may include transmitting, during a beam management procedure, multiple sets of CSI-RSs, wherein each set of CSI-RSs is associated with a same network node transmit beam (block 910). For example, the network node (e.g., using transmission component 1104, depicted in FIG. 11) may transmit, during a beam management procedure, multiple sets of CSI-RSs, wherein each set of CSI-RSs is associated with a same network node transmit beam, as described above.

As further shown in FIG. 9, in some aspects, process 900 may include transmitting multiple CSI-RSs, wherein one CSI-RS of the multiple CSI-RSs is associated with one set of CSI-RSs of the multiple sets of CSI-RSs, and a beam associated with the one CSI-RS corresponds to a beam associated with the one set of CSI-RSs (block 920). For example, the network node (e.g., using transmission component 1104, depicted in FIG. 11) may transmit multiple CSI-RSs, wherein one CSI-RS of the multiple CSI-RSs is associated with one set of CSI-RSs of the multiple sets of CSI-RSs, and wherein a beam associated with the one CSI-RS corresponds to a beam associated with the one set of CSI-RSs, as described above.

As further shown in FIG. 9, in some aspects, process 900 may include receiving multiple CQI reports based at least in part on the multiple CSI-RSs, wherein one CQI report of the multiple CQI reports is based at least in part on the one CSI-RS of the multiple CSI-RSs (block 930). For example, the network node (e.g., using reception component 1102, depicted in FIG. 11) may receive multiple channel quality indicator (CQI) reports based at least in part on the multiple CSI-RSs, wherein one CQI report of the multiple CQI reports is based at least in part on the one CSI-RS of the multiple CSI-RSs, as described above.

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

In a first aspect, the multiple sets of CSI-RSs are associated with multiple P3 procedures of the beam management procedure.

In a second aspect, alone or in combination with the first aspect, process 900 includes selecting a best network node beam based at least in part on the multiple CQI reports.

In a third aspect, alone or in combination with one or more of the first and second aspects, an ordering associated with the multiple sets of CSI-RSs, the multiple CSI-RSs, and the multiple CQI reports is based at least in part on a predefined ordering scheme.

In a fourth aspect, alone or in combination with one or more of the first through third aspects, process 900 includes transmitting, prior to transmitting the multiple sets of CSI-RSs, a plurality of CSI-RSs associated with a P2 procedure of the beam management procedure, and receiving a P2 measurement report indicating top beams.

In a fifth aspect, alone or in combination with one or more of the first through fourth aspects, process 900 includes transmitting, after the multiple CQI reports are received, a beam switch indication.

Although FIG. 9 shows example blocks of process 900, in some aspects, process 900 may include additional blocks, fewer blocks, different blocks, or differently arranged blocks than those depicted in FIG. 9. Additionally, or alternatively, two or more of the blocks of process 900 may be performed in parallel.

FIG. 10 is a diagram of an example apparatus 1000 for wireless communication, in accordance with the present disclosure. The apparatus 1000 may be a UE, or a UE may include the apparatus 1000. In some aspects, the apparatus 1000 includes a reception component 1002 and a transmission component 1004, which may be in communication with one another (for example, via one or more buses and/or one or more other components). As shown, the apparatus 1000 may communicate with another apparatus 1006 (such as a UE, a base station, or another wireless communication device) using the reception component 1002 and the transmission component 1004.

In some aspects, the apparatus 1000 may be configured to perform one or more operations described herein in connection with FIGS. 5-7. Additionally, or alternatively, the apparatus 1000 may be configured to perform one or more processes described herein, such as process 800 of FIG. 8. In some aspects, the apparatus 1000 and/or one or more components shown in FIG. 10 may include one or more components of the UE described in connection with FIG. 2. Additionally, or alternatively, one or more components shown in FIG. 10 may be implemented within one or more components described in connection with FIG. 2. Additionally, or alternatively, one or more components of the set of components may be implemented at least in part 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 a processor to perform the functions or operations of the component.

The reception component 1002 may receive communications, such as reference signals, control information, data communications, or a combination thereof, from the apparatus 1006. The reception component 1002 may provide received communications to one or more other components of the apparatus 1000. In some aspects, the reception component 1002 may perform signal processing on the received communications (such as filtering, amplification, demodulation, analog-to-digital conversion, demultiplexing, deinterleaving, de-mapping, equalization, interference cancellation, or decoding, among other examples), and may provide the processed signals to the one or more other components of the apparatus 1000. In some aspects, the reception component 1002 may include one or more antennas, a modem, a demodulator, a MIMO detector, a receive processor, a controller/processor, a memory, or a combination thereof, of the UE described in connection with FIG. 2.

The transmission component 1004 may transmit communications, such as reference signals, control information, data communications, or a combination thereof, to the apparatus 1006. In some aspects, one or more other components of the apparatus 1000 may generate communications and may provide the generated communications to the transmission component 1004 for transmission to the apparatus 1006. In some aspects, the transmission component 1004 may perform signal processing on the generated communications (such as filtering, amplification, modulation, digital-to-analog conversion, multiplexing, interleaving, mapping, or encoding, among other examples), and may transmit the processed signals to the apparatus 1006. In some aspects, the transmission component 1004 may include one or more antennas, a modem, a modulator, a transmit MIMO processor, a transmit processor, a controller/processor, a memory, or a combination thereof, of the UE described in connection with FIG. 2. In some aspects, the transmission component 1004 may be co-located with the reception component 1002 in a transceiver.

The reception component 1002 may receive, during a beam management procedure, multiple sets of CSI-RSs, wherein each set of CSI-RSs is associated with a same network node transmit beam. The reception component 1002 may receive multiple CSI-RSs, wherein one CSI-RS of the multiple CSI-RSs is associated with one set of CSI-RSs of the multiple sets of CSI-RSs, and wherein a beam associated with the one CSI-RS corresponds to a beam associated with the one set of CSI-RSs. The transmission component 1004 may transmit multiple CQI reports based at least in part on the multiple CSI-RSs, wherein one CQI report of the multiple CQI reports is based at least in part on the one CSI-RS of the multiple CSI-RSs.

The reception component 1002 may receive, prior to receiving the multiple sets of CSI-RSs, a plurality of CSI-RSs associated with a P2 procedure of the beam management procedure. The transmission component 1004 may transmit a P2 measurement report indicating top beams. The reception component 1002 may receive, after the multiple CQI reports are transmitted, a beam switch indication.

The number and arrangement of components shown in FIG. 10 are provided as an example. In practice, there may be additional components, fewer components, different components, or differently arranged components than those shown in FIG. 10. Furthermore, two or more components shown in FIG. 10 may be implemented within a single component, or a single component shown in FIG. 10 may be implemented as multiple, distributed components. Additionally, or alternatively, a set of (one or more) components shown in FIG. 10 may perform one or more functions described as being performed by another set of components shown in FIG. 10.

FIG. 11 is a diagram of an example apparatus 1100 for wireless communication, in accordance with the present disclosure. The apparatus 1100 may be a network node, or a network node may include the apparatus 1100. In some aspects, the apparatus 1100 includes a reception component 1102 and a transmission component 1104, which may be in communication with one another (for example, via one or more buses and/or one or more other components). As shown, the apparatus 1100 may communicate with another apparatus 1106 (such as a UE, a base station, or another wireless communication device) using the reception component 1102 and the transmission component 1104. As further shown, the apparatus 1100 may include the communication manager 150. The communication manager 150 may include a selection component 1108, among other examples.

In some aspects, the apparatus 1100 may be configured to perform one or more operations described herein in connection with FIGS. 5-7. Additionally, or alternatively, the apparatus 1100 may be configured to perform one or more processes described herein, such as process 900 of FIG. 9. In some aspects, the apparatus 1100 and/or one or more components shown in FIG. 11 may include one or more components of the network node described in connection with FIG. 2. Additionally, or alternatively, one or more components shown in FIG. 11 may be implemented within one or more components described in connection with FIG. 2. Additionally, or alternatively, one or more components of the set of components may be implemented at least in part 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 a processor to perform the functions or operations of the component.