Signaling for channel access using multi-beam sensing

Abstract

Methods, systems, and devices for wireless communication are described. Some wireless communication systems can support signaling for channel access using multi-beam sensing. In some cases, a user equipment (UE) can transmit a capability message indicating a capability of the UE to support a per-beam channel access procedure for communicating in one or more shared radio frequency spectrums. In some cases, the UE can receive a control message from a network entity indicating a channel occupancy configuration associated with the per-beam channel access procedure. Additionally, the UE can perform a per-beam channel access procedure for each beam in the set of beams, and can communicate via one or more beams from the set of beams based on the channel occupancy configuration and the per-beam channel access procedure being successful for at least one subset of beams of the set of beams.

Description

[0001] Cross-references

[0002] This patent application claims priority to U.S. patent application No. 18 / 312,299, entitled “SIGNALING FOR CHANNEL ACCESS USING MULTI-BEAM SENSING,” filed by CHANDE et al. on May 4, 2023, which claims the benefit of U.S. provisional patent application No. 63 / 339,329, entitled “SIGNALING FOR CHANNEL ACCESS USING MULTI-BEAM SENSING,” filed by CHANDE et al. on May 6, 2022, each of which is assigned to the assignee of this application. Technical Field

[0003] The following relates to wireless communications, including signaling for channel access using multi-beam sensing. Background Art

[0004] Wireless communication systems are widely deployed to provide various types of communication content, such as voice, video, packet data, messaging, broadcast, and the like. These systems may be able to support communication with multiple users by sharing available system resources (e.g., time, frequency, and power). Examples of such multiple access systems include fourth generation (4G) systems (such as long term evolution (LTE) systems, advanced LTE (LTE-A) systems, or LTE-A Pro systems) and fifth generation (5G) systems (which may be referred to as new radio (NR) systems). These systems may employ 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 spread orthogonal frequency division multiplexing (DFT-S-OFDM). A wireless multiple access communication system may include one or more base stations, each of which supports wireless communication for a communication device, which may be referred to as a user equipment (UE). Summary of the invention

[0005] The described techniques relate to improved methods, systems, devices, and apparatuses that support signaling for channel access using multi-beam sensing. In general, the techniques described herein may enable a user equipment (UE) to send an indication of the UE's ability to support per-beam channel access procedures. Additionally or alternatively, the described techniques may enable the UE to receive an indication of a channel occupancy configuration associated with a per-beam channel access procedure. For example, the UE may send a capability message indicating the UE's ability to support per-beam channel access procedures for communication in one or more shared (e.g., unlicensed) radio frequency spectrum bands. The capability message may include an indication of a threshold (e.g., maximum) number of simultaneous per-beam channel access procedures supported by the UE. Additionally or alternatively, the UE may receive a control message indicating a channel occupancy configuration associated with a per-beam channel access procedure. In this case, the channel occupancy configuration may enable or disable the UE's ability to communicate on a channel during a channel occupancy time (COT) only when a subset of beams from a set of beams is associated with a successful per-beam channel access procedure. In some cases, the UE may (e.g., based on the capabilities of the UE) perform a per-beam channel access procedure on each beam from a set of beams and may communicate via one or more beams based on the channel occupancy configuration and the per-beam channel access procedure being successful on at least that subset of beams.

[0006] A method for wireless communication at a UE is described. The method may include: receiving a control message indicating a channel occupancy configuration associated with a per-beam channel access procedure for communicating in one or more shared radio frequency spectrum bands; performing a per-beam channel access procedure for each beam in a set of multiple beams; and communicating via one or more beams from the set of multiple beams based on the channel occupancy configuration and the per-beam channel access procedure being successful for at least one subset of beams in the set of multiple beams.

[0007] An apparatus for wireless communication at a UE is described. The apparatus may include a processor, a memory coupled to the processor, and instructions stored in the memory. The instructions may be executable by the processor to cause the apparatus to: receive a control message indicating a channel occupancy configuration associated with a per-beam channel access procedure for communicating in one or more shared radio frequency spectrum bands; perform a per-beam channel access procedure for each beam in a set of multiple beams; and communicate via one or more beams from the set of multiple beams based on the channel occupancy configuration and the per-beam channel access procedure being successful for at least one subset of beams in the set of multiple beams.

[0008] Another apparatus for wireless communication at a UE is described. The method may include: means for receiving a control message indicating a channel occupancy configuration associated with a per-beam channel access procedure for communicating in one or more shared radio frequency spectrum bands; means for performing a per-beam channel access procedure for each beam in a set of multiple beams; and means for communicating via one or more beams from the set of multiple beams based on the channel occupancy configuration and the per-beam channel access procedure being successful for at least one subset of beams in the set of multiple beams.

[0009] A non-transitory computer-readable medium storing code for wireless communication at a UE is described. The code may include instructions executable by a processor to: receive a control message indicating a channel occupancy configuration associated with a per-beam channel access procedure for communicating in one or more shared radio frequency spectrum bands; perform a per-beam channel access procedure for each beam in a set of multiple beams; and communicate via one or more beams from the set of multiple beams based on the channel occupancy configuration and the per-beam channel access procedure is successful for at least one subset of beams in the set of multiple beams.

[0010] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, communicating via one or more beams may include operations, features, components, or instructions for performing the following operations: based on the per-beam channel access procedure being successful for the beam subset, communicating on a channel during the COT, the one or more beams including the beam subset.

[0011] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, the channel occupancy configuration enables use of the COT by the UE only when the beam subset can have a successful per-beam channel access procedure.

[0012] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, communicating via the one or more beams may include operations, features, components, or instructions for performing the following operations: communicating on a channel during a COT based on the per-beam channel access procedure being successful for each beam in the set of multiple beams, the one or more beams comprising the set of multiple beams.

[0013] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, the channel occupancy configuration disables use of the COT by the UE only when the beam subset can have a successful per-beam channel access procedure.

[0014] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, executing the per-beam channel access procedure may include operations, features, components, or instructions for performing the following operations: executing the per-beam channel access procedure for each beam in the set of multiple beams based on one or more timers associated with the per-beam channel access procedure, wherein the UE determines that the per-beam channel access procedure may be successful when the one or more timers expire.

[0015] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, the control message includes an indication of the one or more timers associated with the per-beam channel access procedure.

[0016] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, receiving the control message may include operations, features, components, or instructions for performing the following operations: receiving a radio resource control message indicating the channel occupancy configuration, the channel occupancy configuration including a UE-specific configuration for the UE.

[0017] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, receiving the control message may include operations, features, components, or instructions for performing the following operations: receiving a system information message indicating the channel occupancy configuration, the channel occupancy configuration including a cell-specific configuration for a cell provided by a network entity.

[0018] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, the channel occupancy configuration can be based on service type, one or more other wireless devices communicating with the UE, the number of wireless devices in the same cell as the UE, or any combination thereof.

[0019] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, the channel occupancy configuration can be based on a radio access technology (RAT) used by one or more network entities or wireless devices to communicate in the one or more shared radio frequency spectrum bands.

[0020] Some examples of the methods, apparatus, and non-transitory computer-readable media described herein may also include operations, features, components, or instructions for performing the following operations: sending a capability message indicating the UE's ability to support the per-beam channel access procedure, wherein receiving the control message may be based on the capability message.

[0021] A method for wireless communication at a UE is described. The method may include: sending a capability message indicating the UE's ability to support a per-beam channel access procedure for communicating in one or more shared radio frequency spectrum bands; performing a per-beam channel access procedure for one or more beams in a set of multiple beams according to the capability; and communicating via the one or more beams based on the per-beam channel access procedure being successful.

[0022] An apparatus for wireless communication at a UE is described. The apparatus may include a processor, a memory coupled to the processor, and instructions stored in the memory. The instructions may be executable by the processor to cause the apparatus to: send a capability message indicating the UE's ability to support a per-beam channel access procedure for communicating in one or more shared radio frequency spectrum bands; perform a per-beam channel access procedure for one or more beams in a set of multiple beams according to the capability; and communicate via the one or more beams based on the per-beam channel access procedure being successful.

[0023] Another apparatus for wireless communication at a UE is described. The apparatus may include: means for sending a capability message indicating the UE's ability to support a per-beam channel access procedure for communicating in one or more shared radio frequency spectrum bands; means for performing a per-beam channel access procedure for one or more beams in a set of multiple beams based on the capability; and means for communicating via the one or more beams based on the per-beam channel access procedure being successful.

[0024] A non-transitory computer-readable medium storing code for wireless communication at a UE is described. The code may include instructions executable by a processor to: send a capability message indicating the UE's ability to support a per-beam channel access procedure for communicating in one or more shared radio frequency spectrum bands; perform a per-beam channel access procedure for one or more beams in a set of multiple beams according to the capability; and communicate via the one or more beams based on the per-beam channel access procedure being successful.

[0025] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, sending the capability message may include operations, features, components, or instructions for performing the following operations: sending an indication of a threshold number of simultaneous per-beam channel access procedures supported by the UE within the capability message.

[0026] In some examples of the methods, devices, and non-transitory computer-readable media described herein, the indication includes a first threshold number of simultaneous channel access procedures per beam associated with a first type of channel access procedure, a second threshold number of simultaneous channel access procedures per beam associated with a second type of channel access procedure, a third threshold number of simultaneous channel access procedures per beam associated with a third type of channel access procedure, or any combination thereof.

[0027] Some examples of the methods, apparatuses, and non-transitory computer-readable media described herein may further include operations, features, means, or instructions for receiving a control message indicating a channel occupancy configuration that may be associated with the per-beam channel access procedure.

[0028] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, the per-beam channel access procedure can be successful for a subset of beams of the set of multiple beams, and the subset of beams can be used to enable use of a COT by the UE based on the channel occupancy configuration only when the subset of beams can have a successful per-beam channel access procedure, during which communication is performed.

[0029] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, the per-beam channel access procedure can be successful for each beam in the set of multiple beams, and the set of multiple beams can be used to disable use of the COT by the UE based on the channel occupancy configuration only when a subset of beams from the set of multiple beams can have a successful per-beam channel access procedure, during which communication is performed.

[0030] A method of wireless communication at a network entity is described. The method may include: sending a control message indicating a channel occupancy configuration associated with a per-beam channel access procedure for communicating in one or more shared radio frequency spectrum bands; and communicating with a UE via one or more beams from a set of multiple beams based on the channel occupancy configuration.

[0031] An apparatus for wireless communication at a network entity is described. The apparatus may include a processor, a memory coupled to the processor, and instructions stored in the memory. The instructions may be executable by the processor to cause the apparatus to: send a control message indicating a channel occupancy configuration associated with a per-beam channel access procedure for communicating in one or more shared radio frequency spectrum bands; and based on the channel occupancy configuration, communicate with a UE via one or more beams from a set of multiple beams.

[0032] Another apparatus for wireless communication at a network entity is described. The apparatus may include: means for sending a control message indicating a channel occupancy configuration associated with a per-beam channel access procedure for communicating in one or more shared radio frequency spectrum bands; and means for communicating with a UE via one or more beams from a set of multiple beams based on the channel occupancy configuration.

[0033] A non-transitory computer-readable medium storing code for wireless communication at a network entity is described. The code may include instructions executable by a processor to: send a control message indicating a channel occupancy configuration associated with a per-beam channel access procedure for communicating in one or more shared radio frequency spectrum bands; and communicate with a UE via one or more beams from a set of multiple beams based on the channel occupancy configuration.

[0034] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, communicating via the one or more beams may include operations, features, components, or instructions for performing the following operations: based on the channel occupancy configuration, communicating on the channel during the COT, the one or more beams comprising a subset of beams from the set of the multiple beams.

[0035] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, the channel occupancy configuration enables use of the COT by the UE only when the beam subset can have a successful per-beam channel access procedure.

[0036] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, communicating via the one or more beams may include operations, features, components, or instructions for performing the following operations: based on the channel occupancy configuration, communicating on the channel during the COT, the one or more beams comprising a set of the multiple beams.

[0037] In some examples of the methods, apparatus and non-transitory computer-readable media described herein, the channel occupancy configuration disables use of the COT by the UE only when a subset of beams can have a successful per-beam channel access procedure.

[0038] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, sending the control message may include operations, features, components, or instructions for performing the following operations: sending an indication of one or more timers associated with the per-beam channel access procedure, wherein the control message includes the indication.

[0039] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, sending the control message may include operations, features, components, or instructions for performing the following operations: sending a radio resource control message indicating the channel occupancy configuration, the channel occupancy configuration including a UE-specific configuration for the UE.

[0040] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, sending the control message may include operations, features, components, or instructions for performing the following operations: sending a system information message indicating the channel occupancy configuration, the channel occupancy configuration including a cell-specific configuration for a cell provided by the network entity.

[0041] Some examples of the methods, apparatus, and non-transitory computer-readable media described herein may also include operations, features, components, or instructions for identifying the presence of one or more other network entities or wireless devices communicating in the one or more shared radio frequency spectrum bands, wherein the channel occupancy configuration may be based on the RAT used by each of the one or more other network entities or wireless devices.

[0042] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, the channel occupancy configuration can be based on service type, one or more other wireless devices communicating with the UE, the number of wireless devices in the same cell as the UE, or any combination thereof.

[0043] Some examples of the methods, apparatus, and non-transitory computer-readable media described herein may also include operations, features, components, or instructions for performing the following operations: receiving a capability message indicating the UE's ability to support the per-beam channel access procedure, wherein receiving the control message may be based on the capability message.

[0044] A method of wireless communication at a network entity is described. The method may include: receiving a capability message indicating an ability of a UE to support a per-beam channel access procedure for communicating in one or more shared radio frequency spectrum bands; and based on the capability, communicating with the UE via one or more beams from a set of multiple beams.

