Channel occupancy time sharing eligibility

By sending a second communication in the COT in the wireless communication system according to the channel type and the broadcast type of the transmitting UE, the problems of channel congestion and communication failure caused by channel occupation time sharing are solved, and the spectrum usage efficiency is improved.

CN120153750APending Publication Date: 2025-06-13QUALCOMM INC
View PDF 0 Cites 0 Cited by

Patent Information

Application Number
CN202380076815.5
Authority / Receiving Office
CN · China
Patent Type
Applications(China)
Current Assignee / Owner
Priority Date
2023-10-31
Filing Date
2023-11-01
Publication Date
2025-06-13

AI Technical Summary

Technical Problem

In wireless communication systems, channel occupancy time (COT) sharing has problems of channel congestion and communication failure, especially in scenarios with different channel types and broadcast types.

Method used

By sending a second communication in the COT based at least in part on the channel type and the broadcast type in the first communication of the sending UE, the sharing of channel occupancy time is achieved.

Benefits of technology

This approach reduces channel congestion and communication failures between side link UEs, and improves access and use efficiency of unlicensed spectrum.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN120153750A_ABST
    Figure CN120153750A_ABST
Patent Text Reader

Abstract

Aspects of the present disclosure generally relate to wireless communications. In some aspects, a receiving user equipment (UE) may receive, from a transmitting UE, a first communication associated with a channel occupancy time (COT) of the transmitting UE and at least one of a broadcast type or a channel type. The UE may transmit a second communication in the COT of the transmitting UE based at least in part on the broadcast type or the channel type of the first communication. Numerous other aspects are described.
Need to check novelty before this filing date? Find Prior Art

Description

[0001] Cross - Reference to Related Applications

[0002] This patent application claims priority to U.S. Provisional Patent Application No. 63 / 382,582, filed on November 7, 2022, entitled "CHANNEL OCCUPANCY TIMESHARING ELIGIBILITY", and U.S. Non - Provisional Patent Application No. 18 / 499,161, filed on October 31, 2023, entitled "CHANNEL OCCUPANCY TIME SHARING ELIGIBILITY", which are assigned to the assignee of this application. The disclosures of these prior applications are hereby incorporated by reference in their entireties and are considered part of this patent application. Technical Field

[0003] Aspects of the present disclosure generally relate to wireless communication and relate to techniques and apparatus for channel occupancy time (COT) sharing eligibility. Background Art

[0004] Wireless communication systems are widely deployed to provide various telecommunication services such as telephony, video, data, messaging, and broadcasting. A typical wireless communication system may employ multiple access techniques capable of supporting communication with multiple users by sharing available system resources (e.g., bandwidth, transmit power, etc.). Examples of such multiple access techniques include code division multiple access (CDMA) systems, time division multiple access (TDMA) systems, frequency division multiple access (FDMA) systems, orthogonal frequency division multiple access (OFDMA) systems, single - carrier frequency division multiple access (SC - FDMA) systems, time division synchronous code division multiple access (TD - SCDMA) systems, and long - term evolution (LTE). LTE / Advanced LTE is an enhanced set of the Universal Mobile Telecommunications System (UMTS) mobile standard promulgated by the 3rd Generation Partnership Project (3GPP).

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

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

[0007] Some aspects described herein relate to a method of wireless communication performed by a receiving User Equipment (UE). The method may include receiving, from a transmitting UE, a first communication associated with a Channel Occupancy Time (COT) of the transmitting UE and at least one of a broadcast type or a channel type. The method may include transmitting a second communication during the COT of the transmitting UE, at least in part based on the broadcast type or the channel type of the first communication.

[0008] Some aspects described herein relate to a receiving UE for wireless communication. The receiving UE may include a memory and one or more processors coupled to the memory. The one or more processors may be configured to receive, from a transmitting UE, a first communication associated with a COT of the transmitting UE and at least one of a broadcast type or a channel type. The one or more processors may be configured to transmit a second communication during the COT of the transmitting UE, at least in part based on the broadcast type or the channel type of the first communication.

[0009] Some aspects described herein relate to a non-transitory computer-readable medium storing a set of instructions for wireless communication by a receiving UE. The set of instructions, when executed by one or more processors of the receiving UE, may cause the receiving UE to receive, from a transmitting UE, a first communication associated with a COT of the transmitting UE and at least one of a broadcast type or a channel type. The set of instructions, when executed by one or more processors of the receiving UE, may cause the UE to transmit a second communication during the COT of the transmitting UE, at least in part based on the broadcast type or the channel type of the first communication.

[0010] Some aspects described herein relate to an apparatus for wireless communication. The apparatus may include components for receiving, from a transmitting UE, a first communication associated with a COT of the transmitting UE and with at least one of a broadcast type or a channel type. The apparatus may include components for transmitting a second communication in the COT of the transmitting UE based at least in part on the broadcast type or the channel type of the first communication.

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

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

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

[0014] To gain a detailed understanding of the above features of the present disclosure, a more specific description of what was briefly summarized above can be obtained by referring to the various aspects, some of which are illustrated in the accompanying drawings. It should be noted, however, that the drawings merely illustrate certain typical aspects of the present disclosure and are not to be considered as limiting its scope, as the specification may admit other equally valid aspects. The same reference numerals in different drawings may identify the same or similar elements.

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

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

[0017] Figure 3 is a diagram illustrating an example of sidelink communication according to the present disclosure.

[0018] Figure 4A and Figure 4B is a diagram illustrating an example of sidelink communication and access link communication according to the present disclosure.

[0019] Figure 5 is a diagram illustrating an example of signaling associated with channel occupancy time sharing based at least in part on channel type and / or broadcast type according to the present disclosure.

[0020] Figure 6 is a diagram illustrating an example process, such as that performed by a receiving UE, according to the present disclosure.

[0021] Figure 7 is a diagram of an example apparatus for wireless communication according to the present disclosure. Detailed Description

[0022] A user equipment (UE) may communicate on a spectrum that utilizes a channel access mechanism (e.g., an unlicensed channel). For example, before obtaining access to a channel such as an unlicensed channel and / or transmitting thereon, a transmitting device may perform a listen-before-talk (LBT) procedure to contend for access to the unlicensed channel. The LBT procedure generally may include a clear channel assessment (CCA) procedure that is performed to determine whether the channel is available (e.g., not occupied by other transmitters). Specifically, the CCA procedure may include detecting an energy level on the channel and determining whether the energy level meets (e.g., is less than or equal to) a threshold (sometimes referred to as an energy detection threshold, etc.). When the energy level meets (e.g., is not equal to or exceeds) the threshold, the CCA procedure is considered successful, and the transmitting device may obtain access to the channel for a duration referred to as the channel occupancy time (COT), during which the transmitting device may perform transmission without performing additional LBT operations. When the energy level does not meet the threshold, the CCA procedure is unsuccessful, and the contention for channel access may be considered unsuccessful.

[0023] In some deployments, UE-to-UE COT sharing may be enabled. For example, an initiating UE may perform a transmission that may include one or more sidelink control information transmissions indicating when an initial transmission ends, the remaining duration of the COT available for sharing, etc. Accordingly, one or more responding UEs may monitor the sidelink control information transmitted by other UEs (e.g., the initiating UE) to recover COT sharing information that may be used to perform transmission during a period corresponding to the shared COT.

