Uplink-related event-triggered beam management

Abstract

Methods, systems, and devices for wireless communication are described. A user equipment (UE) can detect an uplink event trigger associated with wireless communications with a second network entity, where the uplink event trigger is based on a change in one or more uplink communication parameters satisfying a threshold. The UE can output, based on the uplink event trigger, a beam management message to the second network entity, where the beam management message is associated with a change to a downlink beam for the wireless communications with the second network entity. The UE can perform, based on the beam management message, the wireless communications with the second network entity using the updated downlink beam.

Description

Background Technology

[0001] The following pertains to wireless communication, including uplink-related event-triggered beam management. Wireless communication systems are widely deployed to provide various types of communication content such as voice, video, packet data, message sending and receiving, and broadcasting. These systems can support communication with multiple users by sharing available system resources (e.g., time, frequency, and power). Examples of such multiple access systems include fourth-generation (4G) systems (such as Long Term Evolution (LTE) systems, LTE-A Advanced (LTE-A) systems, or LTE-A Pro systems) and fifth-generation (5G) systems (which may be referred to as New Radio (NR) systems). These systems may employ technologies such as Code Division Multiple Access (CDMA), Time Division Multiple Access (TDMA), Frequency Division Multiple Access (FDMA), Orthogonal FDMA (OFDMA), or Discrete Fourier Transform Extended Orthogonal Frequency Division Multiplexing (DFT-S-OFDM). A wireless multiple access communication system may include one or more base stations, each supporting wireless communication of communication devices, which may be referred to as User Equipment (UE). Summary of the Invention

[0002] The described technology relates to improved methods, systems, devices, and apparatuses for supporting beam management triggered by uplink-related events. For example, the described technology provides various mechanisms for implementing UE-initiated beam reports or beam management requests based on uplink events detected by a User Equipment (UE). Specifically, the UE can identify or otherwise detect one or more uplink events (e.g., uplink path loss changes, antenna changes, or other uplink-related events) triggered by or otherwise associated with a downlink beam of a network entity. Therefore, the UE can identify or otherwise detect uplink event triggering associated with wireless communication with a network entity. Uplink event triggering may be based on a change in uplink parameters that has met a change threshold level. The UE can send or otherwise output a beam management message associated with a change to the downlink beam used for wireless communication to the network entity. The beam management message may be a beam report indicating a change to the downlink beam, or a beam management request initiating a beam update process with the network entity. The UE and network entities can perform wireless communication using updated downlink beams based on beam management messages. For example, a beam management message can trigger an update to the downlink beam that addresses or otherwise mitigates changes in uplink parameters observed by the UE.

[0003] A method for wireless communication performed by a first network entity is described. The method may include: detecting an uplink event trigger associated with wireless communication with a second network entity, wherein the uplink event trigger is based on a change in one or more uplink communication parameters satisfying a threshold; outputting a beam management message to the second network entity based on the uplink event trigger, wherein the beam management message is associated with a change in a downlink beam used for wireless communication with the second network entity; and performing wireless communication with the second network entity using the updated downlink beam based on the beam management message.

[0004] A first network entity for wireless communication is described. The first network entity may include a processing system configured to: detect an uplink event trigger associated with wireless communication with a second network entity, wherein the uplink event trigger is based on a change in one or more uplink communication parameters satisfying a threshold; output a beam management message to the second network entity based on the uplink event trigger, wherein the beam management message is associated with a change in a downlink beam for wireless communication with the second network entity; and perform wireless communication with the second network entity using the updated downlink beam based on the beam management message.

[0005] Another first network entity for wireless communication is described. The first network entity may include: components for detecting and triggering uplink events associated with wireless communication with a second network entity, wherein the uplink event triggering is based on changes in one or more uplink communication parameters satisfying a threshold; components for outputting a beam management message to the second network entity based on the uplink event triggering, wherein the beam management message is associated with a change in a downlink beam for wireless communication with the second network entity; and components for performing wireless communication with the second network entity using the updated downlink beam based on the beam management message.

[0006] A non-transitory computer-readable medium having code for wireless communication stored thereon is described. When executed by a first network entity, the code causes the first network entity to: detect and trigger an uplink event associated with wireless communication with a second network entity, wherein the uplink event trigger is based on a change in one or more uplink communication parameters satisfying a threshold; output a beam management message to the second network entity based on the uplink event trigger, wherein the beam management message is associated with a change in a downlink beam for wireless communication with the second network entity; and, based on the beam management message, perform wireless communication with the second network entity using the updated downlink beam.

[0007] In some examples of the methods described herein, the first network entity, and the nontransitory computer-readable medium, the change in one or more uplink communication parameters includes one or more of the following: a change in uplink power, a change in uplink antenna, a change in cross-link interference associated with full-duplex communication, or a change in the flexibility of the time-division full-duplex scheme.

[0008] In some examples of the methods described herein, the first network entity, and the nontransitory computer-readable medium, the beam management message includes a beam report associated with the downlink beam, and the beam report identifies a change request for the downlink beam.

[0009] In some examples of the methods described herein, the first network entity, and non-transitory computer-readable media, the beam report indicates the updated downlink beam.

[0010] In some examples of the methods described herein, the first network entity, and non-transitory computer-readable media, the beam management message includes a beam management request associated with the downlink beam.

[0011] The methods described herein, some examples of the first network entity, and non-transitory computer-readable media may also include operations, features, components, or instructions for performing a downlink beam update process with the second network entity to identify the updated downlink beam.

[0012] In some examples of the methods described herein, the first network entity, and the nontransitory computer-readable medium, the first layer of the first network entity may be configured to detect the uplink event triggering, and the second layer of the first network entity may be configured to output the beam management message based on information from the first layer, and the first layer may be a higher layer than the second layer.

[0013] In some examples of the methods described herein, the first network entity, and the nontransitory computer-readable medium, a first layer of the first network entity may be configured to detect the uplink event triggering, and a second layer of the first network entity may be configured to output the beam management message, and the uplink event triggering may be based on one or more reference signals associated with the second network entity.

[0014] In some examples of the methods described herein, the first network entity, and the nontransitory computer-readable medium, a first layer of the first network entity may be configured to detect the uplink event triggering, and a second layer of the first network entity may be configured to output the beam management message, and the uplink event triggering may be based on downlink communication associated with the second network entity.

[0015] In some examples of the methods described herein, the first network entity, and the nontransitory computer-readable medium, the beam management message indicates at least one of an uplink event identifier or a downlink event identifier, and the uplink event trigger may be associated with the uplink event identifier or the downlink event identifier.

[0016] In some examples of the methods described herein, the first network entity, and the nontransitory computer-readable medium, the beam management message indicates whether the uplink event triggering can be associated with an uplink event or with a downlink event.

[0017] A method for performing wireless communication by a second network entity is described. The method may include: obtaining from a first network entity a beam management message triggered by an uplink event and associated with wireless communication with the second network entity, wherein the uplink event triggers a change in one or more uplink communication parameters of the first network entity that satisfies a threshold; obtaining the beam management message from the first network entity based on the uplink event trigger, wherein the beam management message is associated with a change in a downlink beam for wireless communication with the second network entity; and performing wireless communication with the first network entity using the updated downlink beam based on the beam management message.

[0018] A second network entity for wireless communication is described. The second network entity may include a processing system configured to: obtain from a first network entity a beam management message triggered by an uplink event based on and associated with wireless communication with the second network entity, wherein the uplink event triggers a change in one or more uplink communication parameters of the first network entity that satisfies a threshold; obtain the beam management message from the first network entity based on the uplink event trigger, wherein the beam management message is associated with a change in a downlink beam for wireless communication with the second network entity; and perform wireless communication with the first network entity using the updated downlink beam based on the beam management message.

[0019] A second network entity for wireless communication is described. This second network entity may include: components for obtaining a beam management message triggered by an uplink event based on and associated with wireless communication with the second network entity from a first network entity, wherein the uplink event triggers a change in one or more uplink communication parameters of the first network entity that satisfies a threshold; components for obtaining the beam management message from the first network entity based on the uplink event trigger, wherein the beam management message is associated with a change in a downlink beam for wireless communication with the second network entity; and components for performing wireless communication with the first network entity using the updated downlink beam based on the beam management message.

[0020] A non-transitory computer-readable medium having code for wireless communication stored thereon is described. When executed by a second network entity, the code causes the second network entity to: obtain from a first network entity a beam management message triggered by an uplink event based on and associated with wireless communication with the second network entity, wherein the uplink event triggers a change in one or more uplink communication parameters of the first network entity that satisfies a threshold; obtain a beam management message from the first network entity based on the uplink event trigger, wherein the beam management message is associated with a change in a downlink beam for wireless communication with the second network entity; and perform wireless communication with the first network entity using the updated downlink beam based on the beam management message.

[0021] In some examples of the methods described herein, the second network entity, and the nontransitory computer-readable medium, the change in one or more uplink communication parameters includes one or more of the following: a change in uplink power, a change in uplink antenna, a change in cross-link interference associated with full-duplex communication, or a change in the flexibility of the time-division full-duplex scheme.

[0022] In some examples of the methods described herein, the second network entity, and the nontransitory computer-readable medium, the beam management message includes a beam report associated with the downlink beam, and the beam report identifies a change request for the downlink beam.

[0023] In some examples of the methods described herein, second network entities, and non-transitory computer-readable media, the beam report indicates the updated downlink beam.

[0024] In some examples of the methods described herein, the second network entity, and non-transitory computer-readable media, the beam management message includes a beam management request associated with the downlink beam.

[0025] The methods described herein, some examples of the second network entity, and nontransitory computer-readable media may also include operations, features, components, or instructions for performing a downlink beam update process with the first network entity to identify the updated downlink beam.

[0026] In some examples of the methods described herein, the second network entity, and the nontransitory computer-readable medium, the beam management message indicates at least one of an uplink event identifier or a downlink event identifier, and the uplink event trigger may be associated with the uplink event identifier or the downlink event identifier.

[0027] In some examples of the methods described herein, the second network entity, and the nontransitory computer-readable medium, the beam management message indicates whether the uplink event triggering can be associated with an uplink event or with a downlink event. Attached Figure Description

[0028] Figure 1 An example of a wireless communication system supporting uplink-related event-triggered beam management according to one or more aspects of this disclosure is shown.

[0029] Figure 2 An example of a wireless communication system supporting uplink-related event-triggered beam management according to one or more aspects of this disclosure is shown.

[0030] Figure 3 An example swimlane diagram of uplink-related event-triggered beam management is shown, according to one or more aspects of this disclosure.

[0031] Figure 4 An example swimlane diagram of uplink-related event-triggered beam management is shown, according to one or more aspects of this disclosure.

