WO2023194909A1

WO2023194909A1 - Prioritizing channel occupancy time sharing

Info

Publication number: WO2023194909A1
Application number: PCT/IB2023/053427
Authority: WO
Inventors: Alexander Golitschek Edler Von Elbwart; Karthikeyan Ganesan; Joachim Löhr; Prateek Basu Mallick; Vijay Nangia; Ravi Kuchibhotla
Original assignee: Lenovo (Singapore) Pte. Ltd.
Priority date: 2022-04-04
Filing date: 2023-04-04
Publication date: 2023-10-12

Abstract

Apparatuses, methods, and systems are disclosed for prioritizing channel occupancy time (COT) sharing. One method (500) includes determining (502), at a user equipment (UE), a transmitter of a plurality of transmitters corresponding to each COT sharing indication of a plurality of COT sharing indications. The method (500) includes determining (504) a COT sharing priority of a plurality of COT sharing priorities for each transmitter of the plurality of transmitters. The method (500) includes determining (506) a COT sharing indication of the plurality of COT sharing indications having a highest COT sharing priority of the plurality of COT sharing priorities. The method (500) includes transmitting (508) a transmission directed to the transmitter corresponding to the COT sharing indication having the highest COT sharing priority.

Description

PRIORITIZING CHANNEL OCCUPANCY TIME SHARING

FIELD

[0001] The subject matter disclosed herein relates generally to wireless communications and more particularly relates to prioritizing channel occupancy time (“COT”) sharing.

BACKGROUND

[0002] In certain wireless communications networks, COT may be used. In such networks, a COT of a set of COTs may be selected.

BRIEF SUMMARY

[0003] Methods for prioritizing COT sharing are disclosed. Apparatuses and systems also perform the functions of the methods. One embodiment of a method includes determining, at a user equipment (“UE”), a transmitter of a plurality of transmitters corresponding to each COT sharing indication of a plurality of COT sharing indications. In some embodiments, the method includes determining a COT sharing priority of a plurality of COT sharing priorities for each transmitter of the plurality of transmitters. In certain embodiments, the method includes determining a COT sharing indication of the plurality of COT sharing indications having a highest COT sharing priority of the plurality of COT sharing priorities. In various embodiments, the method includes transmitting a transmission directed to the transmitter corresponding to the COT sharing indication having the highest COT sharing priority.

[0004] One apparatus for prioritizing COT sharing includes a processor that: determines a transmitter of a plurality of transmitters corresponding to each COT sharing indication of a plurality of COT sharing indications; determines a COT sharing priority of a plurality of COT sharing priorities for each transmitter of the plurality of transmitters; determines a COT sharing indication of the plurality of COT sharing indications having a highest COT sharing priority of the plurality of COT sharing priorities; and transmits a transmission directed to the transmitter corresponding to the COT sharing indication having the highest COT sharing priority.

[0005] Another embodiment of a method for prioritizing COT sharing includes receiving, at a network device, a transmission corresponding to a COT sharing indication of a plurality of COT sharing indications having a highest COT sharing priority of a plurality of COT sharing priorities. Each sharing priority of the plurality of COT sharing priorities corresponds to each transmitter of a plurality of transmitters and to each COT sharing indication of the plurality of COT sharing indications.

[0006] Another apparatus for prioritizing COT sharing includes a receiver that receives a transmission corresponding to a COT sharing indication of a plurality of COT sharing indications having a highest COT sharing priority of a plurality of COT sharing priorities. Each sharing priority of the plurality of COT sharing priorities corresponds to each transmitter of a plurality of transmitters and to each COT sharing indication of the plurality of COT sharing indications.

BRIEF DESCRIPTION OF THE DRAWINGS

[0007] A more particular description of the embodiments briefly described above will be rendered by reference to specific embodiments that are illustrated in the appended drawings. Understanding that these drawings depict only some embodiments and are not therefore to be considered to be limiting of scope, the embodiments will be described and explained with additional specificity and detail through the use of the accompanying drawings, in which:

[0008] Figure 1 is a schematic block diagram illustrating one embodiment of a wireless communication system for prioritizing COT sharing;

[0009] Figure 2 is a schematic block diagram illustrating one embodiment of an apparatus that may be used for prioritizing COT sharing;

[0010] Figure 3 is a schematic block diagram illustrating one embodiment of an apparatus that may be used for prioritizing COT sharing;

[0011] Figure 4 is a schematic block diagram illustrating one embodiment of a system for prioritizing COT sharing;

[0012] Figure 5 is a flow chart diagram illustrating one embodiment of a method for prioritizing COT sharing; and

[0013] Figure 6 is a flow chart diagram illustrating another embodiment of a method for prioritizing COT sharing.

DETAILED DESCRIPTION

[0014] As will be appreciated by one skilled in the art, aspects of the embodiments may be embodied as a system, apparatus, method, or program product. Accordingly, embodiments may take the form of an entirely hardware embodiment, an entirely software embodiment (including firmware, resident software, micro-code, etc.) or an embodiment combining software and hardware aspects that may all generally be referred to herein as a “circuit,” “module” or “system.” Furthermore, embodiments may take the form of a program product embodied in one or more computer readable storage devices storing machine readable code, computer readable code, and/or program code, referred hereafter as code. The storage devices may be tangible, non-transitory, and/or non-transmission. The storage devices may not embody signals. In a certain embodiment, the storage devices only employ signals for accessing code.

[0015] Certain of the functional units described in this specification may be labeled as modules, in order to more particularly emphasize their implementation independence. For example, a module may be implemented as a hardware circuit comprising custom very-large-scale integration (“VLSI”) circuits or gate arrays, off-the-shelf semiconductors such as logic chips, transistors, or other discrete components. A module may also be implemented in programmable hardware devices such as field programmable gate arrays, programmable array logic, programmable logic devices or the like.

[0016] Modules may also be implemented in code and/or software for execution by various types of processors. An identified module of code may, for instance, include one or more physical or logical blocks of executable code which may, for instance, be organized as an object, procedure, or function. Nevertheless, the executables of an identified module need not be physically located together, but may include disparate instructions stored in different locations which, when joined logically together, include the module and achieve the stated purpose for the module.

[0017] Indeed, a module of code may be a single instruction, or many instructions, and may even be distributed over several different code segments, among different programs, and across several memory devices. Similarly, operational data may be identified and illustrated herein within modules, and may be embodied in any suitable form and organized within any suitable type of data structure. The operational data may be collected as a single data set, or may be distributed over different locations including over different computer readable storage devices. Where a module or portions of a module are implemented in software, the software portions are stored on one or more computer readable storage devices.