[0024] Thus, UE-to-UE COT sharing may be achieved by enabling multiple UEs to perform transmission during the COT obtained by an initiating UE (e.g., a UE that has successfully performed an LBT procedure to obtain access to an unlicensed channel), resulting in better access to the unlicensed spectrum, more efficient use of the unlicensed spectrum, etc. In some examples, if a receiving UE is the target receiver of a COT transmission of a transmitting UE (i.e., the transmission for which the transmitting UE obtained the COT or the transmission of the transmitting UE within the COT of the transmitting UE), the receiving UE may be permitted to share the COT of the transmitting UE.

[0025] UEs communicating on sidelinks can use different channel types (e.g., Physical Sidelink Feedback Channel (PSFCH), Physical Sidelink Shared Channel (PSSCH), Physical Sidelink Control Channel (PSCCH), or Sidelink Synchronization Signal Block (S-SSB)) and / or different broadcast types (e.g., unicast, multicast, or broadcast as described elsewhere herein) to communicate. There may be situations where COT sharing results in channel congestion or communication failure regardless of the broadcast type or channel type of the COT transmission of the transmitting UE. For example, a broadcast transmission can reach all UEs within the range of the transmitting UE, but it may be impractical to share the COT of the transmitting UE for each UE within the range of the transmitting UE. As another example, if a receiving UE allowed to transmit on a physical channel such as PSFCH, PSSCH, or PSCCH shares the COT used for S-SSB transmission, it may result in channel congestion.

[0026] Some of the techniques described herein provide COT sharing between a transmitting UE and a receiving UE at least in part based on the channel type and / or broadcast type of a first communication (e.g., COT transmission) of the transmitting UE. For example, a receiving UE can receive a first communication associated with the COT of the transmitting UE and at least one of the broadcast type or channel type. The receiving UE can transmit a second communication (e.g., can perform COT sharing with the COT of the transmitting UE) in the COT at least in part based on the broadcast type or channel type of the communication. For example, the second communication can have a broadcast type and / or channel type that allows COT sharing with the first communication. In this way, channel congestion and communication failure between sidelink UEs are reduced.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[0044] In some aspects, the UE 120 may include a communication manager 140. As described in more detail elsewhere herein, the communication manager 140 may receive, from a transmitting UE, a first communication associated with the COT of the transmitting UE and with at least one of a broadcast type or a channel type; and transmit a second communication in the COT of the transmitting UE based at least in part on the broadcast type or the channel type of the first communication. Additionally or alternatively, the communication manager 140 may perform one or more other operations described herein.

[0045] As indicated above, Figure 1 is provided as an example. Other examples may differ from the example(s) described with respect to Figure 1 which are described.

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

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

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

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

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

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

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

[0053] The controller / processor 240 of the network node 110, the controller / processor 280 of the UE 120, and / orFigure 2 Any other components in may perform one or more techniques associated with COT sharing, as described in more detail elsewhere herein. For example, the controller / processor 240 of the network node 110, the controller / processor 280 of the UE 120, and / or Figure 2 any other components of may perform or direct, for example, Figure 6 the operation of process 600 and / or other processes as described herein. The memories 242 and 282 may store data and program code for the network node 110 and the UE 120, respectively. In some examples, the memories 242 and / or 282 may include non-transitory computer-readable media storing one or more instructions for wireless communication (e.g., code and / or program code). For example, when the one or more instructions are executed by one or more processors of the network node 110 and / or the UE 120 (e.g., directly, or after compilation, transformation, and / or interpretation), the one or more processors, the UE 120, and / or the network node 110 may perform or direct, for example, Figure 6 the operation of process 600 and / or other processes as described herein. In some examples, executing the instructions may include running the instructions, transforming the instructions, compiling the instructions, and / or interpreting the instructions, etc.

[0054] In some aspects, a receiving UE includes components for receiving, from a transmitting UE, a first communication associated with the COT of the transmitting UE and with at least one of a broadcast type or a channel type; and / or components for transmitting a second communication in the COT of the transmitting UE based at least in part on the broadcast type or channel type of the first communication. The components for enabling the receiving UE to perform the operations described herein may include, for example, one or more of the communication manager 140, the antenna 252, the modem 254, the MIMO detector 256, the receiving processor 258, the transmitting processor 264, the TX MIMO processor 266, the controller / processor 280, or the memory 282.

[0055] In some aspects, a single processor may perform all functions described as being performed by the one or more processors. In some aspects, the one or more processors may perform a set of functions jointly. For example, a first set of processors (one or more processors) among the one or more processors may perform a first function described as being performed by the one or more processors, and a second set of processors (one or more processors) among the one or more processors may perform a second function described as being performed by the one or more processors. The first set of processors and the second set of processors may be the same set of processors or may be different sets of processors. References to "one or more processors" should be understood to refer to a combination Figure 2Any one or more of the processors described. A reference to "one or more memories" should be understood to refer to any one or more memories of the corresponding device, such as the memory described in conjunction with Figure 2 the memory described. For example, functions described as being performed by one or more memories may be performed by the same subset or different subsets of the one or more memories.

[0056] The hardware and data processing apparatus for implementing or performing the various illustrative logics, logic blocks, modules, and circuits described in connection with the aspects disclosed herein can be implemented or performed using a general purpose single-chip or multi-chip processor, a digital signal processor (DSP), an application specific integrated circuit (ASIC), a field programmable gate array (FPGA) or other programmable logic device, discrete gate or transistor logic components, discrete hardware components, or any combination thereof. A general purpose processor may be a microprocessor, or any conventional 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, multiple microprocessors, one or more microprocessors in conjunction with a DSP core, or any other such configuration. In some aspects, specific processes and methods may be performed by circuitry dedicated to a given function.

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

[0058] As indicated above, Figure 2 is provided as an example. Other examples may be different from the example described in connection with Figure 2 .

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

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

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

[0062] Figure 3 is a diagram illustrating Example 300 of sidelink communication according to the present disclosure.

[0063] As Figure 3As shown, the first UE 305-1 may communicate with a second UE 305-2 (and one or more other UEs 305) via one or more sidelink channels 310. The UEs 305-1 and 305-2 may communicate using one or more sidelink channels 310 for device-to-device (D2D) communication, vehicle-to-everything (V2X) communication (e.g., which may include vehicle-to-vehicle (V2V) communication, vehicle-to-infrastructure (V2I) communication, and / or vehicle-to-pedestrian (V2P) communication), and / or mesh networking. In some aspects, the UEs 305 (e.g., UE 305-1 and / or UE 305-2) may correspond to one or more other UEs described elsewhere herein, such as UE 120. In some aspects, one or more sidelink channels 310 may use the PC5 interface and / or may operate in a high frequency band (e.g., the 5.9 GHz band). Additionally or alternatively, the UEs 305 may use Global Navigation Satellite System (GNSS) timing to synchronize the timing of transmission time intervals (TTIs) (e.g., frames, subframes, time slots, or symbols).