[0032] Figure 5 and Figure 6 A block diagram of a device supporting uplink-related event-triggered beam management according to one or more aspects of this disclosure is shown.

[0033] Figure 7 A block diagram of a communication manager supporting uplink-related event-triggered beam management, according to one or more aspects of this disclosure, is shown.

[0034] Figure 8 A diagram of a system including a device supporting uplink-related event-triggered beam management, according to one or more aspects of this disclosure, is shown.

[0035] Figure 9 and Figure 10 A block diagram of a device supporting uplink-related event-triggered beam management according to one or more aspects of this disclosure is shown.

[0036] Figure 11 A block diagram of a communication manager supporting uplink-related event-triggered beam management, according to one or more aspects of this disclosure, is shown.

[0037] Figure 12 A diagram of a system including a device supporting uplink-related event-triggered beam management, according to one or more aspects of this disclosure, is shown.

[0038] Figures 13 to 15A flowchart illustrating a method for supporting uplink-related event-triggered beam management according to one or more aspects of this disclosure is shown. Detailed Implementation

[0039] Wireless communication can utilize beamforming techniques based on downlink beams of network entities. For example, network entities can use beamforming techniques to direct downlink communication to user equipment (UE) within a downlink beam. Various techniques can be applied to enable network entities to update or otherwise modify their downlink beams, for example, based on poor or below-threshold performance of the current downlink beam, or changes in downlink path loss. However, such networks do not provide mechanisms for implementing UE-initiated beam reporting or beam management requests based on uplink events observed or otherwise detected by the UE.

[0040] Therefore, the described techniques provide various mechanisms for implementing UE-initiated beam reporting or beam management requests based on uplink events detected by the User Equipment (UE). Specifically, the UE can identify or otherwise detect one or more uplink events (e.g., uplink path loss changes, antenna changes, or other uplink-related events) triggered by or otherwise associated with the downlink beam of a network entity. The UE can identify or otherwise detect uplink event triggers associated with wireless communication with the network entity. Uplink event triggering may be based on a change in uplink parameters that has met a change threshold level. The UE can send or otherwise output a beam management message to the network entity associated with a change to the downlink beam used for wireless communication. The beam management message may be a beam report indicating a change to the downlink beam, or a beam management request initiating a beam update process with the network entity. The UE and the network entity can perform wireless communication using the updated downlink beam based on the beam management message. For example, beam management messages can trigger updates to the downlink beam that address or otherwise mitigate changes in uplink parameters observed by the UE.

[0041] The aspects of this disclosure are first described in the context of a wireless communication system. These aspects are further illustrated and described with reference to apparatus diagrams, system diagrams, and flowcharts relating to beam management triggered by uplink-related events.

[0042] Figure 1An example of a wireless communication system 100 supporting uplink-related event-triggered beam management according to one or more aspects of this disclosure is shown. The wireless communication system 100 may include one or more devices, such as one or more network devices (e.g., network entity 105), one or more UEs 115, and a core network 130. In some aspects, the wireless communication system 100 may be a Long Term Evolution (LTE) network, an Advanced LTE (LTE-A) network, an LTE-A Pro network, a New Radio (NR) network, or a network operating according to other systems and radio technologies, including future systems and radio technologies not explicitly mentioned herein.

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

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

[0045] As described herein, a network entity (which may alternatively be referred to as an entity, node, network node, or wireless entity) can be, can be similar to, can include, or can be included in (e.g., can be a component of) the following: base station (e.g., any base station described herein, including a decomposed base station), UE (e.g., any UE described herein), RedCap device, eRedCap device, ambient Internet of Things (IoT) device, device with energy harvesting (EH) capability, network controller, apparatus, device, computing system, integrated access and backhaul (IAB) node, distributed unit (DU), central unit (CU), remote / radio unit (RU) (which may also be referred to as a remote radio unit (RRU)), and / or another processing entity configured to perform any of the techniques described herein. For example, a network entity can be a UE. As another example, a network entity can be a base station. As used herein, “network entity” can refer to an entity configured to operate in a network, such as network entity 105. For example, “network entity” is not limited to an entity currently located in and / or currently operating in a network. Instead, a network entity can be any entity capable of communicating and / or operating within a network.

[0046] The adjectives "first," "second," "third," etc., are used to distinguish between two or more modified nouns in context, and do not imply absolute modifiers applicable only to a specific corresponding entity throughout the document. For example, a network entity may be referred to as "first network entity" in one discussion and as "second network entity" in another, and vice versa. As an example, the first network entity may be configured to communicate with a second network entity or a third network entity. In one aspect of this example, the first network entity may be a UE, the second network entity may be a base station, and the third network entity may be a UE. In another aspect of this example, the first network entity may be a UE, the second network entity may be a base station, and the third network entity may be a base station. In yet other aspects of this example, the first, second, and third network entities may be different from these examples.

[0047] Similarly, references to UE, base station, device, equipment, computing system, etc., may include disclosures of UE, base station, device, equipment, computing system, etc., as network entities. For example, a disclosure of a UE being configured to receive information from a base station also discloses that a first network entity is configured to receive information from a second network entity. Consistent with this disclosure, once a particular example is extended according to this disclosure (e.g., a disclosure of a UE being configured to receive information from a base station also discloses that a first network entity is configured to receive information from a second network entity), a broader example of a narrower example may be interpreted in reverse, but in a broad, open-ended manner. In the above example where a UE is configured to receive information from a base station and a first network entity is configured to receive information from a second network entity, the first network entity may refer to a first UE, a first base station, a first device, a first equipment, a first computing system, a first set of one or more components, a first processing entity, etc., configured to receive information; and the second network entity may refer to a second UE, a second base station, a second device, a second equipment, a second computing system, a second set of one or more components, a second processing entity, etc.

[0048] As described herein, different terms may be used in various contexts to describe the transmission of information (e.g., any information, signal, etc.). Disclosure of one communication term includes disclosure of other communication terms. For example, a first network entity may be described as being configured to send information to a second network entity. In this example and consistent with this disclosure, disclosure that a first network entity is configured to send information to a second network entity includes disclosure that the first network entity is configured to provide, transmit, output, communicate, or send information to the second network entity. Similarly, in this example and consistent with this disclosure, disclosure that a first network entity is configured to send information to a second network entity includes disclosure that the second network entity is configured to receive, obtain, or decode information provided, transmitted, output, communicate, or sent by the first network entity.

[0049] As shown in the figure, a network entity (e.g., network entity 105) may include a processing system 106. Similarly, a network entity (e.g., UE 115) may include a processing system 112. A processing system may include one or more components (or sub-components), such as those described herein. For example, a corresponding component among these one or more components may be, similar to, include, or be included in at least one memory, at least one communication interface, or at least one processor. For example, a processing system may include one or more components. In such an example, the one or more components may include a first component, a second component, and a third component. In this example, the first component may be coupled to the second and third components. In this example, the first component may be at least one processor, the second component may be a communication interface, and the third component may be at least one memory. A processing system is generally one or more components of a system capable of performing one or more functions (such as any function or combination of functions described herein). For example, one or more components may receive input information (e.g., any information as input, such as a signal, any digital information, or any other information), one or more components may process the input information to generate output information (e.g., any information as output, such as a signal or any other information), one or more components may perform any function as described herein or any combination thereof. As described herein, “input” and “input information” can be used interchangeably. Similarly, as described herein, “output” and “output information” can be used interchangeably. Any information generated by any component can be provided to one or more other systems or components of network entities such as those described herein. For example, a processing system may include a first component configured to receive or obtain information, a second component configured to process the information to generate output information, and / or a third component configured to provide the output information to other systems or components. In this example, the first component may be a communication interface (e.g., a first communication interface), the second component may be at least one processor (e.g., coupled to the communication interface and / or at least one memory), and the third component may be a communication interface (e.g., a first communication interface or a second communication interface). For example, a processing system may include at least one memory, at least one communication interface, and / or at least one processor, wherein the at least one processor may, for example, be coupled to the at least one memory and the at least one communication interface.

[0050] The processing system of the network entity described herein can interface with one or more other components of the network entity, process information received from one or more other components (such as input information), or output such information to one or more other components. For example, the processing system may include a first component configured to interface with one or more other components of the network entity to receive or obtain information, a second component configured to process the information to generate one or more outputs, and / or a third component configured to output the one or more outputs to one or more other components. In this example, the first component may be a communication interface (e.g., a first communication interface), the second component may be at least one processor (e.g., coupled to the communication interface and / or at least one memory), and the third component may be a communication interface (e.g., the first communication interface or the second communication interface). For example, a chip or modem of the network entity may include the processing system. The processing system may include a first communication interface for receiving or obtaining information, and a second communication interface for outputting, transmitting, or providing information. In some aspects, the first communication interface may be an interface configured to receive input information, and such information may be provided to the processing system. In some aspects, the second system interface may be configured to transmit information output from the chip or modem. The second communication interface can also obtain or receive input information, and the first communication interface can also output, send, or provide information.

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

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

[0053] One or more network entities or network equipment in network entity 105 described herein may include or be referred to as base station 140 (e.g., transceiver base station, radio base station, NR base station, access point, radio transceiver, NodeB, eNodeB (eNB), next-generation NodeB or gigabit NodeB (any of which may be referred to as gNB), 5G NB, next-generation eNB (ng-eNB), home NodeB, home eNodeB, or other suitable terms). In some aspects, network entity 105 (e.g., base station 140) may be implemented in an aggregated (e.g., monolithic, standalone) base station architecture that may be configured to utilize a protocol stack that is physically or logically integrated within a single network entity (e.g., network entity 105 or a single RAN node, such as base station 140).

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

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

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

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

[0058] IAB node 104 may refer to a RAN node that provides IAB functionality (e.g., access for UE 115, radio self-backhaul capability). DU 165 may act as a distributed scheduling node toward child nodes associated with IAB node 104, and IAB-MT may act as a scheduled node toward a parent node associated with IAB node 104. That is, an IAB donor may be referred to as a parent node communicating with one or more child nodes (e.g., an IAB donor may relay for UE transmissions via other IAB nodes 104). Additionally or alternatively, IAB node 104 may also be referred to as a parent or child node of other IAB nodes 104, depending on the AN's relay chain or configuration. Therefore, the IAB-MT entity of IAB node 104 can provide a Uu interface for the child IAB node (e.g., IAB node 104) to receive signaling from the parent IAB node (e.g., IAB node 104), and the DU interface (e.g., DU 165) can provide a Uu interface for the parent IAB node to send signaling notifications to the child IAB node or UE 115.

