WO2024033817A1

WO2024033817A1 - Communicating channel occupancy time sharing information

Info

Publication number: WO2024033817A1
Application number: PCT/IB2023/058020
Authority: WO
Inventors: Karthikeyan Ganesan; Alexander Golitschek Edler Von Elbwart; Prateek Basu Mallick; Joachim Löhr
Original assignee: Lenovo (Singapore) Pte. Ltd.
Priority date: 2022-08-08
Filing date: 2023-08-08
Publication date: 2024-02-15

Abstract

Apparatuses, methods, and systems are disclosed for communicating COT sharing information. One method (600) includes receiving (602), at a receiver ("RX") user equipment ("UE"), channel occupancy time ("COT") sharing information from a transmitter ("TX") UE. The COT sharing information includes a COT sharing indicator, a range value, coarse location information, a zone identifier ("ID"), or some combination thereof. The method (600) includes in response to receiving (604) the COT sharing information, determining whether the RX UE is a COT recipient based on whether a present location of the RX UE is within a range indicated by the range value.

Description

COMMUNICATING CHANNEL OCCUPANCY TIME SHARING INFORMATION

FIELD

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

BACKGROUND

[0002] In certain wireless communications systems, COT may be used. In such systems, the COT may be used by multiple devices.

BRIEF SUMMARY

[0003] Methods for communicating COT sharing information are disclosed. Apparatuses and systems also perform the functions of the methods. One embodiment of a method includes receiving, at a receiver (“RX") user equipment (“UE”), COT sharing information from a transmit (“TX”) UE. The COT sharing information includes a COT sharing indicator, a range value, coarse location information, a zone ID, or some combination thereof. In some embodiments, the method includes, in response to receiving the COT sharing information, determining whether the RX UE is a COT recipient based on whether a present location of the RX UE is within a range indicated by the range value.

[0004] One apparatus for communicating COT sharing information includes a receiver to receive, at a RX UE, COT sharing information from a TX UE. The COT sharing information comprises a COT sharing indicator, a range value, coarse location information, a zone ID, or some combination thereof. In some embodiments, the apparatus includes a processor to, in response to receiving the COT sharing information, determine whether the RX UE is a COT recipient based on whether a present location of the RX UE is within a range indicated by the range value.

[0005] Another embodiment of a method for communicating COT sharing information includes transmitting, at a TX UE, COT sharing information to a RX UE. The COT sharing information comprises a COT sharing indicator, a range value, coarse location information, a zone ID, or some combination thereof.

[0006] Another apparatus for communicating COT sharing information includes a transmitter to transmit, from a TX UE, COT sharing information to a RX UE. The COT sharing information comprises a COT sharing indicator, a range value, coarse location information, a zone ID, or some combination thereof. 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 communicating COT sharing information;

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

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

[0011] Figures 4A through 4D are schematic block diagrams illustrating embodiments of sidelink slot structures;

[0012] Figure 5 is a schematic block diagram illustrating one embodiment of a system for range based UE to UE COT sharing;

[0013] Figure 6 is a flow chart diagram illustrating one embodiment of a method for communicating COT sharing information; and

[0014] Figure 7 is a flow chart diagram illustrating another embodiment of a method for communicating COT sharing information.

DETAILED DESCRIPTION

[0015] 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.

[0016] 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.

[0017] 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.

[0018] 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.

[0019] 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.

[0020] 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.

[0021] 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).

[0022] 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.

[0023] 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.

[0024] 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.

[0025] 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.

[0026] 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.

[0027] 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).

[0028] 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.

[0029] 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.

[0030] 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.

[0031] Figure 1 depicts an embodiment of a wireless communication system 100 for communicating COT sharing information. 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.

[0032] 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 UL communication signals. In certain embodiments, the remote units 102 may communicate directly with other remote units 102 via sidelink communication.

[0033] 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- 3 GPP 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 communicab ly 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.