[0064] As Figure 3 Further shown, one or more sidelink channels 310 may include a Physical Sidelink Control Channel (PSCCH) 315, a Physical Sidelink Shared Channel (PSSCH) 320, and / or a Physical Sidelink Feedback Channel (PSFCH) 325. The PSCCH 315 may be used to convey control information, similar to the Physical Downlink Control Channel (PDCCH) and / or the Physical Uplink Control Channel (PUCCH) used for cellular communication with a network node 110 via an access link or access channel. The PSSCH 320 may be used to convey data, similar to the Physical Downlink Shared Channel (PDSCH) and / or the Physical Uplink Shared Channel (PUSCH) used for cellular communication with a network node 110 via an access link or access channel. For example, the PSCCH 315 may carry Sidelink Control Information (SCI) 330, which may indicate various control information for sidelink communication, such as one or more resources (e.g., time resources, frequency resources, and / or spatial resources), where a Transport Block (TB) 335 may be carried on the PSSCH 320. The TB 335 may include data. The PSFCH 325 may be used to convey sidelink feedback 340, such as Hybrid Automatic Repeat reQuest (HARQ) feedback (e.g., acknowledgement or negative acknowledgement (ACK / NACK) information), Transmit Power Control (TPC), and / or Scheduling Request (SR).

[0065] Although shown on the PSCCH 315, in some aspects, the SCI 330 may include multiple communications at different levels, such as a first-level SCI (SCI-1) and a second-level SCI (SCI-2). The SCI-1 may be transmitted on the PSCCH 315. The SCI-2 may be transmitted on the PSSCH 320. The SCI-1 may include, for example, an indication of one or more resources (e.g., time resources, frequency resources, and / or spatial resources) on the PSSCH 320, information for decoding sidelink communications on the PSSCH, a quality of service (QoS) priority value, a resource reservation period, a PSSCH DMRS mode, an SCI format for the SCI-2, a β offset for the SCI-2, the number of PSSCH DMRS ports, and / or an MCS. The SCI-2 may include information associated with data transmission on the PSSCH 320, such as a HARQ process ID, a new data indicator (NDI), a source identifier, a destination identifier, and / or a channel state information (CSI) report trigger.

[0066] In some aspects, one or more sidelink channels 310 may use a resource pool. For example, a scheduling assignment (e.g., included in the SCI 330) may be transmitted across time in a subchannel using a specific resource block (RB). In some aspects, data transmission (e.g., on the PSSCH 320) associated with the scheduling assignment may occupy adjacent RBs in the same subframe as the scheduling assignment (e.g., using frequency division multiplexing). In some aspects, the scheduling assignment and the associated data transmission are not transmitted on adjacent RBs.

[0067] In some aspects, the UE 305 may operate using a sidelink transmission mode (e.g., mode 1), where resource selection and / or scheduling is performed by a network node 110 (e.g., a base station, CU, or DU). For example, the UE 305 may receive (e.g., directly or via one or more network nodes) from the network node 110 a grant for sidelink channel access and / or scheduling (e.g., in downlink control information (DCI) or in a radio resource control (RRC) message, such as a configured grant). In some aspects, the UE 305 may operate using a transmission mode (e.g., mode 2), where resource selection and / or scheduling is performed by the UE 305 (e.g., instead of the network node 110). In some aspects, the UE 305 may perform resource selection and / or scheduling by sensing the channel availability for transmission. For example, the UE 305 may measure the RSSI parameter associated with various sidelink channels (e.g., the sidelink - RSSI (S - RSSI) parameter), may measure the RSRP parameter associated with various sidelink channels (e.g., the PSSCH - RSRP parameter), and / or may measure the RSRQ parameter associated with various sidelink channels (e.g., the PSSCH - RSRQ parameter), and may select a channel for transmitting sidelink communication at least in part based on the measurements.

[0068] Additionally or alternatively, the UE 305 may use the SCI 330 received in the PSCCH 315 to perform resource selection and / or scheduling, and the SCI may indicate the occupied resources and / or channel parameters. Additionally or alternatively, the UE 305 may perform resource selection and / or scheduling by determining the channel busy rate (CBR) associated with each sidelink channel, and the channel busy rate may be used for rate control (e.g., by indicating the maximum number of resource blocks that the UE 305 may use for a particular set of subframes).

[0069] In the transmission mode where the UE 305 performs resource selection and / or scheduling, the UE 305 may generate a sidelink grant and may send the grant in the SCI 330. The sidelink grant may indicate, for example, one or more parameters (e.g., transmission parameters) to be used for an upcoming sidelink transmission, such as one or more resource blocks (e.g., for the TB 335) to be used for an upcoming sidelink transmission on the PSSCH 320, one or more subframes to be used for an upcoming sidelink transmission, and / or the MCS to be used for an upcoming sidelink transmission. In some aspects, the UE 305 may generate a sidelink grant that indicates one or more parameters for semi - persistent scheduling (SPS), such as the periodicity of sidelink transmissions. Additionally or alternatively, the UE 305 may generate a sidelink grant for event - driven scheduling (such as for on - demand sidelink messages).

[0070] As indicated above, Figure 3 is provided as an example. Other examples may differ from the example Figure 3 described.

[0071] Figure 4A and Figure 4B are diagrams illustrating Example 400 of sidelink communication and access link communication according to the present disclosure.

[0072] As Figure 4A shown, the transmitter (Tx) / receiver (Rx) UE 405 and the Rx / Tx UE 410 may communicate with each other via the sidelink, as described above in connection with Figure 3 described. As further shown in the figure, in some sidelink modes, the network node 110 may communicate with the Tx / Rx UE 405 (e.g., directly or via one or more network nodes) via, for example, a first access link. Additionally or alternatively, in some sidelink modes, the network node 110 may communicate with the Rx / Tx UE 410 (e.g., directly or via one or more network nodes) via, for example, a second access link. The Tx / Rx UE 405 and / or the Rx / Tx UE 410 may correspond to one or more UEs described elsewhere herein, such as Figure 1 the UE 120 of Figure 3 or the UE 305 of

[0073] For example, to meet the growing traffic demands, various efforts have been made to improve the spectral efficiency in wireless networks and thus increase the network capacity (e.g., via the use of higher-order modulation, advanced MIMO antenna technology, multi-cell coordination techniques, etc.). Another potential way to increase the network capacity is to expand the system bandwidth. However, the available spectrum in the lower frequency bands that has traditionally been licensed or otherwise allocated to mobile network operators may be limited.

[0074] Accordingly, various techniques have been developed to enable operation of cellular RATs in unlicensed or other shared spectrums. For example, Licensed-Assisted Access (LAA) uses carrier aggregation on the downlink to combine LTE in a licensed band with LTE in an unlicensed band (e.g., the 2.4 and / or 5 GHz bands already occupied by Wireless Local Area Network (WLAN) or “Wi-Fi” devices). As another example, Enhanced LAA (eLAA) and Further Enhanced LAA (feLAA) techniques enable both uplink and downlink LTE operations to be performed in unlicensed spectrum. As yet another example, MulteFire is an LTE-based technology that operates in unlicensed and shared spectrums in stand-alone mode. As yet another example, NR-U enables NR operations to be performed in unlicensed spectrum. Generally, when operating a cellular RAT in unlicensed spectrum (e.g., using LAA, eLAA, feLAA, MulteFire, and / or NR-U), one challenge that arises is the need to ensure fair coexistence with incumbent (e.g., WLAN) systems that may operate in that unlicensed spectrum.