[0045] An apparatus for wireless communication at a network entity is described. The apparatus may include a processor, a memory coupled to the processor, and instructions stored in the memory. The instructions may be executable by the processor to cause the apparatus to: receive a capability message indicating an ability of a UE to support a per-beam channel access procedure for communicating in one or more shared radio frequency spectrum bands; and based on the capability, communicate with the UE via one or more beams from a set of multiple beams.

[0046] Another apparatus for wireless communication at a network entity is described. The apparatus may include: means for receiving a capability message indicating an ability of a UE to support a per-beam channel access procedure for communicating in one or more shared radio frequency spectrum bands; and means for communicating with the UE via one or more beams from a set of multiple beams based on the capability.

[0047] A non-transitory computer-readable medium storing code for wireless communication at a network entity is described. The code may include instructions executable by a processor to: receive a capability message indicating an ability of a UE to support a per-beam channel access procedure for communicating in one or more shared radio frequency spectrum bands; and based on the capability, communicate with the UE via one or more beams from a set of multiple beams.

[0048] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, receiving the capability message may include operations, features, components, or instructions for performing the following operations: receiving within the capability message an indication of a threshold number of simultaneous per-beam channel access procedures supported by the UE.

[0049] In some examples of the methods, devices, and non-transitory computer-readable media described herein, the indication includes a first threshold number of simultaneous channel access procedures per beam associated with a first type of channel access procedure, a second threshold number of simultaneous channel access procedures per beam associated with a second type of channel access procedure, a third threshold number of simultaneous channel access procedures per beam associated with a third type of channel access procedure, or any combination thereof.

[0050] Some examples of the methods, apparatuses, and non-transitory computer-readable media described herein may further include operations, features, means, or instructions for sending a control message indicating a channel occupancy configuration that may be associated with the per-beam channel access procedure.

[0051] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, a beam subset of the set of multiple beams can be used to enable use of a COT by the UE based on the channel occupancy configuration only when the beam subset can have a successful per-beam channel access procedure, during which communication is performed.

[0052] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, the set of multiple beams can be used to disable use of the COT by the UE based on the channel occupancy configuration only when a subset of beams from the set of multiple beams can have a successful per-beam channel access procedure during which communication is performed.

[0053] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, the channel occupancy configuration can be based on a RAT used by one or more network entities or wireless devices to communicate in the one or more shared radio frequency spectrum bands.

[0054] Some examples of the methods, apparatus, and non-transitory computer-readable media described herein may also include operations, features, components, or instructions for identifying the presence of one or more other network entities or wireless devices communicating in the one or more shared radio frequency spectrum bands, wherein the channel occupancy configuration may be based on the RAT used by each of the one or more other network entities or wireless devices. BRIEF DESCRIPTION OF THE DRAWINGS

[0055] 1 illustrates an example of a wireless communication system supporting signaling for channel access using multi-beam sensing according to one or more aspects of the present disclosure.

[0056] 2A, 2B, and 3 illustrate examples of channel access procedures that support signaling for channel access using multi-beam sensing according to one or more aspects of the present disclosure.

[0057] 4 illustrates an example of a process flow in a system supporting signaling for channel access using multi-beam sensing in accordance with one or more aspects of the present disclosure.

[0058] 5 and 6 illustrate block diagrams of devices supporting signaling for channel access using multi-beam sensing according to one or more aspects of the present disclosure.

[0059] 7 illustrates a block diagram of a communications manager that supports signaling for channel access using multi-beam sensing in accordance with one or more aspects of the present disclosure.

[0060] 8 illustrates a diagram of a system including a device supporting signaling for channel access using multi-beam sensing in accordance with one or more aspects of the present disclosure.

[0061] 9 and 10 illustrate block diagrams of devices supporting signaling for channel access using multi-beam sensing according to one or more aspects of the present disclosure.

[0062] 11 illustrates a block diagram of a communications manager that supports signaling for channel access using multi-beam sensing in accordance with one or more aspects of the present disclosure.

[0063] 12 illustrates a diagram of a system including a device supporting signaling for channel access using multi-beam sensing in accordance with one or more aspects of the present disclosure.

[0064] 13 to 16 show flow charts illustrating methods of signaling supporting channel access using multi-beam sensing according to one or more aspects of the present disclosure. DETAILED DESCRIPTION

[0065] Some wireless communication systems may support channel access procedures, such as a listen-before-talk (LBT) procedure or other channel sensing procedures. For example, a wireless device (e.g., user equipment (UE), network entity) may perform an LBT procedure to identify the presence of other signals on a channel in a shared radio frequency spectrum band (e.g., an unlicensed band) to determine whether the wireless device can communicate on the channel (e.g., determine whether the channel is busy). Additionally, some wireless communication systems may support per-beam channel access procedures, such as per-beam LBT procedures. For example, a wireless device may perform independent per-beam sensing of each beam in a set of two or more beams to be used during a channel occupation time (COT). In some cases, the wireless device may simultaneously perform an independent per-beam LBT procedure on each beam in the beam set, such that the success of a failure of a per-beam LBT procedure on a first beam in the beam set may not depend on the success or failure of a per-beam LBT procedure on a second beam in the beam set.

[0066] In some cases, the per-beam LBT procedure may be successful for a subset of beams in a beam set. In this case, the wireless device may determine whether to communicate on the channel during the COT via the subset of beams associated with the successful per-beam channel access procedure. In other examples, the wireless device may determine to avoid communicating on the channel during the COT until the per-beam channel access procedure is successful for each beam in the beam set (e.g., until the wireless device can communicate on the channel via the full beam set). However, in some cases, the network entity may be unaware of the determination made by the UE, which may result in communication inefficiencies.

[0067] The techniques described herein may support signaling for channel access using multi-beam sensing. For example, a UE may send an indication to a network entity of the UE's ability to support a per-beam channel access procedure (e.g., a per-beam LBT procedure). The capability message may include an indication of a threshold (e.g., maximum) number of simultaneous per-beam channel access procedures supported by the UE. In this case, the UE may perform a per-beam sensing procedure (e.g., an LBT procedure) for each beam in a beam set to determine whether any beam (and corresponding resources) are available for communication with another device (e.g., another UE, a network entity).

[0068] Additionally or alternatively, the UE may receive an indication of a channel occupancy configuration (e.g., Subset-BeamsCOT) associated with a per-beam channel access procedure. The channel occupancy configuration may enable or disable the UE's ability to communicate on a channel via a subset of beams during a COT only when a subset of beams from a set of two or more beams has a successful per-beam channel access procedure. For example, the UE may (e.g., based on the UE's capabilities) perform a per-beam channel access procedure on each beam from a set of two or more beams, and the per-beam channel access procedure may be successful on a subset of beams in the set of beams. In some cases, the UE may enable use of COT when a per-beam channel access procedure is successful for a subset of beams based on the channel occupancy configuration, during which COT communication is performed on a channel via a subset of beams (e.g., beams with successful channel access procedures). Among some other reasons, the UE may disable use of COT when the per-beam channel access procedure is successful for a subset of beams based on the channel occupancy configuration, avoiding communication on the channel until the per-beam channel access procedure is successful for every beam in the set of beams.

[0069] Aspects of the present disclosure are first described in the context of wireless communication systems. Aspects of the present disclosure are then described in the context of channel access procedures and process flows. Aspects of the present disclosure are further illustrated and described by and with reference to apparatus diagrams, system diagrams, and flow diagrams related to signaling for channel access using multi-beam sensing.

[0070] 1 illustrates an example of a wireless communication system 100 that supports signaling for channel access using multi-beam sensing according to one or more aspects of the present disclosure. The wireless communication system 100 may include one or more network entities 105, one or more UEs 115, and a core network 130. In some examples, the wireless communication system 100 may be a long term evolution (LTE) network, an advanced LTE (LTE-A) network, an LTE-A Pro network, a new radio (NR) network, or a network operating according to other systems and radio technologies (including future systems and radio technologies not explicitly mentioned herein).

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

[0072] UE 115 can be dispersed throughout the coverage area 110 of the wireless communication system 100, and each UE 115 can be stationary or mobile or stationary and mobile at different times. UE 115 can be a device in different forms or with different capabilities. Some example UE 115 are illustrated in FIG. 1. The UE 115 described herein can communicate with various types of devices (such as other UE 115 or network entity 105 as shown in FIG. 1).

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

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

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

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

[0077] The split of functions between CU 160, DU 165, and RU 170 is flexible and may support different functions depending on which functions (e.g., network layer functions, protocol layer functions, baseband functions, RF functions, and any combination thereof) are performed at CU 160, DU 165, and RU 170. For example, a functional split of a protocol stack may be employed between CU 160 and DU 165 such that CU 160 may support one or more layers of a protocol stack and DU 165 may support one or more different layers of a protocol stack. In some examples, CU 160 may host higher protocol layer (e.g., Layer 3 (L3), Layer 2 (L2)) functions and signaling (e.g., Radio Resource Control (RRC), Service Data Adaptation Protocol (SDAP), Packet Data Convergence Protocol (PDCP)). The CU 160 may be connected to one or more DUs 165 or RUs 170, and the one or more DUs 165 or RUs 170 may host lower protocol layers, such as layer 1 (L1) (e.g., physical (PHY) layer) or L2 (e.g., radio link control (RLC) layer, medium access control (MAC) layer) functions and signaling, and may each be at least partially controlled by the CU 160. Additionally or alternatively, a functional split of the protocol stack may be employed between the DU 165 and the RU 170, such that the DU 165 may support one or more layers of the protocol stack, and the RU 170 may support one or more different layers of the protocol stack. The DU 165 may support one or more different cells (e.g., via one or more RUs 170). In some cases, the functional split between CU 160 and DU 165 or between DU 165 and RU 170 may be within the protocol layer (e.g., some functions of the protocol layer may be performed by one of CU 160, DU 165, or RU 170, while other functions of the protocol layer are performed by the other of CU 160, DU 165, or RU 170). CU 160 may be further functionally split into CU control plane (CU-CP) functions and CU user plane (CU-UP) functions. CU 160 may be connected to one or more DUs 165 via midhaul communication links 162 (e.g., F1, F1-c, F1-u), and DU 165 may be connected to one or more RUs 170 via fronthaul communication links 168 (e.g., open fronthaul (FH) interface). In some examples, midhaul communication link 162 or fronthaul communication link 168 may be implemented according to interfaces (eg, channels) between layers of a protocol stack supported by respective network entities 105 communicating over those communication links.

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

[0079] In the case where the techniques described herein are applied to the context of a disaggregated RAN architecture, one or more components of the disaggregated RAN architecture may be configured to support signaling for channel access using multi-beam sensing as described herein. For example, some operations described as being performed by a UE 115 or a network entity 105 (e.g., a base station 140) may additionally or alternatively be performed by one or more components of the disaggregated RAN architecture (e.g., an IAB node 104, a DU 165, a CU 160, a RU 170, a RIC 175, a SMO 180).

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

[0081] The UE 115 described herein may be able to communicate with various types of devices, such as other UEs 115 that may sometimes act as relays, as well as network entities 105 and network equipment including macro eNBs or gNBs, small cell eNBs or gNBs, relay base stations, etc., as shown in FIG. 1 .

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

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

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

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

[0086] The signal waveform sent on the carrier may include multiple subcarriers (e.g., using multi-carrier modulation (MCM) techniques, such as orthogonal frequency division multiplexing (OFDM) or discrete Fourier transform spread OFDM (DFT-S-OFDM)). In a system that employs MCM techniques, a resource element may refer to a resource of one symbol period (e.g., the duration of one modulation symbol) and one subcarrier, in which case the symbol period and subcarrier spacing may be inversely related. The amount of bits carried by each resource element may depend on the modulation scheme (e.g., the order of the modulation scheme, the coding rate of the modulation scheme, or both), so that the more resource elements a device receives and the higher the order of the modulation scheme, the higher the data rate for the device may be. Wireless communication resources may refer to a combination of RF spectrum resources, time resources, and spatial resources (e.g., spatial layers, beams), and the use of multiple spatial resources may increase the data rate or data integrity of communications with UE 115.

[0087] The time interval of the network entity 105 or the UE 115 may be expressed in multiples of a basic time unit, which may refer to, for example, The sampling period is seconds, where can represent the maximum supported subcarrier spacing, and The maximum supported discrete Fourier transform (DFT) size may be indicated. Time intervals of communication resources may be organized according to radio frames, each having a specified duration (e.g., 10 milliseconds (ms)). Each radio frame may be identified by a system frame number (SFN) (e.g., ranging from 0 to 1023).