[0034] In one implementation, the wireless communication system 100 is compliant with NR protocols standardized in third generation partnership project (“3GPP”), wherein the network unit 104 transmits using an OFDM modulation scheme on the downlink (“DL”) and the remote units 102 transmit on the uplink (“UL”) using a single -carrier frequency division multiple access (“SC-FDMA”) scheme or an orthogonal frequency division multiplexing (“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.

[0035] 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.

[0036] In various embodiments, a remote unit 102 (e.g., RX UE) may receive COT sharing information from a TX UE. The COT sharing information includes a COT sharing indicator, a range value, coarse location information, a zone ID, or some combination thereof. In some embodiments, the remote unit 102 may, in response to receive the COT sharing information, determining whether the RX UE is a COT recipient based on whether a present location of the RX UE is within a range indicated by the range value. Accordingly, the remote unit 102 may be used for communicating COT sharing information.

[0037] In certain embodiments, a remote unit 102 (e.g., TX UE) may transmit sharing information to a RX UE. The COT sharing information comprises a COT sharing indicator, a range value, coarse location information, a zone ID, or some combination thereof. Accordingly, the network unit 104 may be used for communicating COT sharing information.

[0038] Figure 2 depicts one embodiment of an apparatus 200 that may be used for communicating COT sharing information. 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.

[0039] 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.

[0040] 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.

[0041] 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.

[0042] 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.

[0043] 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.

[0044] In certain embodiments, the receiver 212 to receive, at a RX UE, COT sharing information from a TX UE. The COT sharing information comprises a COT sharing indicator, a range value, coarse location information, a zone ID, or some combination thereof. In some embodiments, the processor 202 to, in response to receiving the COT sharing information, determine whether the RX UE is a COT recipient based on whether a present location of the RX UE is within a range indicated by the range value.

[0045] In certain embodiments, the transmitter 210 to transmit, from a TX UE, COT sharing information to a RX UE. The COT sharing information comprises a COT sharing indicator, a range value, coarse location information, a zone ID, or some combination thereof.

[0046] 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. [0047] Figure 3 depicts one embodiment of an apparatus 300 that may be used for communicating COT sharing information. 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.

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

[0049] In certain embodiments, sidelink (“SL”) unlicensed operation may be used and a channel access mechanism for SL in an unlicensed band may be used.

[0050] In some embodiments, gNB initiated COT sharing and/or UE initiated COT sharing may be used. In various embodiments, a group common downlink control information (“DCI”) format 2 0 may indicate one or more COT sharing indicators initiated by the gNB to each of multiple cells, and a UE initiated COT sharing indicator may be shared to a gNB using a field in configured grant (“CG”) uplink control information (“UCI”) (“CG-UCI”).

[0051] In certain embodiments, COT sharing indicator may be used in SL for an unlicensed spectrum to get feedback from receiver (“RX”) UEs, physical sidelink shared channel (“PSSCH”) transmission from RX UEs, and so forth in a remaining channel occupancy duration. In some embodiments, UE-to-UE COT sharing procedures may consider a transmitter (“TX”) UE connection with multiple RX UEs and/or destination identifiers (“IDs”).

[0052] In various embodiments, COT recipients that may use a shared COT may be restricted by transmitting a range value along with COT sharing information. In such embodiments, the restriction may be necessary considering that a COT sharing indicator may be received by multiple UEs which may lead to increased collision in the shared COT. Moreover, limiting a COT recipient may be necessary to limit collision. Table 1 indicates one example of a table that may be used for a channel access priority class (“CAPC”). Table 1: CAPC

[0053] As used herein, the term eNB and/or gNB may be used for a base station (“BS”) but it may be replaceable by any other radio access node (e.g., access point (“AP”), NR, and so forth). Furthermore, certain embodiments described herein are discussed mainly in the context of 5G NR; however, the embodiments herein may be applicable to other mobile communication systems supporting serving cells and/or carriers being configured for sidelink communication over a vehicle to vehicle (“PC5”) interface.

[0054] As used herein, the following definitions may be used for sidelink channel access mechanisms: 1) TX UE: a UE that transmits COT sharing information (e.g., a COT sharing indicator) via a sidelink connection; 2) RX UE: a UE that receives COT sharing information (e.g., a COT sharing indicator) via a sidelink connection; 3) COT initiator: a sidelink device that initiated a channel occupancy (e.g., TX UE); 4) COT donor: a sidelink device that transmits COT sharing information (e.g., a COT sharing indicator, a TX UE) - the COT donor may be identical to the COT initiator; and 5) COT recipient: a sidelink device that receives COT sharing information (e.g., a COT sharing indicator, a RX UE).

[0055] In certain embodiments, a COT sharing indicator is shared by a COT initiator UE with a range or minimum communication range (“MCR”) value. UEs within the MCR may become its COT recipient.