[0075] For example, before obtaining access to a channel such as an unlicensed channel and / or transmitting thereon, a transmitting device (e.g., network node 110, UE 120, UE 405, UE 410, etc.) may perform a Listen-Before-Talk (LBT) procedure to contend for access to the unlicensed channel. The LBT procedure may generally include a Clear Channel Assessment (CCA) procedure that is performed to determine whether the channel is available (e.g., not occupied by other transmitters). Specifically, the CCA procedure may include detecting an energy level on the channel and determining whether the energy level meets (e.g., is less than or equal to) a threshold (sometimes referred to as an energy detection threshold, etc.). When the energy level meets (e.g., is not equal to or exceeds) the threshold, the CCA procedure is considered successful, and the transmitting device may obtain access to the channel for a duration referred to as the Channel Occupancy Time (COT) during which the transmitting device may perform transmission without performing additional LBT operations. When the energy level does not meet the threshold, the CCA procedure is unsuccessful, and the contention for channel access may be considered unsuccessful.

[0076] When the CCA procedure results in a determination that the channel band is unavailable (e.g., due to an energy level detected on the channel indicating that another device is already using the channel), the CCA procedure may be performed again later. In an environment where a transmitting device may obtain limited access to a channel (e.g., due to WLAN activity or transmissions by other devices), an Extended CCA (eCCA) procedure may be employed to increase the likelihood that the transmitting device will successfully obtain access to the channel.

[0077] For example, a transmitting device that executes the eCCA procedure may perform a random number of CCA procedures (from 1 to q) according to the eCCA counter. In the case where the transmitting device senses that the channel has become clear and / or when the transmitting device senses that the channel has become clear, the transmitting device may initiate a random waiting period based on the eCCA counter, and if the channel remains clear during the random waiting period, transmission may begin.

[0078] Thus, although a wireless network may be configured to use unlicensed spectrum to achieve faster data rates, provide a more responsive user experience, offload traffic from licensed spectrum, etc., ensuring fair coexistence with existing systems (e.g., WLAN devices) can be balanced with the efficient use of unlicensed spectrum. For example, even when there is no interference, the LBT procedure for ensuring that no other device is already using the channel introduces a delay before transmission can begin, which can degrade the user experience, resulting in unacceptable performance for latency-sensitive or delay-sensitive applications, etc. In addition, these problems may worsen when the initial CCA procedure is unsuccessful, because the transmitting device can only transmit on the channel after performing an additional number of CCA procedures and determining that the channel has become clear and remains clear for a random waiting period. In addition, in some cases, the COT obtained by the transmitting device may have a duration longer than that required for the transmitting device to perform the desired transmission, which can lead to inefficient use of the unlicensed channel.

[0079] Therefore, in some scenarios, a wireless network may enable the COT obtained by a transmitting device to be shared with other nodes to improve access and efficiency for unlicensed channels. For example, in downlink-to-uplink COT sharing on an access link, network node 110 may obtain a COT using eCCA, and the COT may be shared with one or more UEs (e.g., UE 120, UE 405, UE 410, etc.), and the one or more UEs may then transmit uplink signals within the COT obtained by network node 110. In this case, a UE attempting to initiate an uplink transmission within the COT shared with network node 110 may perform the uplink transmission without having to perform the LBT procedure, or the UE may perform the uplink transmission after performing a single CCA with a shorter LBT procedure (e.g., a Class 2 LBT procedure when the downlink-to-uplink gap duration is between 16 μs and 25 μs, a Class 1 LBT procedure when the downlink-to-uplink gap duration is less than or equal to 16 μs, etc.).

[0080] Additionally or alternatively, the wireless network may support uplink to downlink COT sharing on the access link. In this case, the UE-initiated COT (e.g., for a configured grant PUSCH or scheduled uplink transmission) may be shared with network node 110. In this way, network node 110 may be allowed to transmit control and / or broadcast signals and / or channels for any UE served by network node 110, as long as the transmission includes downlink signals, channels, and / or other transmissions (e.g., PDSCH, PDCCH, reference signals, etc.) intended to be received by the UE that initiated the channel occupancy.

[0081] Additionally or alternatively, the wireless network may support UE-to-UE COT sharing on the sidelink. For example, as shown by reference numeral 415 in Figure 4B , the COT obtained by the initiating UE (e.g., UE 405) may be shared in a frequency division multiplexing (FDM) mode by dividing the COT into multiple interleaves (e.g., time periods during which one or more UEs may perform transmission operations). For example, as Figure 4B shown, the initiating UE may use one or more sidelink resources (e.g., time and frequency resources) to perform transmission in the first interleave after the COT has been obtained, and the responding UE (e.g., UE 410) may use sidelink frequency resources that do not overlap with the sidelink frequency resources used by the initiating UE to perform transmission operations in subsequent interleaves. Thus, as Figure 4B shown, FDM or interleave-based COT sharing may introduce short transmission gaps between the interleaves to allow other UEs to perform transmission operations in subsequent interleaves during the shared COT, and the sidelink control information transmitted by the initiating UE may carry information to support interleave-based COT sharing. The initiating UE may be referred to herein as the transmitting UE, and the responding UE may be referred to as the receiving UE.

[0082] Additionally or alternatively, as shown by reference numeral 420, UE-to-UE COT sharing may be enabled in a time division multiplexing (TDM) mode. In this case, the total COT may be divided into an initial time period during which the initiating UE may perform transmission, and the transmission may include one or more sidelink control information transmissions indicating when the initial transmission ends, the remaining duration of the COT available for sharing, etc. Thus, one or more responding UEs may monitor the sidelink control information transmitted by other UEs (e.g., the initiating UE) to recover the COT sharing information available for performing transmission during the time period corresponding to the shared COT.

[0083] Thus, as described above, UE-to-UE COT sharing can be implemented to achieve better access to unlicensed spectrum, more efficient use of unlicensed spectrum, etc., by enabling multiple UEs to perform transmissions during the COT obtained by an initiating UE (e.g., a UE that has successfully executed an LBT procedure to obtain access to an unlicensed channel). In some examples, if a receiving UE is the target receiver of a COT transmission of a transmitting UE (i.e., the transmission for which the transmitting UE obtained the COT or the transmission of the transmitting UE within the COT of the transmitting UE), the receiving UE may be permitted to share the COT of the transmitting UE.

[0084] UEs communicating on a sidelink may use different channel types (e.g., PSFCH, PSSCH, PSCCH, or sidelink synchronization signal block (S-SSB)) and / or different broadcast types (e.g., unicast, multicast, or broadcast as described elsewhere herein) to communicate. There may be cases where COT sharing results in channel congestion or communication failure without considering the broadcast type or channel type of the COT transmission of the transmitting UE. For example, a broadcast transmission may reach all UEs within the range of the transmitting UE, but it may not be practical for each UE within the range of the transmitting UE to share the COT of the transmitting UE. As another example, if a receiving UE that is permitted to transmit on a physical channel such as PSFCH, PSSCH, or PSCCH shares the COT for S-SSB transmission, it may result in channel congestion.