[0088] Each frame may include multiple consecutively numbered subframes or time slots, and each subframe or time slot may have the same duration. In some examples, a frame may be divided into subframes (e.g., in the time domain), and each subframe may be further divided into multiple 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 multiple symbol periods (e.g., depending on the length of a cyclic prefix added before each symbol period). In some wireless communication systems 100, a time slot may also be divided into multiple mini-time slots containing one or more symbols. Excluding the cyclic prefix, each symbol period may contain one or more (e.g., The duration of a symbol period may depend on the subcarrier spacing or the operating frequency band.

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

[0090] Physical channels may be multiplexed on a carrier according to various techniques. For example, physical control channels and physical data channels may be multiplexed on a downlink carrier using one or more of a time division multiplexing (TDM) technique, a frequency division multiplexing (FDM) technique, or a hybrid TDM-FDM technique. A control region (e.g., a control resource set (CORESET)) for a physical control channel may be defined by a set of symbol periods and may extend across a system bandwidth or a subset of a system bandwidth of a carrier. One or more control regions (e.g., CORESETs) may be configured for a group of UEs 115. For example, one or more of the UEs 115 may monitor or search the control region for control information according to one or more search space sets, and each search space set may include one or more control channel candidates in one or more aggregation levels arranged in a cascaded manner. The aggregation level of the control channel candidates may refer to the amount of control channel resources (e.g., control channel elements (CCEs)) associated with the coded information for a control information format having a given payload size. The search space sets may include a common search space set configured for transmitting control information to a plurality of UEs 115 , and a UE-specific search space set for transmitting control information to a specific UE 115 .

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

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

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

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

[0095] The wireless communication system 100 may operate using one or more frequency bands that may be in the range of 300 megahertz (MHz) to 300 gigahertz (GHz). Typically, the region from 300 MHz to 3 GHz is referred to as the ultra-high frequency (UHF) region or decimeter band because the wavelength range is approximately one decimeter to one meter. UHF waves may be blocked or redirected by buildings and environmental features (which may be referred to as clusters), but the waves may be sufficient to penetrate structures so that macro cells provide service to UEs 115 located indoors. Transmission of UHF waves may be associated with smaller antennas and shorter ranges (e.g., less than 100 kilometers) than transmission using smaller frequencies and longer wavelengths in the high frequency (HF) or very high frequency (VHF) portions of the spectrum below 300 MHz.

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

[0097] The network entity 105 (e.g., base station 140, RU 170) or UE 115 may be equipped with multiple antennas that can be used to employ technologies such as transmit diversity, receive diversity, multiple-input multiple-output (MIMO) communication, or beamforming. The antennas of the network entity 105 or UE 115 may be located in one or more antenna arrays or antenna panels that can support MIMO operations or transmit or receive beamforming. For example, one or more base station antennas or antenna arrays may be co-located at an antenna assembly, such as an antenna tower. In some examples, antennas or antenna arrays associated with the network entity 105 may be located at different geographical locations. The network entity 105 may have an antenna array having a set of rows and columns of antenna ports that the network entity 105 can use to support beamforming for communications with the UE 115. Similarly, the UE 115 may have 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 sent via the antenna ports.

[0098] The network entity 105 or the UE 115 may use MIMO communication to utilize multipath signal propagation and improve spectral efficiency by sending or receiving multiple signals via different spatial layers. Such a technology may be referred to as spatial multiplexing. For example, multiple signals may be sent by a transmitting device via different antennas or different combinations of antennas. Similarly, multiple signals may be received by a receiving device via different antennas or different combinations of antennas. Each of the multiple signals may be referred to as a separate spatial stream and may carry information associated with the same data stream (e.g., the same codeword) or different data streams (e.g., different codewords). Different spatial layers may be associated with different antenna ports for channel measurement and reporting. MIMO technology includes single-user MIMO (SU-MIMO), in which multiple spatial layers are sent to the same receiving device, and multi-user MIMO (MU-MIMO), in which multiple spatial layers are sent to multiple devices.

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

[0100] The wireless communication system 100 may support signaling for channel access using multi-beam sensing. For example, the UE 115 may send a capability message to the network entity 105 indicating the ability of the UE 115 to support a per-beam channel access procedure (such as a per-beam LBT procedure) for communicating on a shared channel (e.g., in one or more shared radio frequency spectrum bands). Additionally or alternatively, the UE 115 may receive a control message indicating a channel occupancy configuration associated with the per-beam channel access procedure. The UE 115 may (e.g., based on the capabilities of the UE 115) perform a per-beam channel access procedure for each beam in a beam set, and the per-beam channel access procedure may be successful on a subset of beams in the beam set. In some cases, the UE 115 may enable use of a COT by the UE 115 only when the subset of beams has a successful per-beam channel access procedure, during which communication is performed on the channel via the subset of beams, based on the channel occupancy configuration.

[0101] In some other cases, the UE 115 may disable the use of the COT by the UE 115 only when the beam subset has a successful per-beam channel access procedure based on the channel occupancy configuration, avoiding communication on the channel via the beam subset during the COT. In this case, the UE 115 may continue to perform the per-beam LBT procedure on the remaining beams in the beam set until the per-beam channel access procedure is successful for each beam in the beam set (e.g., the beam subset and the remaining beams). Additionally, the UE 115 may communicate on the channel during the COT based on the per-beam channel access procedure being successful for each beam in the beam set.

[0102] 2A and 2B illustrate examples of a channel access procedure 200 (including a channel access procedure 200-a and a channel access procedure 200-b) that supports signaling for channel access using multi-beam sensing according to one or more aspects of the present disclosure. In some examples, the channel access procedure 200 may implement aspects of the wireless communication system 100. For example, the channel access procedure 200 may include one or more network entities 105 (e.g., network entity 105-a and network entity 105-b) and one or more UEs 115 (e.g., UE 115-a and UE 115-b), which may be examples of corresponding devices as described with reference to FIG. 1. In the examples of FIGS. 2A and 2B, the network entity 105 may be an example of a CU 160, a DU 165, a RU 170, a base station 140, an IAB node 104, or one or more other network nodes as described with reference to FIG. 1. In some cases, the network entity 105 may send a control message 205 to the UE 115 indicating a channel occupancy configuration associated with a per-beam channel access procedure, such as a per-beam LBT procedure 215 (eg, a per-beam channel access procedure).

[0103] Some wireless communication systems may support channel access procedures, such as LBT procedures (e.g., single LBT procedures). For example, UE 115 may monitor a shared communication channel (e.g., an unlicensed channel) (the shared communication channel may be referred to herein as a channel) by performing an LBT procedure to identify the presence of other signals on the channel (e.g., to determine whether the channel is busy) (e.g., performing channel sensing on the shared communication channel). In some cases, UE 115 may identify the presence of other signals on the channel (e.g., transmitted by other devices), and may be unable to access the channel based on the busyness of the channel (e.g., based on the presence of other signals), which may be referred to as an unsuccessful LBT procedure (e.g., a channel access procedure failure). In some other cases, UE 115 may identify the absence of other signals on the channel (which may be based on one or more signal strength thresholds), and may be able to access the channel based on the channel being idle (e.g., based on the absence of other signals on the channel, based on the detected signal satisfying a threshold), which may be referred to as a successful LBT procedure (e.g., a channel access procedure success). In this case, UE 115 may communicate on the channel during the COT based on the successful LBT procedure.

[0104] The COT may refer to the amount of time that a wireless device (e.g., UE 115, network entity 105) and any other wireless devices sharing the channel occupancy perform transmission on the channel after the wireless device performs one or more corresponding channel access procedures. In some examples, if the transmission interval is less than or equal to a certain duration (e.g., 25µs), the interval duration may be counted in the COT. The COT may be shared for transmission between the network entity 105 and one or more corresponding UEs 115. The COT may include multiple time slots, each of which includes downlink resources, uplink resources, or flexible resources, and the corresponding resources may be associated with one or more beams (e.g., the one or more beams may be associated with TDM). In some cases, the COT may be associated with MU-MIMO transmissions (e.g., using spatial division multiplexing (SDM)). Additionally, the UE 115 may perform an LBT procedure based on one or more beams associated with the COT. For example, at the start of the COT, the UE 115 may first perform an LBT procedure (e.g., a single LBT procedure) for a wide beam, where the wide beam covers each of the one or more beams. The frequency range of the wide beam may include (e.g., cover) frequencies associated with the one or more beams. In some examples, the UE 115 may then perform a per-beam LBT procedure for a relatively narrow beam to determine whether the UE 115 can access the COT.

[0105] In some cases, an LBT procedure may be associated with a type, such as a type 1 LBT procedure, a type 2 LBT procedure, or a type 3 LBT procedure. For example, a UE 115 operating in accordance with a type 1 LBT procedure (e.g., category or CAT 3 LBT) may acquire the COT of a channel when the LBT procedure is required (e.g., based on the UE 115 capabilities) and using a variable sensing and / or backoff period. In another example, a UE 115 operating in accordance with a type 2 LBT procedure (e.g., CAT 2 LBT) may share the COT of a channel (e.g., sharing uplink transmissions and downlink transmissions) at least when required (e.g., based on the individual UE 115 capabilities) and using a fixed sensing period. In another example, a UE 115 operating in accordance with a type 3 LBT procedure (e.g., no LBT) may share the COT of a channel without performing a channel access procedure. In some aspects, an LBT procedure may be referred to as a channel access procedure. In addition, other channel access procedures may be performed as an alternative or in addition to the LBT procedure.

[0106] Some wireless communication systems may support per-beam channel access procedures, such as per-beam LBT procedures. For example, a COT may be associated with a beam set, and the UE 115 may simultaneously perform an independent per-beam LBT procedure on each beam in the beam set (e.g., if the UE 115 is capable of performing per-beam LBT procedures). In some cases (e.g., when the COT uses TDM beams with beam switching), the UE 115 may perform a per-beam LBT procedure at the start of the COT, and may perform an additional LBT procedure (e.g., CAT 2 LBT) before beam switching.

[0107] In some cases, the UE 115 may perform a per-beam LBT procedure (e.g., Type 1 or Type 2) on a beam set, and the per-beam LBT procedure may succeed on a subset of beams in the beam set (e.g., before succeeding on all beams in the beam set). In this case, the UE 115 may determine whether to communicate on the channel (e.g., occupy the COT) via the subset of beams (e.g., LBT-Won-Subset) for which the per-beam LBT procedure succeeded during the COT (e.g., and abandon the per-beam LBT procedure on the remaining beams in the beam subset), or to avoid communicating on the channel during the COT until the per-beam LBT procedure is successful on every beam in the beam set (e.g., All-Beam-COT) (e.g., occupy the channel using every beam in the beam set during the COT).

[0108] In some cases, such as when the UE 115 communicates on the channel during the COT via a subset of beams for which the per-beam LBT procedure is successful, the UE 115 may increase the chance of occupying the COT, however, the network entity 105 may not be aware of the subset of beams on which the COT is occupied. In some other cases, such as when the UE 115 avoids communicating on the channel during the COT until the per-beam LBT procedure is successful on each beam in the beam set, the network entity 105 may know that upon completion of the per-beam LBT procedure, the UE 115 will occupy each beam in the beam set or none of the beams in the beam set. However, the network entity may not be aware of whether the UE 115 is occupying each beam in the beam set or none of the beams in the beam set. The inability of the network entity 105 (e.g., capable of obtaining a COT on a subset of beams or a set of beams) to determine what beams (if any) the UE 115 may occupy during the COT may result in communication inefficiencies.

[0109] Thus, the channel access procedure 200 may support signaling for channel access using multi-beam sensing. In the examples of Figures 2A and 2B, a network entity 105 (e.g., network entity 105-a, network entity 105-b) may communicate with a UE 115 (e.g., UE 115-a, UE 115-b), and the network entity 105 may send a control message 205 indicating a channel occupancy configuration (e.g., RRC configuration) associated with a per-beam channel access procedure, such as a per-beam LBT procedure 215 (e.g., per-beam LBT procedure 215-a, per-beam LBT procedure 215-b, per-beam LBT procedure 215-c, per-beam LBT procedure 215-d). The channel occupancy configuration enables or disables the ability of the UE 115 to communicate on a channel (e.g., a shared channel in one or more shared RF spectrum bands) during COT 220 when a per-beam LBT procedure 215 is successful for a beam subset of a set of two or more beams 210 (e.g., including beam 210-a and beam 210-b or beam 210-c and beam 210-d).

[0110] In some cases, the control message 205 may be an RRC message, and the channel occupancy configuration indicated in the control message 205 may be a UE-specific configuration for the UE 115. In some other cases, the control message 205 may include system information (e.g., may be a system information message), such as one or more system information blocks (SIBs), and the channel occupancy configuration indicated in the control message 205 may be a cell-specific configuration for a cell in which the UE 115 is located (e.g., provided by the network entity 105). That is, the UE 115 and other UEs 115 located in the cell may be configured with the same cell-specific configuration.

[0111] In some cases, the channel occupancy configuration may be based on the traffic type, one or more other wireless devices communicating with the UE 115, the number of wireless devices in the same cell as the UE 115, or any combination thereof. Thus, the network entity 105-a or the network entity 105-b may enable or disable the ability of the UE 115 to communicate on the channel during the COT 220 (e.g., COT 220-a, COT 220-b) when the per-beam LBT procedure 215 is successful for a subset of the beam set 210 based on the traffic type, one or more other wireless devices communicating with the UE 115, the number of wireless devices in the same cell as the UE 115, or any combination thereof. For example, the network entity 105-a may enable the UE 115's ability to communicate on the channel during the COT 220 when the per-beam LBT procedure 215 is successful for a subset of the beam set 210, when the traffic type is associated with low priority traffic, when the number of wireless devices communicating with the UE 115 exceeds a threshold number, when the number of wireless devices in the same cell as the UE 115 exceeds a threshold number, or any combination thereof. Conversely, the network entity 105-a may disable the UE 115's ability to communicate on the channel during the COT 220 when the per-beam LBT procedure 215 is successful for a subset of the beam set 210, when the traffic type is associated with high priority traffic, when the number of wireless devices communicating with the UE 115 is at or below a threshold number, when the number of wireless devices in the same cell as the UE 115 is at or below a threshold number, or any combination thereof.

[0112] Additionally or alternatively, the channel occupancy configuration may be based on a RAT (e.g., 5G NR or other RAT) used by one or more network entities 105 or wireless devices to communicate in one or more shared radio frequency spectrum bands (e.g., the same shared radio frequency spectrum) in which the UE 115 is performing the per-beam LBT procedure 215. For example, the network entity 105 may identify the presence of one or more other network entities 105 or wireless devices communicating in the one or more shared radio frequency spectrum bands, and may enable or disable the UE 115's ability to communicate on a channel in the one or more shared radio frequency spectrum bands during the COT 220 when the per-beam LBT procedure 215 is successful for a subset of beams of the beam set 210. Enabling or disabling the ability to communicate on a channel during the COT 220 when the per-beam LBT procedure 215 is successful for only a subset of beams of the beam set 210 may be based on the presence of one or more other network entities 105 or wireless devices, and may be further based on the RAT used by the other network entities 105 or wireless devices.

[0113] In the example of FIG. 2A , the network entity 105 - a may send a control message 205 - a to the UE 115 - a indicating a channel occupancy configuration that enables use of the COT 220 by the UE 115 - a when only a subset of beams 210 have a successful per-beam LBT procedure 215 . For example, the UE 115 - a may identify a channel that the UE 115 - a may use (e.g., want to use) during the COT 220 - a to communicate with the network entity 105 - a . The COT 220 - a may include resources associated with one or more beams 210 (including beam 210 - a and beam 210 - b ). Thus, at time T0 , the UE 115 - a may initiate (e.g., perform) a per-beam LBT procedure 215 - a on beam 210 - a and (e.g., simultaneously) initiate (e.g., perform) a per-beam LBT procedure 215 - b on beam 210 - b . In some cases, at time T1, the per-beam LBT procedure 215-a on beam 210-a may be successful, while the per-beam LBT procedure 215-b on beam 210-b may be unsuccessful. In this case, the UE 115-a may enable use of the COT 220-a by the UE 115-a when only a subset of the beam set 210 (such as beam 210-a) has a successful per-beam LBT procedure 215 (such as per-beam LBT procedure 215-a), and communicate on the channel via beam 210-a during the COT 220-a. Additionally, the UE 115-a may abandon the per-beam LBT procedure 215-b on beam 210-b (e.g., at time T1). That is, UE 115-a may avoid communicating on the channel via beam 210-b during COT 220-a. In other words, UE 115-a may occupy beam 210-a in COT 220-a and avoid occupying beam 210-b in COT 220-a.

[0114] In some cases, the UE 115-a may perform the per-beam LBT procedure 215 according to a timer, which may be sent in the control message 205. For example, the network entity 105-a may send an indication of the timer in the control message 205-a, such that the time T1 corresponds to the expiration of the timer. That is, the UE 115-a may initiate the per-beam LBT procedure 215 at time T0, and when the timer expires at time T1, the UE 115-a may determine the success or failure of each of the per-beam LBT procedures 215. In some cases, the timer may be associated with a duration, such that the expiration of the timer corresponds to a certain duration (e.g., of performing the per-beam LBT procedure 215), which may exceed a threshold duration associated with the timer. In some other cases, the timer may be a counter, such that the expiration of the counter corresponds to the value of the counter exceeding a threshold. For example, at time T0, UE 115-a may initiate per-beam LBT procedure 215 and start counting (e.g., starting a counter for a plurality of slots or symbols) for a plurality of slots (e.g., NR slots or microslots) or symbols (e.g., OFDM symbols). Additionally, UE 115-a may determine success or failure of per-beam LBT procedure 215 based on the number of slots or symbols counted (e.g., at time T1) exceeding a threshold number.

[0115] In the example of FIG. 2B , the network entity 105 - b may send a control message 205 - b indicating a channel occupancy configuration to the UE 115 - b that disables use of the COT 220 by the UE 115 - b when only a subset of beams 210 have a successful per-beam LBT procedure 215 . For example, the UE 115 - b may identify a channel that the UE 115 - b may use (e.g., want to use) to communicate with the network entity 105 - b during the COT 220 - b. The COT 220 - b may include resources associated with one or more beams 210 , including beam 210 - c and beam 210 - d. Thus, at time T0, the UE 115 - b may initiate (e.g., perform) a per-beam LBT procedure 215 - c on beam 210 - c and (e.g., simultaneously) initiate (e.g., perform) a per-beam LBT procedure 215 - d on beam 210 - d. In some cases, at time T1, the per-beam LBT procedure 215-c on beam 210-c may be successful, while the per-beam LBT procedure 215-d on beam 210-d may be unsuccessful. In this case, UE 115-b may disable the use of COT 220-b by UE 115-b when only beam subset 210 has a successful per-beam LBT procedure 215 based on the channel occupancy configuration, and continue to perform per-beam LBT procedure 215-d on beam 210-d until per-beam LBT procedure 215-d is successful at time T2. Therefore, at time T2, per-beam LBT procedure 215-c and per-beam LBT procedure 215-d may be successful, so that UE 115-b can communicate on the channel via beam 210-c and beam 210-d during COT 220-b. That is, UE 115-b may occupy beam 210-c and beam 210-d in COT 220-b.

[0116] Although much of the present disclosure is described in the context of a per-beam LBT procedure, this should not be viewed as limiting the present disclosure. In fact, it is contemplated herein that channel occupancy configurations may be associated with per-beam channel access procedures (including per-beam LBT procedures). In this regard, other per-beam channel access procedures may be considered with respect to the techniques described herein.

[0117] FIG3 illustrates an example of a channel access procedure 300 that supports signaling for channel access using multi-beam sensing according to one or more aspects of the present disclosure. In some examples, the channel access procedure 300 may implement aspects of the wireless communication system 100 and the channel access procedure 200. For example, the channel access procedure 300 may include one or more network entities 105 (e.g., network entity 105-c) and one or more UEs 115 (e.g., UE 115-c), which may be examples of corresponding devices as described with reference to FIG1 to FIG2. In the example of FIG3, the network entity 105 may be an example of a CU 160, a DU 165, a RU 170, a base station 140, an IAB node 104, or one or more other network nodes as described with reference to FIG1. In some cases, the network entity UE 115-c may send a capability message 305 to the network entity 105-c indicating the ability of the UE 115-c to support per-beam channel access procedures, such as per-beam LBT procedures 320 (e.g., per-beam LBT procedures 320-a, per-beam LBT procedures 320-b).

[0118] As described herein, a UE 115-c may send a capability message 305 to a network entity 105-c indicating an ability of the UE 115-c to support per-beam LBT procedures 320 (e.g., channel access procedures). In some cases, the capability message 305 may include an indication of a threshold number (e.g., a maximum number) of simultaneous per-beam LBT procedures 320 supported by the UE 115-c. In some cases, the threshold amount may be based on the type of the per-beam LBT procedures 320. For example, the per-beam LBT procedures 320 may be associated with a first type (e.g., type 1), a second type (e.g., type 2), or a third type (e.g., type 3). Thus, the indication in the capability message 305 may include a threshold number of simultaneous per-beam LBT procedures 320 associated with the first type, a threshold number of simultaneous per-beam LBT procedures 320 associated with the second type, a threshold number of simultaneous per-beam LBT procedures 320 associated with the third type, or any combination thereof.

[0119] In some cases, the capability message 305 may indicate that the UE 115-c is capable of supporting per-beam LBT procedures 320. Additionally, the network entity 105-c may send a control message 310 indicating a channel occupancy configuration (e.g., an RRC configuration) associated with a per-beam channel access procedure (such as the per-beam LBT procedure 320). That is, the channel occupancy configuration may enable or disable the UE 115-c's ability to communicate on a channel (e.g., a shared channel in one or more shared radio frequency spectrum bands) during a COT 325 when the beam LBT procedure 320 is successful for a beam subset of a set of two or more beams 315 (e.g., including beam 315-a and beam 315-b), as described with reference to FIGS. 2A and 2B.

[0120] In the example of FIG. 3 , the network entity 105 - c may send a control message 310 indicating a channel occupancy configuration that enables use of a COT 325 by the UE 115 - c when only a subset of beams 315 have a successful per-beam LBT procedure 320, as described with reference to FIG. 2A . For example, the UE 115 - c may identify a channel that the UE 115 - c may use (e.g., want to use) to communicate with the network entity 105 - c during the COT 325. The COT 325 may include resources associated with one or more beams 315 (including beam 315 - a and beam 315 - b). Thus, at time T0, the UE 115 - c may initiate (e.g., perform) a per-beam LBT procedure 320 - a on beam 315 - a and initiate (e.g., perform) a per-beam LBT procedure 320 - b on beam 315 - b (e.g., simultaneously). In some cases, at time T1, the per-beam LBT procedure 320-a on beam 315-a may be successful, while the per-beam LBT procedure 320-b on beam 315-b may be unsuccessful. In this case, the UE 115-c may enable use of the COT 325 by the UE 115-c when only a subset of beams 315 (such as beam 315-a) has a successful per-beam LBT procedure 320 (such as per-beam LBT procedure 320-a), communicating on the channel via beam 315-a during the COT 325, based on the per-beam LBT procedure 320-a being successful and the channel occupancy configuration. Additionally, the UE 115-c may abandon the per-beam LBT procedure 320-b on beam 315-b (e.g., at time T1). That is, UE 115-c may avoid communicating on the channel via beam 315-b during COT 325. In other words, UE 115-c may occupy beam 315-a in COT 325 and avoid occupying beam 315-b in COT 325.

[0121] Alternatively (eg, not depicted in FIG. 3 ), the capability message 305 may indicate that the UE 115 - c is not capable of supporting the per-beam LBT procedure 320 . In this case, the network entity 105 - c may refrain from sending the control message 310 .

[0122] Although much of the present disclosure is described in the context of per-beam LBT procedures, this should not be viewed as a limitation of the present disclosure. In fact, it is contemplated herein that a capability message may indicate the ability of a UE to support per-beam channel access procedures, including per-beam LBT procedures. In this regard, other per-beam channel access procedures may be considered with respect to the techniques described herein.

[0123] FIG. 4 illustrates an example of a process flow 400 in a system supporting signaling for channel access using multi-beam sensing according to one or more aspects of the present disclosure. In some examples, the process flow 400 may implement aspects of the wireless communication system 100, the channel access procedure 200, and the channel access procedure 300. For example, the process flow may include one or more network entities 105 (e.g., network entity 105-d) and one or more UEs 115 (e.g., UE 115-d), which may be examples of corresponding devices as described with reference to FIG. 1. In the example of FIG. 4, the network entity 105 may be an example of a CU 160, a DU 165, a RU 170, a base station 140, an IAB node 104, or one or more other network nodes as described with reference to FIG. 1. In some cases, the network entity 105-d may send a control message indicating a channel occupancy configuration associated with a per-beam channel access procedure to the UE 115-d.

[0124] In some cases, at 405, UE 115-d may send a capability message to entity 105-d indicating the ability of UE 115-d to support per-beam channel access procedures for communicating in one or more shared radio frequency spectrum bands. In some cases, the capability message may include an indication of a threshold number of simultaneous per-beam channel access procedures supported by UE 115-d. For example, the indication may include a threshold number of simultaneous per-beam channel access procedures associated with a first type of channel access procedures, a threshold number of simultaneous per-beam channel access procedures associated with a second type of channel access procedures, a threshold number of simultaneous per-beam channel access procedures associated with a third type of channel access procedures, or any combination thereof.

[0125] In some cases, at 410, the network entity 105-d may send a control message to the UE 115-d indicating a channel occupancy configuration associated with a per-beam channel access procedure for communicating in one or more shared radio frequency spectrum bands.

[0126] In some cases, the control message may include an indication of one or more timers associated with a per-beam channel access procedure. In some cases, the control message may be an RRC message such that the UE 115-d may receive an RRC message indicating a channel configuration, the channel occupancy configuration including a UE-specific configuration for the UE 115-d. Alternatively, the control message may be a system information message (e.g., one or more SIBs) such that the UE 115-d may receive a system information message indicating a channel configuration, the channel occupancy configuration including a cell-specific configuration for a cell provided by the network entity 105-d.

[0127] In some cases, the channel occupancy configuration may be based on the radio access technology used by one or more network entities 105 or wireless devices for communicating in one or more shared radio frequency spectrum bands. That is, the network entity 105-d may identify the presence of one or more other network entities 105 or wireless devices communicating in one or more shared radio frequency spectrum bands and may send a control message that enables or disables use of COT by the UE 115-d only when a subset of beams of a set of beam sets have a successful per-beam channel access procedure.

[0128] In some cases, the channel occupancy configuration may be based on the type of traffic, one or more other wireless devices communicating with the UE 115-d, the number of wireless devices in the same cell as the UE 115-d, or any combination thereof.

[0129] At 415, the UE 115-d may perform a per-beam channel access procedure for each beam in the set of beams. In some cases, the UE 115-d may perform the per-beam channel access procedure for each beam in the set of beams based on one or more timers associated with the per-beam channel access procedure (e.g., indicated in the control message). In this case, the UE 115-d may determine that the per-beam channel access procedure is successful for at least one subset of beams in the set of beams upon expiration of the one or more timers.

[0130] At 420, a channel access procedure performed by UE 115-d may be successful, which may indicate that UE 115-d may occupy the COT to communicate on a channel (e.g., a channel of a shared radio frequency spectrum band). For example, at 420-a, a per-beam channel access procedure may be successful for only a subset of beams. In some cases, the channel access procedure may be successful for a threshold number of beams in a set of beams. In this case, when the subset of beams has a successful per-beam channel access procedure, the channel occupancy configuration may enable use of the COT by UE 115-d. Thus, UE 115-d may communicate on the channel via one or more beams from the set of beams during the COT based on the per-beam channel access procedure being successful for the subset of beams.

[0131] In other examples, at 420-b, the per-beam channel access procedure may be successful for all beams in the beam set. In this case, the channel occupancy configuration may have disabled use of the COT by the UE 115-d when a portion of the beam set has a successful per-beam channel access procedure. Thus, because all beams have successful channel access procedures, the UE 115-d may communicate on the channel via one or more beams from the beam set during the COT based on the per-beam channel access procedure being successful for each beam in the beam set.

[0132] In either case, at 425, the UE 115-d may communicate with the network entity 105-d via one or more beams from the set of beams based on the channel occupancy configuration and the fact that the per-beam channel access procedure was successful for at least the subset of beams in the set of beams. In this case, the one or more beams may include the subset of beams or the entire set of beams based on the channel occupancy configuration and how many beams the per-beam channel access procedure was successful on.

[0133] 5 shows a block diagram 500 of a device 505 supporting signaling for channel access using multi-beam sensing according to one or more aspects of the present disclosure. The device 505 may be an example of aspects of the UE 115 as described herein. The device 505 may include a receiver 510, a transmitter 515, and a communication manager 520. The device 505 may also include a processor. Each of these components may communicate with each other (e.g., via one or more buses).

[0134] The receiver 510 may provide means for receiving information (such as packets, user data, control information, or any combination thereof) associated with various information channels (e.g., control channels related to signaling for channel access using multi-beam sensing, data channels, information channels). The information may be communicated to other components of the device 505. The receiver 510 may utilize a single antenna or multiple antennas.

[0135] The transmitter 515 may provide means for transmitting signals generated by other components of the device 505. For example, the 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 signaling for channel access using multi-beam sensing). In some examples, the transmitter 515 may be co-located with the receiver 510 in a transceiver module. The transmitter 515 may utilize a single antenna or multiple antennas.