[0018] Any combination of one or more computer readable medium may be utilized. The computer readable medium may be a computer readable storage medium. The computer readable storage medium may be a storage device storing the code. The storage device may be, for example, but not limited to, an electronic, magnetic, optical, electromagnetic, infrared, holographic, micromechanical, or semiconductor system, apparatus, or device, or any suitable combination of the foregoing.

[0019] More specific examples (a non-exhaustive list) of the storage device would include the following: an electrical connection having one or more wires, a portable computer diskette, a hard disk, a random access memory (“RAM”), a read-only memory (“ROM”), an erasable programmable read-only memory (“EPROM” or Flash memory), a portable compact disc readonly memory (“CD-ROM”), an optical storage device, a magnetic storage device, or any suitable combination of the foregoing. In the context of this document, a computer readable storage medium may be any tangible medium that can contain, or store a program for use by or in connection with an instruction execution system, apparatus, or device. [0020] Code for carrying out operations for embodiments may be any number of lines and may be written in any combination of one or more programming languages including an object oriented programming language such as Python, Ruby, Java, Smalltalk, C++, or the like, and conventional procedural programming languages, such as the "C" programming language, or the like, and/or machine languages such as assembly languages. The code may execute entirely on the user's computer, partly on the user's computer, as a stand-alone software package, partly on the user's computer and partly on a remote computer or entirely on the remote computer or server. In the latter scenario, the remote computer may be connected to the user's computer through any type of network, including a local area network (“LAN”) or a wide area network (“WAN”), or the connection may be made to an external computer (for example, through the Internet using an Internet Service Provider).

[0021] Reference throughout this specification to “one embodiment,” “an embodiment,” or similar language means that a particular feature, structure, or characteristic described in connection with the embodiment is included in at least one embodiment. Thus, appearances of the phrases “in one embodiment,” “in an embodiment,” and similar language throughout this specification may, but do not necessarily, all refer to the same embodiment, but mean “one or more but not all embodiments” unless expressly specified otherwise. The terms “including,” “comprising,” “having,” and variations thereof mean “including but not limited to,” unless expressly specified otherwise. An enumerated listing of items does not imply that any or all of the items are mutually exclusive, unless expressly specified otherwise. The terms “a,” “an,” and “the” also refer to “one or more” unless expressly specified otherwise.

[0022] Furthermore, the described features, structures, or characteristics of the embodiments may be combined in any suitable manner. In the following description, numerous specific details are provided, such as examples of programming, software modules, user selections, network transactions, database queries, database structures, hardware modules, hardware circuits, hardware chips, etc., to provide a thorough understanding of embodiments. One skilled in the relevant art will recognize, however, that embodiments may be practiced without one or more of the specific details, or with other methods, components, materials, and so forth. In other instances, well-known structures, materials, or operations are not shown or described in detail to avoid obscuring aspects of an embodiment.

[0023] Aspects of the embodiments are described below with reference to schematic flowchart diagrams and/or schematic block diagrams of methods, apparatuses, systems, and program products according to embodiments. It will be understood that each block of the schematic flowchart diagrams and/or schematic block diagrams, and combinations of blocks in the schematic flowchart diagrams and/or schematic block diagrams, can be implemented by code. The code may be provided to a processor of a general purpose computer, special purpose computer, or other programmable data processing apparatus to produce a machine, such that the instructions, which execute via the processor of the computer or other programmable data processing apparatus, create means for implementing the functions/acts specified in the schematic flowchart diagrams and/or schematic block diagrams block or blocks.

[0024] The code may also be stored in a storage device that can direct a computer, other programmable data processing apparatus, or other devices to function in a particular manner, such that the instructions stored in the storage device produce an article of manufacture including instructions which implement the function/act specified in the schematic flowchart diagrams and/or schematic block diagrams block or blocks.

[0025] The code may also be loaded onto a computer, other programmable data processing apparatus, or other devices to cause a series of operational steps to be performed on the computer, other programmable apparatus or other devices to produce a computer implemented process such that the code which execute on the computer or other programmable apparatus provide processes for implementing the functions/acts specified in the flowchart and/or block diagram block or blocks.

[0026] The schematic flowchart diagrams and/or schematic block diagrams in the Figures illustrate the architecture, functionality, and operation of possible implementations of apparatuses, systems, methods and program products according to various embodiments. In this regard, each block in the schematic flowchart diagrams and/or schematic block diagrams may represent a module, segment, or portion of code, which includes one or more executable instructions of the code for implementing the specified logical function(s).

[0027] It should also be noted that, in some alternative implementations, the functions noted in the block may occur out of the order noted in the Figures. For example, two blocks shown in succession may, in fact, be executed substantially concurrently, or the blocks may sometimes be executed in the reverse order, depending upon the functionality involved. Other steps and methods may be conceived that are equivalent in function, logic, or effect to one or more blocks, or portions thereof, of the illustrated Figures.

[0028] Although various arrow types and line types may be employed in the flowchart and/or block diagrams, they are understood not to limit the scope of the corresponding embodiments. Indeed, some arrows or other connectors may be used to indicate only the logical flow of the depicted embodiment. For instance, an arrow may indicate a waiting or monitoring period of unspecified duration between enumerated steps of the depicted embodiment. It will also be noted that each block of the block diagrams and/or flowchart diagrams, and combinations of blocks in the block diagrams and/or flowchart diagrams, can be implemented by special purpose hardware-based systems that perform the specified functions or acts, or combinations of special purpose hardware and code.

[0029] The description of elements in each figure may refer to elements of proceeding figures. Like numbers refer to like elements in all figures, including alternate embodiments of like elements.

[0030] Figure 1 depicts an embodiment of a wireless communication system 100 for prioritizing COT sharing. In one embodiment, the wireless communication system 100 includes remote units 102 and network units 104. Even though a specific number of remote units 102 and network units 104 are depicted in Figure 1, one of skill in the art will recognize that any number of remote units 102 and network units 104 may be included in the wireless communication system 100.

[0031] In one embodiment, the remote units 102 may include computing devices, such as desktop computers, laptop computers, personal digital assistants (“PDAs”), tablet computers, smart phones, smart televisions (e.g., televisions connected to the Internet), set-top boxes, game consoles, security systems (including security cameras), vehicle on-board computers, network devices (e.g., routers, switches, modems), aerial vehicles, drones, or the like. In some embodiments, the remote units 102 include wearable devices, such as smart watches, fitness bands, optical head-mounted displays, or the like. Moreover, the remote units 102 may be referred to as subscriber units, mobiles, mobile stations, users, terminals, mobile terminals, fixed terminals, subscriber stations, UE, user terminals, a device, or by other terminology used in the art. The remote units 102 may communicate directly with one or more of the network units 104 via uplink (“UL”) communication signals. In certain embodiments, the remote units 102 may communicate directly with other remote units 102 via sidelink (“SL”) communication.

