User equipment initiated beam management requests associated with multiple transmit-receive points

Abstract

Various aspects of the present disclosure generally relate to wireless communications. In some aspects, a user equipment (UE) may transmit a beam management request communication including a plurality of beam management requests, each of the plurality of beam management requests corresponding to a respective one of a plurality of transmit receive points (TRPs). The UE may perform a beam management operation associated with at least one TRP of the plurality of TRPs based on the beam management request communication. Numerous other aspects are described.

Description

Technical Field

[0001] All aspects of this disclosure relate to wireless communication in general, and to techniques and apparatus for beam management requests initiated by user equipment associated with multiple transmitting and receiving points. Background Technology

[0002] Wireless communication systems are widely deployed to provide a variety of telecommunications services, such as telephone, video, data, messaging, and broadcasting. Typical wireless communication systems employ multiple access technologies that enable communication with multiple users by sharing available system resources (e.g., bandwidth, transmit power, etc.). Examples of such multiple access technologies 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 a set of enhancements to the Universal Mobile Telecommunications System (UMTS) mobile standard issued by the 3rd 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 network nodes via downlink and uplink communication. A "downlink" (or "DL") refers to the communication link from the network node to the UE, and an "uplink" (or "UL") refers to the communication link from the UE to the network node. Some wireless networks may support device-to-device communication, such as via local links (e.g., sidelinks (SL), wireless local area network (WLAN) links, and / or wireless personal area network (WPAN) links, etc.).

[0004] The aforementioned multiple access technologies have been adopted in various telecommunications standards to provide a common protocol that enables different UEs to communicate at the city, country, region, and / or global levels. New Radio (NR) (which may be referred to as 5G) is a set of enhancements to the LTE mobile standard issued by 3GPP. NR is designed to better support mobile broadband internet access by: improving spectrum efficiency; reducing costs; improving service; utilizing new spectrum; and better integrating with other open standards by using Orthogonal Frequency Division Multiplexing (OFDM) with Cyclic Prefix (CP) on the downlink (CP-OFDM), and CP-OFDM and / or Single Carrier Frequency Division Multiplexing (SC-FDM) (also known as Discrete Fourier Transform Extended OFDM (DFT-s-OFDM)) on the uplink; and supporting beamforming, Multiple-Input Multiple-Output (MIMO) antenna technologies and carrier aggregation. Further improvements to LTE, NR, and other radio access technologies remain useful as the demand for mobile broadband access continues to increase. Summary of the Invention

[0005] Some aspects described herein relate to an apparatus for wireless communication at a user equipment (UE). The apparatus may include a memory and one or more processors coupled to the memory. The one or more processors may be configured to transmit beam management request communications comprising a plurality of beam management requests, each beam management request corresponding to a respective TRP among a plurality of transmit-receive points (TRPs). The one or more processors may be configured to perform beam management operations associated with at least one of the plurality of TRPs based on the beam management request communications.

[0006] Some aspects described herein relate to an apparatus for wireless communication at a network node. The apparatus may include a memory and one or more processors coupled to the memory. The one or more processors may be configured to receive beam management request communications comprising a plurality of beam management requests, each beam management request corresponding to a specific TRP among a plurality of TRPs. The one or more processors may be configured to perform beam management operations associated with at least one of the plurality of TRPs based on the beam management request communications.

[0007] Some aspects described herein relate to a method for wireless communication performed by a UE. The method may include sending beam management request communications comprising a plurality of beam management requests, each beam management request corresponding to a corresponding TRP among a plurality of TRPs. The method may include performing beam management operations associated with at least one of the plurality of TRPs based on the beam management request communications.

[0008] Some aspects described herein relate to a method for wireless communication performed by a network node. The method may include receiving beam management request communication comprising a plurality of beam management requests, each beam management request corresponding to a corresponding TRP among a plurality of TRPs. The method may include performing beam management operations associated with at least one of the plurality of TRPs based on the beam management request communication.

[0009] Some aspects described herein relate to a non-transitory computer-readable medium storing a set of instructions for wireless communication by a UE. When executed by one or more processors of the UE, the set of instructions enables the UE to send beam management request communications comprising a plurality of beam management requests, each beam management request corresponding to a specific TRP among a plurality of TRPs. When executed by one or more processors of the UE, the set of instructions enables the UE to perform beam management operations associated with at least one of the plurality of TRPs based on the beam management request communications.

[0010] Some aspects described herein relate to a non-transitory computer-readable medium storing a set of instructions for wireless communication by a network node. When executed by one or more processors of the network node, the set of instructions enables the network node to receive beam management request communications comprising a plurality of beam management requests, each beam management request corresponding to a specific TRP among a plurality of TRPs. When executed by one or more processors of the network node, the set of instructions enables the network node to perform beam management operations associated with at least one of the plurality of TRPs based on the beam management request communications.

[0011] Some aspects described herein relate to an apparatus for wireless communication. The apparatus may include components for transmitting beam management request communication comprising a plurality of beam management requests, each beam management request corresponding to a corresponding TRP among a plurality of TRPs. The apparatus may include components for performing beam management operations associated with at least one of the plurality of TRPs based on the beam management request communication.

[0012] Some aspects described herein relate to an apparatus for wireless communication. The apparatus may include components for receiving beam management request communications comprising a plurality of beam management requests, each beam management request corresponding to a specific TRP among a plurality of TRPs. The apparatus may include components for performing beam management operations associated with at least one of the plurality of TRPs based on the beam management request communications.

[0013] The entirety of the terms includes methods, apparatus, 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 accompanying drawings and description and illustrated as illustrated in the drawings and description.

[0014] The features and technical advantages of the examples according to this disclosure have been summarized rather extensively above in order to better understand the detailed description below. Additional features and advantages will be described below. The disclosed concepts and specific examples can be readily used as the basis for modifying or designing other structures for achieving the same purpose as this disclosure. Such equivalent constructions do not depart from the scope of the appended claims. The characteristics of the concepts disclosed herein, in both their organization and manner of operation, and the associated advantages, will be better understood by considering the following description in conjunction with the accompanying drawings. Each of the drawings provided is for illustrative and descriptive purposes and not as a definition of limitation of the claims.

[0015] While aspects are described herein by way of example, 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 package arrangements. For example, some aspects can be implemented via integrated chip implementations or other devices based on non-modular components (e.g., end-user equipment, vehicles, communication equipment, 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 may include additional components and features for implementing and practicing the claimed and described aspects. For example, the transmission and reception of wireless signals may 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 equipment of various sizes, shapes, and configurations. Attached Figure Description

[0016] To gain a full understanding of the foregoing features of this disclosure, a more specific description of the invention, briefly outlined above, can be obtained by referring to various aspects, some of which are illustrated in the accompanying drawings. However, it should be noted that the drawings illustrate only certain typical aspects of this disclosure and are therefore not to be considered as limiting its scope, as other equally valid aspects are permissible in this description. The same reference numerals in different drawings may identify the same or similar elements.

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

[0018] Figure 2 This 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 This is a diagram illustrating an example decomposed base station architecture according to this disclosure.

[0020] Figure 4 This is a diagram illustrating an example of multi-transmitter-receiver point (mTRP) communication according to this disclosure.

[0021] Figure 5 This is a diagram illustrating an example of a beam management request initiated by a UE associated with multiple Transmit / Receive Points (TRPs) according to this disclosure.

[0022] Figure 6This is a diagram illustrating an example procedure performed by a UE according to this disclosure, for example.

[0023] Figure 7 This is a diagram illustrating an example process performed, for example, by a network node according to this disclosure.

[0024] Figure 8 This is a diagram of an example device for wireless communication according to the present disclosure.

[0025] Figure 9 This is a diagram of an example device for wireless communication according to the present disclosure. Detailed Implementation

[0026] A network node can transmit multiple beams to a user equipment (UE). In some respects, the UE can select a set of beams for communication with the network node. For example, the UE can select the set of beams at least in part based on its association with advantageous characteristics. The UE can generate codewords indicating the set of beams and parameters to be used in the codebook, based at least in part on performing channel estimation of the channel between the network node and the UE. The UE can use the beams to communicate with multiple transmit-receive points (TRPs).

[0027] Once a network node and a UE have selected beams for one or more beam pairs, the network node is aware of the one or more UE beams used by the UE. However, the UE may autonomously switch its receive beams (e.g., the UE beam within a beam pair) based at least in part on changing reception conditions. If the UE autonomously switches its receive beams (e.g., based at least in part on UE mobility, UE rotation, etc.), the network node may not be aware that the UE has switched its receive beams before subsequent Channel State Feedback (CSF) reports and / or subsequent beam reports. Based at least in part on the network node's lack of awareness that the UE has switched its receive beams, the network node may use outdated Channel State Information (CSI), which may degrade the performance of the communication link between the network node and the UE. For example, based at least in part on the network node's use of outdated CSI, the UE may utilize increased error rates and / or suboptimal spectral efficiency, etc., to receive downlink communication, which may consume communication and network resources.

[0028] In some aspects described herein, the UE may determine changes in one or more reception conditions and may (e.g., autonomously) send beam management request communications comprising multiple beam management requests, each beam management request corresponding to a TRP among multiple TRPs, for beam management operations to update at least one beam associated with at least one of the multiple TRPs communicating with the UE. In some aspects, changes in one or more reception conditions may include, or may be at least partially based on, changes in the UE's transmitted beam and / or received beam, changes in link quality (e.g., changes in Reference Signal Received Power (RSRP), Signal-to-Interference-plus-Noise Ratio (SINR), path loss, etc.), UE movement, changes in UE speed, changes in UE orientation, changes in detected reflectors and / or scattering (e.g., changes in the angle and / or intensity of the received signal), etc.

[0029] In some respects, the UE may transmit beam management request communications via one or more MAC CEs and / or via uplink control information (UCI). In some respects, the UE may use existing permissions to transmit beam management request communications, request new permissions to transmit beam management request communications, and / or transmit beam management request communications together with other UCIs (e.g., Hybrid Automatic Repeat Request (HARQ) feedback).

[0030] Based at least in part on receiving a request for radio link adaptation operation, a network node (which may be, include, or be included in one or more TRPs among a plurality of TRPs) may schedule the UE to receive one or more reference signals and / or report measurements and / or metrics associated with one or more reference signals. This facilitates beam synchronization between the TRP and the UE and allows the TRP to receive the current CSI to determine downlink transmission parameters. Based at least in part on the TRP receiving the current CSI to determine downlink transmission parameters, the TRP (e.g., via the network node) may determine appropriate transmission parameters for downlink communication (e.g., modulation and decoding scheme (MCS), transport block size, resource allocation, transmit power, beam direction, etc.), which can conserve communication, network, and / or power resources associated with the UE and / or the TRP.

[0031] Various aspects of this disclosure are described more fully below with reference to the accompanying drawings. However, this disclosure may be embodied in many different forms and should not be construed as limited to any particular structure or function presented throughout this disclosure. Rather, these aspects are provided so that this disclosure will be thorough and complete, and will fully convey the scope of this disclosure to those skilled in the art. Those skilled in the art will appreciate that the scope of this disclosure is intended to cover any aspect of this disclosure disclosed herein, whether implemented independently or in combination with any other aspect of this disclosure. For example, any number of aspects set forth herein may be used to implement an apparatus or method of practice. Furthermore, the scope of this disclosure is intended to cover such apparatus or methods practiced using structures, functionalities, or structures and functionalities other than or different from the various aspects of the disclosure set forth herein. It should be understood that any aspect of the disclosure herein may be embodied by one or more elements of the claims.

[0032] Aspects and examples generally include methods, apparatus, network nodes, systems, computer program products, non-transitory computer-readable media, user equipment, base stations, wireless communication devices and / or processing systems as described or fully described herein with reference to the accompanying drawings and description and illustrated as such.

[0033] This disclosure can be readily used as the basis for modifying or designing other structures for performing the same purposes as this disclosure. Such equivalent constructions do not depart from the scope of the appended claims. The characteristics of the concepts disclosed herein (both their organization and manner of operation) and their associated advantages are better understood in conjunction with the accompanying drawings, based on the following description. Each figure provided in the drawings is for illustrative and descriptive purposes and not as a definition of limitation of the claims.

[0034] While aspects are described herein by way of example, 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 package arrangements. For example, some aspects can be implemented via integrated chip implementations or other devices based on non-modular components (e.g., end-user equipment, vehicles, communication equipment, 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 may include additional components and features for implementing and practicing the claimed and described aspects. For example, the transmission and reception of wireless signals may 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 can be practiced in a wide variety of devices, components, systems, distributed arrangements, and / or end-user equipment of different sizes, shapes, and configurations.

[0035] Various devices and techniques will now be used to illustrate several aspects of a telecommunications system. These devices and techniques will be described in detail below and illustrated in the accompanying drawings by various blocks, modules, components, circuits, steps, processes, or algorithms (collectively, “elements”). These elements can be implemented using hardware, software, or a combination thereof. Whether such elements are implemented as hardware or software depends on the specific application and the design constraints imposed on the system as a whole.

[0036] Although terms generally associated with 5G or New Radio (NR) Radio Access Technology (RAT) may be used herein to describe aspects, aspects of this disclosure may be applied to other RATs, such as 3G RAT, 4G RAT and / or 5G and later (e.g., 6G) RATs.

[0037] Figure 1This is a diagram illustrating an example of a wireless network 100 according to 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., LTE) network, etc. The wireless network 100 may include one or more network nodes 110 (shown as network node 110a, network node 110b, network node 110c, and network node 110d), one or more UEs 120 (shown as UE 120a, UE 120b, UE 120c, UE 120d, and UE 120e), and / or other entities. Network node 110 is a network node that communicates with UE 120. As shown, network node 110 may include one or more network nodes. For example, network node 110 can be an aggregated network node, meaning that the aggregated network node is 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, network node 110 can be a decomposed network node (sometimes referred to as a decomposed base station), meaning that network node 110 is 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)).