[0056] In some embodiments, a SL slot structure contains automatic gain control (“AGC”) symbols at the beginning of the SL slot, then a physical sidelink control channel (“PSCCH”) symbol followed by PSSCH symbols, and the last symbol in the SL slot is configured as a gap symbol (e.g., guard as shown in Figures 4A through 4D) to enable a switching time from TX to RX.

[0057] In various embodiments, a resource pool maybe configured and/or preconfigured with one or two physical sidelink feedback channel (“PSFCH”) symbols, using a PSFCH period of 1, 2, 4, or 8 slots and the slots where the PSFCH occurs may be configured with an additional AGC symbol and a gap symbols as seen from Figures 4A through 4D to enable switching from TX to RX for the reception of hybrid automatic repeat request (“HARQ”) feedback.

[0058] Figures 4A through 4D are schematic block diagrams illustrating embodiments of sidelink slot structures. Specifically, Figure 4A 400 illustrates a slot 402 with 14 sidelink symbols available, a first duplicated symbol 404, and a second duplicated symbol 406. Further, Figure 4B 408 illustrates a slot 410 with 14 side link slots available, MPSSCH physical resource blocks (“PRBs”) 412 over LPSSCH subchannels, MPSCCH PRBs 414, a duplicated symbol 416, and a symbol 418. Moreover, Figure 4C 420 illustrates a slot 422 with 13 sidelink slots available and a duplicated symbol 424. Figure 4D 426 illustrates a slot with 14 sidelink slots available, 127 subcarriers 428, and MS-SSB 430 = 11 RBs.

[0059] In certain embodiments, contiguous transmission may be needed to be performed in a sidelink unlicensed spectrum after initiating a channel occupancy by a COT initiator UE and the gap duration (e.g., guard in Figures 4A through 4D) needed to perform category (“Cat”) 2 listen before talk (“LBT”) to access a shared COT by the COT recipient UE may be less than or equal to 16 and/or 25 microseconds. Thus, in such embodiments, to enable the contiguous transmission in SL, a slot structure may need to be defined without gap symbols and with cyclic prefix extension (“CP-Ext”) symbols to reduce the gap duration.

[0060] In a first embodiment, there may be range based UE to UE COT sharing information (e.g., COT sharing indicator). According to the first embodiment, a TX UE, after performing Cat 4 LBT, may share a remaining COT with another one or more UEs using COT sharing information (e.g., a ‘COT sharing indicator’) as described in relation to Figure 5, where the COT sharing information may be restricted using a range value (e.g., communication range which may be signaled by the UE in sidelink control information (“SCI”) or configured and/or preconfigured in a resource pool). In certain embodiments, a COT initiator’s zone ID may be signaled in SCI as part of COT sharing information so that the receiver UE may compare its own location to that of the COT initiators zone ID and the receiver UE may determine to become a COT recipient only when the RX UEs location is within the indicated range UE.

[0061] In some embodiments, UEs within a communication range may become COT recipients which may further use a remaining channel occupancy duration indicated in COT sharing information (e.g., a COT sharing indicator) to transmit SL control information and data. In such embodiments, UEs outside the communication range may not become a COT recipient which means that the UEs outside the communication range may not use the remaining channel occupancy duration to transmit SL control information and data. [0062] In one implementation, a COT initiator may broadcast or groupcast in first SCI or in second SCI with a COT sharing indicator field set to ‘ I’ and containing a range value to restrict a COT recipient.

[0063] Figure 5 is a schematic block diagram illustrating one embodiment of a system 500 for range based UE to UE COT sharing. The system 500 includes a UE-1 502, a UE-2 504, a UE- 3 506, and a UE-4 508 with some of the UEs within a communication area 510 defined based on a range 512 (e.g., range value). The UE-2 504 is outside the communication area 510, while the UE-3 506 and the UE-4 508 are within the communication area 510. Based on Figure 5, a COT initiator (e.g., UE-1 502) may share its own remaining channel occupancy duration restricting to UEs within the communication area 510 (e.g., UE-3 506 and UE-4 508) which may be the beneficiaries of the COT recipient. The UE-2 504 outside the communication area 510 may still be able to decode the COT sharing information, but since it is outside the communication range it may not become a COT recipient.

[0064] In various embodiments, SCI may explicitly indicate applicability of COT sharing information (e.g., a COT sharing indication) to a certain sidelink physical channel. In one implementation, the COT initiator may indicate as part of COT sharing information to the COT recipient how the shared COT may be used (e.g., such as that the COT recipient may only transmit PSFCH, PSCCH, PSSCH, sidelink-synchronization signal block (“SL-SSB”), positioning reference signal (“PRS”), or a combination thereof in the shared COT).