[0136] The communication manager 520, the receiver 510, the transmitter 515, or various combinations thereof, or various components thereof, may be examples of means for performing various aspects of signaling for channel access using multi-beam sensing as described herein. For example, the communication manager 520, the receiver 510, the transmitter 515, or various combinations thereof, or components thereof, may support methods for performing one or more of the functions described herein.

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

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

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

[0140] According to examples as disclosed herein, the communication manager 520 may support wireless communications at a UE. For example, the communication manager 520 may be configured to or otherwise support a component for receiving a control message indicating a channel occupancy configuration associated with a per-beam channel access procedure for communicating in one or more shared radio frequency spectrum bands. The communication manager 520 may be configured to or otherwise support a component for performing a per-beam channel access procedure for each of a plurality of beams. The communication manager 520 may be configured to or otherwise support a component for communicating via one or more beams from a plurality of beams based at least in part on the channel occupancy configuration and the per-beam channel access procedure being successful for at least one beam subset of the plurality of beams.

[0141] Additionally or alternatively, according to examples as disclosed herein, the communication manager 520 may support wireless communications at the UE. For example, the communication manager 520 may be configured to or otherwise support a component for sending a capability message indicating the UE's ability to support a per-beam channel access procedure for communicating in one or more shared radio frequency spectrum bands. The communication manager 520 may be configured to or otherwise support a component for performing a per-beam channel access procedure for one or more of the plurality of beams based on the capability. The communication manager 520 may be configured to or otherwise support a component for communicating via one or more beams based at least in part on the per-beam channel access procedure being successful.