[0038] In some examples, network node 110 is or includes network nodes (such as RUs) that communicate with UE 120 via radio access links. In some examples, network node 110 is or includes network nodes (such as DUs) that communicate with other network nodes 110 via fronthaul or midhaul links. In some examples, network node 110 is or includes network nodes (such as CUs) that communicate with other network nodes 110 via midhaul links or with the core network via backhaul links. In some examples, network node 110 (such as aggregated network node 110 or decomposed 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, NR base stations, LTE base stations, Node Bs, eNBs (e.g., in 4G), gNBs (e.g., in 5G), access points, TRPs, DUs, RUs, CUs, network mobility elements, core network nodes, network elements, network equipment, RAN nodes, or combinations thereof. In some examples, network nodes 110 can interconnect with each other or with one or more other network nodes 110 in the wireless network 100 using any suitable transport network through various types of fronthaul interfaces, midhaul interfaces, and / or backhaul interfaces (such as direct physical connections, air interfaces, or virtual networks).

[0039] In some examples, network node 110 may provide communication coverage for a specific geographic 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 macrocells, picocells, femtocells, and / or another type of cell. A macrocell may cover a relatively large geographic area (e.g., a radius of several kilometers) and may allow unrestricted access by UE 120 with a service subscription. A picocell may cover a relatively small geographic area and may allow unrestricted access by UE 120 with a service subscription. A femtocell may cover a relatively small geographic 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)). Network node 110 used for macrocells may be referred to as a macro network node. Network node 110 used for picocells may be referred to as a pico network node. The network node 110 used for femtocells can be referred to as a femtocell network node or a home network node. Figure 1 In the example shown, network node 110a can be a macro network node for macro cell 102a, network node 110b can be a pico network node for pico cell 102b, and network node 110c can be a femto network node for femto cell 102c. Network nodes can support one or more (e.g., three) cells. In some examples, the cells may not necessarily be stationary, and the geographical area of ​​the cells may move depending on the location of the mobile network node 110 (e.g., a mobile network node).

[0040] In some aspects, the term "base station" or "network node" may refer to an aggregated base station, a decomposed base station, an integrated access and backhaul (IAB) node, a relay node, or one or more components thereof. For example, in some aspects, "base station" or "network node" may refer to a CU, DU, 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 device configured to perform one or more functions (such as those described herein in conjunction 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 that 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 can be instantiated on a single device. In some aspects, the term "base station" or "network node" may refer to one base station function rather than another. In this way, a single device may include more than one base station.

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

[0042] The wireless network 100 can be a heterogeneous network, comprising different types of network nodes 110, such as macro network nodes, pico network nodes, femto network nodes, or relay network nodes. These different types of network nodes 110 may have different transmit power levels, different coverage areas, and / or different effects on interference in the wireless network 100. For example, macro network nodes may have high transmit power levels (e.g., 5 watts to 40 watts), while pico network nodes, femto network nodes, and relay network nodes may have lower transmit power levels (e.g., 0.1 watts to 2 watts).

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

[0044] UE 120 may be distributed throughout the wireless network 100, and each UE 120 may be stationary or mobile. UE 120 may include, for example, access terminals, terminals, mobile stations, and / or subscriber units. UE 120 may be a cellular phone (e.g., a smartphone), 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, an ultrabook, a medical device, a biometric device, a wearable device (e.g., a smartwatch, smart clothing, smart glasses, a smart wristband, smart jewelry (e.g., a smart ring or 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 GPS device, a UE function of a network node, and / or any other suitable device configured to communicate via wireless or wired media.

[0045] 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 that can 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 NB-IoT (Narrowband IoT) devices. Some UEs 120 may be considered customer premises equipment. UEs 120 may be included within a housing that houses the components of the UE 120, such as processor components and / or memory components. In some examples, the processor components and memory components may be coupled together. For example, the processor components (e.g., one or more processors) and memory components (e.g., memory) may be operatively coupled, communicatively coupled, electronically coupled, and / or electrically coupled.

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

[0047] 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 network node 110 as an intermediary device to communicate with each other). For example, UE 120 may communicate using 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. In such examples, UE 120 may perform scheduling operations, resource selection operations, and / or other operations described elsewhere herein as being performed by network node 110.

[0048] Devices in Wireless Network 100 can communicate using the electromagnetic spectrum, which can be subdivided into various categories, bands, or channels based on frequency or wavelength. For example, devices in Wireless Network 100 can communicate using one or more operating bands. In 5G NR, two initial operating bands have been designated as frequency ranges FR1 (410MHz to 7.125GHz) and FR2 (24.25GHz to 52.6GHz). It should be understood that although a portion of FR1 is greater than 6GHz, FR1 is often (interchangeably) referred to as the “sub-6GHz” band in various documents and articles. Similar naming issues sometimes occur with FR2, which is often (interchangeably) referred to as the “millimeter wave” band in documents and articles, although this is different from the Extremely High Frequency (EHF) band (30GHz to 300GHz) designated as a “millimeter wave” band by the International Telecommunication Union (ITU).

[0049] The frequencies between FR1 and FR2 are generally referred to as mid-band frequencies. Recent 5G NR studies have identified the operating bands used for these mid-band frequencies as the frequency range designation FR3 (7.125 GHz to 24.25 GHz). Bands falling within FR3 can inherit FR1 and / or FR2 characteristics, thus effectively extending the features of FR1 and / or FR2 to mid-band frequencies. Furthermore, higher frequency bands are currently being explored to extend 5G NR operation beyond 52.6 GHz. For example, three higher operating frequency bands have been identified as the frequency range designations FR4a or FR4-1 (52.6 GHz to 71 GHz), FR4 (52.6 GHz to 114.25 GHz), and FR5 (114.25 GHz to 300 GHz). Each of these higher frequency bands falls within the EHF band.

[0050] Considering the examples above, unless otherwise specifically stated, it should be understood that when the term "below 6 GHz" is used herein, it can broadly refer to frequencies below 6 GHz, within FR1, or including intermediate frequency band frequencies. Furthermore, unless otherwise specifically stated, it should be understood that when the term "millimeter wave" is used herein, it can broadly refer to frequencies that can include intermediate frequency band frequencies, within FR2, FR4, FR4-a, or FR4-1 and / or FR5, or within the EHF band. Modifications to frequencies included in these operating frequency bands (e.g., FR1, FR2, FR3, FR4, FR4-a, FR4-1, and / or FR5) are contemplated, and the techniques described herein are applicable to those modified frequency ranges.

[0051] In some aspects, the UE (e.g., UE 120) may include a communication manager 140. As described in more detail elsewhere herein, the communication manager 140 may send beam management request communications including a plurality of beam management requests, each beam management request corresponding to a corresponding TRP among a plurality of TRPs; and perform beam management operations associated with at least one of the plurality of TRPs based on the beam management request communications. Additionally or alternatively, the communication manager 140 may perform one or more other operations described herein.

[0052] 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 receive beam management request communications including a plurality of beam management requests, each beam management request corresponding to a corresponding TRP among a plurality of TRPs; and perform beam management operations associated with at least one of the plurality of TRPs based on the beam management request communications. Additionally or alternatively, the communication manager 150 may perform one or more other operations described herein.

[0053] As indicated above, Figure 1 This is provided as an example. Other examples are available with reference to [the relevant information]. Figure 1 The examples described are different.

[0054] Figure 2 This is a diagram illustrating example 200 of communication between network node 110 and UE 120 in a wireless network 100 according to this disclosure. Network node 110 may be equipped with a set of antennas 234a to 234t, such as T antennas (T≥1). UE 120 may be equipped with a set of antennas 252a to 252r, such as R antennas (R≥1). Network node 110 of example 200 includes one or more radio frequency components, such as antennas 234 and modems 232. In some examples, network node 110 may include an interface, communication components, or another component facilitating communication with UE 120 or another network node. Some network nodes 110 may not include radio frequency components facilitating direct communication with UE 120, such as one or more CUs or one or more DUs.

[0055] At network node 110, transmitting processor 220 may receive data from data source 212 intended for use by UE 120 (or a group of UEs 120). Transmitting processor 220 may select one or more 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) the data for UE 120 based at least in part on the MCS selected for UE 120 and may provide data symbols for UE 120. Transmitting 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 provide overhead symbols and control symbols. Transmitting 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)). The transmit (TX) multiple-input multiple-output (MIMO) processor 230 can perform spatial processing (e.g., pre-decoding) on ​​data symbols, control symbols, overhead symbols, and / or reference symbols, where applicable, and can 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 to 232t). For example, each output symbol stream can be provided to a modulator component (shown as MOD) of modem 232. Each modem 232 can use a corresponding modulator component to process the corresponding output symbol stream (e.g., for OFDM) to obtain an output sample stream. Each modem 232 can also use a corresponding modulator component to process the output sample stream (e.g., convert to analog, amplify, filter, and / or up-convert) to obtain a downlink signal. Modems 232a to 232t can 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 to 234t).