[0032] The network units 104 may be distributed over a geographic region. In certain embodiments, a network unit 104 may also be referred to and/or may include one or more of an access point, an access terminal, a base, a base station, a location server, a core network (“CN”), a radio network entity, a Node-B, an evolved node-B (“eNB”), a 5G node-B (“gNB”), a Home Node-B, a relay node, a device, a core network, an aerial server, a radio access node, an access point (“AP”), new radio (“NR”), a network entity, an access and mobility management function (“AMF”), a unified data management (“UDM”), a unified data repository (“UDR”), a UDM/UDR, a policy control function (“PCF”), a radio access network (“RAN”), a network slice selection function (“NSSF”), an operations, administration, and management (“0AM”), a session management function (“SMF”), a user plane function (“UPF”), an application function, an authentication server function (“AUSF”), security anchor functionality (“SEAF”), trusted non- third generation partnership project (“3GPP”) gateway function (“TNGF”), or by any other terminology used in the art. The network units 104 are generally part of a radio access network that includes one or more controllers communicably coupled to one or more corresponding network units 104. The radio access network is generally communicably coupled to one or more core networks, which may be coupled to other networks, like the Internet and public switched telephone networks, among other networks. These and other elements of radio access and core networks are not illustrated but are well known generally by those having ordinary skill in the art.

[0033] In one implementation, the wireless communication system 100 is compliant with NR protocols standardized in 3GPP, wherein the network unit 104 transmits using an orthogonal frequency division multiplexing (“OFDM”) modulation scheme on the downlink (“DL”) and the remote units 102 transmit on the UL using a single-carrier frequency division multiple access (“SC-FDMA”) scheme or an OFDM scheme. More generally, however, the wireless communication system 100 may implement some other open or proprietary communication protocol, for example, WiMAX, institute of electrical and electronics engineers (“IEEE”) 802. 11 variants, global system for mobile communications (“GSM”), general packet radio service (“GPRS”), universal mobile telecommunications system (“UMTS”), long term evolution (“LTE”) variants, code division multiple access 2000 (“CDMA2000”), Bluetooth®, ZigBee, Sigfox, among other protocols. The present disclosure is not intended to be limited to the implementation of any particular wireless communication system architecture or protocol.

[0034] The network units 104 may serve a number of remote units 102 within a serving area, for example, a cell or a cell sector via a wireless communication link. The network units 104 transmit DL communication signals to serve the remote units 102 in the time, frequency, and/or spatial domain.

[0035] In various embodiments, a remote unit 102 may determine, at a UE, a transmitter of a plurality of transmitters corresponding to each COT sharing indication of a plurality of COT sharing indications. In some embodiments, the remote unit 102 may determine a COT sharing priority of a plurality of COT sharing priorities for each transmitter of the plurality of transmitters. In certain embodiments, the remote unit 102 may determine a COT sharing indication of the plurality of COT sharing indications having a highest COT sharing priority of the plurality of COT sharing priorities. In various embodiments, the remote unit 102 may transmit a transmission directed to the transmitter corresponding to the COT sharing indication having the highest COT sharing priority. Accordingly, the remote unit 102 may be used for prioritizing COT sharing. [0036] In certain embodiments, a network unit 104 may receive, at a network device, a transmission corresponding to a COT sharing indication of a plurality of COT sharing indications having a highest COT sharing priority of a plurality of COT sharing priorities. Each sharing priority of the plurality of COT sharing priorities corresponds to each transmitter of a plurality of transmitters and to each COT sharing indication of the plurality of COT sharing indications. Accordingly, the network unit 104 may be used for prioritizing COT sharing.

[0037] Figure 2 depicts one embodiment of an apparatus 200 that may be used for prioritizing COT sharing. The apparatus 200 includes one embodiment of the remote unit 102. Furthermore, the remote unit 102 may include a processor 202, a memory 204, an input device 206, a display 208, a transmitter 210, and a receiver 212. In some embodiments, the input device 206 and the display 208 are combined into a single device, such as a touchscreen. In certain embodiments, the remote unit 102 may not include any input device 206 and/or display 208. In various embodiments, the remote unit 102 may include one or more of the processor 202, the memory 204, the transmitter 210, and the receiver 212, and may not include the input device 206 and/or the display 208.

[0038] The processor 202, in one embodiment, may include any known controller capable of executing computer-readable instructions and/or capable of performing logical operations. For example, the processor 202 may be a microcontroller, a microprocessor, a central processing unit (“CPU”), a graphics processing unit (“GPU”), an auxiliary processing unit, a field programmable gate array (“FPGA”), or similar programmable controller. In some embodiments, the processor 202 executes instructions stored in the memory 204 to perform the methods and routines described herein. The processor 202 is communicatively coupled to the memory 204, the input device 206, the display 208, the transmitter 210, and the receiver 212.

[0039] The memory 204, in one embodiment, is a computer readable storage medium. In some embodiments, the memory 204 includes volatile computer storage media. For example, the memory 204 may include a RAM, including dynamic RAM (“DRAM”), synchronous dynamic RAM (“SDRAM”), and/or static RAM (“SRAM”). In some embodiments, the memory 204 includes non-volatile computer storage media. For example, the memory 204 may include a hard disk drive, a flash memory, or any other suitable non-volatile computer storage device. In some embodiments, the memory 204 includes both volatile and non-volatile computer storage media. In some embodiments, the memory 204 also stores program code and related data, such as an operating system or other controller algorithms operating on the remote unit 102.

[0040] The input device 206, in one embodiment, may include any known computer input device including a touch panel, a button, a keyboard, a stylus, a microphone, or the like. In some embodiments, the input device 206 may be integrated with the display 208, for example, as a touchscreen or similar touch-sensitive display. In some embodiments, the input device 206 includes a touchscreen such that text may be input using a virtual keyboard displayed on the touchscreen and/or by handwriting on the touchscreen. In some embodiments, the input device 206 includes two or more different devices, such as a keyboard and a touch panel.

[0041] The display 208, in one embodiment, may include any known electronically controllable display or display device. The display 208 may be designed to output visual, audible, and/or haptic signals. In some embodiments, the display 208 includes an electronic display capable of outputting visual data to a user. For example, the display 208 may include, but is not limited to, a liquid crystal display (“LCD”), a light emitting diode (“LED”) display, an organic light emitting diode (“OLED”) display, a projector, or similar display device capable of outputting images, text, or the like to a user. As another, non-limiting, example, the display 208 may include a wearable display such as a smart watch, smart glasses, a heads-up display, or the like. Further, the display 208 may be a component of a smart phone, a personal digital assistant, a television, a table computer, a notebook (laptop) computer, a personal computer, a vehicle dashboard, or the like.