[0142] By including or configuring the communication manager 520 according to the examples described herein, the device 505 (e.g., a processor controlling or otherwise coupled to the receiver 510, the transmitter 515, the communication manager 520, or a combination thereof) may support techniques for signaling a UE's ability to support a per-beam channel access procedure for communicating in one or more shared radio frequency spectrum bands, signaling a channel occupancy configuration associated with the per-beam channel access procedure, or both, which may result in reduced processing, lower power consumption, more efficient use of communication resources, and the like.

[0143] 6 shows a block diagram 600 of a device 605 supporting signaling for channel access using multi-beam sensing according to one or more aspects of the present disclosure. The device 605 may be an example of aspects of the device 505 or UE 115 as described herein. The device 605 may include a receiver 610, a transmitter 615, and a communication manager 620. The device 605 may also include a processor. Each of these components may communicate with each other (e.g., via one or more buses).

[0144] The receiver 610 may provide means for receiving information (such as packets, user data, control information, or any combination thereof) associated with various information channels (e.g., control channels related to signaling for channel access using multi-beam sensing, data channels, information channels). The information may be communicated to other components of the device 605. The receiver 610 may utilize a single antenna or multiple antennas.

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

[0146] The device 605 or its various components may be examples of components for performing various aspects of signaling for channel access using multi-beam sensing as described herein. For example, the communication manager 620 may include a configuration component 625, a channel access procedure component 630, a beam component 635, a capability component 640, or any combination thereof. The communication manager 620 may be an example of various aspects of the communication manager 520 as described herein. In some examples, the communication manager 620 or its various components may be configured to use or otherwise cooperate with the receiver 610, the transmitter 615, or both to perform various operations (e.g., receive, obtain, monitor, output, send). For example, the communication manager 620 may receive information from the receiver 610, transmit information to the transmitter 615, or be integrated with the receiver 610, the transmitter 615, or both to obtain information, output information, or perform various other operations as described herein.

[0147] According to examples as disclosed herein, the communication manager 620 may support wireless communications at a UE. The configuration component 625 may be configured to or otherwise support a means for receiving a control message indicating a channel occupancy configuration associated with a per-beam channel access procedure for communicating in one or more shared radio frequency spectrum bands. The channel access procedure component 630 may be configured to or otherwise support a means for performing a per-beam channel access procedure for each of a plurality of beams. The beam component 635 may be configured to or otherwise support a means for communicating via one or more beams from a plurality of beams based at least in part on the channel occupancy configuration and the per-beam channel access procedure being successful for at least one subset of beams of the plurality of beams.

[0148] Additionally or alternatively, the communication manager 620 may support wireless communications at the UE according to examples as disclosed herein. The capability component 640 may be configured to or otherwise support means for sending a capability message indicating the UE's ability to support a per-beam channel access procedure for communicating in one or more shared radio frequency spectrum bands. The channel access procedure component 630 may be configured to or otherwise support means for performing a per-beam channel access procedure for one or more of the plurality of beams according to the capability. The beam component 635 may be configured to or otherwise support means for communicating via one or more beams based at least in part on the per-beam channel access procedure being successful.

[0149] 7 shows a block diagram 700 of a communication manager 720 that supports signaling for channel access using multi-beam sensing according to one or more aspects of the present disclosure. The communication manager 720 can be an example of aspects of the communication manager 520, the communication manager 620, or both as described herein. The communication manager 720 or its various components can be examples of means for performing various aspects of signaling for channel access using multi-beam sensing as described herein. For example, the communication manager 720 may include a configuration component 725, a channel access procedure component 730, a beam component 735, a capability component 740, a channel occupancy component 745, or any combination thereof. Each of these components can communicate with each other directly or indirectly (e.g., via one or more buses).

[0150] According to examples as disclosed herein, the communication manager 720 may support wireless communications at a UE. The configuration component 725 may be configured to or otherwise support a means for receiving a control message indicating a channel occupancy configuration associated with a per-beam channel access procedure for communicating in one or more shared radio frequency spectrum bands. The channel access procedure component 730 may be configured to or otherwise support a means for performing a per-beam channel access procedure for each of a plurality of beams. The beam component 735 may be configured to or otherwise support a means for communicating via one or more beams from a plurality of beams based at least in part on the channel occupancy configuration and the per-beam channel access procedure being successful for at least one subset of beams of the plurality of beams.

[0151] In some examples, to support communication via one or more beams, the channel occupancy component 745 may be configured to or otherwise support components for communicating on a channel during a COT based at least in part on a per-beam channel access procedure being successful for a beam subset, the one or more beams comprising the beam subset.

[0152] In some examples, the channel occupancy configuration enables use of COT by the UE only when a subset of beams has a successful per-beam channel access procedure.

[0153] In some examples, to support communication via one or more beams, the channel occupancy component 745 may be configured as or otherwise support components for communicating on a channel during a COT based at least in part on a per-beam channel access procedure being successful for each of a plurality of beams, the one or more beams comprising a plurality of beams.

[0154] In some examples, the channel occupancy configuration disables the use of COT by the UE only when a subset of beams has a successful per-beam channel access procedure. In this case, the full set of beams may need to have a successful channel access procedure before the UE can transmit during the COT.

[0155] In some examples, to support execution of a per-beam channel access procedure, the channel access procedure component 730 may be configured as or otherwise support components for executing a per-beam channel access procedure for each of a plurality of beams based at least in part on one or more timers associated with the per-beam channel access procedure, wherein the UE determines that the per-beam channel access procedure is successful when the one or more timers expire.

[0156] In some examples, the control message includes an indication of one or more timers associated with the per-beam channel access procedure.

[0157] In some examples, to support receiving control messages, configuration component 725 may be configured as or otherwise support means for receiving a radio resource control message indicating a channel occupancy configuration, the channel occupancy configuration including a UE-specific configuration for the UE.

[0158] In some examples, to support receiving control messages, configuration component 725 may be configured to or otherwise support means for receiving a system information message indicating a channel occupancy configuration including a cell-specific configuration for a cell provided by a network entity.

[0159] In some examples, the channel occupancy configuration is based at least in part on the traffic type, one or more other wireless devices communicating with the UE, the number of wireless devices in the same cell as the UE, or any combination thereof.

[0160] In some examples, the channel occupancy configuration is based at least in part on a radio access technology used by one or more network entities or wireless devices to communicate in one or more shared radio frequency spectrum bands.

[0161] In some examples, capability component 740 may be configured to or otherwise support means for sending a capability message indicating the UE's ability to support per-beam channel access procedures, wherein receiving the control message is based at least in part on the capability message.

[0162] Additionally or alternatively, the communication manager 720 may support wireless communications at the UE in accordance with examples as disclosed herein. The capability component 740 may be configured to or otherwise support a component for sending a capability message indicating the UE's ability to support a per-beam channel access procedure for communicating in one or more shared radio frequency spectrum bands. In some examples, the channel access procedure component 730 may be configured to or otherwise support a component for performing a per-beam channel access procedure for one or more of the plurality of beams based on the capability. In some examples, the beam component 735 may be configured to or otherwise support a component for communicating via one or more beams based at least in part on the per-beam channel access procedure being successful.

[0163] In some examples, to support sending a capability message, capability component 740 may be configured or otherwise support means for sending, within a capability message, an indication of a threshold number of simultaneous per-beam channel access procedures supported by the UE.

[0164] In some examples, the indication includes a first threshold number of simultaneous channel access procedures per beam associated with a first type of channel access procedure, a second threshold number of simultaneous channel access procedures per beam associated with a second type of channel access procedure, a third threshold number of simultaneous channel access procedures per beam associated with a third type of channel access procedure, or any combination thereof.

[0165] In some examples, configuration component 725 may be configured as or otherwise support means for receiving a control message indicating a channel occupancy configuration associated with a per-beam channel access procedure.

[0166] In some examples, the per-beam channel access procedure is successful for a subset of beams of the plurality of beams. In some examples, the beam subsets are used to enable use of COT by the UE only when the beam subset has a successful per-beam channel access procedure, communicating during the COT, based at least in part on the channel occupancy configuration.

[0167] In some examples, the per-beam channel access procedure is successful for each of the plurality of beams. In some examples, the plurality of beams are used to disable use of the COT by the UE only when a subset of beams from the plurality of beams have a successful per-beam channel access procedure based at least in part on the channel occupancy configuration, communicating during the COT.

[0168] FIG8 shows a diagram of a system 800 including a device 805 that supports signaling for channel access using multi-beam sensing according to one or more aspects of the present disclosure. The device 805 may be an example of a device 505, a device 605, or a UE 115 as described herein, or include components thereof. The device 805 may communicate (e.g., wirelessly) with one or more network entities 105, one or more UEs 115, or any combination thereof. The device 805 may include components for two-way voice and data communications, including components for sending and receiving communications, such as a communication manager 820, an input / output (I / O) controller 810, a transceiver 815, an antenna 825, a memory 830, a code 835, and a processor 840. These components may be electronically communicated or otherwise coupled (e.g., operatively, communicatively, functionally, electronically, electrically) via one or more buses (e.g., bus 845).

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

[0170] In some cases, the device 805 may include a single antenna 825. However, in some other cases, the device 805 may have more than one antenna 825, which may be capable of concurrently transmitting or receiving multiple wireless transmissions. The transceiver 815 may communicate bidirectionally via one or more antennas 825, a wired link, or a wireless link as described herein. For example, the transceiver 815 may represent a wireless transceiver and may communicate bidirectionally with another wireless transceiver. The 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. The transceiver 815 or the transceiver 815 and the one or more antennas 825 may be examples of transmitters 515, transmitters 615, receivers 510, receivers 610, or any combination thereof or any components thereof as described herein.

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

[0172] The processor 840 may include an intelligent hardware device (e.g., a general-purpose processor, a DSP, a CPU, a microcontroller, an ASIC, an FPGA, a programmable logic device, a discrete gate or transistor logic component, a discrete hardware component, or any combination thereof). In some cases, the processor 840 may be configured to operate a memory array using a memory controller. In some other cases, the memory controller may be integrated into the processor 840. The processor 840 may be configured to execute computer-readable instructions stored in a memory (e.g., a memory 830) so that the device 805 performs various functions (e.g., functions or tasks of signaling for channel access using multi-beam sensing). For example, the device 805 or a component of the device 805 may include a processor 840 and a memory 830 coupled to or coupled to the processor 840, and the processor 840 and the memory 830 are configured to perform the various functions described herein.

[0173] According to examples as disclosed herein, the communication manager 820 may support wireless communications at a UE. For example, the communication manager 820 may be configured to or otherwise support a component for receiving a control message indicating a channel occupancy configuration associated with a per-beam channel access procedure for communicating in one or more shared radio frequency spectrum bands. The communication manager 820 may be configured to or otherwise support a component for performing a per-beam channel access procedure for each of a plurality of beams. The communication manager 820 may be configured to or otherwise support a component for communicating via one or more beams from a plurality of beams based at least in part on the channel occupancy configuration and the per-beam channel access procedure being successful for at least one subset of beams of the plurality of beams.