[0056] At UE 120, a set of antennas 252 (shown as antennas 252a to 252r) can receive downlink signals from network node 110 and / or other network nodes 110 and can 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 to 254r). For example, each received signal can be provided to a demodulator component (shown as DEMOD) of modem 254. Each modem 254 can use a corresponding demodulator component to condition (e.g., filter, amplify, downconvert, and / or digitize) the received signal to obtain an input sample. Each modem 254 can use the demodulator component to further process the input sample (e.g., for OFDM) to obtain a received symbol. MIMO detector 256 can obtain the received symbols from modem 254, perform MIMO detection on the received symbols where applicable, and provide the detected symbols. The receiver processor 258 can process (e.g., demodulate and decode) the detected symbols, provide the decoded data for UE 120 to data sink 260, and provide the decoded control information and system information to controller / processor 280. The term "controller / processor" can refer to one or more controllers, one or more processors, or a combination thereof. The channel processor can determine 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 UE 120 may be included in housing 284.

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

[0058] One or more antennas (e.g., antennas 234a to 234t and / or antennas 252a to 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. Antenna panels, antenna groups, sets of antenna elements and / or antenna arrays 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 be coupled to one or more transmitting and / or receiving components (such as...). Figure 2 One or more antenna elements (one or more components in a )

[0059] Each antenna element may include one or more sub-elements for radiating or receiving radio frequency signals. For example, a single antenna element may include a first sub-element that is cross-polarized with a second sub-element, which can be used to independently transmit cross-polarized signals. Antenna elements may include patch antennas, dipole antennas, or other types of antennas arranged in a linear pattern, a two-dimensional pattern, or another pattern. The spacing between antenna elements allows signals transmitted individually by the antenna elements at desired wavelengths to interact or interfere with each other (e.g., to form a desired beam). For example, given a desired wavelength or frequency range, the spacing may provide a quarter wavelength, half wavelength, or other fraction of the wavelength between adjacent antenna elements to allow interaction or interference of signals transmitted by individual antenna elements within that desired range.

[0060] Antenna elements and / or sub-elements can be used to generate a beam. A “beam” can specify a wireless signal to be transmitted, such as in the direction of a receiving device. A beam may include a directional signal, a direction associated with the signal, a set of directional resources associated with the signal (e.g., angle of arrival, horizontal direction, vertical direction), and / or a set of parameters indicating one or more aspects of the directional signal, the direction associated with the signal, and / or the set of directional resources associated with the signal.

[0061] As indicated above, antenna elements and / or sub-elements can be used to generate beams. For example, antenna elements can be individually selected or deselected for the transmission of signals (or multiple signals) by controlling the amplitude of one or more corresponding amplifiers. Beamforming involves generating a beam using multiple signals on different antenna elements, wherein one or more or all of these signals are phase-shifted relative to each other. The formed beam can carry physical or higher-level reference signals or information. As each of the multiple signals is radiated from its respective antenna element, the radiated signals interact with, interfere with (constructive and destructive interference), and are amplified to form the resulting beam. The shape (such as amplitude, width, and / or the presence of sidelobes) and orientation (such as the angle of the beam relative to the surface of the antenna array) can be dynamically controlled by modifying the phase shifts or phase offsets of the multiple signals relative to each other.

[0062] Beamforming can be used for communication between a UE and a network node, such as for millimeter-wave communication. In this case, the network node can provide the UE with a Transmit Configuration Indicator (TCI) state configuration, which indicates the beam that the UE can use, for example, to receive the Physical Downlink Shared Channel (PDSCH). The TCI state indicates the spatial parameters used for communication. For example, the TCI state for communication can identify the source signal (such as a synchronization signal block, channel state information reference signal, etc.) and the spatial parameters to be derived from the source signal for the purpose of transmitting or receiving communication. For example, the TCI state can indicate the Quasi-Co-location (QCL) type. The QCL type can indicate one or more spatial parameters to be derived from the source signal. The source signal can be referred to as the QCL source. The network node can indicate the active TCI state to the UE, which the UE can use to select the beam for receiving the PDSCH.

[0063] Beam indication can be or includes TCI state information elements, beam identifiers (IDs), spatial relationship information, TCI state IDs, closed-loop indexes, panel IDs, TRP IDs, and / or sounding reference signal (SRS) set IDs, etc. TCI state information elements (referred to herein as TCI states) can indicate information associated with beams such as downlink beams. For example, TCI state information elements can indicate TCI state identifiers (e.g., tci-StateID), QCL types (e.g., qcl-Type1, qcl-Type2, qcl-TypeA, qcl-TypeB, qcl-TypeC, qcl-TypeD, etc.), cell identifiers (e.g., ServCellIndex), bandwidth portion identifiers (bwp-Id), reference signal identifiers (such as CSI-RS (e.g., NZP-CSI-RS-ResourceId, SSB-Index, etc.)), etc. Spatial relationship information can similarly indicate information associated with uplink beams.

[0064] Beam indication can be a combined or separate downlink (DL) / uplink (UL) beam indication within a unified TCI framework. In some cases, the network may use at least UE-specific (unicast) downlink control information (DCI) to indicate a combined or separate DL / UL beam indication from an active TCI state, thereby supporting Layer 1 (L1) based beam indication. In some cases, existing DCI formats 1_1 and / or 1_2 may be reused for beam indication. The network may include support mechanisms for UE confirmation of successful decoding of the beam indication. For example, acknowledgment / negation acknowledgment (ACK / NACK) of a PDSCH scheduled via a DCI carrying the beam indication may also be used as an ACK for the DCI.

[0065] Beam indication can be provided for carrier aggregation (CA) scenarios. Within a unified TCI framework, the network can support public TCI state ID updates and activations to provide public QCL information and / or one or more public UL transmit spatial filters across a set of configured component carriers (CCs). This type of beam indication can be applied to in-band CA as well as joint DL / UL beam indication and individual DL / UL beam indication. The public TCI state ID can refer to a reference signal (RS) determined based on the TCI state indicated by the public TCI state ID, used to provide QCL type D indication and to determine the UL transmit spatial filters across that set of configured CCs.

[0066] On the uplink, at UE 120, the transmit processor 264 can receive and process data from data source 262 and control information from controller / processor 280 (e.g., for reporting including RSRP, RSSI, RSRQ, and / or CQI). The transmit processor 264 can generate reference symbols for one or more reference signals. The symbols from the transmit processor 264 can be pre-decoded by the TX MIMO processor 266 where applicable, further processed by the modem 254 (e.g., for DFT-s-OFDM or CP-OFDM), and transmitted to network node 110. In some examples, the modem 254 of UE 120 may include a modulator and demodulator. In some examples, UE 120 includes a transceiver. The transceiver may include any combination of antenna 252, modem 254, MIMO detector 256, receive processor 258, transmit processor 264, and / or TX MIMO processor 266. The transceiver may be used by a processor (e.g., controller / processor 280) and memory 282 to execute this document (e.g., reference). Figures 5 to 9 ( ) any aspect of the methods described in the method.

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

[0068] The controller / processor 240 of network node 110, the controller / processor 280 of UE 120 and / or Figure 2 Any other component may perform one or more techniques associated with beam management requests initiated by the UE and associated with multiple TRPs, as described in more detail elsewhere herein. For example, the controller / processor 240 of network node 110, the controller / processor 280 of UE 120, and / or Figure 2 Any other component that can execute or direct, for example Figure 6 Process 600 Figure 7 The operation of process 700 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 a non-transitory computer-readable medium storing one or more instructions (e.g., code and / or program code) for wireless communication. For example, one or more instructions may cause one or more processors, UE 120 and / or network node 110 to perform or direct, for example, when executed by one or more processors of network node 110 and / or UE 120 (e.g., directly executed, or executed after compilation, transformation and / or interpretation). Figure 6 Process 600 Figure 7The operation of process 700 and / or other processes as described herein. In some examples, the execution instructions may include run instructions, transformation instructions, compilation instructions, and / or interpretation instructions, etc.

[0069] In some aspects, the UE (e.g., UE 120) includes components for transmitting beam management request communications comprising a plurality of beam management requests, each beam management request corresponding to a corresponding TRP among a plurality of TRPs; and / or components for performing beam management operations associated with at least one of the plurality of TRPs based on the beam management request communications. Components for the UE to perform the operations described herein may include one or more of, for example, a communication manager 140, an antenna 252, a modem 254, a MIMO detector 256, a receive processor 258, a transmit processor 264, a TX MIMO processor 266, a controller / processor 280, or a memory 282.

[0070] In some aspects, a network node (e.g., network node 110) includes components for receiving beam management request communications comprising a plurality of beam management requests, each beam management request corresponding to a corresponding TRP among a plurality of TRPs; and / or components for performing beam management operations associated with at least one of the plurality of TRPs based on the beam management request communications. Components for the network node to perform the operations described herein may include one or more of, for example, a communication manager 150, a transmit processor 220, a TX MIMO processor 230, a modem 232, an antenna 234, a MIMO detector 236, a receive processor 238, a controller / processor 240, a memory 242, or a scheduler 246.

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

[0072] As indicated above, Figure 2 This is provided as an example. Other examples are available with reference to [the relevant information]. Figure 2 The examples described are different.

[0073] The deployment of communication systems such as 5G NR systems can be arranged in a variety of ways using various components or parts. In a 5G NR system or network, network nodes, network entities, network mobility elements, RAN nodes, core network nodes, network elements, base stations, or network equipment can be implemented in either a converged or decomposed architecture. For example, a base station (such as a Node B (NB), evolved NB (eNB), NR base station, 5G NB, access point (AP), TRP, or cell, etc.) or one or more units (or components) performing base station functionality can be implemented as a converged base station (also known as a standalone 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 combinations thereof).

[0074] Aggregated base stations (e.g., aggregated network nodes) 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 cell). Decomposed base stations (e.g., decomposed network nodes) can be configured to utilize a protocol stack that is physically or logically distributed across two or more cells (such as one or more CUs, one or more DUs, or one or more RUs). In some examples, the 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 across one or more other network nodes. DUs may be implemented to communicate with one or more RUs. Each of the CU, DU, and RU can also be implemented as a virtual cell, such as a Virtual Central Unit (VCU), a Virtual Distributed Unit (VDU), or a Virtual Radio Unit (VRU), etc.

[0075] Base station type operation or network design can take into account the aggregation characteristics of base station functionality. For example, decomposed base stations can be utilized in IAB networks, Open Radio Access Networks (O-RAN (such as network configurations initiated by the O-RAN Alliance)), or Virtualized Radio Access Networks (vRAN, also known as Cloud Radio Access Networks (C-RAN)) to facilitate the scaling of communication systems by separating base station functionality into one or more units that can be deployed independently. Decomposed base stations can include functionality implemented across two or more units at various physical locations, as well as functionality virtually implemented for at least one unit, which enables flexibility in network design. Each unit of a decomposed base station can be configured for wired or wireless communication with at least one other unit of the decomposed base station.