[0059] For example, IAB node 104 may be referred to as a parent node supporting communication to child IAB nodes, or as a child IAB node associated with an IAB donor, or both. An IAB donor may include a CU 160 having a wired or wireless connection to core network 130 (e.g., backhaul communication link 120) and may act as a parent node of IAB node 104. For example, an IAB donor's DU 165 may relay transmissions to UE 115 via IAB node 104, or may signal transmissions directly to UE 115, or both. An IAB donor's CU 160 may signal the establishment of a communication link to IAB node 104 via an F1 interface, and IAB node 104 may schedule transmissions (e.g., transmissions relayed from the IAB donor to UE 115) via one or more DUs (e.g., DU 165). In other words, data can be relayed to and from IAB node 104 via signaling through the NR Uu interface of the MT to IAB node 104 (e.g., other IAB nodes). Communication with IAB node 104 can be scheduled by the IAB donor or by DU 165 of IAB node 104.

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

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

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

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

[0064] In some aspects, such as in carrier aggregation configurations, carriers may have acquisition or control signaling that coordinates the operation of other carriers. Carriers may be associated with frequency channels (e.g., Evolved Universal Mobile Telecommunications System Terrestrial Radio Access (E-UTRA) Absolute RF Channel Number (EARFCN)) and may be identified according to a channel grating used for discovery by UE 115. Carriers may operate in standalone mode, in which case initial acquisition and connection can be performed by UE 115 via that carrier, or carriers may operate in non-standalone mode, in which case different carriers (e.g., of the same or different RATs) are used to anchor the connection.

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

[0066] A carrier may be associated with a specific bandwidth of the RF spectrum, and in some aspects, the carrier bandwidth may be referred to as the carrier or the “system bandwidth” of the wireless communication system 100. For example, the carrier bandwidth may be one of a set of bandwidths for a carrier for a specific RAT (e.g., 1.4 MHz, 3 MHz, 5 MHz, 10 MHz, 15 MHz, 20 MHz, 40 MHz, or 80 MHz). Devices of the wireless communication system 100 (e.g., network entity 105, UE 115, or both) may have a hardware configuration that supports communication using a specific carrier bandwidth, or may be configured to support communication using one of a set of carrier bandwidths. In some aspects, the wireless communication system 100 may include a network entity 105 or UE 115 that supports concurrent communication using carriers associated with multiple carrier bandwidths. In some aspects, each served UE 115 may be configured to operate using a portion (e.g., a sub-band, BWP) or all of the carrier bandwidth.

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