[0085] Some of the techniques described herein provide COT sharing between a transmitting UE and a receiving UE at least in part based on the channel type and / or broadcast type of a first communication (e.g., a COT transmission) of the transmitting UE. For example, the receiving UE may receive a first communication associated with the COT of the transmitting UE and at least one of the broadcast type or channel type. The receiving UE may transmit a second communication (e.g., may perform COT sharing with the COT of the transmitting UE) within the COT at least in part based on the broadcast type or channel type of the communication. For example, the second communication may have a broadcast type and / or channel type that permits COT sharing with the first communication. In this way, channel congestion and communication failure between sidelink UEs are reduced.

[0086] As indicated above, Figure 4A and Figure 4B are provided as examples. Other examples may be different from the examples described with respect to Figure 4A and Figure 4B described.

[0087] Figure 5FIG. 500 is a diagram illustrating an example 500 of signaling associated with COT sharing that is at least partially based on channel type and / or broadcast type according to the present disclosure. As shown, example 500 includes a transmitting UE (e.g., UE 120, UE 405, UE 410) and a receiving UE (e.g., UE 120, UE 405, UE 410).

[0088] As shown by reference numeral 505 in Figure 5 the transmitting UE may obtain a COT during which the transmitting UE is permitted to transmit over an unlicensed channel. In some aspects, the transmitting UE may successfully perform the LBT procedure to obtain the COT. For example, before obtaining access to the unlicensed channel and transmitting thereon, the transmitting UE may perform the LBT procedure to contend for access to the unlicensed channel. In some aspects, the LBT procedure may include a CCA procedure performed by the transmitting UE to determine whether the unlicensed channel is available (e.g., not occupied by other transmitters). In some aspects, the transmitting UE may detect the energy level on the unlicensed channel and, if the energy level on the unlicensed channel meets (e.g., is less than or equal to) a threshold, may determine that the CCA procedure is successful. In such cases, the transmitting UE may obtain access to the unlicensed channel to obtain the COT during which the transmitting UE may perform transmission without performing additional LBT operations.

[0089] In the case where the energy level detected on the unlicensed channel fails to meet (e.g., is greater than or equal to the threshold), the CCA procedure may be determined to be unsuccessful and the transmitting UE may perform the CCA procedure again and obtain the COT at a later time. Additionally or alternatively, the transmitting UE may obtain the COT by performing another type of channel access procedure. For example, the transmitting UE may obtain the COT by performing an extended CCA (eCCA) procedure.

[0090] As shown by reference numeral 510, the receiving UE may receive COT structure information. For example, the transmitting UE may transmit the COT structure information at least partially based on obtaining the COT. The COT structure information may indicate the resource structure of the COT (e.g., time resources and / or frequency resources).

[0091] As shown by reference numeral 515, the transmitting UE may transmit a first communication and the receiving UE may receive the first communication. In some aspects, the first communication may enable sharing of the COT obtained by the transmitting UE (e.g., the first communication may include a COT sharing indication). In some aspects, the COT sharing indication may be included in sidelink control information (e.g., SCI-1 or SCI-2) transmitted by the transmitting UE to a group of one or more UEs (e.g., the group of UEs including the receiving UE). In some aspects, the receiving UE may be the target receiver of the first communication. For example, the first communication may indicate the identifier of the receiving UE as the target receiver.

[0092] As shown in the figure, the first communication may have a first channel type. For example, the first channel type may be a PSCCH channel type (e.g., the first communication may be transmitted on a PSCCH (such as SCI-1 on the PSCCH)). As another example, the first channel type may be a PSSCH channel type (e.g., the first communication may be transmitted on a PSSCH (such as SCI-2) and / or on a data payload (such as a transport block) on the PSSCH). As yet another example, the first channel type may be a PSFCH channel type (e.g., the first communication may be transmitted on a PSFCH, such as feedback on the PSFCH for sidelink communication). For example, the first channel type may be an S-SSB channel type (e.g., the first communication may be or include an S-SSB). In some aspects, the first communication may have multiple channel types. For example, the first communication may include multiple communications, such as multiple transmissions by a transmitting UE in a COT. Each of the multiple communications may have a corresponding channel type. Only as an example, the first communication may include a first transmission having a PSFCH channel type and a second transmission having a PSSCH channel type.

[0093] As shown in the figure, the first communication may have a first broadcast type. The broadcast type may indicate whether the first communication is a unicast transmission, a multicast transmission, or a broadcast transmission. For example, the broadcast type may be a unicast type, a multicast type, or a broadcast type. A unicast transmission is a transmission from a single transmitting UE to a single receiving UE, such as at least partially based on a transmitter identifier of the transmitting UE and a receiver identifier of the receiving UE. A multicast transmission is a transmission from a single transmitting UE to a group of (one or more) receiving UEs. The multicast transmission may be a connectionless multicast transmission or a managed multicast transmission. The multicast transmission may be directed to the UE group according to a group identifier of the UE group. A broadcast transmission is a transmission from a single transmitting UE to all receiving UEs within the range of the transmitting UE. For example, the broadcast transmission may indicate a range parameter for identifying whether a receiving UE is within the range of the transmitting UE. As another example, all UEs capable of decoding the broadcast transmission may receive the broadcast transmission. In some aspects, the first communication may have multiple broadcast types. For example, the first communication may include multiple transmissions, and each of the multiple transmissions may have a corresponding broadcast type.

[0094] As shown by reference numeral 520, the receiving UE may identify one or more allowed broadcast types and / or channel types of a second communication using a COT at least partially based on the broadcast type and / or the channel type. For example, the receiving UE may identify one or more allowed broadcast types and / or one or more allowed channel types that may share the COT of the transmitting UE.

[0095] In some aspects, a receiving UE may receive configuration information indicating one or more allowed broadcast types and / or one or more allowed channel types. The configuration information may be received from a network node (e.g., via RRC or other semi-static signaling), via a UE profile or other static signaling or configuration, etc. For example, the configuration information may indicate a table. In some aspects, the table may indicate a first broadcast type for a first communication and one or more second broadcast types allowed for a second communication (for the purpose of COT sharing between the first communication and the second communication). Additionally or alternatively, the table may indicate a first channel type for a first communication and one or more second channel types allowed for a second communication (for the purpose of COT sharing between the first communication and the second communication). Thus, at least partially based on the broadcast type and / or channel type of the first communication, the receiving UE may be eligible to use a limited broadcast type and / or a limited channel type for COT sharing.

[0096] Table 1 is an example table indicating allowed second broadcast types for a second communication in view of the first broadcast type of the first communication. Each row corresponds to the first broadcast type. Each column corresponds to the second broadcast type. "Yes" indicates that the second communication of the indicated second broadcast type may use COT sharing in the COT of the first communication of the indicated first broadcast type (e.g., obtained for it) to transmit. In some aspects, Table 1 may be a lower triangular matrix, where the lower triangle is occupied by "Yes", such that the receiving UE does not use COT sharing to transmit to more UEs than the intention of the transmitting UE.