[0042] In certain embodiments, the display 208 includes one or more speakers for producing sound. For example, the display 208 may produce an audible alert or notification (e.g., a beep or chime). In some embodiments, the display 208 includes one or more haptic devices for producing vibrations, motion, or other haptic feedback. In some embodiments, all or portions of the display 208 may be integrated with the input device 206. For example, the input device 206 and display 208 may form a touchscreen or similar touch-sensitive display. In other embodiments, the display 208 may be located near the input device 206.

[0043] In certain embodiments, the processor 202: determines a transmitter of a plurality of transmitters corresponding to each COT sharing indication of a plurality of COT sharing indications; determines a COT sharing priority of a plurality of COT sharing priorities for each transmitter of the plurality of transmitters; determines a COT sharing indication of the plurality of COT sharing indications having a highest COT sharing priority of the plurality of COT sharing priorities; and transmits a transmission directed to the transmitter corresponding to the COT sharing indication having the highest COT sharing priority.

[0044] Although only one transmitter 210 and one receiver 212 are illustrated, the remote unit 102 may have any suitable number of transmitters 210 and receivers 212. The transmitter 210 and the receiver 212 may be any suitable type of transmitters and receivers. In one embodiment, the transmitter 210 and the receiver 212 may be part of a transceiver. [0045] Figure 3 depicts one embodiment of an apparatus 300 that may be used for prioritizing COT sharing. The apparatus 300 includes one embodiment of the network unit 104. Furthermore, the network unit 104 may include a processor 302, a memory 304, an input device 306, a display 308, a transmitter 310, and a receiver 312. As may be appreciated, the processor 302, the memory 304, the input device 306, the display 308, the transmitter 310, and the receiver 312 may be substantially similar to the processor 202, the memory 204, the input device 206, the display 208, the transmitter 210, and the receiver 212 of the remote unit 102, respectively.

[0046] In certain embodiments, the receiver 312 receives a transmission corresponding to a COT sharing indication of a plurality of COT sharing indications having a highest COT sharing priority of a plurality of COT sharing priorities. Each sharing priority of the plurality of COT sharing priorities corresponds to each transmitter of a plurality of transmitters and to each COT sharing indication of the plurality of COT sharing indications.

[0047] It should be noted that one or more embodiments described herein may be combined into a single embodiment.

[0048] In certain embodiments, NR provides mechanisms for operation in an unlicensed spectrum to share a COT with another device. The benefit of such COT sharing is that a device initiating a COT can grant another device the right to use the initiated COT without requiring the target device to initiate its own COT. Initiating a COT may involve a certain sensing time before transmissions are allowed, while starting transmission in a shared COT requires no such sensing or only a fraction of the sensing time required for initiating a COT.

[0049] In some embodiments, in cellular topology with a centralized scheduler, a gNB initiates a COT and may share this COT with one or more UEs, or a UE initiates a COT and may share this COT with a gNB. The sharing of a COT may be indicated by a specific field in downlink control information or uplink control information.

[0050] In various embodiments, such as in a SL environment, a UE may have SL connections to and from multiple UEs. Consequently, a UE may receive COT sharing indicators from a plurality of UEs (and potentially from a gNB as well). Since each of the indicated shared COTs results from a different initiating device that may have remaining COT durations, such a UE then needs to make a selection which of the indicated shared COTs to use and to abide by the rules pertaining to the selected COT.

[0051] In certain embodiments, a UE may select a COT out of a plurality of COTs for which it has received COT sharing indications.

[0052] In some embodiments, COT sharing is possible from a gNB and/or an eNB to a UE, or vice versa from a UE to a gNB and/or an eNB. If an eNB and/or a gNB intends to share its initiated COT with one or more UEs, a common downlink control information (“DQ”) format (e.g., DCI format 2 0 in NR) may include a COT sharing indicator field that would be set to 1 to indicate COT sharing. Additional fields may be present to explicitly indicate the remaining COT duration.

[0053] In some embodiments, COT sharing is possible from a UE to another UE. If a UE intends to share its initiated COT with one or more UEs, a SL control information (“SCI”) format may include a COT sharing indicator field that would be set to 1 to indicate COT sharing. Additional fields may be present to explicitly indicate the remaining COT duration.

[0054] In some embodiments, a SL logical channel prioritization (“LCP”) procedure is applied whenever a new transmission is performed. In such embodiments, radio resource control (“RRC”) controls scheduling of SL data by signaling for each logical channel: 1) sl-Priority where an increasing priority value indicates a lower priority level; 2) sl-PrioritisedBitRate which sets the SL prioritized bit rate (“sPBR”); and/or 3) sl-BucketSizeDuration which sets the SL bucket size duration (“sBSD”).

[0055] In various embodiments, RRC controls an LCP procedure by configuring mapping restrictions for each logical channel: 1) si -configuredGrantType 1 Allowed which sets whether a configured grant Type 1 can be used for SL transmission; 2) sl-AllowedCG-List which sets the allowed configured grant(s) for SL transmission; and/or 3) sl-HARQ-FeedbackEnabled which sets whether the logical channel is allowed to be multiplexed with logical channels with sl-HARQ- LeedbackEnabled set to enabled or disabled. In certain embodiments, the following UE variable is used for an LCP procedure: SBj which is maintained for each logical channel].

[0056] In some embodiments, a medium access control (“MAC”) entity may initialize SBj of the logical channel to zero when a logical channel is established. Lor each logical channel j, the MAC entity may: 1) increment SBj by the product sPBR x T before every instance of the LCP procedure, where T is the time elapsed since SBj was last incremented; and/or 2) if the value of SBj is greater than the SL bucket size (e.g., sPBR x sBSD): set SBj to the SL bucket size. The exact moments when the UE updates SBj between LCP procedures may be up to UE implementation as long as SBj is up to date at the time when a grant is processed by the LCP.