[0065] In certain embodiments, COT sharing information (e.g., a COT sharing indicator) may include an energy detection threshold (e.g., received signal strength indicator (“RSSI”), reference signal received power (“RSRP”), and/or path loss which may be configured and/or preconfigured in a resource pool or signaled in SCI). In such embodiments, UEs, after receiving the COT sharing information, may measure RSSI and/or RSRP values, and UEs within the energy detection threshold (e.g., RSSI and/or RSRP) may become a COT recipient while UEs outside of the threshold may not become the COT recipient.

[0066] In some embodiments, a TX UE (e.g., COT initiator) may share COT sharing information (e.g., a COT sharing indicator) together with one or more destination ID so that COT recipient may transmit a unicast PSSCH toward the COT initiator. However, the TX UE (e.g., COT initiator) may share the COT sharing information with a range value instead of one or more destination ID so the ‘N’ RX UEs that are within the range may become COT recipients. Hence, the range may be applicable for groupcast and/or broadcast COT sharing information and may not be applicable for unicast COT sharing information. [0067] In various embodiments, COT recipients may perform PSSCH transmission and may indicate the same minimum communication range (“MCR”) value to seek HARQ feedback for PSSCH transmission within the shared COT duration by using a groupcast option-1 (e.g., common non-acknowledgement (“NACK”) resource) HARQ feedback and may be indicated as the same or less than the MCR value (e.g., <= MCR value) in the SCI compared to a range based COT sharing information.

[0068] In certain embodiments, an MCR value to seek HARQ feedback using groupcast HARQ feedback option- 1 may be completely different than that of a range based COT sharing information. The MCR value used to seek HARQ feedback may be indicated by a higher layer of a UE; however, the range based COT sharing information may be based on a energy detection threshold.

[0069] Figure 6 is a flow chart diagram illustrating one embodiment of a method 600 for communicating COT sharing information. In some embodiments, the method 600 is performed by an apparatus, such as the 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.

[0070] In various embodiments, the method 600 includes receiving 602, at an RX UE, COT sharing information from a TX UE, wherein the COT sharing information includes a COT sharing indicator, a range value, coarse location information, a zone ID, or some combination thereof. In some embodiments, the method 600, includes in response to receiving 604 the COT sharing information, determining 604 whether the RX UE is a COT recipient based on whether a present location of the RX UE is within a range indicated by the range value.

[0071] In certain embodiments, the RX UE is determined to be the COT recipient in response to the present location of the RX UE being within the range indicated by the range value. In some embodiments, the RX UE is determined to not be the COT recipient in response to the present location of the RX UE being outside the range indicated by the range value. In various embodiments, the method 600 further comprises receiving information indicating that transmissions of the COT recipient within a shared COT duration comprise a PSCCH transmission, a PSSCH transmission, a PSFCH transmission, a PRS, or some combination thereof.

[0072] In one embodiment, the COT sharing information comprises an indication of a transmission of a physical channel within a shared COT. In certain embodiments, the range value is configured as part of a resource pool.

[0073] In some embodiments, the COT sharing information comprises an energy detection threshold. In various embodiments, the COT sharing indicator comprises a destination ID. [0074] Figure 7 is a flow chart diagram illustrating another embodiment of a method 700 for communicating COT sharing information. In some embodiments, the method 700 is performed by an apparatus, such as the remote unit 102. In certain embodiments, the method 700 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.

[0075] In various embodiments, the method 700 includes transmitting 702, at a TX UE, COT sharing information to a RX UE, wherein the COT sharing information comprises a COT sharing indicator, a range value, coarse location information, a zone ID, or some combination thereof.

[0076] In certain embodiments, the RX UE is determined to be a COT recipient in response to a present location of the RX UE being within a range indicated by the range value. In some embodiments, the RX UE is determined to not be a COT recipient in response to a present location of the RX UE being outside a range indicated by the range value. In various embodiments, the method 700 further comprises transmitting information to the RX UE indicating that transmissions of the RX UE within a shared COT duration comprise a PSCCH transmission, a PSSCH transmission, a PSFCH transmission, a PRS, or some combination thereof.