[0097] Second broadcast type: Unicast Second broadcast type: Multicast Second broadcast type: Broadcast First broadcast type: Unicast Yes No No First broadcast type: Multicast Yes Yes No First broadcast type: Broadcast Yes Yes No

[0098] Table 1

[0099] Table 2 is an example table indicating allowed second channel types for a second communication in view of the first channel type of the first communication. Each row corresponds to the first channel type. Each column corresponds to the second channel type. "Yes" indicates that the second communication of the indicated second channel type may use COT sharing in the COT of the first communication of the indicated first channel type (e.g., obtained for it) to transmit.

[0100]

[0101] Table 2

[0102] For example, if a transmitting UE sends unicast communication to a receiving UE, the receiving UE may be able to send unicast data back to the transmitting UE only according to Table 1 (e.g., at least partially based on the first communication being unicast communication and the receiving UE being the target of the first communication). Thus, COT sharing by the receiving UE for multicast or broadcast communication (such as sending PSSCH to other non-COT initiating UEs) is avoided. As another example, if the transmitting UE sends a first multicast transmission to the receiving UE (e.g., to a UE group including the receiving UE), the receiving UE may be allowed to send only unicast communication to the transmitting UE, or may be allowed to send unicast communication and multicast communication to the UE group including the transmitting UE (e.g., the same UE group as the UE group to which the first multicast transmission is sent). This may help to confirm the first multicast transmission, or may help with subsequent group-based communication between UE groups. In some aspects, if the receiving UE uses the COT shared with the first communication to send multicast communication, the target receiver of the multicast communication may be the same as the target receiver of the first communication, which ensures that the multicast communication is only targeted at the target receiver of the first communication of the transmitting UE. If the transmitting UE sends broadcast communication to the receiving UE, the receiving UE may be allowed to send only unicast communication, only unicast or multicast communication, or unicast, multicast, and broadcast communication including the transmitting UE.

[0103] In some aspects, the receiving UE may be eligible to share COT with the first communication at least partially based on the channel type of the first communication of certain channel types. For example, a second communication having a channel type that can carry important information (e.g., S-SSB or PSFCH) may be allowed to share COT with a first communication having a PSSCH channel type. As another example, a second communication having an S-SSB channel type may be allowed to share COT with a first communication having a PSFCH channel type. As another example, a second communication carrying a PSSCH retransmission (e.g., having a PSSCH channel type) may share COT with a first communication having a PSFCH channel type. As another example, when the transmitting UE is the synchronization reference node of the receiving UE (e.g., the node from which the sidelink timing and / or frequency alignment of the receiving UE is derived), a second communication having an S-SSB channel type may be allowed to share COT with a first communication having an S-SSB channel type.

[0104] In some aspects, the first communication or the transmitting UE may include an indication of the broadcast type or channel type for the second communication. For example, the COT structure information may indicate the allowed broadcast type and / or the allowed channel type for the second communication, such as by referring to a semi-statically configured table. Thus, the transmitting UE may use COT sharing with the transmitting UE to select the broadcast type and / or channel type of the second communication of the receiving UE downward.

[0105] In some aspects, one or more allowed broadcast types and / or channel types may be at least partially based on the multiple channel types and / or multiple broadcast types of a first communication. For example, the first communication may have multiple channel types and / or multiple broadcast types. In this example, the receiving UE may select a broadcast type and / or a channel type at least partially based on the multiple channel types and / or multiple broadcast types. For example, the receiving UE may select a broadcast type from all broadcast types that allow COT sharing with any of the multiple broadcast types (e.g., if the first communication includes both multicast and unicast transmissions to the receiving UE, the receiving UE may select multicast as the reference broadcast type in Table 1, which allows the receiving UE to select unicast or multicast for COT sharing). As another example, the receiving UE may select a channel type from all channel types that allow COT sharing with any of the multiple channel types. For example, if the first communication includes both PSSCH and PSFCH transmissions to the receiving UE, the receiving UE may select PSSCH as the reference channel type in Table 2, which allows the receiving UE to select the PSSCH channel type, the PSFCH channel type, the PSCCH channel type, or the S-SSB channel type for COT sharing).

[0106] As indicated by reference numeral 525, the receiving UE may transmit a second communication within the COT of the transmitting UE. The receiving UE may transmit the second communication at least partially based on the broadcast type and / or channel type of the first communication. For example, the second communication may have a broadcast type that allows COT sharing with the first communication having the broadcast type of the first communication. As another example, the second communication may have a channel type that allows COT sharing with the first communication having the channel type of the first communication. In some aspects, the second communication may be directed to the transmitting UE. For example, the transmitting UE may be the target receiver of the second communication, or the transmitting UE may belong to a group of UEs to which the second communication is directed. In some aspects, the receiving UE may transmit an indication of COT sharing with the transmitting UE.

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

[0108] Figure 6 is a diagram illustrating an example process 600 performed, for example, by a receiving UE in accordance with the present disclosure. Example process 600 is an example of operations performed by a receiving UE (e.g., UE 120, UE 405, UE 410, Figure 5 the receiving UE of) associated with channel occupancy time sharing eligibility.

[0109] As Figure 6As shown, in some aspects, process 600 may include receiving, from a transmitting UE, a first communication associated with a COT of the transmitting UE and with at least one of a broadcast type or a channel type (block 610). For example, a receiving UE (e.g., using Figure 7 the communication manager 140 depicted in Figure 5 and / or the receiving component 702) may receive, from the transmitting UE, a first communication associated with the COT of the transmitting UE and with at least one of a broadcast type or a channel type, as described above, for example, in connection with

[0110] reference numeral 515 of Figure 6 As further shown, in some aspects, process 600 may include transmitting a second communication in the COT of the transmitting UE, at least in part, based on the broadcast type or the channel type of the first communication (block 620). For example, a UE (e.g., using Figure 7 the communication manager 140 depicted in Figure 5 and / or the transmitting component 704) may transmit a second communication in the COT of the transmitting UE, at least in part, based on the broadcast type or the channel type of the first communication, as described above, for example, in connection with

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

[0112] In a first aspect, the second communication is associated with the same broadcast type as the first communication.

[0113] In a second aspect, either alone or in combination with the first aspect, the first communication is associated with a multicast broadcast type, and the second communication is associated with a unicast broadcast type or a multicast broadcast type, at least in part, based on the first communication being associated with the multicast broadcast type.

[0114] In a third aspect, either alone or in combination with one or more of the first and second aspects, the first communication is associated with a unicast broadcast type, and the second communication is associated with a unicast broadcast type, at least in part, based on the first communication being associated with the unicast broadcast type.

[0115] In a fourth aspect, either alone or in combination with one or more of the first through third aspects, the first communication is associated with a broadcast broadcast type, and the second communication is associated with a unicast broadcast type or a multicast broadcast type, at least in part, based on the first communication being associated with the broadcast broadcast type.

[0116] In a fifth aspect, either alone or in combination with one or more of the first through fourth aspects, the second communication is associated with a multicast broadcast type and is directed to a UE group that includes the transmitting UE.