[0057] In various embodiments, a MAC entity may, for each SL control information (“SCI”) corresponding to a new transmission: 1) select a destination associated to one of unicast, groupcast and broadcast, having at least one of the MAC control element (“CE”) (“MAC CE”) and the logical channel with the highest priority, among the logical channels that satisfy all the following conditions and MAC CEs, if any, for the SL grant associated with the SCI: a) SL data is available for transmission, b) SBj > 0, in case there is any logical channel having SBj > 0, c) si- configuredGrantTypel Allowed, if configured, is set to true if the SL grant is a configured grant Type 1, d) si -Allowed CG-List, if configured, includes the configured grant index associated with the SL grant, and e) sl-HARQ-FeedbackEnabled is set to disabled, if a physical SL feedback channel (“PSFCH”) is not configured for the SL grant associated to the SCI (e.g., if multiple destinations have the logical channels satisfying all conditions above with the same highest priority or if multiple destinations have either the MAC CE and/or the logical channels satisfying all conditions above with the same priority as the MAC CE, which destination is selected among them may be up to UE implementation); 2) select the logical channels satisfying all the following conditions among the logical channels belonging to the selected destination: a) SL data is available for transmission, b) si -configuredGrantTypel Allowed, if configured, is set to true if the SL grant is a configured grant Type 1, and c) sl-AllowedCG-List, if configured, includes the configured grant index associated with the SL grant, cl) if a PSFCH is configured for the SL grant associated with the SCI: cla) sl-HARQ-FeedbackEnabled is set to enabled if sl-HARQ-FeedbackEnabled is set to enabled for the highest priority logical channel satisfying the above conditions, or clb) sl- HARQ-FeedbackEnabled is set to disabled if sl-HARQ-FeedbackEnabled is set to disabled for the highest priority logical channel satisfying the above conditions, c2) else: sl-HARQ- FeedbackEnab led is set to disabled. sl-HARQ-FeedbackEnabled is set to disabled for the transmission of a MAC protocol data unit (“PDU”) only carrying channel state information (“CSI”) reporting MAC CE.

[0058] As used herein, the following may apply: 1) receiver (“RX”) UE: a UE that receives control signaling or data via a SL or a downlink connection; 2) transmit (‘TX”) UE: a UE that transmits a control signaling or data via a SL or an uplink connection; 3) COT initiator: a device that initiated a channel occupancy (e.g., a UE or a gNB); 4) COT donor: a device that transmits a COT sharing indicator (e.g., a TX UE or a gNB) - the COT donor may be identical to the COT initiator; and/or 5) COT recipient: a device that receives a COT sharing indicator (e.g., an RX UE or a gNB).

[0059] Moreover, in certain embodiments, a COT may be characterized by one or more of the following properties: 1) COT initiator: the node initiating a COT (e.g., following a channel access procedure; 2) channel access priority class: one or more classes that imply a required sensing duration when initiating a COT and/or MCOT; 3) maximum COT (“MCOT”): the maximum COT duration of a channel occupancy counted or measured from a first transmission after initiation of the COT; and/or 4) remaining COT duration: the (maximum) remaining number of slots within a channel occupancy. [0060] In some embodiments, each shared COT may have individual characteristics. For sharing, the MCOT or the remaining COT duration after sharing the COT is relevant. A COT recipient needs to respect the MCOT as from the COT initiator's perspective. For example, if a COT initiator initiates a COT at time tO with an MCOT of tMCOT=6 ms, then all transmissions belonging to that COT must terminate at latest at time t0+ tMCOT. If the COT initiator transmits during the first 2 ms of the COT and indicates COT sharing to be allowed after 2 ms, the COT initiator may indicate a remaining COT duration of 4 ms (=tMCOT - 2 ms). Any transmissions outside the COT require a new COT initiation procedure. Consequently, care must be taken when a COT recipient selects a COT, or equivalently selects a COT initiator, if multiple COT sharing indications are received. The selected COT then determines at least the maximum remaining time during which the COT recipient may transmit without initiating a new COT.

[0061] In various embodiments, a COT donor is also the COT's initiator. However, there may be cases where these are not equivalent. For example, the COT initiator can be a first COT donor for a first COT recipient. Before the maximum COT duration has expired, the first COT recipient then becomes a second COT donor for a second COT recipient. Transmissions from the second COT recipient then still need to take the COT characteristics from the COT initiator into account. Therefore, it is beneficial if a COT donor includes a remaining COT duration indicator rather than the MCOT value itself, as the remaining COT duration will indicate how much longer the COT may last, regardless whether the COT donor is the COT initiator or not.

[0062] In certain embodiments, a selection of a shared COT may be per transmission carrier. Alternatively, the selection may be per listen-before-talk (“LBT”) subband or per resource pool. In such a case, it may be feasible for a COT recipient to select multiple shared COTs (e.g., determine multiple COT donors if corresponding LBT subbands or resource pools are not overlapping). This can be the case if the resource pools correspond to different LBT subbands where the channel access procedures are performed independently. For example, a UE may receive a first COT sharing indicator from a first COT donor for transmissions in a first resource pool and a second COT sharing indicator from a second COT donor for transmissions in a second resource pool. If the first and second resource pool have non-overlapping frequency resources, then channel access procedures, COT sharing and corresponding transmissions can be done independently. Then it is sufficient to select a COT donor per such resource pool or per such LBT subband. This example may be extended to pertain to beamformed transmissions, then a COT donor may be selected per transmission and/or reception beam.

[0063] In a first embodiment, a COT recipient selects a determined COT donor according to the following: 1) a COT recipient determines COT donors of each COT sharing indication received in the same time unit (e.g., a COT sharing indication is received in SL control information (“SCI”) - the 2nd-stage SCI includes the layer 1 source identifier (“ID”) and destination ID of a transmission that represent identifiers (in the physical layer) of the TX UE and intended recipients (e.g., RX UEs) - therefore the COT recipient may determine the COT donor from the layer 1 source ID); 2) for each of the COT donors determined, determine a reference signal received power (“RSRP”) value of the received physical SL control channel (“PSCCH”) and/or PSSCH (e.g., including other SL channels or signals); and/or 3) select, as a determined COT donor, the COT donor from the determined COT donors with the highest RSRP value.

[0064] In the first embodiment, the COT recipient uses the shared COT according to at least the MCOT (or equivalently the remaining COT duration) applicable to the determined COT donor.

[0065] According to a first variant of the first embodiment, a COT recipient selects a determined COT donor according to the following: 1) the COT recipient determines the COT donors of each COT sharing indication that takes effect in the same time unit - for example, a COT sharing indication is received in an SCI - the 2nd-stage SCI includes the layer 1 source ID and destination ID of a transmission that represent identifiers (e.g., in the physical layer) of the TX UE and intended recipients (e.g., RX UEs) - therefore, the COT Recipient can determine the COT donor from the layer 1 source ID - the SCI including the COT sharing indication may additionally indicate an offset in time to determine the time unit in which the COT recipient may start its transmissions in the shared COT; 2) for each of the COT donors, determine an RSRP value of received PSCCH and/or PSSCH (alternatively or additionally including other SL channels or signals, e.g. reference symbols); and/or 3) select as a determined COT donor the COT donor from the determined COT donors with the highest RSRP value. The COT recipient then uses the shared COT according to at least the MCOT (or equivalently the remaining COT duration) applicable to the determined COT donor.