[0174] Additionally or alternatively, according to examples as disclosed herein, the communication manager 820 may support wireless communications at the UE. For example, the communication manager 820 may be configured to or otherwise support a component for sending a capability message indicating the UE's ability to support a per-beam channel access procedure for communicating in one or more shared radio frequency spectrum bands. The communication manager 820 may be configured to or otherwise support a component for performing a per-beam channel access procedure for one or more beams of a plurality of beams based on the capability. The communication manager 820 may be configured to or otherwise support a component for communicating via one or more beams based at least in part on the per-beam channel access procedure being successful.

[0175] By including or configuring the communication manager 820 according to the examples described herein, the device 805 may support techniques for signaling a UE's ability to support a per-beam channel access procedure for communicating in one or more shared radio frequency spectrum bands, signaling a channel occupancy configuration associated with the per-beam channel access procedure, or both, which may result in improved communication reliability, reduced latency, improved user experience related to reduced processing, reduced power consumption, more efficient use of communication resources, improved coordination between devices, extended battery life, improved utilization of processing power, and so on.

[0176] In some examples, the communication manager 820 may be configured to perform various operations (e.g., receive, monitor, transmit) using or otherwise cooperating with the transceiver 815, one or more antennas 825, or any combination thereof. Although the communication manager 820 is illustrated as a separate component, in some examples, one or more functions described with reference to the communication manager 820 may be supported or performed by the processor 840, the memory 830, the code 835, or any combination thereof. For example, the code 835 may include instructions executable by the processor 840 to cause the device 805 to perform various aspects of signaling for channel access using multi-beam sensing as described herein, or the processor 840 and the memory 830 may be otherwise configured to perform or support such operations.

[0177] 9 shows a block diagram 900 of a device 905 supporting signaling for channel access using multi-beam sensing according to one or more aspects of the present disclosure. The device 905 may be an example of aspects of the network entity 105 as described herein. The device 905 may include a receiver 910, a transmitter 915, and a communication manager 920. The device 905 may also include a processor. Each of these components may communicate with each other (e.g., via one or more buses).

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

[0179] The transmitter 915 may provide means for outputting (e.g., transmitting, providing, conveying, transmitting) information generated by other components of the device 905. For example, the 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 examples, the transmitter 915 may support outputting information by sending signals via one or more antennas. Additionally or alternatively, the transmitter 915 may support outputting information by sending signals via one or more wired (e.g., electrical, optical) interfaces, wireless interfaces, or any combination thereof. In some examples, the transmitter 915 and the receiver 910 may be co-located in a transceiver, which may include a modem or be coupled to a modem.

[0180] The communication manager 920, the receiver 910, the transmitter 915, or various combinations thereof, or various components thereof, may be examples of means for performing various aspects of signaling for channel access using multi-beam sensing as described herein. For example, the communication manager 920, the receiver 910, the transmitter 915, or various combinations thereof, or components thereof, may support methods for performing one or more of the functions described herein.

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

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

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

[0184] According to examples as disclosed herein, the communication manager 920 may support wireless communications at a network entity. For example, the communication manager 920 may be configured to or otherwise support a means for sending a control message indicating a channel occupancy configuration associated with a per-beam channel access procedure for communicating in one or more shared radio frequency spectrum bands. The communication manager 920 may be configured to or otherwise support a means for communicating with a UE via one or more beams from a plurality of beams based at least in part on the channel occupancy configuration.

[0185] Additionally or alternatively, according to examples as disclosed herein, the communication manager 920 may support wireless communications at a network entity. For example, the communication manager 920 may be configured to or otherwise support a means for receiving a capability message indicating the UE's ability to support a per-beam channel access procedure for communicating in one or more shared radio frequency spectrum bands. The communication manager 920 may be configured to or otherwise support a means for communicating with the UE via one or more beams from a plurality of beams based at least in part on the capability.

[0186] By including or configuring the communication manager 920 according to the examples described herein, the device 905 (e.g., a processor controlling or otherwise coupled to the receiver 910, the transmitter 915, the communication manager 920, or a combination thereof) may support techniques for signaling a UE's ability to support a per-beam channel access procedure for communicating in one or more shared radio frequency spectrum bands, signaling a channel occupancy configuration associated with the per-beam channel access procedure, or both, which may result in reduced processing, lower power consumption, more efficient use of communication resources, and the like.

[0187] 10 shows a block diagram 1000 of a device 1005 supporting signaling for channel access using multi-beam sensing according to one or more aspects of the present disclosure. The device 1005 may be an example of aspects of the device 905 or network entity 105 as described herein. The device 1005 may include a receiver 1010, a transmitter 1015, and a communication manager 1020. The device 1005 may also include a processor. Each of these components may communicate with each other (e.g., via one or more buses).

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

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

[0190] The device 1005 or its various components may be examples of means for performing various aspects of signaling for channel access using multi-beam sensing as described herein. For example, the communication manager 1020 may include a configuration component 1025, a beam component 1030, a capability component 1035, or any combination thereof. The communication manager 1020 may be an example of various aspects of the communication manager 920 as described herein. In some examples, the communication manager 1020 or its various components may be configured to perform various operations (e.g., receive, obtain, monitor, output, send) using or otherwise cooperating with the receiver 1010, the transmitter 1015, or both. For example, the communication manager 1020 may receive information from the receiver 1010, transmit information to the transmitter 1015, or be integrated in combination with the receiver 1010, the transmitter 1015, or both to obtain information, output information, or perform various other operations as described herein.

[0191] According to examples as disclosed herein, the communication manager 1020 can support wireless communications at a network entity. The configuration component 1025 can be configured to or otherwise support means for sending a control message indicating a channel occupancy configuration associated with a per-beam channel access procedure for communicating in one or more shared radio frequency spectrum bands. The beam component 1030 can be configured to or otherwise support means for communicating with a UE via one or more beams from a plurality of beams based at least in part on the channel occupancy configuration.

[0192] Additionally or alternatively, according to examples as disclosed herein, the communication manager 1020 can support wireless communications at a network entity. The capability component 1035 can be configured to or otherwise support means for receiving a capability message indicating the UE's ability to support a per-beam channel access procedure for communicating in one or more shared radio frequency spectrum bands. The beam component 1030 can be configured to or otherwise support means for communicating with the UE via one or more beams from the plurality of beams based at least in part on the capability.

[0193] FIG. 11 shows a block diagram 1100 of a communication manager 1120 supporting signaling for channel access using multi-beam sensing according to one or more aspects of the present disclosure. The communication manager 1120 may be an example of aspects of the communication manager 920, the communication manager 1020, or both as described herein. The communication manager 1120 or its various components may be examples of means for performing various aspects of signaling for channel access using multi-beam sensing as described herein. For example, the communication manager 1120 may include a configuration component 1125, a beam component 1130, a capability component 1135, a channel occupancy component 1140, a timer component 1145, or any combination thereof. Each of these components may communicate with each other directly or indirectly (e.g., via one or more buses), which communication may include communication within a protocol layer of a protocol stack, communication associated with a logical channel of a protocol stack (e.g., between protocol layers of a protocol stack, within a device, component, or virtualized component associated with the network entity 105, between devices, components, or virtualized components associated with the network entity 105), or any combination thereof.

[0194] According to examples as disclosed herein, the communication manager 1120 can support wireless communications at a network entity. The configuration component 1125 can be configured to or otherwise support means for sending a control message indicating a channel occupancy configuration associated with a per-beam channel access procedure for communicating in one or more shared radio frequency spectrum bands. The beam component 1130 can be configured to or otherwise support means for communicating with a UE via one or more beams from a plurality of beams based at least in part on the channel occupancy configuration.

[0195] In some examples, to support communication via one or more beams, channel occupancy component 1140 may be configured as or otherwise support components for communicating on a channel during a COT based at least in part on a channel occupancy configuration, the one or more beams comprising a beam subset from a plurality of beams.

[0196] In some examples, the channel occupancy configuration enables use of COT by the UE only when a subset of beams has a successful per-beam channel access procedure.

[0197] In some examples, to support communication via one or more beams, channel occupancy component 1140 may be configured as or otherwise support components for communicating on a channel during a COT based at least in part on a channel occupancy configuration, the one or more beams including a plurality of beams.

[0198] In some examples, the channel occupancy configuration disables use of COT by the UE only when a subset of beams has a successful per-beam channel access procedure.

[0199] In some examples, to support sending a control message, timer component 1145 may be configured or otherwise support means for sending an indication of one or more timers associated with a per-beam channel access procedure, wherein the control message includes the indication.

[0200] In some examples, to support sending control messages, configuration component 1125 may be configured as or otherwise support means for sending a radio resource control message indicating a channel occupancy configuration, the channel occupancy configuration including a UE-specific configuration for the UE.

[0201] In some examples, to support sending control messages, configuration component 1125 may be configured to or otherwise support means for sending a system information message indicating a channel occupancy configuration, the channel occupancy configuration comprising a cell-specific configuration for a cell provided by a network entity.

[0202] In some examples, configuration component 1125 may be configured to or otherwise support components for identifying the presence of one or more other network entities or wireless devices communicating in one or more shared radio frequency spectrum bands, wherein the channel occupancy configuration is based at least in part on a radio access technology used by each of the one or more other network entities or wireless devices.

[0203] In some examples, the channel occupancy configuration is based at least in part on the traffic type, one or more other wireless devices communicating with the UE, the number of wireless devices in the same cell as the UE, or any combination thereof.

[0204] In some examples, capability component 1135 may be configured to or otherwise support means for receiving a capability message indicating the UE's ability to support per-beam channel access procedures, wherein receiving the control message is based at least in part on the capability message.

[0205] Additionally or alternatively, according to examples as disclosed herein, the communication manager 1120 can support wireless communications at a network entity. The capability component 1135 can be configured to or otherwise support a means for receiving a capability message indicating the UE's ability to support a per-beam channel access procedure for communicating in one or more shared radio frequency spectrum bands. In some examples, the beam component 1130 can be configured to or otherwise support a means for communicating with the UE via one or more beams from a plurality of beams based at least in part on the capability.

[0206] In some examples, to support receiving a capabilities message, capabilities component 1135 may be configured or otherwise support means for receiving within a capabilities message an indication of a threshold number of simultaneous per-beam channel access procedures supported by the UE.

[0207] In some examples, the indication includes a first threshold number of simultaneous channel access procedures per beam associated with a first type of channel access procedure, a second threshold number of simultaneous channel access procedures per beam associated with a second type of channel access procedure, a third threshold number of simultaneous channel access procedures per beam associated with a third type of channel access procedure, or any combination thereof.

[0208] In some examples, configuration component 1125 may be configured as or otherwise support means for sending a control message indicating a channel occupancy configuration associated with a per-beam channel access procedure.

[0209] In some examples, a beam subset of a plurality of beams is used to enable use of COT by the UE only when the beam subset has a successful per-beam channel access procedure, communicating during the COT, based at least in part on a channel occupancy configuration.

[0210] In some examples, multiple beams are used to disable use of COT by the UE only when a subset of beams from the multiple beams have a successful per-beam channel access procedure, communicating during the COT, based at least in part on a channel occupancy configuration.

[0211] FIG. 12 shows a diagram of a system 1200 including a device 1205 that supports signaling for channel access using multi-beam sensing according to one or more aspects of the present disclosure. The device 1205 may be an example of a device 905, a device 1005, or a network entity 105 as described herein, or include components thereof. The device 1205 may communicate with one or more network entities 105, one or more UEs 115, or any combination thereof, which may include communication through one or more wired interfaces, through one or more wireless interfaces, or any combination thereof. The device 1205 may include components that support output and acquisition of communications, such as a communication manager 1220, a transceiver 1210, an antenna 1215, a memory 1225, a code 1230, and a processor 1235. These components may be electronically communicated or otherwise coupled (e.g., operatively, communicatively, functionally, electronically, electrically) via one or more buses (e.g., bus 1240).

[0212] The transceiver 1210 may support bidirectional communication via a wired link, a wireless link, or both as described herein. In some examples, the transceiver 1210 may include a wired transceiver and may communicate bidirectionally with another wired transceiver. Additionally or alternatively, in some examples, the transceiver 1210 may include a wireless transceiver and may communicate bidirectionally with another wireless transceiver. In some examples, the device 1205 may include one or more antennas 1215 that are capable of (e.g., concurrently) sending or receiving wireless transmissions. The 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. Where applicable, the transceiver 1210 or the transceiver 1210 and one or more antennas 1215 or a wired interface may be an example of a transmitter 915, a transmitter 1015, a receiver 910, a receiver 1010, or any combination thereof or any component thereof as described herein. In some examples, the transceiver may be operable 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).

[0213] Memory 1225 may include RAM and ROM. Memory 1225 may store computer-readable, computer-executable code 1230 including instructions that, when executed by processor 1235, cause device 1205 to perform 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 processor 1235, but may (e.g., when compiled and executed) cause a computer to perform the functions described herein. In some cases, memory 1225 may also include, among other things, a BIOS that may control basic hardware or software operations, such as interaction with peripheral components or devices.