[0117] In a sixth aspect, either alone or in combination with one or more of the first to fifth aspects, the first communication is also directed to a UE group including the transmitting UE, and the UE group includes the receiving UE.

[0118] In a seventh aspect, either alone or in combination with one or more of the first to sixth aspects, process 600 includes receiving a configuration indicating one or more allowed broadcast types for a second communication, wherein the one or more allowed broadcast types are at least partially based on the broadcast type associated with the first communication.

[0119] In an eighth aspect, either alone or in combination with one or more of the first to seventh aspects, the first communication indicates one or more allowed broadcast types for the second communication.

[0120] In a ninth aspect, either alone or in combination with one or more of the first to eighth aspects, the COT structure indicator of the first communication indicates one or more allowed broadcast types.

[0121] In a tenth aspect, either alone or in combination with one or more of the first to ninth aspects, the first communication is associated with a plurality of broadcast types including a broadcast type, and the method further includes selecting a broadcast type for the second communication at least partially based on the plurality of broadcast types.

[0122] In an eleventh aspect, either alone or in combination with one or more of the first to tenth aspects, the channel type is a first channel type, and the second communication has a second channel type at least partially based on the first channel type.

[0123] In a twelfth aspect, either alone or in combination with one or more of the first to eleventh aspects, the first channel type is a physical sidelink shared channel type, and the second channel type is a sidelink synchronization signal block channel type or a feedback channel type.

[0124] In a thirteenth aspect, either alone or in combination with one or more of the first to twelfth aspects, the first channel type is a feedback channel type, and the second channel type is a sidelink synchronization signal block channel type.

[0125] In a fourteenth aspect, either alone or in combination with one or more of the first to thirteenth aspects, the first channel type is a sidelink synchronization signal block type, and the second channel type is a sidelink synchronization signal block channel type.

[0126] In a fifteenth aspect, either alone or in combination with one or more of the first to fourteenth aspects, the transmitting UE is a synchronization reference node of the receiving UE.

[0127] In a sixteenth aspect, either alone or in combination with one or more of aspects one to fifteen, process 600 includes receiving a configuration indicating one or more allowed channel types for a second communication, wherein the one or more allowed channel types are based at least in part on a first channel type associated with the first communication.

[0128] In a seventeenth aspect, either alone or in combination with one or more of aspects one to sixteen, the first communication is associated with a plurality of channel types including the first channel type, and the method further comprises selecting a second channel type for the second communication based at least in part on the plurality of channel types.

[0129] although Figure 6 An example block diagram of process 600 is shown, but in some aspects, process 600 may include Figure 6 The blocks depicted may be additional blocks, fewer blocks, different blocks, or blocks arranged in a different manner than those depicted. Additionally or alternatively, two or more of the blocks of process 600 may be performed in parallel.

[0130] Figure 7 is a diagram of an example apparatus 700 for wireless communication according to the present disclosure. Apparatus 700 may be a UE, or a UE may include apparatus 700. In some aspects, apparatus 700 includes a receiving component 702 and a transmitting component 704 that may communicate with each other (e.g., via one or more buses and / or one or more other components). As shown, apparatus 700 may communicate with another apparatus 706 (such as a UE, a base station, or another wireless communication device) using receiving component 702 and transmitting component 704. As further shown, apparatus 700 may include a communication manager 140. Communication manager 140 may include one or more of identification component 708, etc.