[0077] In one embodiment, the COT sharing information comprises an indication of a transmission of a physical channel within a shared COT. In certain embodiments, the range value is configured as part of a resource pool.

[0078] In some embodiments, the COT sharing information comprises an energy detection threshold. In various embodiments, the COT sharing indicator comprises a destination ID.

[0079] In one embodiment, an apparatus comprises: a receiver to receive, at a RX UE, COT sharing information from a TX UE, wherein the COT sharing information comprises a COT sharing indicator, a range value, coarse location information, a zone ID, or some combination thereof; and a processor to, in response to receiving the COT sharing information, determine whether the RX UE is a COT recipient based on whether a present location of the RX UE is within a range indicated by the range value.

[0080] In certain embodiments, the RX UE is determined to be the COT recipient in response to the present location of the RX UE being within the range indicated by the range value.

[0081] In some embodiments, the RX UE is determined to not be the COT recipient in response to the present location of the RX UE being outside the range indicated by the range value .

[0082] In various embodiments, the receiver to further receive information indicating that transmissions of the COT recipient within a shared COT duration comprise a PSCCH transmission, a PSSCH transmission, a PSFCH transmission, a PRS, or some combination thereof. [0083] In one embodiment, the COT sharing information comprises an indication of a transmission of a physical channel within a shared COT.

[0084] In certain embodiments, the range value is configured as part of a resource pool.

[0085] In some embodiments, the COT sharing information comprises an energy detection threshold.

[0086] In various embodiments, the COT sharing indicator comprises a destination ID.

[0087] In one embodiment, a method at a RX UE, the method comprises: receiving COT sharing information from a TX UE, wherein the COT sharing information comprises a COT sharing indicator, a range value, coarse location information, a zone ID, or some combination thereof; and in response to receiving the COT sharing information, determining whether the RX UE is a COT recipient based on whether a present location of the RX UE is within a range indicated by the range value.

[0088] In certain embodiments, the RX UE is determined to be the COT recipient in response to the present location of the RX UE being within the range indicated by the range value.

[0089] In some embodiments, the RX UE is determined to not be the COT recipient in response to the present location of the RX UE being outside the range indicated by the range value .

[0090] In various embodiments, the method further comprises receiving information indicating that transmissions of the COT recipient within a shared COT duration comprise a PSCCH transmission, a PSSCH transmission, a PSFCH transmission, a PRS, or some combination thereof.

[0091] In one embodiment, the COT sharing information comprises an indication of a transmission of a physical channel within a shared COT.

[0092] In certain embodiments, the range value is configured as part of a resource pool.

[0093] In some embodiments, the COT sharing information comprises an energy detection threshold.

[0094] In various embodiments, the COT sharing indicator comprises a destination ID.

[0095] In one embodiment, an apparatus comprises: a transmitter to transmit, from a TX UE, COT sharing information to a RX UE, wherein the COT sharing information comprises a COT sharing indicator, a range value, coarse location information, a zone ID, or some combination thereof.

[0096] In certain embodiments, the RX UE is determined to be a COT recipient in response to a present location of the RX UE being within a range indicated by the range value.

[0097] In some embodiments, the RX UE is determined to not be a COT recipient in response to a present location of the RX UE being outside a range indicated by the range value. [0098] In various embodiments, the transmitter to further transmit information to the RX UE indicating that transmissions of the RX UE within a shared COT duration comprise a PSCCH transmission, a PSSCH transmission, a PSFCH transmission, a PRS, or some combination thereof.

[0099] In one embodiment, the COT sharing information comprises an indication of a transmission of a physical channel within a shared COT.

[0100] In certain embodiments, the range value is configured as part of a resource pool.

[0101] In some embodiments, the COT sharing information comprises an energy detection threshold.

[0102] In various embodiments, the COT sharing indicator comprises a destination ID.

[0103] In one embodiment, a method at a TX UE, the method comprises: transmitting COT sharing information to a RX UE, wherein the COT sharing information comprises a COT sharing indicator, a range value, coarse location information, a zone ID, or some combination thereof.

[0104] In certain embodiments, the RX UE is determined to be a COT recipient in response to a present location of the RX UE being within a range indicated by the range value.

[0105] In some embodiments, the RX UE is determined to not be a COT recipient in response to a present location of the RX UE being outside a range indicated by the range value.

[0106] In various embodiments, the method further comprises transmitting information to the RX UE indicating that transmissions of the RX UE within a shared COT duration comprise a PSCCH transmission, a PSSCH transmission, a PSFCH transmission, a PRS, or some combination thereof.