[0066] According to a second variant of the first embodiment, a COT recipient selects a determined COT donor according to the following: 1) the COT recipient determines the COT donors of each COT sharing indication that is applied to the same time unit - for example, a COT sharing indication is received in an SCI - the 2nd-stage SCI includes the layer 1 source ID and destination ID of a transmission that represent identifiers (e.g., in the physical layer) of the TX UE and intended recipients (e.g., RX UEs) - therefore, the COT recipient can determine the COT donor from the layer 1 source ID - the SCI including the COT sharing indication may additionally indicate an offset in time to determine the time unit in which the COT recipient may start its transmissions in the shared COT - for a given time unit in which the COT recipient intends to transmit, the COT recipient uses this information to determine whether the respective time unit is part of a shared COT and which nodes are respective COT donors; 2) for each of the COT donors, determine an RSRP value of received PSCCH and/or PSSCH (alternatively or additionally including other SL channels or signals, e.g. reference symbols); and/or 3) select as a determined COT donor the COT donor from the determined COT donors with the highest RSRP value. The COT recipient then uses the time unit for transmission to at least the determined COT donor according to the applicable rules to that shared COT.

[0067] In a second embodiment, a COT recipient selects a determined COT donor according to the following: 1) the COT recipient determines the COT donors of each COT sharing indication received in the same time unit - for example, a COT sharing indication is received in an SCI - the 2nd-stage SCI includes the layer 1 source ID and destination ID of a transmission that represent identifiers (e.g., in the physical layer) of the TX UE and intended recipients (e.g., RX UEs) - therefore, the COT recipient can determine the COT donor from the layer 1 source ID; 2) for each of the COT donors, determine a priority value (e.g., as included in the SCI); and/or 3) select as a determined COT donor the COT donor from the determined COT donors with the highest priority value. The COT recipient then uses the shared COT according to at least the MCOT (or equivalently the remaining COT duration) applicable to the determined COT donor.

[0068] According to a first variant of the second embodiment, a COT recipient selects a determined COT donor according to the following: 1) the COT recipient determines the COT donors of each COT sharing indication that is taking effect in the same time unit - for example, a COT sharing indication is received in an SCI - the 2nd-stage SCI includes the layer 1 source ID and destination ID of a transmission that represent identifiers (e.g., in the physical layer) of the TX UE and intended recipients (e.g., RX UEs) - therefore, the COT recipient can determine the COT donor from the layer 1 source ID - the SCI including the COT sharing indication may additionally indicate an offset in time to determine the time unit in which the COT recipient may start its transmissions in the shared COT; 2) for each of the COT donors, determine a priority value (e.g., as included in the SCI); and/or 3) select as a determined COT donor the COT donor from the determined COT donors with the highest priority value. The COT recipient then uses the shared COT according to at least the MCOT (or equivalently the remaining COT duration) applicable to the determined COT donor.

[0069] According to a second variant of the second embodiment, a COT recipient selects a determined COT donor according to the following: 1) the COT recipient determines the COT donors of each COT sharing indication that is applied to the same time unit - for example, a COT sharing indication is received in an SCI - the 2nd-stage SCI includes the layer 1 source ID and destination ID of a transmission that represent identifiers (e.g., in the physical layer) of the TX UE and intended recipients (e.g., RX UEs) - therefore the COT recipient can determine the COT Donor from the layer 1 source ID - the SCI including the COT sharing indication may additionally indicate an offset in time to determine the time unit in which the COT recipient may start its transmissions in the shared COT - for a given time unit in which the COT recipient intends to transmit, the COT recipient uses this information to determine whether the respective time unit is part of a shared COT and which nodes are respective COT donors; 2) for each of the COT donors, determine a priority value (e.g., as included in the SCI); and/or 3) select as a determined COT donor the COT donor from the determined COT donors with the highest priority value. The COT recipient then uses the time unit for transmission to at least the determined COT donor according to the applicable rules to that shared COT.

[0070] In a third embodiment, a COT recipient selects a determined COT donor according to the following: 1) the COT recipient determines the COT donors of each COT sharing indication received in the same time unit - for example, a COT sharing indication is received in an SCI - the 2nd-stage SCI includes the layer 1 source ID and destination ID of a transmission that represent identifiers (e.g., in the physical layer) of the TX UE and intended recipients (e.g., RX UEs) - therefore, the COT recipient can determine the COT donor from the layer 1 source ID; 2) for each of the COT donors, determine the highest logical channel priority among the SL logical channels with the COT donor (e.g., source ID of the node indicating COT sharing such as by SCI) as associated destination having data available - in other words the COT recipient determines a COT donor priority for each of the determined COT donors; 3) select as a determined COT donor the COT donor from the determined COT donors with the highest logical channel priority value (alternatively the COT donor with the highest determined COT donor priority); and/or 4) if step 3 results in a plurality of determined COT donors with the same determined logical channel priority value, select from that plurality of determined COT donors the one with the largest amount of data for the determined highest logical channel priority value. The COT recipient then uses the shared COT according to at least the MCOT (or equivalently the remaining COT duration) applicable to the determined COT donor.

[0071] According to a first variant of the third embodiment, a COT recipient selects a determined COT donor according to the following: 1) the COT recipient determines the COT donors of each COT sharing indication that is taking effect in the same time unit - for example, a COT sharing indication is received in a SCI - the 2nd-stage SCI includes the layer 1 source ID and destination ID of a transmission that represent identifiers (e.g., in the physical layer) of the TX UE and intended recipients (e.g., RX UEs) - therefore the COT recipient can determine the COT donor from the layer 1 source ID - the SCI including the COT sharing indication may additionally indicate an offset in time to determine the time unit in which the COT recipient may start its transmissions in the shared COT; 2) for each of the COT donors, determine the highest logical channel priority among the SL logical channels with the COT donor (e.g., source ID of the node indicating COT sharing such as by SCI) as associated destination having data available - in other words the COT recipient determines a COT donor priority for each of the determined COT donors; 3) select as a determined COT donor the COT Donor from the determined COT donors with the determined highest logical channel priority value (alternatively the COT donor with the highest determined COT donor priority); and/or 4) if step 3 results in a plurality of determined COT donors with the same determined logical channel priority value, select from that plurality of determined COT donors the one with the largest amount of data for the determined highest logical channel priority value. The COT recipient then uses the shared COT according to at least the MCOT (or equivalently the remaining COT duration) applicable to the determined COT Donor.