[0131] In some aspects, the apparatus 700 may be configured to perform Figure 4A , Figure 4B and Figure 5 Additionally or alternatively, the apparatus 700 may be configured to perform one or more of the processes described herein (such as Figure 6 In some aspects, the apparatus 700 and / or Figure 7 One or more of the components shown may include a combination of Figure 2 One or more components of the UE. Additionally or alternatively, Figure 7 One or more of the components shown may be combined with Figure 2implemented within one or more of the described components. Additionally or alternatively, one or more of the set of components may be at least partially implemented as software stored in a memory. For example, a component (or a part of a component) may be implemented as instructions or code stored in a non-transitory computer-readable medium and executable by a controller or a processor to perform the functions or operations of the component.

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

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

[0134] The receiving component 702 may receive a first communication from the transmitting UE that is associated with the COT of the transmitting UE and with at least one of a broadcast type or a channel type. The transmitting component 704 may transmit a second communication in the COT of the transmitting UE at least partially based on the broadcast type or the channel type of the first communication. For example, the second communication may use a channel type and / or a broadcast type identified by the identifying component 708 at least partially based on the broadcast type or the channel type of the first communication, as described herein.

[0135] The receiving component 702 may receive a configuration (sometimes referred to herein as configuration information) indicating one or more allowed broadcast types for a second communication, where the one or more allowed broadcast types are at least partially based on the broadcast type associated with a first communication.

[0136] The receiving component 702 may receive a configuration (sometimes referred to herein as configuration information) indicating one or more allowed channel types for a second communication, where the one or more allowed channel types are at least partially based on a first channel type associated with a first communication.

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

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

[0139] Aspect 1: A method of wireless communication performed by a receiving user equipment (UE), comprising: receiving, from a transmitting UE, a first communication associated with a channel occupancy time (COT) of the transmitting UE and with at least one of a broadcast type or a channel type; and transmitting a second communication in the COT of the transmitting UE at least partially based on the broadcast type or the channel type of the first communication.

[0140] Aspect 2: The method according to aspect 1, wherein the second communication is associated with the same broadcast type as the first communication.

[0141] Aspect 3: The method according to any one of aspects 1 to 2, wherein the first communication is associated with a multicast broadcast type, and wherein the second communication is associated with a unicast broadcast type or the multicast broadcast type at least partially based on the first communication being associated with the multicast broadcast type.

[0142] Aspect 4: The method according to any one of aspects 1 to 3, wherein the first communication is associated with a unicast broadcast type, and wherein the second communication is associated with the unicast broadcast type at least partially based on the first communication being associated with the unicast broadcast type.

[0143] Aspect 5: The method according to any one of Aspects 1 to 4, wherein the first communication is associated with a broadcast type, and wherein the second communication is associated with a unicast type or a multicast type at least partially based on the first communication being associated with the broadcast type.

[0144] Aspect 6: The method according to any one of Aspects 1 to 5, wherein the second communication is associated with a multicast type and is directed to a UE group including the transmitting UE.

[0145] Aspect 7: The method according to Aspect 6, wherein the first communication is also directed to the UE group including the transmitting UE, and wherein the UE group includes the receiving UE.

[0146] Aspect 8: The method according to any one of Aspects 1 to 7, further comprising: receiving a configuration indicating one or more allowed broadcast types for the second communication, wherein the one or more allowed broadcast types are at least partially based on the broadcast type associated with the first communication.

[0147] Aspect 9: The method according to any one of Aspects 1 to 8, wherein the first communication indicates one or more allowed broadcast types for the second communication.

[0148] Aspect 10: The method according to Aspect 9, wherein a COT structure indicator of the first communication indicates the one or more allowed broadcast types.

[0149] Aspect 11: The method according to any one of Aspects 1 to 10, wherein the first communication is associated with multiple broadcast types including the broadcast type, and the method further comprises selecting a broadcast type for the second communication at least partially based on the multiple broadcast types.

[0150] Aspect 12: The method according to any one of Aspects 1 to 11, wherein the channel type is a first channel type, and wherein the second communication has a second channel type at least partially based on the first channel type.

[0151] Aspect 13: The method according to Aspect 12, wherein the first channel type is a physical sidelink shared channel type, and the second channel type is a sidelink synchronization signal block channel type or a feedback channel type.

[0152] Aspect 14: The method according to Aspect 12, wherein the first channel type is a feedback channel type, and the second channel type is a sidelink synchronization signal block channel type.

[0153] Aspect 15: The method according to aspect 12, wherein the first channel type is a sidelink synchronization signal block type, and the second channel type is the sidelink synchronization signal block channel type.

[0154] Aspect 16: The method according to aspect 15, wherein the transmitting UE is a synchronization reference node of the receiving UE.

[0155] Aspect 17: The method according to aspect 12, further comprising: receiving a configuration indicating one or more allowed channel types for the second communication, wherein the one or more allowed channel types are at least partially based on the first channel type associated with the first communication.

[0156] Aspect 18: The method according to aspect 12, wherein the first communication is associated with multiple channel types including the first channel type, and the method further comprises selecting the second channel type for the second communication at least partially based on the multiple channel types.

[0157] Aspect 19: An apparatus for wireless communication at a device, comprising: a processor; a memory coupled to the processor; and instructions stored in the memory and executable by the processor to cause the device to perform the method according to one or more of aspects 1 to 18.

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

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

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

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

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

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

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

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

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

Claims

1. A receiving user equipment (UE) for wireless communication, comprising: one or more memories; and one or more processors coupled to the one or more memories and individually or jointly configured to: receive from a transmitting UE a first communication associated with a channel occupancy time (COT) of the transmitting UE and with at least one of a broadcast type or a channel type; and transmit a second communication at least partially based on at least one of the broadcast type or the channel type of the first communication during the COT of the transmitting UE.

2. The receiving UE according to claim 1, wherein the second communication is associated with the same broadcast type as the first communication.

3. The receiving UE according to claim 1, wherein the first communication has a multicast broadcast type, and wherein the second communication has a unicast broadcast type or the multicast broadcast type at least partially based on the first communication having the multicast broadcast type.

4. The receiving UE according to claim 1, wherein the first communication has a unicast broadcast type, and wherein the second communication has the unicast broadcast type at least partially based on the first communication having the unicast broadcast type.

5. The receiving UE according to claim 1, wherein the first communication has a broadcast broadcast type, and wherein the second communication has a unicast broadcast type or a multicast broadcast type at least partially based on the first communication having the broadcast broadcast type.

6. The receiving UE according to claim 1, wherein the second communication has a multicast broadcast type and is directed to a UE group including the transmitting UE.

7. The receiving UE according to claim 6, wherein the first communication is also directed to the UE group including the transmitting UE, and wherein the UE group includes the receiving UE.

8. The receiving UE according to claim 1, wherein the one or more processors are individually or jointly configured to receive a configuration indicating one or more allowed broadcast types for the second communication, wherein the one or more allowed broadcast types are at least partially based on the broadcast type associated with the first communication.

9. The receiving UE according to claim 1, wherein the first communication indicates one or more allowed broadcast types for the second communication.

10. The receiving UE according to claim 9, wherein a COT sharing indication of the first communication indicates the one or more allowed broadcast types.

11. The receiving UE according to claim 1, wherein the first communication is associated with multiple broadcast types including the broadcast type, and the one or more processors are individually or jointly configured to select a broadcast type for the second communication at least partially based on the multiple broadcast types.

12. The receiving UE according to claim 1, wherein the channel type is a first channel type, and wherein the second communication has a second channel type at least partially based on the first channel type.

13. The receiving UE according to claim 12, wherein the first channel type is a physical sidelink shared channel type, and the second channel type is a sidelink synchronization signal block channel type or a feedback channel type.

14. The receiving UE according to claim 12, wherein the first channel type is a feedback channel type, and the second channel type is a sidelink synchronization signal block channel type.

15. The receiving UE according to claim 12, wherein the first channel type is a sidelink synchronization signal block type, and the second channel type is the sidelink synchronization signal block channel type.

16. The receiving UE according to claim 15, wherein the transmitting UE is a synchronization reference node of the receiving UE.

17. The receiving UE according to claim 12, wherein the one or more processors are configured, individually or jointly, to receive a configuration indicating one or more allowed channel types for the second communication, wherein the one or more allowed channel types are at least partially based on the first channel type associated with the first communication.

18. The receiving UE according to claim 12, wherein the first communication is associated with multiple channel types including the first channel type, and the one or more processors are further configured to select the second channel type for the second communication at least partially based on the multiple channel types.

19. A method of wireless communication performed by a receiving user equipment (UE), comprising: receiving, from a transmitting UE, a first communication associated with a channel occupancy time (COT) of the transmitting UE and at least one of a broadcast type or a channel type; and transmitting a second communication in the COT of the transmitting UE at least partially based on at least one of the broadcast type or the channel type of the first communication.

20. The method according to claim 19, wherein the second communication is associated with the same broadcast type as the first communication.

21. The method according to claim 19, wherein the first communication is associated with a multicast broadcast type, and wherein the second communication is associated with a unicast broadcast type or the multicast broadcast type at least partially based on the first communication being associated with the multicast broadcast type.

22. The method according to claim 19, wherein the first communication is associated with a unicast broadcast type, and wherein the second communication is associated with the unicast broadcast type at least partially based on the first communication being associated with the unicast broadcast type.

23. The method according to claim 19, wherein the second communication is associated with a multicast broadcast type and is directed to a group of UEs including the transmitting UE.

24. The method according to claim 19, wherein the first communication indicates one or more allowed broadcast types for the second communication.

25. The method according to claim 24, wherein a COT sharing indication of the first communication indicates the one or more allowed broadcast types.

26. The method according to claim 19, wherein the first communication is associated with a plurality of broadcast types including the broadcast type, and the method further comprises selecting, at least in part based on the plurality of broadcast types, a broadcast type for the second communication.

27. The method according to claim 19, wherein the channel type is a first channel type, and wherein the second communication has a second channel type that is at least in part based on the first channel type.

28. The method according to claim 27, wherein the first channel type is a physical sidelink shared channel type, and the second channel type is a sidelink synchronization signal block channel type or a feedback channel type.

29. A non-transitory computer-readable medium storing a set of instructions for wireless communication, the set of instructions comprising: one or more instructions that, when executed by one or more processors of a receiving user equipment (UE), cause the UE to: receive, from a transmitting UE, a first communication associated with a channel occupancy time (COT) of the transmitting UE and with at least one of a broadcast type or a channel type; and transmit, at least in part based on at least one of the broadcast type or the channel type of the first communication, a second communication during the COT of the transmitting UE.

30. An apparatus for wireless communication, comprising: means for receiving, from a transmitting user equipment (UE), a first communication associated with a channel occupancy time (COT) of the transmitting UE and with at least one of a broadcast type or a channel type; and means for transmitting, at least in part based on at least one of the broadcast type or the channel type of the first communication, a second communication during the COT of the transmitting UE.