[0107] In one embodiment, the COT sharing information comprises an indication of a transmission of a physical channel within a shared COT.

[0108] In certain embodiments, the range value is configured as part of a resource pool.

[0109] In some embodiments, the COT sharing information comprises an energy detection threshold.

[0110] In various embodiments, the COT sharing indicator comprises a destination ID.

[0111] 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 . A receiver (RX) user equipment (UE), comprising: at least one memory; and at least one processor coupled with the at least one memory and configured to cause the RX UE to: receive channel occupancy time (COT) sharing information from a transmitter (TX) UE, wherein the COT sharing information comprises a COT sharing indicator, a range value, coarse location information, a zone identifier (ID), or a combination thereof; and in response to receiving the COT sharing information, determine whether the RX UE is a COT recipient based on whether a present location of the RX UE is within a range indicated by the range value.

2. The RX UE of claim 1, wherein the RX UE is determined to be the COT recipient in response to the present location of the RX UE being within the range indicated by the range value.

3. The RX UE of claim 1, wherein the RX UE is determined to not be the COT recipient in response to the present location of the RX UE being outside the range indicated by the range value.

4. The RX UE of claim 1, wherein the at least one processer is configured to cause the RX UE to further receive information indicating that transmissions of the COT recipient within a shared COT duration comprise a physical sidelink control channel (PSCCH) transmission, a physical sidelink shared channel (PSSCH) transmission, a physical sidelink feedback channel (PSFCH) transmission, a positioning reference signal (PRS), or a combination thereof.

5. The RX UE of claim 1, wherein the COT sharing information comprises an indication of a transmission of a physical channel within a shared COT.

6. The RX UE of claim 1, wherein the range value is configured as part of a resource pool. The RX UE of claim 1, wherein the COT sharing information comprises an energy detection threshold. The RX UE of claim 1, wherein the COT sharing indicator comprises a destination ID. A processor for wireless communication, comprising : at least one controller coupled with at least one memory and configured to cause the processor to: receive channel occupancy time (COT) sharing information from a transmitter (TX) user equipment (UE), wherein the COT sharing information comprises a COT sharing indicator, a range value, coarse location information, a zone identifier (ID), or a combination thereof; and in response to receiving the COT sharing information, determine whether a receiver (RX) UE is a COT recipient based on whether a present location of the RX UE is within a range indicated by the range value. The processor of claim 9, wherein the RX UE is determined to be the COT recipient in response to the present location of the RX UE being within the range indicated by the range value. A transmitter (TX) user equipment (UE), comprising: at least one memory; and at least one processor coupled with the at least one memory and configured to cause the TX UE to: transmit channel occupancy time (COT) sharing information to a receiver (RX) UE, wherein the COT sharing information comprises a COT sharing indicator, a range value, coarse location information, a zone identifier (ID), or a combination thereof. The TX UE of claim 11, wherein the RX UE is determined to be a COT recipient in response to a present location of the RX UE being within a range indicated by the range value. The TX UE of claim 11, wherein the RX UE is determined to not be a COT recipient in response to a present location of the RX UE being outside a range indicated by the range value. The TX UE of claim 11, wherein the at least one processer is configured to cause the TX UE to further transmit information to the RX UE indicating that transmissions of the RX UE within a shared COT duration comprise a physical sidelink control channel (PSCCH) transmission, a physical sidelink shared channel (PSSCH) transmission, a physical sidelink feedback channel (PSFCH) transmission, a positioning reference signal (PRS), or a combination thereof. The TX UE of claim 11, wherein the COT sharing information comprises an indication of a transmission of a physical channel within a shared COT. The TX UE of claim 11, wherein the range value is configured as part of a resource pool. The TX UE of claim 11, wherein the COT sharing information comprises an energy detection threshold. The TX UE of claim 11, wherein the COT sharing indicator comprises a destination ID. A processor for wireless communication, comprising: at least one controller coupled with at least one memory and configured to cause the processor to transmit channel occupancy time (COT) sharing information to a receiver (RX) user equipment (UE), wherein the COT sharing information comprises a COT sharing indicator, a range value, coarse location information, a zone identifier (ID), or a combination thereof. The processor of claim 19, wherein the RX UE is determined to be a COT recipient in response to a present location of the RX UE being within a range indicated by the range value.