[0214] The processor 1235 may include an intelligent hardware device (e.g., a general-purpose processor, a DSP, an ASIC, a CPU, an FPGA, a microcontroller, a programmable logic device, a discrete gate or transistor logic, a discrete hardware component, or any combination thereof). In some cases, the processor 1235 may be configured to operate a memory array using a memory controller. In some other cases, the memory controller may be integrated into the processor 1235. The processor 1235 may be configured to execute computer-readable instructions stored in a memory (e.g., a memory 1225) so that the device 1205 performs various functions (e.g., functions or tasks of signaling for channel access using multi-beam sensing). For example, the device 1205 or a component of the device 1205 may include a processor 1235 and a memory 1225 coupled to the processor 1235, and the processor 1235 and the memory 1225 are configured to perform various functions described herein. Processor 1235 can 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 can host functionality (e.g., by executing code 1230) to perform the functions of device 1205.

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

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

[0217] According to examples as disclosed herein, the communication manager 1220 may support wireless communications at a network entity. For example, the communication manager 1220 may be configured to or otherwise support a means for sending a control message indicating a channel occupancy configuration associated with a per-beam channel access procedure for communicating in one or more shared radio frequency spectrum bands. The communication manager 1220 may be configured to or otherwise support a means for communicating with a UE via one or more beams from a plurality of beams based at least in part on the channel occupancy configuration.

[0218] Additionally or alternatively, according to examples as disclosed herein, the communication manager 1220 may support wireless communications at a network entity. For example, the communication manager 1220 may be configured to or otherwise support a means for receiving a capability message indicating the UE's ability to support a per-beam channel access procedure for communicating in one or more shared radio frequency spectrum bands. The communication manager 1220 may be configured to or otherwise support a means for communicating with the UE via one or more beams from the plurality of beams based at least in part on the capability.

[0219] By including or configuring the communication manager 1220 according to the examples described herein, the device 1205 may support techniques for signaling a UE's ability to support a per-beam channel access procedure for communicating in one or more shared radio frequency spectrum bands, signaling a channel occupancy configuration associated with the per-beam channel access procedure, or both, which may result in improved communication reliability, reduced latency, improved user experience related to reduced processing, reduced power consumption, more efficient use of communication resources, improved coordination between devices, extended battery life, improved utilization of processing power, and so on.

[0220] In some examples, the communication manager 1220 may be configured to perform various operations (e.g., receive, obtain, monitor, output, transmit) using or otherwise cooperating with the transceiver 1210, one or more antennas 1215 (where applicable), or any combination thereof. Although the communication manager 1220 is illustrated as a separate component, in some examples, one or more functions described with reference to the communication manager 1220 may be supported or performed by the processor 1235, the memory 1225, the code 1230, the transceiver 1210, or any combination thereof. For example, the code 1230 may include instructions executable by the processor 1235 to cause the device 1205 to perform various aspects of signaling for channel access using multi-beam sensing as described herein, or the processor 1235 and the memory 1225 may be otherwise configured to perform or support such operations.

[0221] FIG. 13 illustrates a flow chart of a method 1300 for supporting signaling for channel access using multi-beam sensing according to one or more aspects of the present disclosure. The operations of the method 1300 may be implemented by a UE or a component thereof as described herein. For example, the operations of the method 1300 may be performed by a UE 115 as described with reference to FIGS. 1 to 8. In some examples, the UE may execute an instruction set to control the functional elements of the UE to perform the described functions. Additionally or alternatively, the UE may use dedicated hardware to perform various aspects of the described functions.

[0222] At 1305, the method may include receiving a control message indicating a channel occupancy configuration associated with a per-beam channel access procedure for communicating in one or more shared radio frequency spectrum bands. The operations of 1305 may be performed according to examples as disclosed herein. In some examples, aspects of the operations of 1305 may be performed by a configuration component 725 as described with reference to FIG. 7.

[0223] At 1310, the method may include performing a per-beam channel access procedure for each of the plurality of beams. The operations of 1310 may be performed according to examples as disclosed herein. In some examples, aspects of the operations of 1310 may be performed by a channel access procedure component 730 as described with reference to FIG. 7.

[0224] At 1315, the method may include communicating via one or more beams from the plurality of beams based at least in part on the channel occupancy configuration and the per-beam channel access procedure being successful for at least one beam subset of the plurality of beams. The operations of 1315 may be performed according to examples as disclosed herein. In some examples, aspects of the operations of 1315 may be performed by a beam component 735 as described with reference to FIG. 7 .

[0225] FIG. 14 shows a flow chart of a method 1400 for supporting signaling for channel access using multi-beam sensing according to one or more aspects of the present disclosure. The operations of the method 1400 may be implemented by a UE or a component thereof as described herein. For example, the operations of the method 1400 may be performed by a UE 115 as described with reference to FIGS. 1 to 8. In some examples, the UE may execute an instruction set to control the functional elements of the UE to perform the described functions. Additionally or alternatively, the UE may use dedicated hardware to perform various aspects of the described functions.

[0226] At 1405, the method may include sending a capability message indicating the UE's ability to support per-beam channel access procedures for communicating in one or more shared radio frequency spectrum bands. The operations of 1405 may be performed according to examples as disclosed herein. In some examples, aspects of the operations of 1405 may be performed by a capability component 740 as described with reference to FIG. 7.

[0227] At 1410, the method may include performing a per-beam channel access procedure for one or more beams of the plurality of beams according to capabilities. The operations of 1410 may be performed according to examples as disclosed herein. In some examples, aspects of the operations of 1410 may be performed by a channel access procedure component 730 as described with reference to FIG. 7.

[0228] At 1415, the method may include communicating via one or more beams based at least in part on the per-beam channel access procedure being successful. The operations of 1415 may be performed according to examples as disclosed herein. In some examples, aspects of the operations of 1415 may be performed by a beam component 735 as described with reference to FIG. 7.

[0229] FIG. 15 illustrates a flow chart of a method 1500 for supporting signaling for channel access using multi-beam sensing according to one or more aspects of the present disclosure. The operations of the method 1500 may be implemented by a network entity or a component thereof as described herein. For example, the operations of the method 1500 may be performed by a network entity as described with reference to FIGS. 1 to 4 and FIGS. 9 to 12. In some examples, the network entity may execute an instruction set to control the functional elements of the network entity to perform the described functions. Additionally or alternatively, the network entity may use dedicated hardware to perform various aspects of the described functions.

[0230] At 1505, the method may include sending a control message indicating a channel occupancy configuration associated with a per-beam channel access procedure for communicating in one or more shared radio frequency spectrum bands. The operations of 1505 may be performed according to examples as disclosed herein. In some examples, aspects of the operations of 1505 may be performed by a configuration component 1125 as described with reference to FIG. 11.

[0231] At 1510, the method may include communicating with the UE via one or more beams from a plurality of beams based at least in part on a channel occupancy configuration. The operations of 1510 may be performed according to examples as disclosed herein. In some examples, aspects of the operations of 1510 may be performed by a beamforming component 1130 as described with reference to FIG. 11.

[0232] FIG. 16 illustrates a flow chart of a method 1600 for supporting signaling for channel access using multi-beam sensing according to one or more aspects of the present disclosure. The operations of the method 1600 may be implemented by a network entity or a component thereof as described herein. For example, the operations of the method 1600 may be performed by a network entity as described with reference to FIGS. 1 to 4 and FIGS. 9 to 12. In some examples, the network entity may execute an instruction set to control the functional elements of the network entity to perform the described functions. Additionally or alternatively, the network entity may use dedicated hardware to perform various aspects of the described functions.

[0233] At 1605, the method may include receiving a capability message indicating the UE's ability to support a per-beam channel access procedure for communicating in one or more shared radio frequency spectrum bands. The operations of 1605 may be performed according to examples as disclosed herein. In some examples, aspects of the operations of 1605 may be performed by a capability component 1135 as described with reference to FIG. 11.

[0234] At 1610, the method may include communicating with the UE via one or more beams from the plurality of beams based at least in part on the capabilities. The operations of 1610 may be performed according to examples as disclosed herein. In some examples, aspects of the operations of 1610 may be performed by a beam component 1130 as described with reference to FIG. 11.

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

[0236] Aspect 1: A method for wireless communication at a UE, the method comprising: receiving a control message indicating a channel occupancy configuration associated with a per-beam channel access procedure for communicating in one or more shared radio frequency spectrum bands; performing a per-beam channel access procedure for each of a plurality of beams; and communicating via one or more beams from the plurality of beams based at least in part on the channel occupancy configuration and the per-beam channel access procedure being successful for at least one subset of the plurality of beams.

[0237] Aspect 2: A method according to Aspect 1, wherein communicating via the one or more beams includes: communicating on the channel during the channel occupancy time based at least in part on the per-beam channel access procedure being successful for the beam subset, the one or more beams including the beam subset.

[0238] Aspect 3: The method according to aspect 2, wherein the channel occupancy configuration enables the channel occupancy time to be used by the UE only when the beam subset has a successful per-beam channel access procedure.

[0239] Aspect 4: A method according to Aspect 1, wherein communicating via the one or more beams includes: communicating on the channel during the channel occupancy time based at least in part on the per-beam channel access procedure being successful for each of the multiple beams, the one or more beams including the multiple beams.

[0240] Aspect 5: The method according to aspect 4, wherein the channel occupancy configuration disables the use of the channel occupancy time by the UE only when the beam subset has a successful per-beam channel access procedure.

[0241] Aspect 6: A method according to any one of Aspects 1 to 5, wherein executing the per-beam channel access procedure includes: executing the per-beam channel access procedure for each of the multiple beams based at least in part on one or more timers associated with the per-beam channel access procedure, wherein the UE determines that the per-beam channel access procedure is successful when the one or more timers expire.

[0242] Aspect 7: The method according to aspect 6, wherein the control message includes an indication of the one or more timers associated with the per-beam channel access procedure.

[0243] Aspect 8: The method according to any one of aspects 1 to 7, wherein receiving the control message comprises: receiving a radio resource control message indicating the channel occupancy configuration, the channel occupancy configuration comprising a UE-specific configuration for the UE.

[0244] Aspect 9: The method according to any one of aspects 1 to 8, wherein receiving the control message comprises: receiving a system information message indicating the channel occupancy configuration, the channel occupancy configuration comprising a cell-specific configuration for a cell provided by a network entity.

[0245] Aspect 10: A method according to any one of Aspects 1 to 9, wherein the channel occupancy configuration is based at least in part on a service type, one or more other wireless devices communicating with the UE, the number of wireless devices in the same cell as the UE, or any combination thereof.

[0246] Aspect 11: A method according to any one of Aspects 1 to 10, wherein the channel occupancy configuration is based at least in part on a RAT used by one or more network entities or wireless devices to communicate in the one or more shared radio frequency spectrum bands.

[0247] Aspect 12: The method according to any one of Aspects 1 to 11 further includes: sending a capability message indicating the ability of the UE to support the per-beam channel access procedure, wherein receiving the control message is at least partially based on the capability message.

[0248] Aspect 13: A method for performing wireless communications at a UE, the method comprising: sending a capability message indicating the UE's ability to support a per-beam channel access procedure for communicating in one or more shared radio frequency spectrum bands; performing a per-beam channel access procedure for one or more of a plurality of beams based on the capability; and communicating via the one or more beams based at least in part on the success of the per-beam channel access procedure.

[0249] Aspect 14: The method according to aspect 13, wherein sending the capability message includes: sending an indication of a threshold number of simultaneous per-beam channel access procedures supported by the UE within the capability message.

[0250] Aspect 15: A method according to Aspect 14, wherein the indication includes a first threshold number of simultaneous channel access procedures per beam associated with a first type of channel access procedure, a second threshold number of simultaneous channel access procedures per beam associated with a second type of channel access procedure, a third threshold number of simultaneous channel access procedures per beam associated with a third type of channel access procedure, or any combination thereof.

[0251] Aspect 16: The method according to any one of aspects 13 to 15, further comprising: receiving a control message indicating a channel occupancy configuration associated with the per-beam channel access procedure.

[0252] Aspect 17: A method according to Aspect 16, wherein the per-beam channel access procedure is successful for a beam subset of the multiple beams, and the beam subset is used to enable communication during the channel occupancy time using the channel occupancy time by the UE only when the beam subset has a successful per-beam channel access procedure, at least in part based on the channel occupancy configuration.

[0253] Aspect 18: A method according to any one of Aspects 16 to 17, wherein the per-beam channel access procedure is successful for each of the multiple beams, and the multiple beams are used to disable, at least in part based on the channel occupancy configuration, use of channel occupancy time by the UE only when a subset of beams from the multiple beams have a successful per-beam channel access procedure, and to communicate during the channel occupancy time.

[0254] Aspect 19: A method for wireless communication at a network entity, the method comprising: sending a control message indicating a channel occupancy configuration associated with a per-beam channel access procedure for communicating in one or more shared radio frequency spectrum bands; and communicating with a UE via one or more beams from a plurality of beams based at least in part on the channel occupancy configuration.

[0255] Aspect 20: A method according to Aspect 19, wherein communicating via the one or more beams includes: communicating on the channel during the channel occupancy time based at least in part on the channel occupancy configuration, and the one or more beams include a beam subset from the multiple beams.

[0256] Aspect 21: The method according to aspect 20, wherein the channel occupancy configuration enables use of the channel occupancy time by the UE only when the beam subset has a successful per-beam channel access procedure.

[0257] Aspect 22: A method according to Aspect 19, wherein communicating via the one or more beams includes: communicating on the channel during the channel occupancy time based at least in part on the channel occupancy configuration, and the one or more beams include the multiple beams.

[0258] Aspect 23: The method according to aspect 22, wherein the channel occupancy configuration disables the use of the channel occupancy time by the UE only when a subset of beams has a successful per-beam channel access procedure.

[0259] Aspect 24: A method according to any one of Aspects 19 to 23, wherein sending the control message comprises: sending an indication of one or more timers associated with the per-beam channel access procedure, wherein the control message includes the indication.