[0068] It can support one or more sets of parameters for a carrier, and the set of parameters may include subcarrier spacing ( The carrier can be divided into one or more BWPs with the same or different sets of parameters. In some respects, the UE 115 can be configured with multiple BWPs. In some respects, a single BWP for a carrier can be active at a given time, and communication for the UE 115 can be limited to one or more active BWPs.

[0069] The time interval for network entity 105 or UE 115 can be expressed as a multiple of a basic time unit, such as the sampling period. seconds, in response It can represent the supported subcarrier spacing, and This can represent the supported Discrete Fourier Transform (DFT) size. The time interval for organizing communication resources can be based on radio frames, each with a specified duration (e.g., 10 milliseconds (ms)). Each radio frame can be identified by a System Frame Number (SFN) (e.g., ranging from 0 to 1023).

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

[0071] A subframe, time slot, micro-time slot, or symbol can be the smallest scheduling unit of the wireless communication system 100 (e.g., in the time domain) and can be referred to as a Transmission Time Interval (TTI). In some aspects, the duration of the TTI (e.g., the number of symbol periods in the TTI) can be variable. Additionally or alternatively, the smallest scheduling unit of the wireless communication system 100 can be dynamically selected (e.g., in a burst form of a shortened TTI (sTTI)).

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

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

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

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

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

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

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

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

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

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

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

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

[0084] Wireless communication system 100 can operate using one or more frequency bands in the range of 300 MHz to 300 GHz. Generally, the area from 300 MHz to 3 GHz is referred to as the Ultra High Frequency (UHF) band or decimeter band because the wavelength range is approximately one decimeter to one meter in length. UHF waves may be blocked or redirected by buildings and environmental features (which may be referred to as clusters), but these waves are sufficient to penetrate structures so that macrocells can provide service to UE 115 located indoors. Compared to communication using smaller frequencies and longer waves in the lower frequencies (HF) or very high frequencies (VHF) portions of the spectrum below 300 MHz, communication using UHF waves can be associated with smaller antennas and shorter ranges (e.g., less than one hundred kilometers).

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

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

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

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

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

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

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

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

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

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

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

[0096] A first network entity (e.g., UE 115) can detect and trigger uplink events associated with wireless communication with a second network entity (e.g., network entity 105), wherein the uplink event trigger is based on changes to one or more uplink communication parameters satisfying a threshold. The first network entity can output a beam management message to the second network entity based on the uplink event trigger, wherein the beam management message is associated with a change to the downlink beam used for wireless communication with the second network entity. The first network entity can then perform wireless communication with the second network entity using the updated downlink beam based on the beam management message.

[0097] A second network entity (e.g., network entity 105) may obtain from a first network entity a beam management message triggered by an uplink event related to and associated with wireless communication with the second network entity, wherein the uplink event triggers a change in one or more uplink communication parameters of the first network entity that meets a threshold. The second network entity may obtain the beam management message from the first network entity based on the uplink event trigger, wherein the beam management message is associated with a change to the downlink beam used for wireless communication with the second network entity. The second network entity may then perform wireless communication with the first network entity using the updated downlink beam based on the beam management message.

[0098] Figure 2 An example of a wireless communication system 200 supporting uplink-related event-triggered beam management according to one or more aspects of this disclosure is shown. The wireless communication system 200 may implement aspects of the wireless communication system 100. The wireless communication system 200 may include a UE 205 and a network entity 210, which may be examples of the corresponding devices described herein.

[0099] Wireless networks typically use beamforming communication between transmitting and receiving devices. Beamforming communication may involve the transmitting device applying various digital or analog weighting factors to steer the transmitted signal toward the receiving device. This steer of the transmitted signal can be considered the transmitting beam of the transmitting device. In some aspects, the receiving device may use similar techniques to generate a receiving beam, where the receiving device's antenna is steered toward the transmitting device. This steer performed by the receiving device can be considered the receiving beam of the receiver. When the transmitting device is a network entity (e.g., network entity 210), the transmitting beam may be referred to as a downlink beam. When the transmitting device is a UE (e.g., UE 205), the transmitting beam may be referred to as an uplink beam.

[0100] Such networks provide various mechanisms for UEs or network entities to manage downlink beams. These techniques can be based on the performance of the downlink beams, as measured or otherwise determined by the UE or network entities. Various channel performance metrics for the downlink beams can be monitored, measured, or otherwise determined by the UE or network entities and used to manage the downlink beams. Either or both devices can use these channel performance metrics to determine when it is necessary to update the downlink beams to new or different transmission beams.

[0101] For example, these metrics can be based on determining that the downlink beam performance has deteriorated below a performance threshold (e.g., based on wireless communication performed using the downlink beam or based on a reference signal transmitted using the downlink beam). These metrics can also be based on determining that a new downlink beam has become better than the current downlink beam by a certain offset or that its performance has reached a threshold. Such metrics can be combined (e.g., the current downlink beam is performing poorly while a different downlink beam is improving).

[0102] Channel performance metrics can be based on various measurements or observations of the downlink beam. For example, the signal strength (e.g., RSRP) value of the downlink beam can be measured or otherwise determined by the UE or a network entity. Another example is based on the number of decoding errors at the UE (e.g., the UE cannot decode a radio signal transmitted by a network entity using a downlink beam). Therefore, such networks can provide mechanisms for updating the downlink beam of a network entity based on channel performance metrics. For example, the UE can send or otherwise output a beam report to the network entity indicating a new downlink beam to be selected. The network entity can receive or otherwise obtain the beam report and select the indicated downlink beam for wireless communication with the UE. Another example may include the UE sending a beam management request that initiates a beam update process with the network entity. The beam update process may include various techniques for the network entity to identify or otherwise determine the optimal downlink beam to switch to for wireless communication with the UE. However, such networks do not provide mechanisms for the UE to initiate a beam update process with the network entity based on uplink-related events.

[0103] Therefore, the various aspects of the described technology generally provide UE-initiated or event-driven beam reporting, which facilitates rapid beam switching based on uplink events. Uplink signaling from UE 205 may take into account the UE-initiated or event-driven nature of uplink transmissions (e.g., primarily designed for beam reporting purposes). Uplink signaling from UE 205 may be based on event-triggered beam reporting, UE-requested beam management, or report-based beam switching or activation.

[0104] For example, UE 205 and network entity 210 may perform wireless communications, which may include both downlink and uplink communications. Downlink wireless communications may include network entity 210 using a downlink beam (e.g., beamforming downlink communications). However, UE 205 may detect, identify, or otherwise determine uplink event triggers associated with the wireless communications. Uplink event triggers may be based on or otherwise associated with uplink communication parameters of the uplink communication. For example, uplink communication parameters may have reached or otherwise satisfied a threshold. Based on the uplink event trigger, UE 205 may send or otherwise output a beam management message to network entity 210 associated with a change to the downlink beam being used for wireless communications. UE 205 and network entity 210 may perform wireless communications using the updated downlink beam based on the beam management message.

[0105] In some respects, changes to uplink communication parameters that have reached or otherwise satisfied thresholds may include or be based on uplink power. For example, uplink event triggering may be based on uplink power events. Uplink power events may include changes in path loss associated with uplink communication. An uplink event may be triggered when the amount of path loss change reaches a (pre)configured threshold. Uplink power events may include changes in the maximum permissible exposure (MPE) associated with uplink communication. For example, UE 205 may have an MPE limit that restricts or otherwise controls the amount of transmit power that UE 205 can use for uplink communication. Once the MPE limit is reached, UE 205 may need to reduce the amount of uplink transmit power. Therefore, an uplink event may be triggered once the MPE value exceeds a (pre)configured threshold.

[0106] Uplink event triggering can be based on uplink antenna changes. UE 205 may be equipped with multiple antennas or ports for transmitting uplink signals. Changes to the antennas or ports used for transmitting uplink signals can trigger uplink events. For example, uplink event triggering can be based on UE 205 switching the antenna panel used for uplink communication (e.g., switching from antenna panel A to antenna panel B). As another example, uplink event triggering can be based on UE 205 switching the antenna used for uplink communication from a two-port configuration to a four-port configuration.

[0107] Uplink event triggering can be based on changes in cross-link interference (CLI) associated with full-duplex communication. For example, a change in full-duplex communication or a hybrid of full-duplex and full-duplex communication can trigger an uplink event. For instance, UE 205 may perform full-duplex communication or a hybrid of full-duplex and full-duplex communication with network entity 210, which may include simultaneously (e.g., concurrently) performing both uplink communication transmission and downlink communication reception. UE 205 may measure, identify, or otherwise determine that the CLI associated with performing full-duplex communication has reached or otherwise satisfied a threshold level. This can trigger an uplink event at UE 205.

[0108] Uplink event triggering can be based on changes in the flexibility of the TDD scheme. For example, UE 205 may perform TDD-based communication with two cells (e.g., cell A and cell B). This may include UE 205 performing downlink communication with cell A and uplink communication with cell B. UE 205 may identify or otherwise determine that a CLI due to different links has reached or otherwise met a threshold level. This may trigger an uplink event at UE 205.

[0109] In some aspects, the first layer of UE 205 can be configured to detect uplink event triggering, and the second layer of UE 205 can be configured to output beam management messages to network entity 210 based on information from the first layer. In this example, the first layer can be a higher layer than the second layer. For example, uplink-related event triggering detection can be performed at a higher layer and then indicated to a lower layer. This could include the higher layer detecting an MPE event, an uplink antenna change, or other event, and then sending an indication of triggering to the lower layer to initiate the transmission of a beam management message.

[0110] In some aspects, the first layer of UE 205 can be configured to detect uplink event triggering, and the second layer of UE 205 can be configured to output beam management messages to network entity 210. Uplink event triggering can be based on a reference signal associated with network entity 210. In this example, the first and second layers can be the same layer. For example, any dedicated detection reference signal can be used at layer one (L1) to perform uplink event triggering detection. This can include configuring a path loss reference signal for uplink event triggering detection based on path loss changes. This can include configuring CSI-RS for CLI-based uplink event triggering detection. Therefore, UE 205 can use any reference signal to detect or otherwise determine that an uplink event triggering has occurred.

[0111] In some aspects, the first layer of UE 205 can be configured to detect uplink event triggering, and the second layer of UE 205 can be configured to output beam management messages to network entity 210. Uplink event triggering can be based on downlink communication associated with network entity 210. In this example, the first and second layers can be the same layer. For example, uplink event triggering detection can be performed at L1 without using any dedicated detection reference signal. This may include UE 205 using the DMRS of the PDSCH to detect or otherwise determine that an uplink event triggering has occurred.

[0112] In some respects, beam management messages may carry or otherwise convey indications of uplink event identifiers or downlink event identifiers. For example, an uplink event identifier or downlink event identifier may be associated with an uplink event trigger (e.g., the event identifier may indicate which uplink-related event or downlink-related event has triggered the beam management message). This allows UE 205 to trigger beam management messages for different downlink and uplink events. Event identifiers can be used to distinguish between uplink and downlink events. For example, different event identifiers may be (pre-)configured for different uplink and different downlink events. As another example, an event identifier pool may be shared between uplink and downlink events. Therefore, UE 205 may indicate event identifiers in beam management messages to indicate to network entity 210 the nature or event that has triggered the beam management message. As a non-limiting example, event identifier 1 may indicate a first downlink event, event identifier 2 may indicate a first uplink event, event identifier 3 may indicate a second downlink event, and so on.

[0113] In some respects, beam management messages may carry or otherwise convey an indication of whether an uplink event triggering is associated with an uplink event or a downlink event. For example, UE 205 may use one bit (or more) to indicate to network entity 210 whether the detected event is an uplink event or a downlink event.

[0114] Figure 3 An example of a swimlane diagram 300 supporting uplink-related event-triggered beam management according to one or more aspects of this disclosure is shown. Swimlane diagram 300 may implement aspects of wireless communication system 100 or wireless communication system 200. The aspects of swimlane diagram 300 may be implemented at or by a UE 305 and a network entity 310, which may be examples of the corresponding devices described herein. For example, UE 305 may be an example of a first network entity, and network entity 310 may be an example of a second network entity.

[0115] At 315, UE 305 may perform beam measurements. Beam measurements may be used for or otherwise associated with a downlink beam associated with network entity 310 (e.g., a downlink beam used for wireless communication between UE 305 and network entity 310). Beam measurements may also be used for or otherwise associated with uplink-related events. For example, beam measurements may be for uplink power events, uplink antenna change events, changes in CLI associated with full-duplex communication, or changes in the flexibility of the TDD scheme associated with wireless communication between UE 305 and network entity 310. In some aspects, UE 305 may use beam measurements to detect or otherwise determine whether changes to uplink communication parameters associated with wireless communication between UE 305 and network entity 310 have reached a threshold.

[0116] At 320, UE 305 may detect or otherwise determine that an uplink trigger associated with wireless communication has occurred. Uplink event triggering may be based on changes in uplink communication parameters reaching or otherwise satisfying a threshold. UE 305 may detect or otherwise determine that an uplink-related event has occurred based on beam measurements. For example, UE 305 may detect or otherwise determine that the path loss level has changed beyond a (pre)configured threshold or that the MPE value is greater than a (pre)configured threshold. UE 305 may detect or otherwise determine that UE 305 has switched from a first antenna panel to a second antenna panel (e.g., from antenna panel A to antenna panel B) or has changed from communication using a first number of antenna ports to communication using a second number of antenna ports. UE 305 may detect or otherwise determine that a strong CLI (e.g., exceeding a threshold) has been observed due to full-duplex communication. UE 305 may detect or otherwise determine that a strong CLI has occurred because UE 305 is communicating with different links (e.g., with two cells). Therefore, UE 305 can detect uplink event triggering based on changes in uplink communication parameters that have met thresholds.

[0117] At 325, UE 305 may send or otherwise output (and network entity 310 may receive or otherwise obtain) a beam management message based on an uplink event trigger. That is, the beam management message may be initiated by the UE in response to UE 305 detecting a change in uplink communication parameters. The beam management message may be associated with a change to the downlink beam currently used for wireless communication between UE 305 and network entity 310. For example, the beam management message may initiate a change from the current downlink beam used for wireless communication to an updated downlink beam that will be used for future wireless communication.

[0118] exist Figure 3In the non-limiting example shown, the beam management message may be a beam report. The beam report may carry or otherwise convey an indication of a request to change the currently used downlink. In some aspects, the beam report may carry or otherwise convey an indication of information identifying an updated downlink beam to which the user should switch. For example, UE 305 may identify or otherwise determine a preferred downlink beam to be used for wireless communication. The preferred downlink beam may be determined based on UE 305 to have performance that will be better than the current downlink beam by a threshold amount. The preferred downlink beam may be determined based on UE 305 to have the expected performance of the preferred downlink beam reached a (pre)configured threshold.

[0119] In some respects, the beam report may carry or otherwise convey the identifier of the preferred downlink beam. For example, the beam report may carry the identifier of an updated downlink beam to be used by network entity 310.

[0120] An updated downlink beam can typically be selected to eliminate or mitigate the impact on uplink communication associated with uplink event triggering. For example, an updated downlink beam can eliminate or otherwise mitigate changes to uplink communication parameters observed or otherwise detected by UE 305.

[0121] Therefore, at 330, UE 305 and network entity 310 can use an updated downlink (DL) beam (e.g., based on a beam management message) to perform wireless communication. For example, in response to a beam report from UE 305 identifying an updated downlink beam, the current downlink beam being used by network entity 310 can be changed to the updated downlink beam.

[0122] Figure 4 An example of a swimlane diagram 400 supporting uplink-related event-triggered beam management according to one or more aspects of this disclosure is shown. Swimlane diagram 400 may implement aspects of wireless communication system 100 or wireless communication system 200. The aspects of swimlane diagram 400 may be implemented at or by a UE 405 and a network entity 410, which may be examples of the corresponding devices described herein. For example, UE 405 may be an example of a first network entity, and network entity 410 may be an example of a second network entity.

[0123] At 415, UE 405 may perform beam measurements. Beam measurements may be used for or otherwise associated with a downlink beam associated with network entity 410 (e.g., a downlink beam used for wireless communication between UE 405 and network entity 410). Beam measurements may also be used for or otherwise associated with uplink-related events. For example, beam measurements may be for uplink power events, uplink antenna change events, changes in CLI associated with full-duplex communication, or changes in the flexibility of the TDD scheme associated with wireless communication between UE 405 and network entity 410. In some aspects, UE 405 may use beam measurements to detect or otherwise determine whether changes to uplink communication parameters associated with wireless communication between UE 405 and network entity 410 have reached a threshold.

[0124] At 420, UE 405 may detect or otherwise determine that an uplink trigger associated with wireless communication has occurred. Uplink event triggering may be based on changes in uplink communication parameters reaching or otherwise satisfying a threshold. UE 405 may detect or otherwise determine that an uplink-related event has occurred based on beam measurements. For example, UE 405 may detect or otherwise determine that the path loss level has changed beyond a (pre)configured threshold or that the MPE value is greater than a (pre)configured threshold. UE 405 may detect or otherwise determine that UE 305 has switched from a first antenna panel to a second antenna panel (e.g., from antenna panel A to antenna panel B) or has changed from communication using a first number of antenna ports to communication using a second number of antenna ports. UE 405 may detect or otherwise determine that a strong CLI (e.g., exceeding a threshold) has been observed due to full-duplex communication. UE 405 may detect or otherwise determine that a strong CLI has occurred because UE 405 is communicating with different links (e.g., with two cells). Therefore, UE 405 can detect uplink event triggering based on changes in uplink communication parameters that have met thresholds.

[0125] At 425, UE 405 may send or otherwise output (and network entity 410 may receive or otherwise acquire) a beam management message based on an uplink event trigger. That is, the beam management message may be initiated by the UE in response to UE 405 detecting a change in uplink communication parameters. The beam management message may be associated with a change to the downlink beam currently used for wireless communication between UE 405 and network entity 410. For example, the beam management message may initiate a change from the current downlink beam used for wireless communication to an updated downlink beam that will be used for future wireless communication.

[0126] exist Figure 4In the non-limiting example shown, the beam management message can be a beam management request. A beam management request may carry or otherwise convey an indication that a channel performance metric associated with the current downlink beam has failed or otherwise fallen below a threshold. A beam management request typically triggers a beam update process performed by network entity 410.

[0127] Therefore, at 430, UE 405 and network entity 410 may perform a beam update procedure to identify an updated downlink beam. The beam update procedure may include one or more iterations, wherein network entity 410 transmits various signals (e.g., reference signals) measured by UE 405, and wherein UE 405 reports the measurement results to network entity 410. Network entity 410 may select or otherwise identify an updated downlink beam to be used for ongoing wireless communication with UE 405 based on the results of the beam update procedure.

[0128] An updated downlink beam can typically be selected to eliminate or mitigate the impact on uplink communication associated with uplink event triggering. For example, an updated downlink beam can eliminate or otherwise mitigate changes to uplink communication parameters observed or otherwise detected by UE 405.

[0129] Therefore, at 435, UE 405 and network entity 410 can use an updated downlink (DL) beam (e.g., based on a beam management message) to perform wireless communication. For example, in response to a beam report from UE 405 identifying an updated downlink beam, the current downlink beam being used by network entity 410 can be changed to the updated downlink beam.

[0130] Figure 5 A block diagram 500 of a device 505 supporting uplink-related event-triggered beam management according to one or more aspects of this disclosure is shown. Device 505 may be an example of various aspects of a UE 115 as described herein. Device 505 may include a receiver 510, a transmitter 515, and a communication manager 520. Device 505 or one or more components of device 505 (e.g., receiver 510, transmitter 515, communication manager 520) may include at least one processor that may be coupled to at least one memory to individually or jointly support or implement the described techniques. Each of these components may communicate with each other (e.g., via one or more buses).

[0131] Receiver 510 may provide components for receiving information (such as packets, user data, control information, or any combination thereof) associated with various information channels (e.g., control channels, data channels, information channels, or beam management related to uplink events). The information may be passed to other components of device 505. Receiver 510 may utilize a single antenna or a collection of antennas.

[0132] Transmitter 515 may provide components for transmitting signals generated by other components of device 505. For example, transmitter 515 may transmit information (such as packets, user data, control information, or any combination thereof) associated with various information channels (e.g., control channels, data channels, information channels related to uplink-related event-triggered beam management). In some aspects, transmitter 515 may be co-located with receiver 510 in a transceiver module. Transmitter 515 may utilize a single antenna or a collection of multiple antennas.

[0133] The communication manager 520, receiver 510, transmitter 515, or various combinations or components thereof may be examples of components used to perform various aspects of uplink-related event-triggered beam management as described herein. For example, the communication manager 520, receiver 510, transmitter 515, or various combinations or components thereof may be able to perform one or more of the functions described herein.

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

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

[0136] In some respects, the communication manager 520 may be configured to use or otherwise cooperate with the receiver 510, transmitter 515, or both to perform various operations (e.g., receiving, acquiring, monitoring, outputting, transmitting). For example, the communication manager 520 may receive information from the receiver 510, transmit information to the transmitter 515, or be integrated in combination with the receiver 510, transmitter 515, or both to acquire information, output information, or perform various other operations as described herein.

[0137] Communication manager 520 can support wireless communication according to examples disclosed herein. For example, communication manager 520 is capable of, configured to, or operable to support components for detecting and associated with uplink event triggering for wireless communication with a second network entity, wherein the uplink event triggering is based on a change in one or more uplink communication parameters satisfying a threshold. Communication manager 520 is capable of, configured to, or operable to support components for outputting beam management messages to a second network entity based on uplink event triggering, wherein the beam management messages are associated with a change in the downlink beam for wireless communication with the second network entity. Communication manager 520 is capable of, configured to, or operable to support components for performing wireless communication with the second network entity using an updated downlink beam based on the beam management message.

[0138] By including or configuring a communication manager 520 according to an example as described herein, device 505 (e.g., controlling receiver 510, transmitter 515, communication manager 520 or a combination thereof or at least one processor otherwise coupled to them) can support techniques for implementing UE-initiated beam reporting or beam management requests based on the detection of uplink-related event triggering.

[0139] Figure 6A block diagram 600 of a device 605 supporting uplink-related event-triggered beam management according to one or more aspects of this disclosure is shown. Device 605 may be an example of aspects of device 505 or UE 115 as described herein. Device 605 may include a receiver 610, a transmitter 615, and a communication manager 620. Device 605 or one or more components of device 605 (e.g., receiver 610, transmitter 615, communication manager 620) may include at least one processor that may be coupled to at least one memory to support the described techniques. Each of these components may communicate with each other (e.g., via one or more buses).

[0140] Receiver 610 may provide components for receiving information (such as packets, user data, control information, or any combination thereof) associated with various information channels (e.g., control channels, data channels, information channels, or beam management related to uplink events). The information may be passed to other components of device 605. Receiver 610 may utilize a single antenna or a collection of antennas.

[0141] Transmitter 615 may provide components for transmitting signals generated by other components of device 605. For example, transmitter 615 may transmit information (such as packets, user data, control information, or any combination thereof) associated with various information channels (e.g., control channels, data channels, information channels related to uplink-related event-triggered beam management). In some aspects, transmitter 615 may be co-located with receiver 610 in a transceiver module. Transmitter 615 may utilize a single antenna or a collection of multiple antennas.

[0142] Device 605 or its various components may be examples of parts for performing various aspects of uplink-related event-triggered beam management as described herein. For example, communication manager 620 may include event detection manager 625, beam message manager 630, update beam manager 635, or any combination thereof. Communication manager 620 may be examples of aspects of communication manager 520 as described herein. In some aspects, communication manager 620 or its various components may be configured to use or otherwise cooperate with receiver 610, transmitter 615, or both to perform various operations (e.g., receiving, acquiring, monitoring, outputting, transmitting). For example, communication manager 620 may receive information from receiver 610, transmit information to transmitter 615, or be integrated in combination with receiver 610, transmitter 615, or both to acquire information, output information, or perform various other operations as described herein.

[0143] Communication manager 620 can support wireless communication according to the examples disclosed herein. Event detection manager 625 is capable of, configured to, or operable to support components for detecting uplink event triggering associated with wireless communication with a second network entity, wherein the uplink event triggering is based on changes in one or more uplink communication parameters satisfying a threshold. Beam message manager 630 is capable of, configured to, or operable to support components for outputting beam management messages to a second network entity based on uplink event triggering, wherein the beam management messages are associated with changes to the downlink beam for wireless communication with the second network entity. Update beam manager 635 is capable of, configured to, or operable to support components for performing wireless communication with the second network entity using an updated downlink beam based on beam management messages.

[0144] Figure 7 A block diagram 700 of a communication manager 720 supporting uplink-dependent event-triggered beam management according to one or more aspects of this disclosure is shown. The communication manager 720 may be an example of aspects of the communication manager 520, communication manager 620, or both as described herein. The communication manager 720 or its various components may be examples of parts for performing various aspects of uplink-dependent event-triggered beam management as described herein. For example, the communication manager 720 may include an event detection manager 725, a beam message manager 730, an update beam manager 735, a downlink beam manager 740, or any combination thereof. Each of these components, or its components or sub-components (e.g., one or more processors, one or more memories), may communicate directly or indirectly with each other (e.g., via one or more buses).

[0145] Communication Manager 720 can support wireless communication according to the examples disclosed herein. Event Detection Manager 725 is capable of, configured to, or operable to support components for detecting uplink event triggering associated with wireless communication with a second network entity, wherein the uplink event triggering is based on a change in one or more uplink communication parameters satisfying a threshold. Beam Message Manager 730 is capable of, configured to, or operable to support components for outputting beam management messages to a second network entity based on uplink event triggering, wherein the beam management messages are associated with a change in the downlink beam for wireless communication with the second network entity. Update Beam Manager 735 is capable of, configured to, or operable to support components for performing wireless communication with the second network entity using an updated downlink beam based on beam management messages.

[0146] In some aspects, the change in one or more uplink communication parameters includes one or more of the following: a change in uplink power, a change in uplink antenna, a change in cross-link interference associated with full-duplex communication, or a change in the flexibility of the time-division full-duplex scheme. In some aspects, the beam management message includes a beam report associated with the downlink beam. In some aspects, the beam report identifies a request for change to the downlink beam. In some aspects, the beam report indicates an updated downlink beam. In some aspects, the beam management message includes a beam management request associated with the downlink beam.

[0147] In some respects, the downlink beam manager 740 is capable of, can be configured to, or is operable to support components for performing a downlink beam update process with a second network entity to identify the updated downlink beam.

[0148] In some aspects, the first layer of the first network entity is configured to detect uplink event triggering, and the second layer of the first network entity is configured to output beam management messages based on information from the first layer. In some aspects, the first layer is a higher layer than the second layer. In some aspects, the first layer of the first network entity is configured to detect uplink event triggering, and the second layer of the first network entity is configured to output beam management messages. In some aspects, uplink event triggering is based on one or more reference signals associated with the second network entity. In some aspects, the first layer of the first network entity is configured to detect uplink event triggering, and the second layer of the first network entity is configured to output beam management messages. In some aspects, uplink event triggering is based on downlink communication associated with the second network entity.

[0149] In some aspects, beam management messages indicate at least one of an uplink event identifier or a downlink event identifier. In some aspects, uplink event triggering is associated with either an uplink event identifier or a downlink event identifier. In some aspects, beam management messages indicate whether uplink event triggering is associated with an uplink event or a downlink event.

[0150] Figure 8A diagram of a system 800 including device 805 supporting uplink-related event-triggered beam management, according to one or more aspects of this disclosure, is shown. Device 805 may be an example of device 505, device 605, or UE 115 as described herein, or may include components thereof. Device 805 may communicate with one or more other devices (e.g., network entity 105, UE 115, or a combination thereof) (e.g., wirelessly). Device 805 may include components for bidirectional voice and data communication, including components for transmitting and receiving communications, such as a communication manager 820, an input / output (I / O) controller (e.g., I / O controller 810), a transceiver 815, one or more antennas 825, at least one memory 830, code 835, and at least one processor 840. These components may communicate electronically or be otherwise coupled (e.g., operative ground, communicative ground, functional ground, electronic ground, electrical ground) via one or more buses (e.g., bus 845).

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

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

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

[0154] At least one processor 840 may include one or more intelligent hardware devices (e.g., one or more general-purpose processors, one or more DSPs, one or more central processing units (CPUs), one or more graphics processing units (GPUs), one or more neural processing units (NPUs) (also referred to as neural network processors or deep learning processors (DLPs)), one or more microcontrollers, one or more ASICs, one or more FPGAs, one or more programmable logic devices, discrete gate or transistor logic, one or more discrete hardware components, or any combination thereof). In some cases, at least one processor 840 may be configured to use a memory controller to operate a memory array. In some other cases, the memory controller may be integrated into at least one processor 840. At least one processor 840 may be configured to execute computer-readable instructions stored in memory (e.g., at least one memory 830) to cause device 805 to perform various functions (e.g., functions or tasks supporting uplink-related event-triggered beam management). For example, device 805 or components of device 805 may include at least one processor 840 and at least one memory 830 coupled to or coupled to at least one processor 840, the at least one processor 840 and the at least one memory 830 being configured to perform the various functions described herein. In some aspects, at least one processor 840 may include multiple processors, and at least one memory 830 may include multiple memories. One or more of the multiple processors may be coupled to one or more of the multiple memories, which may be configured individually or collectively to perform the various functions described herein. In some aspects, at least one processor 840 may be a component of a processing system, which may refer to a system of machines (such as a series of machines), circuits (including, for example, one or both of processor circuitry (which may include at least one processor 840) and memory circuitry (which may include at least one memory 830)) or components that receive or receive input and process the input to produce, generate, or obtain a set of outputs. The processing system may be configured to perform one or more of the functions described herein. For example, at least one processor 840 or a processing system including at least one processor 840 may be configured, capable of being configured, or operable to cause device 805 to perform one or more of the functions described herein. Furthermore, as described herein, “configured to,” “capable of being configured to,” and “capable of operating to” are used interchangeably and may be associated with the ability to perform one or more of the functions described herein when executing code 835 (e.g., processor-executable code) stored in at least one memory 830 or otherwise.

[0155] The communication manager 820 can support wireless communication according to examples disclosed herein. For example, the communication manager 820 is capable of, configured to, or operable to support components for detecting and associated with uplink event triggering for wireless communication with a second network entity, wherein the uplink event triggering is based on changes in one or more uplink communication parameters satisfying a threshold. The communication manager 820 is capable of, configured to, or operable to support components for outputting beam management messages to a second network entity based on uplink event triggering, wherein the beam management messages are associated with changes to the downlink beam for wireless communication with the second network entity. The communication manager 820 is capable of, configured to, or operable to support components for performing wireless communication with the second network entity using an updated downlink beam based on the beam management message.

[0156] By including or configuring a communication manager 820 according to an example as described herein, device 805 can support techniques for implementing UE-initiated beam reporting or beam management requests based on the detection of uplink-related event triggering.

[0157] In some aspects, the communication manager 820 may be configured to use or otherwise coordinate with the transceiver 815, one or more antennas 825, or any combination thereof to perform various operations (e.g., receiving, monitoring, transmitting). Although the communication manager 820 is illustrated as a separate component, in some aspects, one or more functions described with reference to the communication manager 820 may be supported or executed by at least one processor 840, at least one memory 830, code 835, or any combination thereof. For example, code 835 may include instructions that can be executed by at least one processor 840 to cause the device 805 to perform various aspects of uplink-related event-triggered beam management as described herein, or at least one processor 840 and at least one memory 830 may be otherwise configured to perform or support such operations individually or jointly.

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

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

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

[0161] The communication manager 920, receiver 910, transmitter 915, or various combinations or components thereof may be examples of components used to perform various aspects of uplink-related event-triggered beam management as described herein. For example, the communication manager 920, receiver 910, transmitter 915, or various combinations or components thereof may be able to perform one or more of the functions described herein.

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

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

[0164] In some respects, the communication manager 920 may be configured to use or otherwise cooperate with the receiver 910, transmitter 915, or both to perform various operations (e.g., receiving, acquiring, monitoring, outputting, transmitting). For example, the communication manager 920 may receive information from the receiver 910, transmit information to the transmitter 915, or be integrated in combination with the receiver 910, transmitter 915, or both to acquire information, output information, or perform various other operations as described herein.

[0165] Communication manager 920 may support wireless communication according to examples disclosed herein. For example, communication manager 920 may be capable of, configured to, or operable to support components for obtaining beam management messages triggered by uplink events based on and associated with wireless communication with a second network entity from a first network entity, wherein the uplink event triggers a change in one or more uplink communication parameters of the first network entity that satisfies a threshold. Communication manager 920 may be capable of, configured to, or operable to support components for obtaining beam management messages from a first network entity based on uplink event triggering, wherein the beam management messages are associated with a change in the downlink beam for wireless communication with the second network entity. Communication manager 920 may be capable of, configured to, or operable to support components for performing wireless communication with the first network entity using an updated downlink beam based on the beam management messages.

[0166] By including or configuring a communication manager 920 according to an example as described herein, device 905 (e.g., controlling receiver 910, transmitter 915, communication manager 920 or a combination thereof, or at least one processor otherwise coupled to them) can support techniques for implementing UE-initiated beam reporting or beam management requests based on the detection of uplink-related event triggering.

[0167] Figure 10 A block diagram 1000 of a device 1005 supporting uplink-related event-triggered beam management according to one or more aspects of this disclosure is shown. Device 1005 may be an example of aspects of device 905 or network entity 105 as described herein. Device 1005 may include receiver 1010, transmitter 1015, and communication manager 1020. Device 1005 or one or more components of device 1005 (e.g., receiver 1010, transmitter 1015, communication manager 1020) may include at least one processor that may be coupled to at least one memory to support the described techniques. Each of these components may communicate with each other (e.g., via one or more buses).

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

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

[0170] Device 1005 or its various components may be examples of parts for performing various aspects of uplink-related event-triggered beam management as described herein. For example, communication manager 1020 may include beam message manager 1025, event trigger manager 1030, update beam manager 1035, or any combination thereof. Communication manager 1020 may be examples of aspects of communication manager 920 as described herein. In some aspects, communication manager 1020 or its various components may be configured to use or otherwise cooperate with receiver 1010, transmitter 1015, or both to perform various operations (e.g., receiving, acquiring, monitoring, outputting, transmitting). For example, communication manager 1020 may receive information from receiver 1010, transmit information to transmitter 1015, or be integrated in combination with receiver 1010, transmitter 1015, or both to acquire information, output information, or perform various other operations as described herein.

[0171] Communication manager 1020 can support wireless communication according to examples disclosed herein. Beam message manager 1025 is capable of, configured to, or operable to support components for obtaining beam management messages triggered by uplink events based on and associated with wireless communication with a second network entity from a first network entity, wherein the uplink event triggers a change in one or more uplink communication parameters of the first network entity that satisfies a threshold. Event trigger manager 1030 is capable of, configured to, or operable to support components for obtaining beam management messages from a first network entity based on uplink event triggering, wherein the beam management messages are associated with a change in the downlink beam for wireless communication with the second network entity. Update beam manager 1035 is capable of, configured to, or operable to support components for performing wireless communication with the first network entity using an updated downlink beam based on beam management messages.

[0172] Figure 11 A block diagram 1100 of a communication manager 1120 supporting uplink-dependent event-triggered beam management according to one or more aspects of this disclosure is shown. The communication manager 1120 may be an example of a communication manager 920, a communication manager 1020, or aspects thereof as described herein. The communication manager 1120 or its various components may be examples of parts for performing various aspects of uplink-dependent event-triggered beam management as described herein. For example, the communication manager 1120 may include a beam message manager 1125, an event triggering manager 1130, an update beam manager 1135, a downlink beam manager 1140, or any combination thereof. Each of these components, or its components or sub-components (e.g., one or more processors, one or more memories), may communicate directly or indirectly with each other (e.g., via one or more buses). Communication may include communication within the protocol layers of the protocol stack, communication associated with logical channels of the protocol stack (e.g., between protocol layers of the protocol stack, within devices, components or virtualization components associated with network entity 105, between devices, components or virtualization components associated with network entity 105), or any combination thereof.

[0173] Communication manager 1120 can support wireless communication according to the examples disclosed herein. Beam message manager 1125 is capable of, configured to, or operable to support components for obtaining uplink event-triggered beam management messages triggered from a first network entity and associated with wireless communication with a second network entity, wherein the uplink event triggers a change in one or more uplink communication parameters of the first network entity that satisfies a threshold. Event trigger manager 1130 is capable of, configured to, or operable to support components for obtaining beam management messages from a first network entity based on uplink event triggering, wherein the beam management messages are associated with a change in the downlink beam for wireless communication with the second network entity. Update beam manager 1135 is capable of, configured to, or operable to support components for performing wireless communication with the first network entity using an updated downlink beam based on beam management messages.

[0174] In some aspects, the change in one or more uplink communication parameters includes one or more of the following: a change in uplink power, a change in uplink antenna, a change in cross-link interference associated with full-duplex communication, or a change in the flexibility of the time-division full-duplex scheme. In some aspects, the beam management message includes a beam report associated with the downlink beam. In some aspects, the beam report identifies a request for change to the downlink beam. In some aspects, the beam report indicates an updated downlink beam. In some aspects, the beam management message includes a beam management request associated with the downlink beam.

[0175] In some aspects, the downlink beam manager 1140 is capable of, configured to, or operable to support components for performing a downlink beam update procedure with a first network entity to identify the updated downlink beam. In some aspects, the beam management message indicates at least one of an uplink event identifier or a downlink event identifier. In some aspects, uplink event triggering is associated with either an uplink event identifier or a downlink event identifier. In some aspects, the beam management message indicates whether uplink event triggering is associated with an uplink event or a downlink event.

[0176] Figure 12A diagram of a system 1200 including device 1205 supporting uplink-related event-triggered beam management, according to one or more aspects of this disclosure, is shown. Device 1205 may be an example of device 905, device 1005, or network entity 105 as described herein, or may include components thereof. Device 1205 may communicate with other network devices or network equipment, such as one or more network entities in network entity 105, UE 115, or any combination thereof. Communication may include communication via one or more wired interfaces, one or more wireless interfaces, or any combination thereof. Device 1205 may include components supporting output and acquisition of communication, such as a communication manager 1220, one or more transceivers 1210, an antenna 1215, at least one memory 1225, code 1230, and at least one processor 1235. These components may communicate electronically or otherwise (e.g., operative ground, communication ground, functional ground, electronic ground, electrical ground) via one or more buses (e.g., bus 1240).

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

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

[0179] At least one processor 1235 may include one or more intelligent hardware devices (e.g., one or more general-purpose processors, one or more DSPs, one or more central processing units (CPUs), one or more graphics processing units (GPUs), one or more neural processing units (NPUs) (also referred to as neural network processors or deep learning processors (DLPs)), one or more microcontrollers, one or more ASICs, one or more FPGAs, one or more programmable logic devices, discrete gate or transistor logic, one or more discrete hardware components, or any combination thereof). In some cases, at least one processor 1235 may be configured to use a memory controller to operate a memory array. In some other cases, the memory controller may be integrated into one or more processors in at least one processor 1235. At least one processor 1235 may be configured to execute computer-readable instructions stored in memory (e.g., one or more memories in at least one memory 1225) to cause device 1205 to perform various functions (e.g., functions or tasks supporting uplink-related event-triggered beam management). For example, device 1205 or components thereof may include at least one processor 1235 and at least one memory 1225 coupled to one or more of the at least one processor 1235, the at least one processor 1235 and the at least one memory 1225 being configured to perform the various functions described herein. The at least one processor 1235 may be an example of a cloud computing platform (e.g., one or more physical nodes and supporting software such as an operating system, virtual machine, or container instance) that may (e.g., by executing code 1230) host functions for performing the functions of device 1205. The at least one processor 1235 may be any one or more suitable processors capable of executing scripts or instructions of one or more software programs stored in device 1205 (such as within one or more memories of at least one memory 1225). In some aspects, the at least one processor 1235 may include multiple processors, and the at least one memory 1225 may include multiple memories. One or more of the multiple processors may be coupled to one or more of the multiple memories, the multiple memories being configured individually or collectively to perform the various functions described herein. In some aspects, at least one processor 1235 may be a component of a processing system, which may refer to a system of machines (such as a series of machines), circuits (including, for example, one or both of processor circuitry (which may include at least one processor 1235) and memory circuitry (which may include at least one memory 1225)) or components that receive or obtain input and process the input to produce, generate or obtain a set of outputs. The processing system may be configured to perform one or more of the functions described herein.For example, at least one processor 1235 or a processing system including at least one processor 1235 may be configured, configured to, or operated to cause device 1205 to perform one or more of the functions described herein. Furthermore, as described herein, “configured to,” “configurable to,” and “operable to” are used interchangeably and may be associated with the ability to perform one or more of the functions described herein when executing code stored in at least one memory 1225 or otherwise.

[0180] In some aspects, bus 1240 may support communication at the protocol layer of the protocol stack (e.g., within a protocol layer). In some aspects, bus 1240 may support communication associated with logical channels of the protocol stack (e.g., between protocol layers of the protocol stack), which may include communication performed within components of device 1205, or communication performed between different components of device 1205 that are co-addressable or may be located in different locations (e.g., where device 1205 may refer to a system in which one or more of communication manager 1220, transceiver 1210, at least one memory 1225, code 1230 and at least one processor 1235 may be located in one component of different components or partitioned between different components).

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

[0182] Communication manager 1220 may support wireless communication according to examples disclosed herein. For example, communication manager 1220 may be capable of, configured to, or operable to support components for obtaining beam management messages triggered by uplink events based on and associated with wireless communication with a second network entity from a first network entity, wherein the uplink event triggers a change in one or more uplink communication parameters of the first network entity that satisfies a threshold. Communication manager 1220 may be capable of, configured to, or operable to support components for obtaining beam management messages from a first network entity based on uplink event triggering, wherein the beam management messages are associated with a change in the downlink beam for wireless communication with the second network entity. Communication manager 1220 may be capable of, configured to, or operable to support components for performing wireless communication with the first network entity using an updated downlink beam based on the beam management messages.

[0183] By including or configuring a communication manager 1220 according to an example as described herein, device 1205 can support techniques for implementing UE-initiated beam reporting or beam management requests based on the detection of uplink-related event triggering.

[0184] In some aspects, the communication manager 1220 may be configured to use or otherwise coordinate with the transceiver 1210, one or more antennas 1215 (e.g., where applicable), or any combination thereof to perform various operations (e.g., receiving, acquiring, monitoring, outputting, transmitting). Although the communication manager 1220 is illustrated as a separate component, in some aspects, one or more functions described with reference to the communication manager 1220 may be supported or performed by the transceiver 1210, one or more processors in at least one processor 1235, one or more memories in at least one memory 1225, code 1230, or any combination thereof (e.g., by a processing system including at least a portion of at least one processor 1235, at least one memory 1225, code 1230, or any combination thereof). For example, code 1230 may include instructions that can be executed by one or more processors in at least one processor 1235 to cause the device 1205 to perform various aspects of uplink-related event-triggered beam management as described herein, or at least one processor 1235 and at least one memory 1225 may be otherwise configured to perform or support such operations individually or jointly.

[0185] Figure 13 A flowchart illustrating a method 1300 for supporting uplink-related event-triggered beam management according to one or more aspects of this disclosure is shown. Operation of method 1300 may be implemented by a UE or its components as described herein. For example, operation of method 1300 may be implemented by, as referenced... Figures 1 to 8The UE 115 described herein is used to perform this function. In some aspects, the UE can execute a set of instructions to control the functional elements of the UE to perform the described function. Additionally or alternatively, the UE may use dedicated hardware to perform aspects of the described function.

[0186] At 1305, the method may include detecting and triggering an uplink event associated with wireless communication with a second network entity, wherein the uplink event triggering is based on a change in one or more uplink communication parameters satisfying a threshold. The operation of 1305 may be performed according to examples as disclosed herein. In some aspects, aspects of the operation of 1305 may be provided by reference to [reference needed]. Figure 7 The described event detection manager 725 is used to perform this.

[0187] At 1310, the method may include outputting a beam management message to a second network entity based on an uplink event trigger, wherein the beam management message is associated with a change to the downlink beam used for wireless communication with the second network entity. Operation of 1310 may be performed according to examples as disclosed herein. In some aspects, aspects of the operation of 1310 may be derived from references... Figure 7 The described beam message manager 730 is used to execute this.

[0188] At 1315, the method may include performing wireless communication with a second network entity using an updated downlink beam based on a beam management message. The operation of 1315 may be performed according to examples as disclosed herein. In some aspects, aspects of the operation of 1315 may be derived from references... Figure 7 The described update beam manager 735 is used to perform this.

[0189] Figure 14 A flowchart illustrating a method 1400 for supporting uplink-related event-triggered beam management according to one or more aspects of this disclosure is shown. Operation of method 1400 may be implemented by a UE or its components as described herein. For example, operation of method 1400 may be performed by, as referenced... Figures 1 to 8 The UE 115 described herein is used to perform this function. In some aspects, the UE can execute a set of instructions to control the functional elements of the UE to perform the described function. Additionally or alternatively, the UE may use dedicated hardware to perform aspects of the described function.

[0190] At 1405, the method may include detecting and triggering an uplink event associated with wireless communication with a second network entity, wherein the uplink event triggering is based on a change in one or more uplink communication parameters satisfying a threshold. The operation of 1405 may be performed according to examples as disclosed herein. In some aspects, aspects of the operation of 1405 may be derived from references... Figure 7 The described event detection manager 725 is used to perform this.

[0191] At 1410, the method may include outputting a beam management message to a second network entity based on an uplink event trigger, wherein the beam management message is associated with a change to the downlink beam used for wireless communication with the second network entity. Operation of 1410 may be performed according to examples as disclosed herein. In some aspects, aspects of the operation of 1410 may be derived from references... Figure 7 The described beam message manager 730 is used to execute this.

[0192] At 1415, the method may include performing a downlink beam update procedure with a second network entity based on beam management messages to identify the updated downlink beam. The operation of 1415 may be performed according to examples as disclosed herein. In some aspects, aspects of the operation of 1415 may be derived from references... Figure 7 The described update beam manager 735 is used to perform this.

[0193] At 1420, the method may include using an updated downlink beam to perform wireless communication with a second network entity. The operation of 1420 may be performed according to examples as disclosed herein. In some aspects, aspects of the operation of 1420 may be derived from references... Figure 7 The downlink beam manager 740 described herein is used to perform this action.

[0194] Figure 15 A flowchart illustrating a method 1500 for supporting uplink-related event-triggered beam management according to one or more aspects of this disclosure is shown. Operation of method 1500 may be implemented by a network entity or its components as described herein. For example, operation of method 1500 may be implemented by, as referenced... Figures 1 to 4 as well as Figures 9 to 12 The network entity described herein performs the function. In some aspects, the network entity may execute a set of instructions to control the functional elements of the network entity to perform the described function. Additionally or alternatively, the network entity may use dedicated hardware to perform aspects of the described function.

[0195] At 1505, the method may include obtaining from a first network entity an uplink event-triggered beam management message based on and associated with wireless communication with a second network entity, wherein the uplink event triggers a change in one or more uplink communication parameters based on the first network entity that satisfies a threshold. Operation of 1505 may be performed according to examples as disclosed herein. In some aspects, aspects of the operation of 1505 may be provided by reference to [reference needed]. Figure 11 The beam message manager 1125 described is used to execute this.

[0196] At 1510, the method may include obtaining a beam management message from a first network entity based on an uplink event trigger, wherein the beam management message is associated with a change to a downlink beam for wireless communication with a second network entity. Operation of 1510 may be performed according to examples as disclosed herein. In some aspects, aspects of the operation of 1510 may be derived from references... Figure 11 The event trigger manager 1130 described is used to execute this.

[0197] At 1515, the method may include performing wireless communication with the first network entity using an updated downlink beam based on a beam management message. The operation of 1515 may be performed according to examples as disclosed herein. In some aspects, aspects of the operation of 1515 may be derived from references... Figure 11 The described update beam manager 1135 is executed.

[0198] The following provides an overview of the various aspects of this disclosure: Aspect 1: A method for wireless communication performed by a first network entity, the method comprising: detecting an uplink event trigger associated with wireless communication with a second network entity, wherein the uplink event trigger is based on a change in one or more uplink communication parameters satisfying a threshold; outputting a beam management message to the second network entity based on the uplink event trigger, wherein the beam management message is associated with a change in a downlink beam for wireless communication with the second network entity; and performing wireless communication with the second network entity using the updated downlink beam based on the beam management message.

[0199] Aspect 2: According to the method of aspect 1, the change of one or more uplink communication parameters includes one or more of the following: change of uplink power, change of uplink antenna, change of cross-link interference associated with duplex communication, or change of flexibility of time division duplex scheme.

[0200] Aspect 3: The method according to any one of Aspects 1 to 2, wherein the beam management message includes a beam report associated with the downlink beam, and the beam report identifies a change request for the downlink beam.

[0201] Aspect 4: The method according to aspect 3, wherein the beam report indicates the updated downlink beam.

[0202] Aspect 5: The method according to any one of Aspects 1 to 4, wherein the beam management message includes a beam management request associated with the downlink beam.

[0203] Aspect 6: According to the method of aspect 5, the method further includes: performing a downlink beam update process with the second network entity to identify the updated downlink beam.

[0204] Aspect 7: The method according to any one of Aspects 1 to 6, wherein the first layer of the first network entity is configured to detect the uplink event triggering, and the second layer of the first network entity is configured to output the beam management message based on information from the first layer, and the first layer is a higher layer than the second layer.

[0205] Aspect 8: The method according to any one of Aspects 1 to 7, wherein the first layer of the first network entity is configured to detect the uplink event triggering, and the second layer of the first network entity is configured to output the beam management message, and the uplink event triggering is based on one or more reference signals associated with the second network entity.

[0206] Aspect 9: The method according to any one of Aspects 1 to 8, wherein the first layer of the first network entity is configured to detect the uplink event triggering, and the second layer of the first network entity is configured to output the beam management message, and the uplink event triggering is based on downlink communication associated with the second network entity.

[0207] Aspect 10: The method according to any one of Aspects 1 to 9, wherein the beam management message indicates at least one of an uplink event identifier or a downlink event identifier, and the uplink event trigger is associated with the uplink event identifier or the downlink event identifier.

[0208] Aspect 11: The method according to any one of Aspects 1 to 10, wherein the beam management message indicates whether the uplink event triggering is associated with an uplink event or with a downlink event.

[0209] Aspect 12: A method for wireless communication by a second network entity, the method comprising: obtaining from a first network entity a beam management message triggered by an uplink event based on and associated with wireless communication with the second network entity, wherein the uplink event trigger is based on a change in one or more uplink communication parameters of the first network entity satisfying a threshold; obtaining the beam management message from the first network entity based on the uplink event trigger, wherein the beam management message is associated with a change in a downlink beam for wireless communication with the second network entity; and performing wireless communication with the first network entity using the updated downlink beam based on the beam management message.

[0210] Aspect 13: According to the method of aspect 12, the change of one or more uplink communication parameters includes one or more of the following: change of uplink power, change of uplink antenna, change of cross-link interference associated with duplex communication, or change of flexibility of time division duplex scheme.

[0211] Aspect 14: The method according to any one of Aspects 12 to 13, wherein the beam management message includes a beam report associated with the downlink beam, and the beam report identifies a change request for the downlink beam.

[0212] Aspect 15: The method according to aspect 14, wherein the beam report indicates the updated downlink beam.

[0213] Aspect 16: The method according to any one of Aspects 12 to 15, wherein the beam management message includes a beam management request associated with the downlink beam.

[0214] Aspect 17: The method according to aspect 16, the method further comprising: performing a downlink beam update procedure with the first network entity to identify the updated downlink beam.

[0215] Aspect 18: The method according to any one of Aspects 12 to 17, wherein the beam management message indicates at least one of an uplink event identifier or a downlink event identifier, and the uplink event trigger is associated with the uplink event identifier or the downlink event identifier.

[0216] Aspect 19: The method according to any one of Aspects 12 to 18, wherein the beam management message indicates whether the uplink event triggering is associated with an uplink event or with a downlink event.

[0217] Aspect 20: A first network entity for wireless communication, the first network entity including a processing system configured to perform the method according to any one of aspects 1 to 11.

[0218] Aspect 21: A first network entity for wireless communication, the first network entity comprising at least one component for performing the method according to any one of aspects 1 to 11.

[0219] Aspect 22: A non-transitory computer-readable medium having stored thereon code for wireless communication, the code causing the first network entity to perform the method according to any one of aspects 1 to 11 when executed by the first network entity.

[0220] Aspect 23: A second network entity for wireless communication, the second network entity including a processing system configured to perform the method according to any one of aspects 12 to 19.

[0221] Aspect 24: A second network entity for wireless communication, the second network entity comprising at least one component for performing the method according to any one of aspects 12 to 19.

[0222] Aspect 25: A non-transitory computer-readable medium having stored thereon code for wireless communication, the code causing the second network entity to perform the method according to any one of aspects 12 to 19 when executed by the second network entity.

[0223] The methods described in this paper describe possible specific implementations, and the operations and steps can be rearranged or otherwise modified, and other specific implementations are also possible. Furthermore, aspects from two or more of these methods can be combined.

[0224] While aspects of LTE, LTE-A, LTE-A Pro, or NR systems may be described for illustrative purposes, and the terms LTE, LTE-A, LTE-A Pro, or NR may be used in most of the description, the techniques described herein are also applicable to networks outside of LTE, LTE-A, LTE-A Pro, or NR networks. For example, the techniques described can be applied to a variety of other wireless communication systems, such as Ultra Mobile Broadband (UMB), IEEE 802.11 (Wi-Fi), IEEE 802.16 (WiMAX), IEEE 802.20, Flash-OFDM, and other systems and radio technologies not explicitly mentioned herein.

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

[0226] The various exemplary blocks and components described in connection with this disclosure can be implemented or performed using a general-purpose processor, DSP, ASIC, CPU, graphics processing unit (GPU), neural processing unit (NPU), FPGA or other programmable logic device, discrete gate or transistor logic unit, discrete hardware component, or any combination thereof designed to perform the functions described herein. A general-purpose processor may be a microprocessor, but in alternative embodiments, a processor may be any processor, controller, microcontroller, or state machine. A processor may also be implemented as a combination of computing devices (e.g., a combination of a DSP and a microprocessor, multiple microprocessors, one or more microprocessors combined with a DSP core, or any other such configuration). Any function or operation described herein that can be performed by a processor may be performed by multiple processors capable of performing the described function or operation individually or jointly.

[0227] The functions described herein can be implemented using hardware, software executed by a processor, firmware, or any combination thereof. When implemented using software executed by a processor, the functions can be stored as one or more instructions or code on a computer-readable medium or transmitted using one or more instructions or code on a computer-readable medium. Other examples and specific implementations are within the scope of this disclosure and the claims. For example, due to the nature of software, the functions described herein can be implemented using software executed by a processor, hardware, firmware, hardwiring, or any combination of these. Features implementing the functions can also be physically located in various locations, including portions distributed such that the functions are implemented in different physical locations.

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

[0229] As used herein, the term "or" is inclusive unless restrictive language is used relative to the listed alternatives. For example, a reference to "X is based on A or B" should be interpreted as including, within its scope, X is based on A, X is based on B, and X is based on both A and B. In this respect, a reference to "X is based on A or B" means "at least one of A or B" or "one or more of A or B," because "or" is inclusive. Similarly, a reference to "X is based on A, B, or C" should be interpreted as including, within its scope, X is based on A, X is based on B, X is based on C, X is based on both A and B, X is based on both A and C, X is based on both B and C, and X is based on both A, B, and C. In this respect, a reference to "X is based on A, B, or C" means "at least one of A, B, or C" or "one or more of A, B, or C," because "or" is inclusive. As an example of restrictive language, the reference to "X is based on either A or B" should be interpreted as including, within its scope, both X based on A and X based on B, but excluding X based on both A and B. Furthermore, as used herein, the phrase "based on" should not be interpreted as a reference to a closed set of information, one or more conditions, one or more factors, etc. In other words, the phrase "based on A" (where "A" can be information, conditions, factors, etc.) should be interpreted as "based on at least A," unless specifically stated differently. Moreover, as used herein, the phrase "set" should be understood to include the possibility of a set having one member. That is, the phrase "set" should be interpreted in the same way as "one or more" or "at least one."

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

[0231] The term "determine" encompasses a variety of actions, and therefore, "determine" can include calculation, computation, processing, derivation, investigation, searching (such as by searching in a table, database, or other data structure), ascertainment, etc. Furthermore, "determine" can include receiving (e.g., receiving information), accessing (e.g., accessing data stored in memory), etc. Moreover, "determine" can include parsing, acquiring, selecting, choosing, creating, and other similar actions.

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

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

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

Claims

1. A first network entity, the first network entity comprising: Processing system, the processing system being configured to: Detection and uplink event triggering associated with wireless communication with a second network entity, wherein the uplink event triggering is based on changes in one or more uplink communication parameters satisfying a threshold; Based on the uplink event triggering, a beam management message is output to the second network entity, wherein the beam management message is associated with a change to the downlink beam used for wireless communication with the second network entity; as well as Based on the beam management message, an updated downlink beam is used to perform wireless communication with the second network entity.

2. The first network entity of claim 1, wherein the change in one or more uplink communication parameters includes one or more of the following: a change in uplink power, a change in uplink antenna, a change in cross-link interference associated with full-duplex communication, or a change in the flexibility of the time-division full-duplex scheme.

3. The first network entity of claim 1, wherein the beam management message includes a beam report associated with the downlink beam, and wherein the beam report identifies a change request for the downlink beam.

4. The first network entity of claim 3, wherein the beam report indicates the updated downlink beam.

5. The first network entity of claim 1, wherein the beam management message includes a beam management request associated with the downlink beam.

6. The first network entity according to claim 5, wherein the processing system is configured to: Perform a downlink beam update procedure with the second network entity to identify the updated downlink beam.

7. The first network entity of claim 1, wherein a first layer of the first network entity is configured to detect the uplink event triggering, and a second layer of the first network entity is configured to output the beam management message based on information from the first layer, and wherein the first layer is a higher layer than the second layer.

8. The first network entity of claim 1, wherein a first layer of the first network entity is configured to detect the uplink event triggering, and a second layer of the first network entity is configured to output the beam management message, and wherein the uplink event triggering is based on one or more reference signals associated with the second network entity.

9. The first network entity of claim 1, wherein a first layer of the first network entity is configured to detect the uplink event triggering, and a second layer of the first network entity is configured to output the beam management message, and wherein the uplink event triggering is based on downlink communication associated with the second network entity.

10. The first network entity of claim 1, wherein the beam management message indicates at least one of an uplink event identifier or a downlink event identifier, and wherein the uplink event trigger is associated with the uplink event identifier or the downlink event identifier.

11. The first network entity of claim 1, wherein the beam management message indicates whether the uplink event triggering is associated with an uplink event or with a downlink event.

12. A second network entity, the second network entity comprising: Processing system, the processing system being configured to: A beam management message is obtained from a first network entity that is triggered by an uplink event based on and associated with a wireless communication with a second network entity, wherein the uplink event triggers a change in one or more uplink communication parameters of the first network entity that satisfies a threshold. A beam management message is obtained from the first network entity based on the uplink event triggering, wherein the beam management message is associated with a change in the downlink beam for wireless communication with the second network entity. as well as Based on the beam management message, an updated downlink beam is used to perform wireless communication with the first network entity.

13. The second network entity of claim 12, wherein the change in one or more uplink communication parameters includes one or more of the following: a change in uplink power, a change in uplink antenna, a change in cross-link interference associated with full-duplex communication, or a change in the flexibility of the time-division full-duplex scheme.

14. The second network entity of claim 12, wherein the beam management message includes a beam report associated with the downlink beam, and wherein the beam report identifies a change request for the downlink beam.

15. The second network entity of claim 14, wherein the beam report indicates the updated downlink beam.

16. The second network entity of claim 12, wherein the beam management message includes a beam management request associated with the downlink beam.

17. The second network entity of claim 16, wherein the processing system is configured to: Perform a downlink beam update procedure with the first network entity to identify the updated downlink beam.

18. The second network entity of claim 12, wherein the beam management message indicates at least one of an uplink event identifier or a downlink event identifier, and wherein the uplink event trigger is associated with the uplink event identifier or the downlink event identifier.

19. The second network entity of claim 12, wherein the beam management message indicates whether the uplink event triggering is associated with an uplink event or with a downlink event.

20. A method for wireless communication performed by a first network entity, the method comprising: Detection and uplink event triggering associated with wireless communication with a second network entity, wherein the uplink event triggering is based on changes in one or more uplink communication parameters satisfying a threshold; Based on the uplink event triggering, a beam management message is output to the second network entity, wherein the beam management message is associated with a change to the downlink beam used for wireless communication with the second network entity; as well as Based on the beam management message, an updated downlink beam is used to perform wireless communication with the second network entity.

Images