[0076] Figure 3This is an illustration of an example disaggregated base station architecture 300 according to this disclosure. The disaggregated base station architecture 300 may include a CU 310, which may communicate directly with the core network 320 via a backhaul link, or indirectly with the core network 320 via one or more disaggregated control units (such as 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 may communicate with one or more DUs 330 via a corresponding midhaul link (such as via an F1 interface). Each DU 330 may communicate with one or more RUs 340 via a corresponding fronthaul link. Each RU 340 may communicate with one or more UEs 120 via a corresponding RF access link. In some implementations, a UE 120 may be served simultaneously by multiple RUs 340.

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

[0078] In some aspects, the CU 310 can host one or more higher-level 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, etc. Each control function can be implemented using an interface configured to signal to other control functions hosted by the CU 310. The CU 310 can be configured to handle user plane functions (e.g., Central Unit-User Plane (CU-UP) functions), control plane functions (e.g., Central Unit-Control Plane (CU-CP) functions), or combinations thereof. In some implementations, the CU 310 may be logically split 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 can communicate bidirectionally with the CU-CP units via an interface such as an E1 interface. The CU 310 may be implemented to communicate with the DU 330 for network control and signaling purposes, as needed.

[0079] Each DU 330 may correspond to a logical unit comprising one or more base station functions for controlling the operation of one or more RU 340s. In some aspects, the DU 330 may host one or more of the Radio Link Control (RLC) layer, Medium Access Control (MAC) layer, and one or more high physical (PHY) layers, at least in part, according to functional splits (such as those defined by 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, etc. In some aspects, the DU 330 may also host one or more low 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, etc. Each layer (which may also be referred to as a module) may be implemented using an interface configured to communicate signals with other layers (and modules) hosted by the DU 330 or with control functions hosted by the CU 310.

[0080] 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, based on function splitting (e.g., function splitting defined by 3GPP) (such as lower-layer function splitting). In this architecture, each RU 340 can be operated to handle over-the-air (OTA) communications with one or more UE 120s. In some specific implementations, the real-time and non-real-time aspects of control plane and user plane communications with the RU 340 can be controlled by the corresponding DU 330. In some scenarios, this configuration allows each DU 330 and CU 310 to be implemented in a cloud-based RAN architecture, such as a vRAN architecture.

[0081] The SMO framework 305 can be configured to support RAN deployment and provisioning of both non-virtualized 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, which can be managed via operation and maintenance interfaces such as the O1 interface. For virtualized network elements, the SMO framework 305 can be configured to interact with cloud computing platforms such as the Open Cloud (O-Cloud) platform 390 to perform network element lifecycle management (such as instantiating virtualized network elements) via cloud computing platform interfaces such as the O2 interface. Such virtualized network elements may include, but are not limited to, CU 310, DU 330, RU 340, non-RT RIC 315, and near-RTTRIC 325. In some specific implementations, the SMO framework 305 may communicate with the hardware aspects of the 4G RAN, such as the Open eNB (O-eNB) 311, via the O1 interface. Additionally, in some implementations, the SMO framework 305 can communicate directly with each of one or more RUs 340 via a corresponding O1 interface. The SMO framework 305 may also include a non-RT RIC 315 configured to support the functionality of the SMO framework 305.

[0082] The non-RT RIC 315 can be configured to include logical functions that enable non-real-time control and optimization of RAN elements and resources, including artificial intelligence / machine learning (AI / ML) workflows for model training and updates, or policy-based guidance for 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 an A1 interface. The near-RT RIC 325 can be configured to include logical functions that enable near real-time control and optimization of RAN elements and resources via an interface, such as an E2 interface, through data collection and actions, connecting one or more CU 310s, one or more DU 330s, or both, and O-eNBs to the near-RT RIC 325.

[0083] 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 an external server. This information can be utilized by the near-RT RIC 325 and can be received from non-network data sources or network functions at the SMO framework 305 or the non-RT RIC 315. In some examples, the non-RT RIC 315 or 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 in performance and employ AI / ML models to perform corrective actions via the SMO framework 305 (such as reconfiguration via the O1 interface) or via the creation of RAN management policies (such as A1 interface policies).

[0084] As indicated above, Figure 3 This is provided as an example. Other examples are available with reference to [the relevant information]. Figure 3 The examples described are different.

[0085] A network node (e.g., network node 110) may transmit a number of beams to a UE (e.g., UE 120). A “beam” may specify the direction of transmission, such as a radio signal transmitted in the direction of a receiving device. A beam may include a directional signal, a direction associated with the signal, a set of directional resources associated with the signal (e.g., angle of arrival, horizontal direction, vertical direction), and / or a set of parameters indicating one or more aspects of the directional signal, the direction associated with the signal, and / or the set of directional resources associated with the signal. For example, a network node may use an antenna panel to generate beams that generate beams with spatial and / or phase shifts relative to each other. The network node and the UE may select a set of beams to be used for communication between the network node and the UE. For example, this set of beams transmitted from the network node to the UE may be referred to herein as a communication link, downlink, etc. The communication link between the network node and the UE may propagate in a medium and / or through various geometric paths, which are collectively referred to herein as a channel between the network node and the UE.

[0086] In some aspects, the UE may select a set of beams for communicating with the network node. For example, the UE may select the set of beams at least in part based on its association with favorable characteristics (e.g., satisfactory received power, satisfactory SINR value, etc.). The UE may generate codewords indicating the set of beams and parameters to be used in the codebook based at least in part on performing channel estimation of the channel between the network node and the UE. In some aspects, the codebook may be a HARQ codebook.

[0087] One such codebook is the Type II codebook specified in 5G / NR. The Type II codebook uses a two-stage process to generate codewords: a first stage where a set of beams is selected for the bandwidth of the communication link (e.g., sometimes referred to herein as W1), and a second stage where linear combination is performed on a set of subbands using that set of beams for each subband. The codewords may be at least partially based on linear combination and may indicate the set of beams and / or corresponding amplitude, phase coefficients, etc. Thus, the UE can provide an indication of the channel state at the UE and can request the set of beams to be used for the UE. The Type II codebook provides a more accurate specification of the channel state than the Type I codebook, which provides a predefined codeword-based method for specifying the selected beams. Therefore, the Type II codebook can be referred to as a high-resolution codebook compared to the Type I codebook. The Type II codebook improves MU-MIMO performance on the communication link.

[0088] A UE can communicate with multiple TRPs using beamforming. A TRP is a network node configured to transmit and receive signals. For example, a TRP may include one or more components of a base station. In some cases, a UE can communicate with multiple TRPs simultaneously (e.g., at the same time) based on an mTRP configuration. In mTRP downlink communication, the UE can receive multiple communications, each from a different TRP.

[0089] Figure 4 This is a diagram illustrating example 400 of mTRP communication (sometimes referred to as multi-panel communication) according to this disclosure. Figure 4 As shown, multiple TRPs 405 can communicate with the same UE 120. A network node may include multiple TRPs 405, or multiple TRPs 405 may be distributed across multiple network nodes.

[0090] Multiple TRPs 405 (shown as TRP A and TRP B) can communicate with the same UE 120 in a coordinated manner (e.g., using coordinated multicast) to improve reliability and / or increase throughput. Such communication can be coordinated via interfaces between TRPs 405 (e.g., backhaul interfaces and / or access node controllers). When TRPs 405 are co-located at the same network node (e.g., when TRPs 405 are different antenna arrays or panels of the same network node), the interface can have lower latency and / or higher capacity, and when TRPs 405 are located at different network nodes, the interface can have higher latency and / or lower capacity (compared to co-location). Different TRPs 405 can communicate with the UE 120 using different QCL relationships (e.g., different TCI states), different DMRS ports, and / or different layers (e.g., different layers in multi-layer communication).

[0091] In the first multi-TRP transmission mode (e.g., mode 1), a single physical downlink control channel (PDCCH) can be used to schedule downlink data communication for a single PDSCH. In this case, multiple TRPs 405 (e.g., TRP A and TRP B) can transmit communication to UE 120 on the same PDSCH. For example, a single codeword with different spatial layers for different TRPs 405 can be used to transmit communication (e.g., one codeword is mapped to a first set of layers transmitted by a first TRP 405 and to a second set of layers transmitted by a second TRP 405). As another example, multiple codewords can be used to transmit communication, where different codewords are transmitted by different TRPs 405 (e.g., using different sets of layers). In either case, different TRPs 405 can use different QCL relationships (e.g., different TCI states) for different DMRS ports corresponding to different layers. For example, a first TRP 405 may use a first QCL relationship or a first TCI state for a first group of DMRS ports corresponding to a first group layer, and a second TRP 405 may use a second (different) QCL relationship or a second (different) TCI state for a second (different) group of DMRS ports corresponding to a second (different) group layer. In some aspects, the TCI state in the DCI (e.g., transmitted on the PDCCH, such as DCI format 1_0 or DCI format 1_1) may indicate a first QCL relationship (e.g., by indicating a first TCI state) and a second QCL relationship (e.g., by indicating a second TCI state). The first TCI state and the second TCI state may be indicated using a TCI field in the DCI. Generally, in this multi-TRP transmission mode (e.g., mode 1), the TCI field may indicate a single TCI state (for single TRP transmission) or multiple TCI states (for multi-TRP transmission as discussed herein).

[0092] In the second multi-TRP transmission mode (e.g., mode 2), multiple PDCCHs can be used to schedule downlink data communication for multiple corresponding PDSCHs (e.g., one PDCCH per PDSCH). In this case, the first PDCCH can be scheduled to transmit a first codeword by the first TRP 405, and the second PDCCH can be scheduled to transmit a second codeword by the second TRP 405. Furthermore, the first DCI (e.g., transmitted by the first TRP 405) can be scheduled to communicate with the first PDSCH associated with a first set of DMRS ports having a first QCL relationship (e.g., indicated by a first TCI state) for the first TRP 405, and the second DCI (e.g., transmitted by the second TRP 405) can be scheduled to communicate with the second PDSCH associated with a second set of DMRS ports having a second QCL relationship (e.g., indicated by a second TCI state) for the second TRP 405. In this case, the DCI (e.g., having DCI format 1_0 or DCI format 1_1) can indicate the corresponding TCI state for TRP 405. The TCI field of a DCI indicates the corresponding TCI state (for example, the TCI field of a first DCI indicates a first TCI state and the TCI field of a second DCI indicates a second TCI state).

[0093] Each communication in an mTRP configuration can be a spatial layer of a joint communication associated with a PDSCH. Joint communication is communication involving more than one signal sharing one or more time resources. Each TRP can be located at a different location than each other TRP, and therefore, each corresponding communication can be associated with one or more different corresponding spatial resources. Thus, each corresponding communication can be a spatial layer of a joint communication. A spatial layer of a joint communication is a portion of a joint communication corresponding to a set of spatial resources. For example, a joint communication may include a first spatial layer corresponding to a first set of spatial resources and a second spatial layer corresponding to a second set of spatial resources.

[0094] To receive joint communications from multiple TRPs, a single wide beam corresponding to a single TCI state can be used. However, a single wide beam can lead to the application of a single spatial filter for all layers of the joint communications, which may not be coherent (e.g., the layers of the joint communications may not have corresponding phases, making it possible for these layers to be constructively combined at the receiving device). Spatial filters are mechanisms (e.g., processes, procedures, circuits, and / or software, etc.) used to guide electromagnetic signals into a specific path. In some cases, coherent joint transmission (CJT) configurations can be used in coherent joint communications to facilitate more efficient application of spatial filters, potentially resulting in less signal loss and higher spectral efficiency.

[0095] Once a network node and a UE have selected beams for one or more beam pairs, the network node is aware of the one or more UE beams used by the UE. However, the UE may autonomously switch its receive beams (e.g., the UE beams within a beam pair) based at least in part on changing reception conditions. If the UE autonomously switches its receive beams (e.g., based at least in part on UE mobility, UE rotation, etc.), the network node may not be aware that the UE has switched receive beams before subsequent CSF reports and / or subsequent beam reports. Based at least in part on the network node's lack of awareness that the UE has switched receive beams, the network node may use outdated CSIs, which could degrade the performance of the communication link between the network node and the UE. For example, based at least in part on the network node using outdated CSIs, the UE may utilize increased error rates and / or suboptimal spectral efficiency, etc., to receive downlink communication, which could consume communication and network resources.

[0096] In some aspects described herein, the UE may determine changes in one or more reception conditions and may (e.g., autonomously) send beam management request communications comprising multiple beam management requests, each beam management request corresponding to a TRP among multiple TRPs, for beam management operations to update at least one beam associated with at least one of the multiple TRPs communicating with the UE. In some aspects, changes in one or more reception conditions may include, or may be at least partially based on, changes in the UE's transmitted beam and / or received beam, changes in link quality (e.g., changes in RSRP, SINR, path loss, etc.), UE movement, changes in UE speed, changes in UE orientation, changes in detected reflectors and / or scattering (e.g., changes in the angle and / or intensity of the received signal), etc.

[0097] In some respects, the UE may transmit beam management request communications via one or more MAC CEs and / or via UCI communications. In some respects, the UE may use existing permissions to transmit beam management request communications, request new permissions to transmit beam management request communications, and / or transmit beam management request communications together with other UCIs (e.g., HARQ feedback).

[0098] Based at least in part on receiving a request for radio link adaptation operation, a network node (which may be, include, or be included in one or more TRPs among a plurality of TRPs) may schedule the UE to receive one or more reference signals and / or report measurements and / or metrics associated with one or more reference signals. This facilitates beam synchronization between the TRP and the UE and allows the TRP to receive the current CSI to determine downlink transmission parameters. Based at least in part on the TRP receiving the current CSI to determine downlink transmission parameters, the TRP (e.g., via the network node) may determine appropriate transmission parameters (e.g., MCS, transport block size, resource allocation, transmit power, beam direction, etc.) for downlink communication, which can conserve communication, network, and / or power resources associated with the UE and / or the TRP.

[0099] As indicated above, Figure 4 This is provided as an example. Other examples are available with reference to [the relevant information]. Figure 4 The examples described are different.

[0100] Figure 5 This is a diagram illustrating example 500 associated with a beam management request initiated by a UE related to mTRP according to this disclosure. Figure 5 As shown, UE 502 and network node 504 can communicate with each other. In some aspects, UE 502 can be, similar to, or include... Figures 1 to 4 The UE 120 depicted, or included in that UE. In some respects, network node 504 may be, similar to, or include. Figure 1 , Figure 2 and Figure 4 The network node 110 and / or Figure 3 One or more components of the depicted decomposed base station architecture 300, or included in the network node and / or the one or more components. Network node 504 may be or include multiple TRPs.

[0101] As indicated by reference numeral 506, network node 504 may send configuration information, and UE 502 may receive configuration information. In some aspects, the configuration information may be carried in one or more RRC messages. The configuration information may be associated with reporting CSIs associated with multiple TRPs. In some aspects, the configuration information may include at least one of an RSRP threshold or a SINR threshold for determining changes in reception conditions. In some aspects, one or more of the RSRP threshold and SINR threshold may be specified in the wireless communication standard and thus maintained in the UE's memory. In some aspects, the configuration information may indicate at least one CC and / or at least one CC group associated with TCI, CSI report configuration, and / or beam management requests, etc.

[0102] As indicated by reference numeral 508, network node 504 may transmit a first set of reference signals, and UE 502 may receive the first set of reference signals. As indicated by reference numeral 510, UE 502 may determine a change in one or more reception conditions. For example, in some aspects, the change may include the RSRP associated with the QCL reference signal corresponding to the TCI satisfying an RSRP threshold. In some aspects, the change may include the SINR associated with the QCL reference signal corresponding to the TCI satisfying a SINR threshold.

[0103] As shown by reference numeral 512, UE 502 may send beam management request communications, and network node 504 may receive such beam management request communications. In some aspects, the beam management request communications may include multiple beam management requests. Each of the multiple beam management requests may correspond to a corresponding TRP among a plurality of TRPs. In some aspects, the beam management request communications may indicate a change in one or more reception conditions associated with one or more of the multiple TRPs. In some aspects, the change in one or more reception conditions may include at least one of the following: an RSRP that satisfies an RSRP threshold associated with a QCL reference signal corresponding to a TCI, or an SINR that satisfies a SINR threshold associated with a QCL reference signal corresponding to a TCI.

[0104] In some aspects, UE 502 may transmit beam management request communication based on transmitting a UCI that includes multiple beam management requests. In some aspects, the UCI includes a HARQ codebook, and the multiple beam management requests may include multiple bits appended to the HARQ codebook. In some aspects, transmitting beam management request communication may include transmitting beam management request communication based on the UCI including the HARQ codebook. In some aspects, the multiple beam management requests may correspond to at least one corresponding TCI, and transmitting beam management request communication may include transmitting beam management request communication based on at least one TCI being applied to the physical downlink shared channel in the HARQ codebook.

[0105] In some aspects, UCI can be scheduled to be multiplexed with additional UCI. For example, additional UCI may include at least one of HARQ codebook, scheduling request, CSI Part 1 communication, or CSI Part 2 communication. The UCI priority associated with beam management request communication may be equal to the priority associated with HARQ codebook and the priority associated with scheduling request. In some aspects, the UCI priority associated with beam management request communication may be equal to the priority associated with CSI Part 1 communication, lower than the priority associated with HARQ codebook, and lower than the priority associated with scheduling request.

[0106] In some aspects, the UCI priority associated with beam management request communication may be equal to the priority associated with CSI Part 2 communication and lower than the priority associated with CSI Part 1 communication. In some aspects, the UCI priority associated with beam management request communication may be lower than the priority associated with CSI Part 2 communication. In some aspects, UE 502 may transmit beam management request communication based on transmitting a MAC CE that includes multiple beam management requests. In some aspects, the beam management request among the multiple beam management requests may be associated with at least one of a corresponding CC or a corresponding CC group.

[0107] In some aspects, each of the multiple beam management requests may include only one bit corresponding to the corresponding TRP. Each of the multiple beam management requests may include a set of bits corresponding to the corresponding TRP, and the number of bits in that set may be based on a bit number condition. In some aspects, each of the multiple beam management requests may include a set of bits corresponding to the corresponding TRP, and UE 502 may receive an indication of the number of bits in that set.

[0108] As shown by reference numeral 514, UE 502 and network node 504 can perform beam management operations. Beam management operations can be performed based on beam management request communications. UE 502 and network node 504 can perform beam management operations associated with at least one of a plurality of TRPs.

[0109] As indicated above, Figure 5 This is provided as an example. Other examples are available with reference to [the relevant information]. Figure 5 The examples described are different.

[0110] Figure 6 This is a diagram illustrating an example procedure 600 performed by a UE according to this disclosure. Example procedure 600 is an example in which a UE (e.g., UE 502) performs operations associated with beam management requests initiated by a UE and associated with multiple TRPs.

[0111] like Figure 6 As shown, in some aspects, process 600 may include sending beam management request communication comprising a plurality of beam management requests, each of the plurality of beam management requests corresponding to a corresponding TRP among a plurality of TRPs (box 610). For example, a UE (e.g., using...) Figure 8 The transmitting component 804 and / or communication manager 806 depicted herein can transmit beam management request communications that include a plurality of beam management requests, each of which corresponds to a corresponding TRP among a plurality of TRPs, as described above.

[0112] like Figure 6 As further shown, in some aspects, process 600 may include performing beam management operations associated with at least one of a plurality of TRPs based on beam management request communication (box 620). For example, the UE (e.g., using...) Figure 8 The communication manager 806 described above can perform beam management operations associated with at least one of a plurality of TRPs based on beam management request communications.

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

[0114] In a first aspect, the beam management request communication indicates a change in one or more reception conditions associated with one or more of a plurality of TRPs. In a second aspect, alone or in combination with the first aspect, the change in one or more reception conditions includes at least one of the following: an RSRP that satisfies an RSRP threshold associated with a QCL reference signal corresponding to a TCI, or an SINR that satisfies a SINR threshold associated with a QCL reference signal corresponding to a TCI. In a third aspect, alone or in combination with the second aspect, process 600 includes receiving an RRC message indicating at least one of the RSRP threshold or the SINR threshold. In a fourth aspect, alone or in combination with one or more of the second to third aspects, the UE's memory includes an indication of at least one of the RSRP threshold or the SINR threshold.

[0115] In a fifth aspect, individually or in combination with one or more of the first to fourth aspects, transmitting beam management request communication includes transmitting a UCI comprising multiple beam management requests. In a sixth aspect, individually or in combination with the fifth aspect, the UCI comprises a HARQ codebook, and wherein the multiple beam management requests comprise multiple bits appended to the HARQ codebook. In a seventh aspect, individually or in combination with the sixth aspect, transmitting beam management request communication includes transmitting beam management request communication based on the UCI comprising a HARQ codebook. In an eighth aspect, individually or in combination with one or more of the sixth to seventh aspects, the multiple beam management requests correspond to at least one corresponding TCI, and wherein transmitting beam management request communication includes transmitting beam management request communication based on at least one TCI being applied to a physical downlink shared channel in the HARQ codebook.

[0116] In the ninth aspect, either alone or in combination with one or more of the fifth to eighth aspects, the UCI is scheduled to be multiplexed with an additional UCI. In the tenth aspect, either alone or in combination with the ninth aspect, the additional UCI may include at least one of a HARQ codebook, a scheduling request, CSI Part 1 communication, or CSI Part 2 communication. In the eleventh aspect, either alone or in combination with the tenth aspect, the UCI priority associated with the beam management request communication is equal to the priority associated with the HARQ codebook and the priority associated with the scheduling request. In the twelfth aspect, either alone or in combination with the tenth aspect, the UCI priority associated with the beam management request communication is equal to the priority associated with CSI Part 1 communication, lower than the priority associated with the HARQ codebook, and lower than the priority associated with the scheduling request. In the thirteenth aspect, either alone or in combination with the tenth aspect, the UCI priority associated with the beam management request communication is equal to the priority associated with CSI Part 2 communication and lower than the priority associated with CSI Part 1 communication. In the fourteenth aspect, either alone or in conjunction with the tenth aspect, the UCI priority associated with beam management request communications is lower than the priority associated with communications associated with CSI Part 2.

[0117] In the fifteenth aspect, individually or in combination with one or more of the first to fourth aspects, transmitting beam management request communication includes transmitting a MAC control element (MAC CE) including multiple beam management requests. In the sixteenth aspect, individually or in combination with one or more of the first to fifteenth aspects, a beam management request among the multiple beam management requests is associated with at least one of a corresponding CC or a corresponding CC group. In the seventeenth aspect, individually or in combination with the sixteenth aspect, process 600 includes receiving configuration information indicating at least one of the corresponding CC or a corresponding CC group. In the eighteenth aspect, individually or in combination with one or more of the sixteenth to seventeenth aspects, at least one of the corresponding CC or a corresponding CC group is associated with a TCI associated with the beam management request.

[0118] In the nineteenth aspect, individually or in combination with one or more of the first to eighteenth aspects, each of the plurality of beam management requests includes only one bit corresponding to the corresponding TRP. In the twentieth aspect, individually or in combination with one or more of the first to eighteenth aspects, each of the plurality of beam management requests includes a set of bits corresponding to the corresponding TRP, wherein the number of bits in the set of bits is based on a bit number condition. In the twenty-first aspect, individually or in combination with one or more of the first to eighteenth aspects, each of the plurality of beam management requests includes a set of bits corresponding to the corresponding TRP, the method further comprising receiving an indication of the number of bits in that set of bits.

[0119] although Figure 6 An example box of process 600 is shown, but in some respects, process 600 may include... Figure 6 The boxes depicted in the diagram may be fewer, different, or arranged differently than additional boxes. Alternatively, two or more boxes in the process 600 may be executed in parallel.

[0120] Figure 7 This is a diagram illustrating an example procedure 700 performed by a network node, for example, according to this disclosure. Example procedure 700 is an example in which a network node (e.g., network node 504) performs operations associated with beam management requests initiated by UEs associated with multiple TRPs.

[0121] like Figure 7 As shown, in some aspects, process 700 may include receiving beam management request communication comprising a plurality of beam management requests, each of the plurality of beam management requests corresponding to a corresponding TRP among a plurality of TRPs (box 710). For example, a network node (e.g., using...) Figure 9 The receiving component 902 and / or communication manager 906 depicted herein can receive beam management request communications that include a plurality of beam management requests, each of which corresponds to a corresponding TRP among a plurality of TRPs, as described above.

[0122] like Figure 7 As further shown, in some aspects, process 700 may include performing beam management operations associated with at least one of a plurality of TRPs based on beam management request communication (box 720). For example, a network node (e.g., using...) Figure 9 The communication manager 906 depicted above can perform beam management operations associated with at least one of a plurality of TRPs based on beam management request communications.

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

[0124] In a first aspect, beam management request communication indicates a change in one or more reception conditions associated with one or more of a plurality of TRPs. In a second aspect, alone or in combination with the first aspect, the change in one or more reception conditions includes at least one of the following: an RSRP that satisfies an RSRP threshold associated with a QCL reference signal corresponding to a TCI, or an SINR that satisfies a SINR threshold associated with a QCL reference signal corresponding to a TCI. In a third aspect, alone or in combination with the second aspect, process 700 includes sending an RRC message indicating at least one of the RSRP threshold or SINR threshold. In a fourth aspect, alone or in combination with one or more of the first to third aspects, receiving beam management request communication includes receiving a UCI including a plurality of beam management requests. In a fifth aspect, alone or in combination with the fourth aspect, the UCI includes a HARQ codebook, and wherein the plurality of beam management requests includes a plurality of bits appended to the HARQ codebook. In a sixth aspect, alone or in combination with the fifth aspect, receiving beam management request communication includes receiving beam management request communication based on a HARQ codebook included in the UCI.

[0125] In the seventh aspect, individually or in combination with one or more of the fifth to sixth aspects, multiple beam management requests correspond to at least one corresponding TCI, and wherein receiving beam management request communications includes receiving beam management request communications based on a physical downlink shared channel applied to the HARQ codebook by at least one TCI. In the eighth aspect, individually or in combination with one or more of the first to seventh aspects, a UCI is scheduled to be multiplexed with an additional UCI.

[0126] In the ninth aspect, either alone or in conjunction with the eighth aspect, the additional UCI includes at least one of the HARQ codebook, scheduling request, CSI Part 1 communication, or CSI Part 2 communication. In the tenth aspect, either alone or in conjunction with the ninth aspect, the UCI priority associated with the beam management request communication is equal to the priority associated with the HARQ codebook and the priority associated with the scheduling request. In the eleventh aspect, either alone or in conjunction with the ninth aspect, the UCI priority associated with the beam management request communication is equal to the priority associated with CSI Part 1 communication, lower than the priority associated with the HARQ codebook, and lower than the priority associated with the scheduling request. In the twelfth aspect, either alone or in conjunction with the ninth aspect, the UCI priority associated with the beam management request communication is equal to the priority associated with CSI Part 2 communication and lower than the priority associated with CSI Part 1 communication. In the thirteenth aspect, either alone or in conjunction with the ninth aspect, the UCI priority associated with the beam management request communication is lower than the priority associated with CSI Part 2 communication.

[0127] In the fourteenth aspect, receiving beam management request communication, either alone or in combination with one or more of the first to thirteenth aspects, includes receiving a MAC CE comprising multiple beam management requests. In the fifteenth aspect, either alone or in combination with one or more of the first to fourteenth aspects, a beam management request among the multiple beam management requests is associated with at least one of a corresponding CC or a corresponding CC group. In the sixteenth aspect, either alone or in combination with the fifteenth aspect, process 700 includes sending configuration information indicating at least one of the corresponding CC or a corresponding CC group. In the seventeenth aspect, either alone or in combination with one or more of the fifteenth to sixteenth aspects, at least one of the corresponding CC or a corresponding CC group is associated with a TCI associated with the beam management request.

[0128] In the eighteenth aspect, individually or in combination with one or more of the first to seventeenth aspects, each of the plurality of beam management requests includes only one bit corresponding to the corresponding TRP. In the nineteenth aspect, individually or in combination with one or more of the first to eighteenth aspects, each of the plurality of beam management requests includes a set of bits corresponding to the corresponding TRP, wherein the number of bits in the set of bits is based on a bit number condition. In the twentieth aspect, individually or in combination with one or more of the first to nineteenth aspects, each of the plurality of beam management requests includes a set of bits corresponding to the corresponding TRP, the method further including receiving an indication of the number of bits in that set of bits.

[0129] although Figure 7 An example box of process 700 is shown, but in some respects, process 700 may include... Figure 7 The boxes depicted in the diagram may be fewer, different, or arranged differently than additional boxes, boxes, or boxes in a different manner. Alternatively, two or more boxes in the process 700 may be executed in parallel.

[0130] Figure 8 This is a diagram illustrating an example device 800 for wireless communication according to the present disclosure. Device 800 may be a UE, or a UE may include device 800. In some aspects, device 800 includes a receiving component 802, a transmitting component 804, and / or a communication manager 806 that can communicate with each other (e.g., via one or more buses and / or one or more other components). In some aspects, the communication manager 806 is combined with... Figure 1 The described communication manager 140. As shown, device 800 can communicate with another device 808 (such as a UE or a network node (such as a CU, DU, RU or base station)) using receiving component 802 and transmitting component 804.

[0131] In some respects, device 800 can be configured to perform the functions described herein. Figure 5 One or more operations described herein. Additionally or alternatively, the apparatus 800 may be configured to perform one or more processes described herein, such as Figure 6 The process is 600. In some respects, Figure 8 The illustrated device 800 and / or one or more components may include a combination Figure 2 One or more components of the described UE. Additionally or alternatively, Figure 8 One or more components shown can be combined Figure 2 Implementation within one or more of the described components. Additionally or alternatively, one or more of the components in a set of components may be implemented at least partially as software stored in 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 function or operation of the component.

[0132] Receiver 802 may receive communications from device 808, such as reference signals, control information, data communications, or combinations thereof. Receiver 802 may provide the received communications to one or more other components of device 800. In some aspects, receiver 802 may perform signal processing on the received communications (such as filtering, amplification, demodulation, analog-to-digital conversion, demultiplexing, deinterleaving, demapping, equalization, interference cancellation, or decoding, etc.) and may provide the processed signals to one or more other components of device 800. In some aspects, receiver 802 may include combinations of... Figure 2 The described UE includes one or more antennas, modems, demodulators, MIMO detectors, receiver processors, controllers / processors, memory, or combinations thereof.

[0133] Transmitting component 804 can transmit communications, such as reference signals, control information, data communications, or combinations thereof, to device 808. In some aspects, one or more other components of device 800 can generate communications and provide the generated communications to transmitting component 804 for transmission to device 808. In some aspects, transmitting component 804 can perform signal processing (such as filtering, amplification, modulation, digital-to-analog conversion, multiplexing, interleaving, mapping, or encoding, etc.) on the generated communications and can transmit the processed signals to device 808. In some aspects, transmitting component 804 may include combinations of... Figure 2 The described UE includes one or more antennas, modems, modulators, transmit MIMO processors, transmit processors, controllers / processors, memory, or combinations thereof. In some aspects, the transmit component 804 may be co-located with the receive component 802 in a transceiver.

[0134] The communication manager 806 may support the operation of the receiving component 802 and / or the transmitting component 804. For example, the communication manager 806 may receive information associated with configuring the reception of communications by the receiving component 802 and / or the transmission of communications by the transmitting component 804. Additionally or alternatively, the communication manager 806 may generate control information and / or provide control information to the receiving component 802 and / or the transmitting component 804 to control the reception and / or transmission of communications.

[0135] Transmitting component 804 can transmit beam management request communications including multiple beam management requests, each beam management request corresponding to a corresponding TRP among a plurality of TRPs. Communication manager 806 can perform beam management operations associated with at least one of the plurality of TRPs based on the beam management request communications. Receiving component 802 can receive an RRC message indicating at least one of an RSRP threshold or a SINR threshold. Receiving component 802 can receive configuration information indicating at least one of a corresponding CC or a corresponding CC group.

[0136] Figure 8 The number and arrangement of components shown are provided as an example. In reality, they can exist in... Figure 8 The components shown are compared to additional components, fewer components, different components, or components arranged in a different manner. Furthermore, Figure 8 The two or more components shown can be implemented within a single component, or Figure 8 The single component shown can be implemented as multiple distributed components. Additionally or alternatively, Figure 8 The set (one or more) components shown are executable and described as being composed of Figure 8 The other set of components shown performs one or more functions.

[0137] Figure 9 This is a diagram of an example device 900 for wireless communication according to the present disclosure. Device 900 may be a network node, or a network node may include device 900. In some aspects, device 900 includes a receiving component 902, a transmitting component 904, and / or a communication manager 906 that can communicate with each other (e.g., via one or more buses and / or one or more other components). In some aspects, the communication manager 906 is combined with... Figure 1 The described communication manager 150. As shown, device 900 can communicate with another device 908 (such as a UE or a network node (such as a CU, DU, RU or base station)) using receiving component 902 and transmitting component 904.

[0138] In some respects, device 900 can be configured to perform the functions described herein. Figure 5One or more operations described herein. Additionally or alternatively, device 900 may be configured to perform one or more processes described herein, such as Figure 7 The process is 700. In some respects, Figure 9 The illustrated device 900 and / or one or more components may include a combination Figure 2 One or more components of the described network node. Additionally or alternatively, Figure 9 One or more components shown can be combined Figure 2 Implementation within one or more of the described components. Additionally or alternatively, one or more of the components in a set of components may be implemented at least partially as software stored in 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 function or operation of the component.

[0139] Receiver 902 may receive communications from device 908, such as reference signals, control information, data communications, or combinations thereof. Receiver 902 may provide the received communications to one or more other components of device 900. In some aspects, receiver 902 may perform signal processing on the received communications (such as filtering, amplification, demodulation, analog-to-digital conversion, demultiplexing, deinterleaving, demapping, equalization, interference cancellation, or decoding, etc.) and may provide the processed signals to one or more other components of device 900. In some aspects, receiver 902 may include combinations of... Figure 2 The described network node includes one or more antennas, modems, demodulators, MIMO detectors, receiver processors, controllers / processors, memory, or combinations thereof. In some aspects, receiver component 902 and / or transmitter component 904 may include or be included in a network interface. The network interface may be configured to acquire and / or output signals for device 900 via one or more communication links, such as backhaul links, midhaul links, and / or fronthaul links.

[0140] Transmitting component 904 can transmit communications, such as reference signals, control information, data communications, or combinations thereof, to device 908. In some aspects, one or more other components of device 900 can generate communications and provide the generated communications to transmitting component 904 for transmission to device 908. In some aspects, transmitting component 904 can perform signal processing (such as filtering, amplification, modulation, digital-to-analog conversion, multiplexing, interleaving, mapping, or encoding, etc.) on the generated communications and can transmit the processed signals to device 908. In some aspects, transmitting component 904 may include combinations of... Figure 2The described network node includes one or more antennas, modems, modulators, transmit MIMO processors, transmit processors, controllers / processors, memory, or combinations thereof. In some aspects, the transmit component 904 may be co-located with the receive component 902 in a transceiver.

[0141] The communication manager 906 may support the operation of the receiving component 902 and / or the transmitting component 904. For example, the communication manager 906 may receive information associated with configuring the reception of communications by the receiving component 902 and / or the transmission of communications by the transmitting component 904. Additionally or alternatively, the communication manager 906 may generate control information and / or provide control information to the receiving component 902 and / or the transmitting component 904 to control the reception and / or transmission of communications.

[0142] The receiving component 902 can receive beam management request communications including multiple beam management requests, each beam management request corresponding to a corresponding TRP among a plurality of TRPs. The communication manager 906 can perform beam management operations associated with at least one of the multiple TRPs based on the beam management request communications. The transmitting component 904 can transmit an RRC message indicating at least one of an RSRP threshold or a SINR threshold. The transmitting component 904 can also transmit configuration information indicating at least one of a corresponding CC or a corresponding CC group.

[0143] Figure 9 The number and arrangement of components shown are provided as an example. In reality, they can exist in... Figure 9 The components shown are compared to additional components, fewer components, different components, or components arranged in a different manner. Furthermore, Figure 9 The two or more components shown can be implemented within a single component, or Figure 9 The single component shown can be implemented as multiple distributed components. Additionally or alternatively, Figure 9 The set (one or more) components shown are executable and described as being composed of Figure 9 The other set of components shown performs one or more functions.

[0144] The following provides an overview of some aspects of this disclosure:

[0145] Aspect 1: A method of wireless communication performed by a user equipment (UE), the method comprising: transmitting a beam management request communication including a plurality of beam management requests, each of the plurality of beam management requests corresponding to a corresponding TRP among a plurality of transmit-receive points (TRPs); and performing a beam management operation associated with at least one of the plurality of TRPs based on the beam management request communication.

[0146] Aspect 2: According to the method of aspect 1, wherein the beam management request communication indicates a change in one or more reception conditions associated with one or more of the plurality of TRPs.

[0147] Aspect 3: According to the method of aspect 2, the change of the one or more reception conditions includes at least one of the following: an RSRP that satisfies a reference signal received power (RSRP) threshold associated with a quasi-co-address (QCL) reference signal corresponding to a transmit configuration indicator (TCI), or an SINR that satisfies a signal-to-interference-plus-noise ratio (SINR) threshold associated with the QCL reference signal corresponding to the TCI.

[0148] Aspect 4: According to the method of aspect 3, the method further includes receiving a radio resource control (RRC) message indicating at least one of the RSRP threshold or the SINR threshold.

[0149] Aspect 5: The method according to any one of Aspect 3 or 4, wherein the memory of the UE includes an indication of at least one of the RSRP threshold or the SINR threshold.

[0150] Aspect 6: The method according to any one of Aspects 1 to 5, wherein sending the beam management request communication includes sending uplink control information (UCI) including the plurality of beam management requests.

[0151] Aspect 7: According to the method of aspect 6, wherein the UCI includes a Hybrid Automatic Repeat Request (HARQ) codebook, and wherein the plurality of beam management requests include a plurality of bits appended to the HARQ codebook.

[0152] Aspect 8: According to the method of aspect 7, sending the beam management request communication includes sending the beam management request communication based on the UCI including the HARQ codebook.

[0153] Aspect 9: The method according to any one of Aspects 7 or 8, wherein the plurality of beam management requests correspond to at least one corresponding transmit configuration indicator (TCI), and wherein transmitting the beam management request communication includes transmitting the beam management request communication based on the at least one TCI being applied to the physical downlink shared channel in the HARQ codebook.

[0154] Aspect 10: The method according to any one of Aspects 6 to 9, wherein the UCI is scheduled to be multiplexed with an additional UCI.

[0155] Aspect 11: According to the method of aspect 10, the additional UCI includes at least one of a Hybrid Automatic Repeat Request (HARQ) codebook, a scheduling request, Channel State Information (CSI) Part 1 communication, or CSI Part 2 communication.

[0156] Aspect 12: According to the method of aspect 11, wherein the UCI priority associated with the beam management request communication is equal to the priority associated with the HARQ codebook and the priority associated with the scheduling request.

[0157] Aspect 13: According to the method of aspect 11, the UCI priority associated with the beam management request communication is equal to the priority associated with the CSI part 1 communication, lower than the priority associated with the HARQ codebook, and lower than the priority associated with the scheduling request.

[0158] Aspect 14: According to the method of aspect 11, wherein the UCI priority associated with the beam management request communication is equal to the priority associated with the CSI section 2 communication and is lower than the priority associated with the CSI section 1 communication.

[0159] Aspect 15: According to the method of aspect 11, wherein the UCI priority associated with the beam management request communication is lower than the priority associated with the CSI part 2 communication.

[0160] Aspect 16: The method according to any one of Aspects 1 to 5, wherein sending the beam management request communication includes sending a Media Access Control (MAC) control element (MAC CE) including the plurality of beam management requests.

[0161] Aspect 17: The method according to any one of Aspects 1 to 16, wherein the beam management request of the plurality of beam management requests is associated with at least one of the corresponding component carriers (CCs) or the corresponding CC groups.

[0162] Aspect 18: The method according to aspect 17, the method further comprising receiving configuration information indicating the corresponding CC or at least one of the corresponding CC groups.

[0163] Aspect 19: The method of any one of claim 17 or 18, wherein the corresponding CC or at least one of the corresponding CC groups is associated with a transmit configuration indicator (TCI) associated with the beam management request.

[0164] Aspect 20: The method according to any one of aspects 1 to 19, wherein each of the plurality of beam management requests includes only one bit corresponding to the respective TRP.

[0165] Aspect 21: The method according to any one of aspects 1 to 19, wherein each of the plurality of beam management requests includes a set of bits corresponding to the respective TRP, and wherein the number of bits in the set of bits is based on a bit number condition.

[0166] Aspect 22: The method according to any one of aspects 1 to 19, wherein each of the plurality of beam management requests includes a set of bits corresponding to the respective TRP, the method further comprising receiving an indication of the number of bits in the set of bits.

[0167] Aspect 23: A method of wireless communication performed by a network node, the method comprising receiving a beam management request communication including a plurality of beam management requests, each of the plurality of beam management requests corresponding to a corresponding TRP among a plurality of transmit-receive points (TRPs); and performing a beam management operation associated with at least one of the plurality of TRPs based on the beam management request communication.

[0168] Aspect 24: The method according to aspect 23, wherein the beam management request communication indicates a change in one or more reception conditions associated with one or more of the plurality of TRPs.

[0169] Aspect 25: According to the method of aspect 24, the change of said one or more reception conditions includes at least one of the following: an RSRP that satisfies a reference signal received power (RSRP) threshold associated with a quasi-co-address (QCL) reference signal corresponding to a transmit configuration indicator (TCI), or an SINR that satisfies a signal-to-interference-plus-noise ratio (SINR) threshold associated with the QCL reference signal corresponding to said TCI.

[0170] Aspect 26: The method according to aspect 25 further includes sending the Radio Resource Control (RRC) message indicating at least one of the RSRP threshold or the SINR threshold.

[0171] Aspect 27: The method according to any one of Aspects 23 to 26, wherein receiving the beam management request communication includes receiving uplink control information (UCI) including the beam management request.

[0172] Aspect 28: According to the method of aspect 27, wherein the UCI includes a Hybrid Automatic Repeat Request (HARQ) codebook, and wherein the plurality of beam management requests include a plurality of bits appended to the HARQ codebook.

[0173] Aspect 29: The method according to aspect 28, wherein receiving the beam management request communication includes receiving the beam management request communication based on the UCI including the HARQ codebook.

[0174] Aspect 30: The method according to any one of Aspects 28 or 29, wherein the plurality of beam management requests correspond to at least one corresponding transmit configuration indicator (TCI), and wherein receiving the beam management request communication comprises receiving the beam management request communication based on the at least one TCI being applied to the physical downlink shared channel in the HARQ codebook.

[0175] Aspect 31: The method according to any one of Aspects 27 to 30, wherein the UCI is scheduled to be multiplexed with an additional UCI.

[0176] Aspect 32: According to the method of aspect 31, the additional UCI includes at least one of a Hybrid Automatic Repeat Request (HARQ) codebook, a scheduling request, Channel State Information (CSI) Part 1 communication, or CSI Part 2 communication.

[0177] Aspect 33: According to the method of aspect 32, the UCI priority associated with the beam management request communication is equal to the priority associated with the HARQ codebook and the priority associated with the scheduling request.

[0178] Aspect 34: According to the method of aspect 32, the UCI priority associated with the beam management request communication is equal to the priority associated with the CSI part 1 communication, lower than the priority associated with the HARQ codebook, and lower than the priority associated with the scheduling request.

[0179] Aspect 35: According to the method of aspect 32, the UCI priority associated with the beam management request communication is equal to the priority associated with the CSI section 2 communication and lower than the priority associated with the CSI section 1 communication.

[0180] Aspect 36: According to the method of aspect 32, the UCI priority associated with the beam management request communication is lower than the priority associated with the CSI part 2 communication.

[0181] Aspect 37: The method according to any one of Aspects 23 to 26, wherein receiving the beam management request communication includes receiving a Media Access Control (MAC) control element (MAC CE) including the beam management request.

[0182] Aspect 38: The method according to any one of Aspects 23 to 37, wherein the beam management request of the plurality of beam management requests is associated with at least one of the corresponding component carriers (CCs) or the corresponding CC groups.

[0183] Aspect 39: According to the method of aspect 38, the method further includes sending configuration information indicating the corresponding CC or the at least one of the corresponding CC groups.

[0184] Aspect 40: The method of any one of claim 38 or 39, wherein the corresponding CC or at least one of the corresponding CC groups is associated with a transmit configuration indicator (TCI) associated with the beam management request.

[0185] Aspect 41: The method according to any one of Aspects 23 to 40, wherein each of the plurality of beam management requests includes only one bit corresponding to the respective TRP.

[0186] Aspect 42: The method according to any one of aspects 23 to 40, wherein each of the plurality of beam management requests includes a set of bits corresponding to the respective TRP, and wherein the number of bits in the set of bits is based on a bit number condition.

[0187] Aspect 43: The method according to any one of aspects 23 to 40, wherein each of the plurality of beam management requests includes a set of bits corresponding to the respective TRP, the method further comprising: receiving an indication of the number of bits in the set of bits.

[0188] Aspect 44: 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 22.

[0189] Aspect 45: 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 perform the method according to one or more of aspects 1 to 22.

[0190] Aspect 46: 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 22.

[0191] Aspect 47: A non-transitory computer-readable medium storing code for wireless communication, said code including instructions executable by a processor to perform the methods described in one or more of aspects 1 to 22.

[0192] Aspect 48: A non-transitory computer-readable medium storing a set of instructions for wireless communication, the set of instructions 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 22.

[0193] Aspect 49: 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 23 to 43.

[0194] Aspect 50: 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 perform the method according to one or more of aspects 23 to 43.

[0195] Aspect 51: An apparatus for wireless communication, the apparatus comprising at least one component for performing the method according to one or more of aspects 23 to 43.

[0196] Aspect 52: A non-transitory computer-readable medium storing code for wireless communication, said code including instructions executable by a processor to perform the methods according to one or more of aspects 23 to 43.

[0197] Aspect 53: A non-transitory computer-readable medium storing a set of instructions for wireless communication, the set of instructions 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 23 to 43.

[0198] While the foregoing disclosure provides examples and descriptions, it is not intended to be exhaustive or to limit aspects to the precise forms disclosed. Modifications and variations can be made based on the foregoing disclosure, or from various aspects of practice.

[0199] As used herein, the term "component" is intended to be interpreted broadly as hardware and / or a combination of hardware and software. Whether referred to as software, firmware, middleware, microcode, hardware description language, or other names, "software" should be interpreted broadly as meaning instructions, instruction sets, code, code segments, program code, programs, subroutines, software modules, applications, software applications, software packages, routines, subroutines, objects, executable files, threads of execution, procedures, and / or functions, etc. As used herein, a "processor" is implemented in hardware and / or a combination of hardware and software. It will be apparent to those skilled in the art that the systems and / or methods described herein can be implemented in various forms of hardware and / or combinations of hardware and software. The actual dedicated control hardware or software code used to implement these systems and / or methods is not limiting in any way. Therefore, no specific software code is referenced herein to describe the operation and behavior of the systems and / or methods, as those skilled in the art will understand that the software and hardware can be designed, at least in part, based on the descriptions herein, to implement the systems and / or methods.

[0200] As used in this article, depending on the context, "meeting the threshold" can mean 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.

[0201] Although specific combinations of features are set forth in the claims and / or disclosed in the specification, these combinations are not intended to limit the disclosure of various aspects. Many of these features may be combined in ways not specifically set forth in the claims and / or not disclosed in the specification. The disclosure of various aspects includes each dependent claim in combination with each other claim in the claim set. As used herein, the phrase referring to “at least one of” in the list of entries means any combination of these entries, including a single member. As an 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).

[0202] No element, action, or instruction used herein should be construed as essential or necessary unless explicitly stated otherwise. Furthermore, as used herein, the articles “a” and “an” are intended to include one or more items and are used interchangeably with “one or more.” Furthermore, as used herein, the article “described” is intended to include one or more items mentioned in connection with the article “described” and is used interchangeably with “one or more.” Furthermore, as used herein, the terms “set” and “group” are intended to include one or more items and are used interchangeably with “one or more.” If only one item is desired, the phrase “only one” or similar terminology will be used. Furthermore, as used herein, the terms “having” and the like are intended to be open-ended terms that do not limit the elements they modify (e.g., an element “having” A may also have B). Furthermore, the phrase “based on” is intended to mean “at least partially based on” unless otherwise explicitly stated. Furthermore, as used herein, the term “or” is intended to be open-ended when used in a series and is interchangeable with “and / or” unless otherwise explicitly stated (e.g., if used in conjunction with “any” or “only one”).

Claims

1. An apparatus for wireless communication at a user equipment (UE), the apparatus comprising: Memory; and One or more processors coupled to the memory, at least in part based on information stored in the memory, wherein the one or more processors are configured to: Sending beam management request communication including multiple beam management requests, each of the multiple beam management requests corresponding to a corresponding TRP in a plurality of transmit-receive points (TRPs); as well as The beam management request communication is used to perform beam management operations associated with at least one of the plurality of TRPs.

2. The apparatus of claim 1, wherein the beam management request communication indicates a change in one or more reception conditions associated with one or more of the plurality of TRPs.

3. The apparatus of claim 2, wherein the change in the one or more receiving conditions comprises at least one of the following: The RSRP that satisfies the Reference Signal Received Power (RSRP) threshold associated with the quasi-co-address (QCL) reference signal corresponding to the Transmit Configuration Indicator (TCI), or SINR that satisfies the signal-to-interference-plus-noise ratio (SINR) threshold, associated with the QCL reference signal corresponding to the TCI.

4. The apparatus of claim 3, wherein the one or more processors are further configured to receive a Radio Resource Control (RRC) message indicating at least one of the RSRP threshold or the SINR threshold.

5. The apparatus of claim 3, wherein the memory of the UE includes an indication of at least one of the RSRP threshold or the SINR threshold.

6. The apparatus of claim 1, wherein, in order to send the beam management request communication, the one or more processors are configured to send uplink control information (UCI) including the plurality of beam management requests.

7. The apparatus of claim 6, wherein the UCI includes a Hybrid Automatic Repeat Request (HARQ) codebook, and wherein the plurality of beam management requests include a plurality of bits appended to the HARQ codebook.

8. The apparatus of claim 7, wherein, in order to send the beam management request communication, the one or more processors are configured to send the beam management request communication based on the UCI including the HARQ codebook.

9. The apparatus of claim 7, wherein the plurality of beam management requests correspond to at least one corresponding transmit configuration indicator (TCI), and wherein, in order to transmit the beam management request communication, the one or more processors are configured to transmit the beam management request communication based on the physical downlink shared channel applied to the at least one TCI in the HARQ codebook.

10. The apparatus of claim 6, wherein the UCI is scheduled to be multiplexed with an additional UCI.

11. The apparatus of claim 10, wherein the additional UCI comprises at least one of a Hybrid Automatic Repeat Request (HARQ) codebook, a scheduling request, Channel State Information (CSI) Part 1 communication, or CSI Part 2 communication.

12. The apparatus of claim 11, wherein the UCI priority associated with the beam management request communication is equal to the priority associated with the HARQ codebook and the priority associated with the scheduling request.

13. The apparatus of claim 11, wherein the UCI priority associated with the beam management request communication is equal to the priority associated with the CSI Part 1 communication, lower than the priority associated with the HARQ codebook, and lower than the priority associated with the scheduling request.

14. The apparatus of claim 11, wherein the UCI priority associated with the beam management request communication is equal to the priority associated with the CSI section 2 communication and lower than the priority associated with the CSI section 1 communication.

15. The apparatus of claim 11, wherein the UCI priority associated with the beam management request communication is lower than the priority associated with the CSI part 2 communication.

16. The apparatus of claim 1, wherein, in order to send the beam management request communication, the one or more processors are configured to send a media access control (MAC) control element (MACCE) including the plurality of beam management requests.

17. The apparatus of claim 1, wherein the beam management request of the plurality of beam management requests is associated with at least one of a corresponding component carrier (CC) or a corresponding CC group.

18. The apparatus of claim 17, wherein the one or more processors are further configured to receive configuration information indicating the respective CC or at least one of the respective CC groups.

19. The apparatus of claim 17, wherein the corresponding CC or at least one of the corresponding CC groups is associated with a transmit configuration indicator (TCI) associated with the beam management request.

20. The apparatus of claim 1, wherein each of the plurality of beam management requests includes only one bit corresponding to the respective TRP.

21. The apparatus of claim 1, wherein each of the plurality of beam management requests includes a set of bits corresponding to the respective TRP, and wherein the number of bits in the set of bits is based on a bit number condition.

22. The apparatus of claim 1, wherein each of the plurality of beam management requests includes a set of bits corresponding to the respective TRP, and wherein the one or more processors are further configured to receive an indication of the number of bits in the set of bits.

23. An apparatus for wireless communication at a network node, the apparatus comprising: Memory; and One or more processors coupled to the memory, at least in part based on information stored in the memory, wherein the one or more processors are configured to: Receive beam management request communication including multiple beam management requests, each of the multiple beam management requests corresponding to a corresponding TRP in a plurality of transmit-receive points (TRPs); as well as The beam management request communication is used to perform beam management operations associated with at least one of the plurality of TRPs.

24. The apparatus of claim 23, wherein the beam management request communication indicates a change in one or more reception conditions associated with one or more of the plurality of TRPs.

25. The apparatus of claim 23, wherein, in order to receive the beam management request communication, the one or more processors are configured to receive uplink control information (UCI) including the plurality of beam management requests.

26. The apparatus of claim 23, wherein, in order to receive the beam management request communication, the one or more processors are configured to receive a media access control (MAC) control element (MACCE) including the plurality of beam management requests.

27. A method for wireless communication performed by a user equipment (UE), the method comprising: Sending beam management request communication including multiple beam management requests, each of the multiple beam management requests corresponding to a corresponding TRP in a plurality of transmit-receive points (TRPs); as well as The beam management request communication is used to perform beam management operations associated with at least one of the plurality of TRPs.

28. The method of claim 27, wherein the beam management request communication indicates a change in one or more reception conditions associated with one or more of the plurality of TRPs.

29. A method for wireless communication performed by a network node, the method comprising: Receive beam management request communication including multiple beam management requests, each of the multiple beam management requests corresponding to a corresponding TRP in a plurality of transmit-receive points (TRPs); as well as The beam management request communication is used to perform beam management operations associated with at least one of the plurality of TRPs.

30. The method of claim 29, wherein the beam management request communication indicates a change in one or more reception conditions associated with one or more of the plurality of TRPs.

Images