[0260] Aspect 25: The method according to any one of aspects 19 to 24, wherein sending the control message comprises: sending a radio resource control message indicating the channel occupancy configuration, the channel occupancy configuration comprising a UE-specific configuration for the UE.

[0261] Aspect 26: The method according to any one of aspects 19 to 25, wherein sending the control message comprises: sending a system information message indicating the channel occupancy configuration, the channel occupancy configuration comprising a cell-specific configuration for a cell provided by the network entity.

[0262] Aspect 27: The method according to any one of Aspects 19 to 26 further includes: identifying the presence of one or more other network entities or wireless devices communicating in the one or more shared radio frequency spectrum bands, wherein the channel occupancy configuration is at least partially based on the RAT used by each of the one or more other network entities or wireless devices.

[0263] Aspect 28: A method according to any one of Aspects 19 to 27, wherein the channel occupancy configuration is based at least in part on a service type, one or more other wireless devices communicating with the UE, the number of wireless devices in the same cell as the UE, or any combination thereof.

[0264] Aspect 29: The method according to any one of Aspects 19 to 28 further includes: receiving a capability message indicating the UE's ability to support the per-beam channel access procedure, wherein receiving the control message is at least partially based on the capability message.

[0265] Aspect 30: A method for wireless communications at a network entity, the method comprising: receiving a capability message indicating the ability of a UE to support a per-beam channel access procedure for communicating in one or more shared radio frequency spectrum bands; and communicating with the UE via one or more beams from a plurality of beams based at least in part on the capability.

[0266] Aspect 31: The method according to aspect 30, wherein receiving the capability message includes: receiving an indication of a threshold number of simultaneous per-beam channel access procedures supported by the UE within the capability message.

[0267] Aspect 32: A method according to Aspect 31, wherein the indication includes a first threshold number of simultaneous channel access procedures per beam associated with a first type of channel access procedure, a second threshold number of simultaneous channel access procedures per beam associated with a second type of channel access procedure, a third threshold number of simultaneous channel access procedures per beam associated with a third type of channel access procedure, or any combination thereof.

[0268] Aspect 33: The method according to any one of Aspects 30 to 32, further comprising: sending a control message indicating a channel occupancy configuration associated with the per-beam channel access procedure.

[0269] Aspect 34: A method according to Aspect 33, wherein a beam subset of the multiple beams is used to enable communication during the channel occupancy time by the UE using the channel occupancy time only when the beam subset has a successful per-beam channel access procedure based at least in part on the channel occupancy configuration.

[0270] Aspect 35: A method according to any one of Aspects 33 to 34, wherein the multiple beams are used to disable, at least in part based on the channel occupancy configuration, use of channel occupancy time by the UE only when a subset of beams from the multiple beams has a successful per-beam channel access procedure, and communicate during the channel occupancy time.

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

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

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

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

[0275] Aspect 40: An apparatus for wireless communication at a UE, the apparatus comprising: at least one means for performing a method according to any one of aspects 13 to 18.

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

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

[0278] Aspect 43: An apparatus for wireless communication at a network entity, the apparatus comprising: at least one means for performing the method according to any one of aspects 19 to 29.

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

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

[0281] Aspect 46: An apparatus for wireless communication at a network entity, the apparatus comprising: at least one means for performing the method according to any one of aspects 30 to 35.

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

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

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

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

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

[0287] The functions described herein may be implemented in hardware, software executed by a processor, firmware, or any combination thereof. When implemented in software executed by a processor, the functions may be stored as one or more instructions or codes on a computer-readable medium, or sent via a computer-readable medium. Other examples and specific implementations are within the scope of the present disclosure and the appended claims. For example, due to the nature of software, the functions described herein may be implemented using software executed by a processor, hardware, firmware, hard wiring, or any combination of these items. Features that implement the functions may also be physically located at different locations, including being distributed so that various parts of the functions are implemented at different physical locations.

[0288] Computer-readable media include both non-transient computer storage media and communication media, including any media that facilitates the transfer of computer programs from one place to another.Non-transient storage media can be any available media that can be accessed by a general or special computer.By way of example and not limitation, non-transient computer-readable media may include RAM, ROM, electrically erasable programmable ROM (EEPROM), flash memory, compact disc (CD) ROM or other optical disc storage device, disk storage or other magnetic storage device or can be used to carry or store desired program code components and any other non-transient media that can be accessed by a general or special computer or a general or special processor in the form of instructions or data structures.Moreover, any connection is appropriately referred to as computer-readable media.For example, if software is sent 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 in the definition of computer-readable media. Disk and disc, as used herein, includes CD, laser disc, optical disc, digital versatile disc (DVD), floppy disk and Blu-ray disc where disks usually reproduce data magnetically, while discs reproduce data optically with lasers. Combinations of the above are also included within the scope of computer-readable media.

[0289] As used herein (including in the claims), "or" used in a list of items (e.g., a list of items followed by a phrase such as "at least one of" or "one or more of") indicates an inclusive list, such that, for example, a list of at least one of A, B, or C means A or B or C or AB or AC or BC or ABC (i.e., A and B and C). In addition, as used herein, the phrase "based on" should not be interpreted as a reference to a closed set of conditions. For example, an example step described as "based on condition A" can be based on condition A and condition B without departing from the scope of the present disclosure. In other words, as used herein, the phrase "based on" should be interpreted in the same manner as the phrase "based at least in part on."

[0290] The term "determining" encompasses a variety of actions, and thus, "determining" may include calculating, computing, processing, deriving, investigating, looking up (such as via looking up in a table, database or other data structure), ascertaining, etc. Additionally, "determining" may include receiving (such as receiving information), accessing (such as accessing data in a memory), and similar actions. Additionally, "determining" may include resolving, obtaining, selecting, choosing, establishing, and other such similar actions.

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

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

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

Claims

1. An apparatus for wireless communication at a user equipment (UE), the apparatus comprising: processor; and a memory coupled to the processor, wherein the memory includes instructions executable by the processor to cause the apparatus to: receiving a control message indicating a channel occupancy configuration associated with a per-beam channel access procedure for communicating in one or more shared radio frequency spectrum bands; performing a per-beam channel access procedure for each beam of the plurality of beams; as well as Based at least in part on the channel occupancy configuration and the per-beam channel access procedure being successful for at least one subset of beams of the plurality of beams, communicating via one or more beams from the plurality of beams.

2. The apparatus of claim 1 , wherein the instructions for communicating via the one or more beams are executable by the processor to cause the apparatus to: Based at least in part on the per-beam channel access procedure being successful for the subset of beams, communicating on a channel during a channel occupancy time, the one or more beams comprising the subset of beams.

3. The apparatus of claim 2, wherein the channel occupancy configuration enables use of the channel occupancy time by the UE only when the beam subset has a successful per-beam channel access procedure.

4. The apparatus of claim 1 , wherein the instructions for communicating via the one or more beams are executable by the processor to cause the apparatus to: Based at least in part on the per-beam channel access procedure being successful for each beam in the plurality of beams, communicating on a channel during a channel occupancy time, the one or more beams comprising the plurality of beams.

5. The apparatus of claim 4, wherein the channel occupancy configuration disables use of the channel occupancy time by the UE only when the beam subset has a successful per-beam channel access procedure.

6. The apparatus of claim 1, wherein the instructions for performing the per-beam channel access procedure are executable by the processor to cause the apparatus to: The per-beam channel access procedure is performed for each of the plurality of beams based at least in part on one or more timers associated with the per-beam channel access procedure, wherein the UE determines that the per-beam channel access procedure is successful upon expiration of the one or more timers.

7. The apparatus of claim 6, wherein the control message comprises an indication of the one or more timers associated with the per-beam channel access procedure.

8. The apparatus of claim 1, wherein the instructions for receiving the control message are executable by the processor to cause the apparatus to: A radio resource control message is received indicating the channel occupancy configuration, the channel occupancy configuration comprising a UE-specific configuration for the UE.

9. The apparatus of claim 1 , wherein the instructions for receiving the control message are executable by the processor to cause the apparatus to: A system information message is received indicating the channel occupancy configuration, the channel occupancy configuration comprising a cell-specific configuration for a cell provided by a network entity.

10. An apparatus according to claim 1, wherein the channel occupancy configuration is based at least in part on service type, one or more other wireless devices communicating with the UE, the number of wireless devices in the same cell as the UE, radio access technology used by one or more network entities or wireless devices to communicate in the one or more shared radio frequency spectrum bands, or any combination thereof.

11. The apparatus of claim 1 , wherein the instructions are further executable by the processor to cause the apparatus to: A capability message is sent indicating an ability of the UE to support the per-beam channel access procedure, wherein receiving the control message is based at least in part on the capability message.

12. An apparatus for wireless communication at a user equipment (UE), the apparatus comprising: processor; and a memory coupled to the processor, wherein the memory includes instructions executable by the processor to cause the apparatus to: sending a capability message indicating the UE's ability to support a per-beam channel access procedure for communicating in one or more shared radio frequency spectrum bands; performing a per-beam channel access procedure for one or more beams of the plurality of beams according to the capability; as well as Based at least in part on the per-beam channel access procedure being successful, communicating via the one or more beams.

13. The apparatus of claim 12, wherein the instructions for sending the capability message are executable by the processor to cause the apparatus to: An indication of a threshold number of simultaneous per-beam channel access procedures supported by the UE is sent within the capability message.

14. An apparatus according to claim 13, wherein the indication comprises a first threshold number of simultaneous channel access procedures per beam associated with a first type of channel access procedure, a second threshold number of simultaneous channel access procedures per beam associated with a second type of channel access procedure, a third threshold number of simultaneous channel access procedures per beam associated with a third type of channel access procedure, or any combination thereof.

15. The apparatus of claim 12, wherein the instructions are further executable by the processor to cause the apparatus to: A control message is received indicating a channel occupancy configuration associated with the per-beam channel access procedure.

16. An apparatus for wireless communication at a network entity, the apparatus comprising: processor; and a memory coupled to the processor, wherein the memory includes instructions executable by the processor to cause the apparatus to: transmitting a control message indicating a channel occupancy configuration associated with a per-beam channel access procedure for communicating in one or more shared radio frequency spectrum bands; as well as Based at least in part on the channel occupancy configuration, communicating with a user equipment (UE) via one or more beams from the plurality of beams.

17. The apparatus of claim 16, wherein the instructions for communicating via the one or more beams are executable by the processor to cause the apparatus to: Based at least in part on the channel occupancy configuration, communicating on the channel during a channel occupancy time, the one or more beams comprising a subset of beams from the plurality of beams.

18. The apparatus of claim 17, wherein the channel occupancy configuration enables use of the channel occupancy time by a user equipment (UE) only when the subset of beams has a successful per-beam channel access procedure.

19. The apparatus of claim 16, wherein the instructions for communicating via the one or more beams are executable by the processor to cause the apparatus to: Based at least in part on the channel occupancy configuration, communicating on the channel during a channel occupancy time, the one or more beams comprising the plurality of beams.

20. The apparatus of claim 19, wherein the channel occupancy configuration disables use of the channel occupancy time by a UE only when a subset of beams has a successful per-beam channel access procedure.

21. The apparatus of claim 16, wherein the instructions for sending the control message are executable by the processor to cause the apparatus to: An indication of one or more timers associated with the per-beam channel access procedure is sent, wherein the control message includes the indication.

22. The apparatus of claim 16, wherein the instructions for sending the control message are executable by the processor to cause the apparatus to: A radio resource control message is sent indicating the channel occupancy configuration, the channel occupancy configuration comprising a UE-specific configuration for the UE.

23. The apparatus of claim 16, wherein the instructions for sending the control message are executable by the processor to cause the apparatus to: A system information message is sent indicating the channel occupancy configuration, the channel occupancy configuration comprising a cell-specific configuration for a cell provided by the network entity.

24. The apparatus of claim 16, wherein the instructions are further executable by the processor to cause the apparatus to: Identifying the presence of one or more other network entities or wireless devices communicating in the one or more shared radio frequency spectrum bands, wherein the channel occupancy configuration is based at least in part on a radio access technology used by each of the one or more other network entities or wireless devices.

25. The apparatus of claim 16, wherein the instructions are further executable by the processor to cause the apparatus to: A capability message is received indicating a capability of the UE to support the per-beam channel access procedure, wherein receiving the control message is based at least in part on the capability message.

26. An apparatus for wireless communication at a network entity, the apparatus comprising: processor; and a memory coupled to the processor, wherein the memory includes instructions executable by the processor to cause the apparatus to: receiving a capability message indicating a capability of a user equipment (UE) to support a per-beam channel access procedure for communicating in one or more shared radio frequency spectrum bands; as well as Based at least in part on the capabilities, communicating with the UE via one or more beams from a plurality of beams.

27. The apparatus of claim 26, wherein the instructions for receiving the capability message are executable by the processor to cause the apparatus to: An indication of a threshold number of simultaneous per-beam channel access procedures supported by the UE is received within the capabilities message.

28. An apparatus according to claim 27, wherein the indication comprises a first threshold number of simultaneous channel access procedures per beam associated with a first type of channel access procedure, a second threshold number of simultaneous channel access procedures per beam associated with a second type of channel access procedure, a third threshold number of simultaneous channel access procedures per beam associated with a third type of channel access procedure, or any combination thereof.

29. The apparatus of claim 26, wherein the instructions are further executable by the processor to cause the apparatus to: A control message is sent indicating a channel occupancy configuration associated with the per-beam channel access procedure.

30. The apparatus of claim 29, wherein a beam subset of the plurality of beams is used to enable use of channel occupancy time by the UE for communication during the channel occupancy time based at least in part on the channel occupancy configuration only when the beam subset has a successful per-beam channel access procedure.

Images