[0072] According to a second variant of the third embodiment, a COT recipient selects a determined COT donor according to the following: 1) the COT recipient determines the COT donors of each COT sharing indication that is applied to the same time unit - for example, a COT sharing indication is received in an SCI - the 2nd-stage SCI includes the layer 1 source ID and destination ID of a transmission that represent identifiers (e.g., in the physical layer) of the TX UE and intended recipients (e.g., RX UEs) - therefore, the COT recipient can determine the COT donor from the layer 1 source ID - the SCI including the COT sharing indication may additionally indicate an offset in time to determine the time unit in which the COT recipient may start its transmissions in the shared COT - for a given time unit in which the COT recipient intends to transmit, the COT recipient uses this information to determine whether the respective time unit is part of a shared COT and which nodes are respective COT donors; 2) for each of the COT donors, determine the highest logical channel priority among the SL logical channels with the COT donor (e.g., source ID of the node indicating COT sharing such as by SCI) as associated destination having data available - in other words the COT recipient determines a COT donor priority for each of the determined COT donors; 3) select as a determined COT donor the COT donor from the plurality determined COT donors with the determined highest logical channel priority value (alternatively the COT donor with the highest determined COT donor priority); and/or 4) if step 3 results in a plurality of determined COT donors with the same determined logical channel priority value, select from that plurality of determined COT donors the one with the largest amount of data for the determined highest logical channel priority value. The COT recipient then uses the time unit for transmission to at least the determined COT donor according to the applicable rules to that shared COT.

[0073] In a fourth embodiment, a UE determines a destination ID for a transmission on a SL channel. The destination ID may be equivalent to a COT donor as being determined according to the first, second, and/or third embodiment or their variants. In a next step, the UE prioritizes transmission to the destination ID (e.g., a COT donor) in an LCP procedure. Specifically, in a first step in the LCP procedure, the UE sets the destination to the destination ID of the selected COT donor. In a subsequent second step, the UE further selects the logical channels satisfying predefined conditions among the logical channels belonging to the destination set in a first step. [0074] For example, a first and second step may be as shown in Table 1 .

Table 1

[0075] Figure 4 is a schematic block diagram illustrating one embodiment of a system 400 for prioritizing COT sharing. The system 400 includes a first UE 402 and a second UE 404 (or base station). Each of the communications of the system 400 may include one or more messages. The first UE 402 determines 406 a transmitter of a plurality of transmitters corresponding to each COT sharing indication of a plurality of COT sharing indications; determines 408 a COT sharing priority of a plurality of COT sharing priorities for each transmitter of the plurality of transmitters; and determines 410 a COT sharing indication of the plurality of COT sharing indications having a highest COT sharing priority of the plurality of COT sharing priorities. In a first communication 412, the UE first 402 transmits a transmission directed to the transmitter corresponding to the COT sharing indication having the highest COT sharing priority.

[0076] Figure 5 is a flow chart diagram illustrating one embodiment of a method 500 for prioritizing COT sharing. In some embodiments, the method 500 is performed by an apparatus, such as the remote unit 102. In certain embodiments, the method 500 may be performed by a processor executing program code, for example, a microcontroller, a microprocessor, a CPU, a GPU, an auxiliary processing unit, a FPGA, or the like.

[0077] In various embodiments, the method 500 includes determining 502, at a UE, a transmitter of a plurality of transmitters corresponding to each COT sharing indication of a plurality of COT sharing indications. In some embodiments, the method 500 includes determining 504 a COT sharing priority of a plurality of COT sharing priorities for each transmitter of the plurality of transmitters. In certain embodiments, the method 500 includes determining 506 a COT sharing indication of the plurality of COT sharing indications having a highest COT sharing priority of the plurality of COT sharing priorities. In various embodiments, the method 500 includes transmitting 508 a transmission directed to the transmitter corresponding to the COT sharing indication having the highest COT sharing priority.

[0078] In certain embodiments, the method 500 further comprises deriving a COT sharing priority of the plurality of COT sharing priorities based on a signal quality of a received signal or a channel. In some embodiments, the signal quality comprises a reference signal received power (RSRP) value. In various embodiments, the received signal or the channel comprises a physical SL control channel (PSCCH), a physical SL shared channel (PSSCH), a SL reference signal, SL channel state information reference signal, or some combination thereof.

[0079] In one embodiment, a COT sharing priority of the plurality of COT sharing priorities is determined by a priority value included with the COT sharing indication. In certain embodiments, a COT sharing priority of the plurality of COT sharing priorities is determined by a highest logical channel priority among SL logical channels having data available for the transmitter indicating COT sharing. In some embodiments, the method 500 further comprises setting a destination in a logical channel prioritization procedure as the transmitter indicating COT sharing with the highest COT sharing priority.

[0080] Figure 6 is a flow chart diagram illustrating another embodiment of a method 600 for prioritizing COT sharing. In some embodiments, the method 600 is performed by an apparatus, such as a network unit 104 or a remote unit 102. In certain embodiments, the method 600 may be performed by a processor executing program code, for example, a microcontroller, a microprocessor, a CPU, a GPU, an auxiliary processing unit, a FPGA, or the like.

[0081] In various embodiments, the method 600 includes receiving 602, at a network device or at a remote device, a transmission corresponding to a COT sharing indication of a plurality of COT sharing indications having a highest COT sharing priority of a plurality of COT sharing priorities. Each sharing priority of the plurality of COT sharing priorities corresponds to each transmitter of a plurality of transmitters and to each COT sharing indication of the plurality of COT sharing indications.

[0082] In certain embodiments, a COT sharing priority of the plurality of COT sharing priorities is determined by a priority value included with the COT sharing indication. In some embodiments, a COT sharing priority of the plurality of COT sharing priorities is determined by a highest logical channel priority among SE logical channels having data available for the transmitter indicating COT sharing.

[0083] In one embodiment, an apparatus comprises a processor that: determines a transmitter of a plurality of transmitters corresponding to each COT sharing indication of a plurality of COT sharing indications; determines a COT sharing priority of a plurality of COT sharing priorities for each transmitter of the plurality of transmitters; determines a COT sharing indication of the plurality of COT sharing indications having a highest COT sharing priority of the plurality of COT sharing priorities; and transmits a transmission directed to the transmitter corresponding to the COT sharing indication having the highest COT sharing priority.

[0084] In certain embodiments, the processor derives a COT sharing priority of the plurality of COT sharing priorities based on a signal quality of a received signal or a channel.

[0085] In some embodiments, the signal quality comprises a reference signal received power (RSRP) value.

[0086] In various embodiments, the received signal or the channel comprises a PSCCH, a PSSCH, a SL reference signal, SL channel state information reference signal, or some combination thereof.

[0087] In one embodiment, a COT sharing priority of the plurality of COT sharing priorities is determined by a priority value included with the COT sharing indication. [0088] In certain embodiments, a COT sharing priority of the plurality of COT sharing priorities is determined by a highest logical channel priority among SL logical channels having data available for the transmitter indicating COT sharing.

[0089] In some embodiments, the processor sets a destination in a logical channel prioritization procedure as the transmitter indicating COT sharing with the highest COT sharing priority.

[0090] In one embodiment, a method in a UE comprises: determining a transmitter of a plurality of transmitters corresponding to each COT sharing indication of a plurality of COT sharing indications; determining a COT sharing priority of a plurality of COT sharing priorities for each transmitter of the plurality of transmitters; determining a COT sharing indication of the plurality of COT sharing indications having a highest COT sharing priority of the plurality of COT sharing priorities; and transmitting a transmission directed to the transmitter corresponding to the COT sharing indication having the highest COT sharing priority.

[0091] In certain embodiments, the method further comprises deriving a COT sharing priority of the plurality of COT sharing priorities based on a signal quality of a received signal or a channel.

[0092] In some embodiments, the signal quality comprises a reference signal received power (RSRP) value.

[0093] In various embodiments, the received signal or the channel comprises a PSCCH, a PSSCH, a SL reference signal, SL channel state information reference signal, or some combination thereof.

[0094] In one embodiment, a COT sharing priority of the plurality of COT sharing priorities is determined by a priority value included with the COT sharing indication.

[0095] In certain embodiments, a COT sharing priority of the plurality of COT sharing priorities is determined by a highest logical channel priority among SL logical channels having data available for the transmitter indicating COT sharing.

[0096] In some embodiments, the method further comprises setting a destination in a logical channel prioritization procedure as the transmitter indicating COT sharing with the highest COT sharing priority.

[0097] In one embodiment, an apparatus comprises a receiver of a network device or of a remote device that receives a transmission corresponding to a COT sharing indication of a plurality of COT sharing indications having a highest COT sharing priority of a plurality of COT sharing priorities, wherein each sharing priority of the plurality of COT sharing priorities corresponds to each transmiter of a plurality of transmiters and to each COT sharing indication of the plurality of COT sharing indications.

[0098] In certain embodiments, a COT sharing priority of the plurality of COT sharing priorities is determined by a priority value included with the COT sharing indication.

[0099] In some embodiments, a COT sharing priority of the plurality of COT sharing priorities is determined by a highest logical channel priority among SL logical channels having data available for the transmitter indicating COT sharing.

[0100] In one embodiment, a method in a network device comprises receiving a transmission corresponding to a COT sharing indication of a plurality of COT sharing indications having a highest COT sharing priority of a plurality of COT sharing priorities, wherein each sharing priority of the plurality of COT sharing priorities corresponds to each transmiter of a plurality of transmiters and to each COT sharing indication of the plurality of COT sharing indications.

[0101] In certain embodiments, a COT sharing priority of the plurality of COT sharing priorities is determined by a priority value included with the COT sharing indication.

[0102] In some embodiments, a COT sharing priority of the plurality of COT sharing priorities is determined by a highest logical channel priority among SL logical channels having data available for the transmitter indicating COT sharing.

[0103] Embodiments may be practiced in other specific forms. The described embodiments are to be considered in all respects only as illustrative and not restrictive. The scope of the invention is, therefore, indicated by the appended claims rather than by the foregoing description. All changes which come within the meaning and range of equivalency of the claims are to be embraced within their scope.

Claims

1 . An apparatus for wireless communications, the apparatus comprising: a processor; and a memory coupled to the processor, the memory comprising instructions executable by the processor to cause the apparatus to: determine a transmitter of a plurality of transmitters corresponding to each channel occupancy time (COT) sharing indication of a plurality of COT sharing indications; determine a COT sharing priority of a plurality of COT sharing priorities for each transmitter of the plurality of transmitters; determine a COT sharing indication of the plurality of COT sharing indications having a highest COT sharing priority of the plurality of COT sharing priorities; and transmit a transmission directed to the transmitter corresponding to the COT sharing indication having the highest COT sharing priority.

2. The apparatus of claim 1, wherein the instructions are further executable by the processor to cause the apparatus to derive a COT sharing priority of the plurality of COT sharing priorities based at least in part on a signal quality of a received signal or a channel.

3. The apparatus of claim 2, wherein the signal quality comprises a reference signal received power (RSRP) value.

4. The apparatus of claim 2, wherein the received signal or the channel comprises a physical sidelink (SL) control channel (PSCCH), a physical SL shared channel (PSSCH), a SL reference signal, a SL channel state information reference signal (CSI-RS), or a combination thereof.

5. The apparatus of claim 1, wherein a COT sharing priority of the plurality of COT sharing priorities is determined by a priority value included with the COT sharing indication. The apparatus of claim 1, wherein a COT sharing priority of the plurality of COT sharing priorities is determined by a highest logical channel priority among SL logical channels having data available for the transmitter indicating COT sharing. The apparatus of claim 1, wherein the instructions are further executable by the processor to cause the apparatus to set a destination in a logical channel prioritization procedure as the transmitter indicating COT sharing with the highest COT sharing priority. A method in a user equipment (UE), the method comprising: determining a transmitter of a plurality of transmitters corresponding to each channel occupancy time (COT) sharing indication of a plurality of COT sharing indications; determining a COT sharing priority of a plurality of COT sharing priorities for each transmitter of the plurality of transmitters; determining a COT sharing indication of the plurality of COT sharing indications having a highest COT sharing priority of the plurality of COT sharing priorities; and transmitting a transmission directed to the transmitter corresponding to the COT sharing indication having the highest COT sharing priority. The method of claim 8, further comprising deriving a COT sharing priority of the plurality of COT sharing priorities based at least in part on a signal quality of a received signal or a channel. The method of claim 9, wherein the signal quality comprises a reference signal received power (RSRP) value. The method of claim 9, wherein the received signal or the channel comprises a physical SL control channel (PSCCH), a physical SL shared channel (PSSCH), a SL reference signal, SL channel state information reference signal (CSI-RS), or a combination thereof. The method of claim 8, wherein a COT sharing priority of the plurality of COT sharing priorities is determined by a priority value included with the COT sharing indication.

13. An apparatus for wireless communications, the apparatus comprising: a processor; and a memory coupled to the processor, the memory comprising instructions executable by the processor to cause the apparatus to: receive a transmission corresponding to a channel occupancy time (COT) sharing indication of a plurality of COT sharing indications having a highest COT sharing priority of a plurality of COT sharing priorities, wherein each sharing priority of the plurality of COT sharing priorities corresponds to each transmitter of a plurality of transmitters and to each COT sharing indication of the plurality of

COT sharing indications.

14. The apparatus of claim 13, wherein a COT sharing priority of the plurality of COT sharing priorities is determined by a priority value included with the COT sharing indication. 15. The apparatus of claim 13, wherein a COT sharing priority of the plurality of COT sharing priorities is determined by a highest logical channel priority among SL logical channels having data available for the transmitter indicating COT sharing.