Channel occupancy time sharing

Abstract

Apparatuses, methods, and systems are disclosed for channel occupancy time sharing. A method (800) includes determining (802) channel occupancy time sharing for at least one user equipment. The method (800) includes transmitting (804) information indicating the channel occupancy time sharing to the at least one user equipment. The channel occupancy time sharing indicates shared information for at least one uplink communication, at least one sidelink communication, or a combination thereof. The method (800) includes receiving (806) the at least one uplink communication, the at least one sidelink communication, or the combination thereof based on the channel occupancy time sharing.

Description

[0001] Cross-references to related applications

[0002] This application claims priority to U.S. Patent Application No. 63 / 040,386, filed June 17, 2020, entitled “Apparatus, Methods, and Systems for a Non-Licensed Operation for a Cross-Link Sharing (NR Sidelink),” which is incorporated herein by reference in its entirety. Technical Field

[0003] The topics disclosed in this article generally relate to wireless communication, and more specifically to channel occupancy time sharing. Background Technology

[0004] In some wireless communication networks, network devices, user equipment, and / or sidelink devices may be used. The transmission times of such devices may interfere with each other. Summary of the Invention

[0005] A method for channel occupancy time sharing is disclosed. Apparatus and systems also perform the functions of the method. One embodiment of the method includes determining channel occupancy time sharing for at least one user equipment. In some embodiments, the method includes transmitting information indicating channel occupancy time sharing to at least one user equipment. The channel occupancy time sharing indicates sharing information for at least one uplink communication, at least one sidelink communication, or a combination thereof. In some embodiments, the method includes receiving at least one uplink communication, at least one sidelink communication, or a combination thereof based on the channel occupancy time sharing.

[0006] An apparatus for channel occupancy time sharing includes a user equipment. In some embodiments, the apparatus includes a processor that determines channel occupancy time sharing for at least one user equipment. In various embodiments, the apparatus includes a transmitter that transmits information indicating channel occupancy time sharing to at least one user equipment. The channel occupancy time sharing indicates sharing information for at least one uplink communication, at least one sidelink communication, or a combination thereof. In some embodiments, the apparatus includes a receiver that receives at least one uplink communication, at least one sidelink communication, or a combination thereof based on the channel occupancy time sharing.

[0007] Another embodiment of the method for channel occupancy time sharing includes performing a listen-before-speak procedure at the user equipment. In some embodiments, the method includes initiating channel occupancy time sharing for the user equipment based on the listen-before-speak procedure. The channel occupancy time sharing indicates shared information to be transmitted from the user equipment for at least one uplink communication, at least one sidelink communication, or a combination thereof. In some embodiments, the method includes transmitting at least one uplink communication, at least one sidelink communication, or a combination thereof from the user equipment based on the channel occupancy time sharing.

[0008] Another apparatus for channel occupancy time sharing includes a user equipment. In some embodiments, the apparatus includes a processor that: performs a listen-before-speak procedure; and initiates channel occupancy time sharing for the user equipment based on the listen-before-speak procedure. The channel occupancy time sharing indicates shared information to be transmitted from the user equipment for at least one uplink communication, at least one sidelink communication, or a combination thereof. In various embodiments, the apparatus includes a transmitter that transmits at least one uplink communication, at least one sidelink communication, or a combination thereof based on channel occupancy time sharing. Attached Figure Description

[0009] A more detailed description of the embodiments briefly described above will be presented with reference to specific embodiments illustrated in the accompanying drawings. It should be understood that these drawings depict only some embodiments and are not intended to be limiting of the scope; the embodiments will be described and explained with additional features and details using the drawings, wherein:

[0010] Figure 1 This is a schematic block diagram illustrating one embodiment of a wireless communication system for sharing channel occupancy time;

[0011] Figure 2 This is a schematic block diagram illustrating one embodiment of a device that can be used for channel occupancy time sharing;

[0012] Figure 3 This is a schematic block diagram illustrating one embodiment of a device that can be used for channel occupancy time sharing;

[0013] Figure 4 This is a schematic block diagram illustrating an embodiment of a gNB initiating a COT shared with UL and / or SL;

[0014] Figure 5 This is a schematic block diagram illustrating an embodiment of a COT initiated by a UE and shared with a gNB and other SL UEs;

[0015] Figure 6 This is a schematic block diagram illustrating an embodiment of COT sharing initiated by an SL UE;

[0016] Figure 7 This is a schematic block diagram illustrating one embodiment of SL COT sharing in a relay environment;

[0017] Figure 8 This is a flowchart illustrating one embodiment of a method for sharing channel occupancy time; and

[0018] Figure 9 This is a flowchart illustrating another embodiment of a method for sharing channel occupancy time. Detailed Implementation

[0019] As those skilled in the art will understand, aspects of the embodiments can be embodied as a system, apparatus, method, or program product. Therefore, embodiments can take the form of a completely hardware embodiment, a completely software embodiment (including firmware, resident software, microcode, etc.), or an embodiment combining software and hardware aspects, which are generally referred to herein as “circuit,” “module,” or “system.” Furthermore, embodiments can take the form of a program product embodied in one or more computer-readable storage devices stored in machine-readable code, computer-readable code, and / or program code, hereinafter referred to as code. The storage device can be tangible, non-transitory, and / or non-transferable. The storage device may not embody signals. In one embodiment, the storage device only uses signals for accessing the code.

[0020] Certain functional units described in this specification may be designated as modules to more specifically emphasize their implementation independence. For example, a module may be implemented as hardware circuitry comprising custom-designed very large-scale integration (“VLSI”) circuitry or gate arrays, off-the-shelf semiconductors such as logic chips, transistors, or other discrete components. Modules may also be implemented in programmable hardware devices such as field-programmable gate arrays, programmable array logic, programmable logic devices, etc.

[0021] Modules can also be implemented in code and / or software to be executed by various types of processors. The identified code module may, for example, comprise one or more physical or logical blocks of executable code, which may be organized, for example, as objects, procedures, or functions. However, the executable files of the identified module do not need to be physically located together, but may include unrelated instructions stored in different locations, which, when logically connected together, constitute the module and achieve the module's stated purpose.

[0022] In practice, a code module can be a single instruction or many instructions, and can even be distributed across several different code segments, different programs, and across several memory devices. Similarly, in this document, operational data can be identified and visualized within a module, and can be represented in any suitable form and organized within any suitable type of data structure. Operational data can be collected as a single dataset or can be distributed across different locations, including different computer-readable storage devices. Where a module or part of a module is implemented in software, the software portion is stored on one or more computer-readable storage devices.

[0023] Any combination of one or more computer-readable media may be used. A computer-readable medium may be a computer-readable storage medium. A computer-readable storage medium may be a storage device for storing code. A storage device may be, for example, but not limited to, electronic, magnetic, optical, electromagnetic, infrared, holographic, micromechanical, or semiconductor systems, apparatuses, or devices, or any suitable combination thereof.

[0024] More specific examples of storage devices (a non-exhaustive list) will include the following: electrical connections having one or more wires, portable computer disks, hard disks, random access memory (“RAM”), read-only memory (“ROM”), erasable programmable read-only memory (“EPROM” or flash memory), portable optical disc read-only memory (“CD-ROM”), optical storage devices, magnetic storage devices, or any suitable combination of the foregoing. In the context of this document, a computer-readable storage medium can be any tangible medium capable of containing or storing programs for use by or in connection with an instruction execution system, apparatus, or device.

[0025] The code used to perform the operations of the embodiments can be any number of lines and can be written in any combination of one or more programming languages, including object-oriented programming languages ​​such as Python, Ruby, Java, Smalltalk, and C++, and traditional procedural programming languages ​​such as the "C" programming language, and / or machine languages ​​such as assembly language. The code can be executed entirely on the user's computer, partially on the user's computer, or as a standalone software package on the user's computer, partially on a remote computer, or entirely on a remote computer or server. In the latter scenario, the remote computer can be connected to the user's computer via any type of network, including a local area network ("LAN") or a wide area network ("WAN"), or it can be connected to an external computer (e.g., via the Internet through an Internet service provider).

[0026] Throughout this specification, references to "an embodiment," "embodiment," or similar language mean that a particular feature, structure, or characteristic described in connection with that embodiment is included in at least one embodiment. Therefore, unless expressly stated otherwise, throughout this specification, the phrases "in an embodiment," "in an embodiment," and similar language may, but not necessarily all refer to the same embodiment, but rather mean "one or more, but not all, embodiments." Unless expressly stated otherwise, the terms "comprising," "including," "having," and variations thereof mean "including, but not limited to,". Unless expressly stated otherwise, the list of enumerated items does not imply that any or all items are mutually exclusive. Unless expressly stated otherwise, the terms "a," "an," and "the" also mean "one or more".

[0027] Furthermore, the features, structures, or characteristics of the described embodiments can be combined in any suitable manner. Numerous specific details, such as examples of programming, software modules, user selection, network transactions, database queries, database structures, hardware modules, hardware circuits, hardware chips, etc., are provided in the following description to provide a thorough understanding of the embodiments. However, those skilled in the art will recognize that the embodiments can be practiced without one or more of these specific details, or using other methods, components, materials, etc. In other instances, well-known structures, materials, or operations have not been shown or described in detail to avoid obscuring some aspects of the embodiments.

[0028] The following description of aspects of embodiments is based on schematic flowcharts and / or schematic block diagrams of methods, apparatus, systems, and program products according to embodiments. It will be understood that each block of the schematic flowcharts and / or schematic block diagrams, and combinations of blocks in the schematic flowcharts and / or schematic block diagrams, can be implemented by code. The code can be provided to a processor of a general-purpose computer, special-purpose computer, or other programmable data processing apparatus to generate machinery, such that instructions executable via the processor of the computer or other programmable data processing apparatus create means for implementing the functions / operations specified in the blocks or blocks of the schematic flowcharts and / or schematic block diagrams.

[0029] The code may also be stored in a storage device that can instruct a computer, other programmable data processing device or other device to operate in a particular manner, such that the instructions stored in the storage device produce an article of art including instructions that implement the functions / operations specified in the boxes or some boxes of the schematic flowchart and / or schematic block diagram.

[0030] The code may also be loaded onto a computer, other programmable data processing apparatus or other device, causing a series of operational steps to be performed on the computer, other programmable apparatus or other device to produce a computer-implemented process, such that the code executing on the computer or other programmable apparatus provides a process for implementing the functions / operations specified in the boxes or some boxes of the flowchart and / or block diagram.

[0031] The schematic flowcharts and / or schematic block diagrams in the accompanying drawings illustrate the architecture, functionality, and operation of possible implementations of apparatus, systems, methods, and program products according to different embodiments. In this regard, each block in the schematic flowcharts and / or schematic block diagrams may represent a module, segment, or portion of code, which includes one or more executable instructions for implementing a specified logical function.

[0032] It should also be noted that in some alternative implementations, the functions marked in the boxes may not occur in the order indicated in the figures. For example, depending on the functionality involved, two consecutively shown boxes may actually be executed substantially simultaneously, or these blocks may sometimes be executed in reverse order. Other steps and methods that are functionally, logically, or effectively equivalent to one or more boxes or portions thereof in the illustrated figures are conceivable.

[0033] While various arrow and line types may be used in flowcharts and / or block diagrams, it should be understood that they do not limit the scope of the respective embodiments. In fact, some arrows or other connectors may be used solely to indicate the logical flow of the depicted embodiment. For example, an arrow may indicate a wait or monitoring period of unspecified duration between enumeration steps in a depicted embodiment. It will also be noted that each block in the block diagram and / or flowchart, and combinations of some blocks in the block diagram and / or flowchart, can be implemented by a dedicated hardware-based system performing a specific function or operation, or by a combination of dedicated hardware and code.

[0034] The description of the elements in each figure can be referenced to the elements in the preceding figures. The same numbers refer to the same elements in all figures, including alternative embodiments of the same elements.

[0035] Figure 1 An embodiment of a wireless communication system 100 for sharing channel occupancy time is depicted. In one embodiment, the wireless communication system 100 includes a remote unit 102 and a network unit 104. Although Figure 1 A specific number of remote units 102 and network units 104 are depicted, but those skilled 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.

[0036] In one embodiment, remote unit 102 may include computing devices such as desktop computers, laptop computers, personal digital assistants (“PDAs”), tablet computers, smartphones, smart TVs (e.g., internet-connected televisions), set-top boxes, game consoles, security systems (including surveillance cameras), in-vehicle computers, network devices (e.g., routers, switches, modems), aircraft, drones, etc. In some embodiments, remote unit 102 includes wearable devices such as smartwatches, fitness bands, optical head-mounted displays, etc. Furthermore, remote unit 102 may be referred to as a subscriber unit, mobile device, mobile station, user, terminal, mobile terminal, fixed terminal, subscriber station, UE, user terminal, device, or other terms used in the art. Remote unit 102 may communicate directly with one or more network units 104 via UL communication signals. In some embodiments, remote unit 102 may communicate directly with other remote units 102 via sidelink communication.

[0037] Network unit 104 may be distributed across a geographical area. In some embodiments, network unit 104 may also be referred to as and / or may include access point, access terminal, base station, base station, core network (“CN”), radio network entity, node-B, evolved node-B (“eNB”), 5G node-B (“gNB”), home node-B, relay node, device, core network, air server, radio access node, access point (“AP”), new radio (“NR”), network entity, access and mobility management function (“AMF”), unified data management (“UDM”), unified data repository (“UDR”), UDM / UDR, policy control function (“PCF”), radio access network (“RAN”), network slice selection function (“NSSF”), operation, administration and management (“OAM”), session management function (“SMF”), user plane function (“UPF”), application function, authentication server function (“AUSF”), security anchor functionality (“SEAF”), trusted non-3GPP gateway function (“TNGF”), or any other term used in the art. Network unit 104 is typically part of a radio access network that includes one or more controllers communicatively coupled to one or more corresponding network units 104. The radio access network is typically communicatively coupled to one or more core networks, which may be coupled to other networks such as the Internet and the public switched telephone network. These and other elements of the radio access and core networks are not illustrated, but are generally well known to those skilled in the art.

[0038] In one implementation, the wireless communication system 100 conforms to the NR protocol standardized in the 3rd Generation Partnership Project (“3GPP”), wherein network unit 104 transmits using an OFDM modulation scheme on the downlink (“DL”), and remote unit 102 transmits using a single-carrier frequency division multiple access (“SC-FDMA”) scheme or an orthogonal frequency division multiplexing (“OFDM”) scheme on the uplink (“UL”). However, more generally, the wireless communication system 100 may implement other open or proprietary communication protocols, such as WiMAX, IEEE 802.11 variants, GSM, GPRS, UMTS, LTE variants, and CDMA2000. Protocols such as ZigBee and Sigfoxx. This disclosure is not intended to be limited to any particular wireless communication system architecture or protocol implementation.

[0039] Network unit 104 can serve multiple remote units 102 within a service area, such as a cell or cell sector, via a wireless communication link. Network unit 104 transmits DL communication signals to serve the remote units 102 in the time, frequency, and / or spatial domains.

[0040] In various embodiments, network unit 104 can determine channel occupancy time sharing for at least one user equipment. In some embodiments, network unit 104 can transmit information indicating channel occupancy time sharing to at least one user equipment. This channel occupancy time sharing indicates sharing information for at least one uplink communication, at least one sidelink communication, or a combination thereof. In some embodiments, network unit 104 can receive at least one uplink communication, at least one sidelink communication, or a combination thereof based on channel occupancy time sharing. Therefore, network unit 104 can be used for channel occupancy time sharing.

[0041] In some embodiments, remote unit 102 (e.g., user equipment) can perform a listen-before-speak process. In some embodiments, remote unit 102 can initiate channel occupancy time sharing for the user equipment based on the listen-before-speak process. This channel occupancy time sharing indicates shared information to be transmitted from the user equipment for at least one uplink communication, at least one sidelink communication, or a combination thereof. In various embodiments, remote unit 102 can transmit at least one uplink communication, at least one sidelink communication, or a combination thereof based on channel occupancy time sharing. Therefore, remote unit 102 can be used for channel occupancy time sharing.

[0042] Figure 2An embodiment of an apparatus 200 that can be used for channel occupancy time sharing is depicted. Apparatus 200 includes one embodiment of a 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 some 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, memory 204, transmitter 210, and receiver 212, and may not include the input device 206 and / or display 208.

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

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

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

[0046] In one embodiment, display 208 may include any known electronically controllable display or display device. Display 208 may be designed to output visual, auditory, and / or tactile signals. In some embodiments, display 208 includes an electronic display capable of outputting visual data to a user. For example, 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 devices capable of outputting images, text, etc., to a user. As another non-limiting example, display 208 may include wearable displays such as smartwatches, smart glasses, head-up displays, etc. Furthermore, display 208 may be a component of a smartphone, personal digital assistant, television, desktop computer, laptop computer, personal computer, vehicle dashboard, etc.

[0047] In some embodiments, display 208 includes one or more speakers for generating sound. For example, display 208 may generate an audible alarm or notification (e.g., a buzzer or beep). In some embodiments, display 208 includes one or more haptic devices for generating vibration, motion, or other haptic feedback. In some embodiments, all or part of display 208 may be integrated with input device 206. For example, input device 206 and display 208 may form a touchscreen or similar touch-sensitive display. In other embodiments, display 208 may be located near input device 206.

[0048] Processor 202 can execute a listen-before-speak process and initiate channel occupancy time sharing for the user equipment based on the listen-before-speak process. This channel occupancy time sharing indicates shared information to be transmitted from the user equipment for at least one uplink communication, at least one sidelink communication, or a combination thereof. In various embodiments, transmitter 210 can transmit at least one uplink communication, at least one sidelink communication, or a combination thereof based on channel occupancy time sharing.

[0049] 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 transmitters 210 and receivers 212 may be of any suitable type. In one embodiment, the transmitters 210 and receivers 212 may be part of a transceiver.

[0050] Figure 3 An embodiment of an apparatus 300 that can be used for channel occupancy time sharing is depicted. Apparatus 300 includes one embodiment of a network unit 104. Furthermore, 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. It will be understood that the processor 302, memory 304, input device 306, display 308, transmitter 310, and receiver 312 may be substantially similar to the processor 202, memory 204, input device 206, display 208, transmitter 210, and receiver 212 of remote unit 102, respectively.

[0051] Processor 302 can determine channel occupancy time sharing for at least one user equipment. In various embodiments, transmitter 310 can transmit information indicating channel occupancy time sharing to at least one user equipment. This channel occupancy time sharing indicates sharing information for at least one uplink communication, at least one sidelink communication, or a combination thereof. In various embodiments, receiver 312 can receive at least one uplink communication, at least one sidelink communication, or a combination thereof based on channel occupancy time sharing.

[0052] In some embodiments, transmitter 310 may transmit the information described herein and / or receiver 312 may transmit the information described herein and / or processor 302 may process the information described herein.

[0053] In some embodiments, sidelink (“SL”) operation may be situated in unlicensed and / or licensed shared access spectrum used for Industrial Internet of Things (“IIoT”) and where channel access technologies may be based on frame-based devices (“FBE”) or load-based devices (“LBE”) in commercial use. In some embodiments, SL operation may be limited to licensed bands and intelligent transmission spectrum (“ITS”) bands. In various embodiments, clear channel assessment (e.g., Type 1 channel access procedure (also known as LBTCat.4)) and short listen-before-speak (“LBT”) (e.g., Lbt Cat.4), and / or channel occupancy time (“COT”) sharing may be used.

[0054] In some embodiments, unauthorized and / or authorized sidelink shared access operations may be used with COT sharing via a new Radio User Equipment to Network interface (“NR-UU”) and a new Radio User Equipment to User Equipment interface (“NR-PC5”). In various embodiments, COT sharing may be used between downlink (“DL”), uplink (“UL”), SL, and / or SL Ue.

[0055] As used herein, the terms eNB and / or gNB can be used for a base station, but such terms can be replaced by any other radio access node (e.g., base station (“BS”), eNB, gNB, AP, NR, etc.). Furthermore, the various embodiments described herein can be described in relation to a type of mobile communication system (e.g., fifth-generation (“5G”) new radio (“NR”); however, any embodiments described herein can be applied to other mobile communication systems (e.g., systems that support serving cells and / or carriers configured for sidelink communication via a PC5 interface).

[0056] In some embodiments, aspects of COT sharing can be initiated by the gNB, UE, and / or SL-UE for SL transmission.

[0057] In a first embodiment, gNB-COT sharing with other UEs may exist for performing uplink and / or sidelink transmissions. In a first embodiment, if a gNB performs LBT (e.g., according to Cat.4 (Clear Channel Assessment (“CCA”)) and acquires a channel for downlink transmissions, the gNB may initiate COT sharing with the UE for transmissions to perform uplink and / or sidelink transmissions.

[0058] In some embodiments, such as DL-COT sharing between UL and / or SL: after the gNB performs LBT (e.g., according to Cat.4 (CCA) procedures), the gNB can initiate COT sharing for SL and / or UL by transmitting an indicator field in an NR downlink control information (“DCI”) format that is separate for both UL and SL for sharing the gNB-initiated COT, or in an NR DCI format that provides COT sharing interface information. In such embodiments, the interface information may include information indicating an uplink, a sidelink, or both uplink and sidelink.

[0059] In various embodiments, such as for DL-COT sharing between UL and / or SL, information fields in NR-DCI format 2_0 can be used, which provide COT sharing information to provide information related to SL transmission, such as: a COT sharing interface indicator for sharing COT with SL and / or UL, a slot timing offset, a symbol timing offset for initiating SL transmission during the remaining channel occupancy (“CO”) duration, the SL-CO duration in the remaining CO, the channel access priority level (e.g., the maximum COT (“MCOT”) duration), the total remaining CO duration, and / or the SL LBT type to be performed by the SL UE before SL transmission. In such embodiments, UL transmission information may include: UL-CO duration, slot timing offset, symbol timing offset, and / or the UL LBT type to be performed. Moreover, in such embodiments, the applied slot or symbol timing offset may be relative to the end of the slot or symbol in which the corresponding NR-DCI format 2_0 is detected.

[0060] In some embodiments, such as for DL-COT sharing between UL and / or SL, different NR DCI formats can be used to indicate COT sharing initiated by gNB for UL and / or SL respectively, using additional information fields as described herein.

[0061] In some embodiments, such as for DL-COT sharing between UL and / or SL, the gNB transmits a set of common NR DCIs or unicast DCIs for sharing the gNB-initiated COT. In such embodiments, the UE can be notified about sharing the gNB COT with UL and / or SL via the unicast DCI format used for gNB COT sharing, and this can be determined by the UE's ability to perform both UL and SL simultaneously, or otherwise it can depend on a slot format indicator ("SFI") to perform UL and SL transmissions in UL and SL slots. If no SFI information is available, COT sharing may depend on the indicated SL CO duration or UL CO duration. Furthermore, in such embodiments, the UE can be notified about sharing the gNB COT with UL and / or SL via a set of common DCIs used for gNB COT sharing. In such embodiments, an indicator specifying a destination group identifier ("ID") can be used in the DCI field, or the information can be scrambled by the destination group ID, where the gNB COT is shared only with a specific destination group in the SL.

[0062] In various embodiments, such as for DL-COT sharing between UL and / or SL, Cat2 (e.g., short LBT) can be performed if SL and / or UL transmissions are performed during the remaining CO duration.

[0063] In some embodiments, such as for DL-COT sharing between UL and / or SL, the sidelink UE can transmit control channels, data channels, or any broadcast channels during the remaining CO duration.

[0064] In some embodiments, such as for DL-COT sharing between UL and / or SL, the sidelink UE may not share gNB-COT with other sidelink UEs (e.g., the sidelink UE that is the recipient of COT sharing may not further indicate that it shares the same COT with the other sidelink UE).

[0065] Figure 4 Figure 400 is a schematic block diagram 400 illustrating an embodiment of COT sharing initiated by a gNB with UL and / or SL. Figure 400 illustrates a system including a gNB 402, a first UE 404, and a second UE 406. The gNB 402 transmits a DL-initiated COT share 408 for UL communication 410 and SL communication 412. The DL-initiated COT share 408 may include a gNB-COT format 414, which includes a DL transmission 416, a first UL transmission 418, a first SL transmission 420, a second SL transmission 422, and a second UL transmission 424.

[0066] In some embodiments, gNB-scheduled SL transmissions can exist on a COT share initiated by the gNB. In such embodiments, after the gNB performs an LBT Cat 4 (e.g., CCA) procedure, the gNB can initiate a COT share for SL transmission during the remaining CO duration using an NR-DCI containing an SL grant along with a COT share indicator. Furthermore, in such embodiments, NR-SL-DCI format 3_0 provides a grant for SL transmission and can indicate: information regarding slot timing offsets or symbol timing offsets for initiating SL transmission during the remaining CO duration, the SL-CO share duration in the remaining CO, the channel access priority level (e.g., MCOT duration), the total remaining CO duration, and / or the SL LBT type to be performed by the SL UE before SL transmission. In such embodiments, if a corresponding DCI format 2_0 is detected, the slot or symbol timing offset can be applied relative to the end of the slot or symbol. Furthermore, in such embodiments, the gNB can schedule an NR DCI with an SL grant without any COT share indicator, and the SL UE can perform an LBT Cat-4 CCA and acquire a channel for SL transmission.

[0067] In some embodiments, there may be autonomous resource selection for COT sharing initiated by the gNB. In such an embodiment, after the gNB performs the LBT Cat 4 (CCA) procedure, the gNB may use NR-DCI to initiate COT sharing for SL transport during the remaining CO duration, where the SL UE may perform autonomous SL transport using configured licensed resources, or the SL UE may perform transport based on random resource selection.

[0068] In various embodiments, an information field can be used in NR-DCI format 2_0, which provides COT sharing information to provide information related to SL transmission, such as: a COT indicator to share COT with SL and / or UL, a slot timing offset, a symbol timing offset for initiating SL transmission in the remaining CO duration, the SL-CO sharing duration in the remaining CO, the channel access priority level (e.g., MCOT duration), the total remaining CO duration, and / or the SL LBT type to be performed by the SL UE before SL transmission. In such embodiments, a slot or symbol timing offset can be applied relative to the detected end of a slot or symbol corresponding to NR-DCI format 2_0.

[0069] In some embodiments, different NR DCI formats can be used to individually indicate COT sharing initiated by gNB for UL and / or SL.

[0070] In some embodiments, if the gNB transmits COT sharing information and / or its duration in the DCI for sidelink purposes but there is no associated SL license, the UE may use the configured license and / or use random resource selection to perform autonomous SL transmissions.

[0071] In various embodiments, if the gNB grants the UE an SL license but does not provide information about COT sharing for the SL, or if there is not enough remaining COT duration for the SL transmission until the sidelink slots and / or symbol configuration in the SFI begin, the SL UE may initiate a Cat 4LBT for the SL transmission, or may perform both UL and SL transmissions simultaneously.

[0072] In some embodiments, if the gNB transmits a COT sharing indicator, the UE may transmit SL in a UL slot or symbol depending on the NR SL-UL priority rule, or may perform simultaneous UL and SL transmissions.

[0073] Some of the embodiments described herein can be applied to other embodiments related to COT sharing initiated by a UE and / or COT sharing and relay COT sharing initiated by an SL UE with other SL UEs, if a SL UE can also grant permission to another SL UE.

[0074] In the second embodiment, a UE-initiated COT sharing - UL & SL can exist. Furthermore, in the second embodiment, the UE only performs one LBT procedure, which can be either UL or SL. Additionally, the UE initiates channel occupancy sharing with the gNB and / or other SL UEs (e.g., the same RAT and / or different RATs).

[0075] In various embodiments, sharing of channel occupancy initiated by a UE with a gNB and / or another SL UE can be supported, allowing the UE to initiate sharing of COT with the gNB and / or another link UE simultaneously or in different time slots (e.g., via SFI values), depending on whether the UE supports simultaneous UL and SL transmissions.

[0076] In some embodiments, the UE may use Level 1 Side Link Control Information (“SCI”), Level 2 SCI, or a combination of both to indicate: a UE COT sharing indicator to the SL UE, a slot timing offset, a symbol timing offset for initiating SL transmission, the SL-CO duration in the remaining CO, a channel access priority level (e.g., MCOT duration), the remaining CO duration, the SL LBT type, and a destination group ID or destination ID. In such embodiments, the SCI format may be broadcast, multicast, or unicast, depending on whether the UE wants to share the COT with the SL UE on a one-to-one or one-to-many basis.

[0077] In some embodiments, for UL-DL-SL: the UE may transmit configured licensed (“CG”) uplink control information (“UCI”) (“CG-UCI”) at the end of UL CO to share the UE-initiated COT with the gNB, wherein the CG-UCI may include the DL CO sharing duration in the remaining CO duration of the UE-initiated COT, and may simultaneously transmit SCI in the SL to share the UE-initiated COT with other SL UEs, wherein the SCI includes a COT sharing indicator and SL timing offset, a row in a table, a table ID notifying the start of SL transmission, and / or the SL CO sharing duration in the remaining CO duration of the UE-initiated COT.

[0078] In various embodiments, if the SCI is not transmitted because UL-SL cannot be transmitted simultaneously, the UE may not share the UE-initiated COT with other UEs.

[0079] In some embodiments, for UL-SL-DL: the UE can transmit the SL-CO duration in CG-UCI or at the end of SL transmission, allowing the gNB to start DL transmission immediately after SL channel occupancy is complete.

[0080] In some embodiments, for SL-DL-UL: the UE may transmit information in CG-UCI about the duration of DL CO sharing, as well as the start of the DL transmission timing offset, table index, and / or row number.

[0081] In various embodiments, for SL-UL-DL: at the end of UL CO, the UE-initiated COT can be shared with a gNB and the CG UCI can include the DL CO shared duration, which can be the remaining CO duration.

[0082] In some embodiments, the UE performs multiple LBTs for UL and / or SL transmissions synchronously (e.g., in parallel, concurrently) or in a time-domain manner (e.g., sequentially) on a set of panels and / or beams. In such embodiments, the sharing of channel occupancy initiated by the UE can be limited only within the interface, panel, and / or beam initiating the LBT.

[0083] Figure 5 Figure 500 is a schematic block diagram 500 illustrating an embodiment of UE-initiated COT sharing with a gNB and other SL UEs. Figure 500 illustrates a system including a gNB 502, a first UE 504 (UE A), and a second UE 506 (UE B). The first UE 504 transmits UL-initiated COT sharing 508 for DL ​​communication 510 and SL communication 512 and 514. UL-initiated COT sharing 508 may include UE-COT format 516, which includes UL transmission 518, SL-UE A to SL-UE B transmission 520, SL-UE B to SL-UE A transmission 522, and DL transmission 524.

[0084] In the third embodiment, UE-to-UE COT sharing and / or SL COT sharing may exist. In the third embodiment, UE A may perform LBT Cat.4 (CCA) and may acquire a channel for sidelink transmission. In such an embodiment, UE A may initiate SL COT sharing with other SL UEs (e.g., UE B) for performing sidelink transmission and the SCI indicates a COT sharing indicator and / or includes explicit restrictions for SL transmissions within the SL UE.

[0085] In some embodiments, an indicator may be used in the first or second level of specifying SL transmission restrictions between SL UEs. In one example, a UE may transmit a Physical Side Link Feedback Channel (“PSFCH”) only to the UE that initiated the channel occupancy during the remaining CO duration. And in another example, a UE may transmit a Physical Side Link Control Channel (“PSCCH”) and / or a Physical Side Link Shared Channel (“PSSCH”) only to the UE that initiated the channel occupancy during the remaining CO duration.

[0086] In various embodiments, if the limit indicator is absent and / or zero, SL transmissions can be carried out with all SL UEs that are part of the destination group ID and / or destination ID. In one example, UE A can transmit PSFCH feedback (e.g., PSCCH originating from the destination group ID and / or destination ID specified in the SCI) to all SL UEs that are part of the destination group ID during the remaining CO duration, provided that the feedback includes transmissions to the UE that initiated the channel occupancy. In another example, UE A can transmit PSSCH transmissions to all SL UEs that are part of the destination group ID during the remaining CO duration, provided that the transmission includes transmissions to the SL UE that initiated the channel occupancy.

[0087] In some embodiments, UE A may use a first-level SCI, a second-level SCI, or a combination of both to indicate: a COT sharing indicator to other SL UEs, a timeslot timing offset, a symbol timing offset for initiating SL transmission, and / or a row in a table and / or a table ID indicating the start of SL transmission and / or the remaining CO duration of the SL CO sharing duration for the UE-initiated COT for each SL UE, a channel access priority level (e.g., MCOT duration), the remaining CO duration, the SL LBT type, the destination group ID, and / or the destination ID. In such embodiments, the SCI format may be broadcast, multicast, or unicast, depending on whether the UE wants to share the COT one-to-one or one-to-multiple SL UEs. The transmission of the COT sharing indicator in the SCI may be x timeslots prior to the start of the SL transmission (e.g., considering UE processing time requirements).

[0088] In some embodiments, if a UE transmits COT sharing and / or its duration in an SCI for sidelink purposes, but no associated SL license exists, the UE may use the configured license, random resource selection, or a combination thereof to transmit.

[0089] In various embodiments, if the UE receives a COT sharing indicator but does not receive the associated permission, the UE may transmit a scheduling resource (“SR”) to the gNB for the remaining CO duration or may initiate a new COT for transmitting the SR.

[0090] In some embodiments, the UE initiating COT sharing may provide SL permission and COT sharing indicator for other UE transmissions (e.g., UE B to UE A, UE C to UE A, UE D to UE A) in the same SCI, in a separate SCI, or in a second-level SCI.

[0091] Figure 6Figure 600 is a schematic block diagram 600 illustrating an embodiment of COT sharing initiated by an SL UE. Figure 600 illustrates a system including a first UE 602 (UE A), a second UE 604 (UE B), a third UE 606 (UE C), and a fourth UE 608 (UE D). The first UE 602 transmits a COT sharing 610 initiated by the SL UE with the second UE 604, the third UE 606, and the fourth UE 608. The COT sharing 610 initiated by the SL UE may include a transmission 612 from SL UE A to SL UE B, a transmission 614 from SL UE B to SL UE A, a transmission 616 from SL UE C to SL UE A, and a transmission 618 from SL UE D to SL UE A.

[0092] In the fourth embodiment, SL COT sharing can be performed in a relay environment. In the fourth embodiment, UE A performs LBT Cat.4 (CCA) to obtain a channel for sidelink transmission, and if the SCI indicates a COT sharing indicator and / or includes explicit restrictions on the use of COT sharing by UE A, UE A can initiate SL COT sharing with other SL UEs to perform sidelink transmission, wherein the hop count, the depth of the sharing hierarchy, and / or nested COT sharing can be restricted and specified as part of the COT sharing indicator.

[0093] In some embodiments, the SCI includes information fields (e.g., a first SCI, a second SCI, or a combination of both) in addition to the SL COT sharing indicator and timing offset. The information fields can provide information related to nested COT sharing and the number of devices used for nested COT sharing (e.g., such as...). Figure 7 (As shown).

[0094] Figure 7 Figure 700 is a schematic block diagram 700 illustrating an embodiment of SL COT sharing in a relay environment. Figure 700 illustrates a system including a first UE 702 (UE A), a second UE 704 (UE B), a third UE 706 (UE C), and a fourth UE 708 (UE D). The first UE 702 transmits a COT sharing 710 initiated by the SL UE with the second UE 704, the third UE 706, and the fourth UE 708. The SL UE-initiated COT sharing 710 may include a transmission 712 from SL UE A to SL UE B, a transmission 714 from SL UE B to SL UE C, a transmission 716 from SL UE C to SL UE D, and a transmission 718 from SL UE D to SL UE A.

[0095] In various embodiments, if nested sharing is disabled: UE A shares COT with UE B, allowing UE B to transmit to both UE A and UE C, but UE B is not allowed to share the same and / or remaining COT duration initiated by UE A and UE C, allowing UE C to transmit to any UE in the group.

[0096] In some embodiments, if nested sharing is enabled (e.g., allowed): UE A shares COT with UE B, allowing UE B to transmit to UE A, and UE C and UE B are allowed to share the same and / or remaining COT duration initiated further by UE A with UE C, allowing UE C to transmit to any UE in the group. All UEs can perform Cat 2 (short LBT) before any SL transmission.

[0097] Figure 8 This is a flowchart illustrating one embodiment of a method 800 for sharing channel occupancy time. In some embodiments, method 800 is performed by a device such as network unit 104. In some embodiments, method 800 may be performed by a processor that executes program code, such as a microcontroller, microprocessor, CPU, GPU, auxiliary processing unit, FPGA, etc.

[0098] In various embodiments, method 800 includes determining 802 channel occupancy time sharing for at least one user equipment. In some embodiments, method 800 includes transmitting information 804 indicating channel occupancy time sharing to at least one user equipment. This channel occupancy time sharing indicates sharing information for at least one uplink communication, at least one sidelink communication, or a combination thereof. In some embodiments, method 800 includes receiving 806 at least one uplink communication, at least one sidelink communication, or a combination thereof based on channel occupancy time sharing.

[0099] In some embodiments, the information indicating channel occupancy time sharing includes a downlink control information format transmit interface field that indicates channel occupancy time sharing for at least one uplink communication, at least one sidelink communication, or a combination thereof. In some embodiments, the downlink control information format further includes the duration of channel occupancy time sharing for at least one uplink communication, at least one sidelink communication, or a combination thereof. In various embodiments, the downlink control information format includes a unicast downlink control information format to indicate channel occupancy time sharing for at least one uplink communication, at least one sidelink communication, or a combination thereof.

[0100] In one embodiment, the sidelink grant in the downlink control information format includes a destination identifier indicating at least one user equipment (UE) to use channel occupancy time sharing. In some embodiments, the sidelink grant in the downlink control information initiates channel occupancy time sharing and transmits the duration for the channel occupancy time sharing. In some embodiments, the sidelink grant in the downlink control information includes a field to notify a receiver of channel occupancy time sharing information, indicating further sharing of the same channel occupancy time with another UE performing sidelink communication. In various embodiments, at least one UE autonomously performs sidelink transmissions based on channel occupancy time sharing and duration.

[0101] Figure 9 This is a flowchart illustrating one embodiment of a method 900 for sharing channel occupancy time. In some embodiments, method 900 is performed by a device such as remote unit 102. In some embodiments, method 900 may be performed by a processor that executes program code, such as a microcontroller, microprocessor, CPU, GPU, auxiliary processing unit, FPGA, etc.

[0102] In various embodiments, method 900 includes performing a 902 listen-before-speak procedure. In some embodiments, method 900 includes initiating a 904 channel occupancy time sharing for the user equipment based on the listen-before-speak procedure. This channel occupancy time sharing indicates shared information to be transmitted from the user equipment for at least one uplink communication, at least one sidelink communication, or a combination thereof. In some embodiments, method 900 includes transmitting a 906 at least one uplink communication, at least one sidelink communication, or a combination thereof based on the channel occupancy time sharing.

[0103] In some embodiments, method 900 further includes transmitting first-level sidelink control information, second-level sidelink control information, or combinations thereof, indicating a channel occupancy time sharing indicator, remaining duration, channel access priority level, or a combination thereof. In some embodiments, the first-level sidelink control information, second-level sidelink control information, or combinations thereof are transmitted using broadcast, multicast, or unicast transmission. In various embodiments, the first-level sidelink control information, second-level sidelink control information, or combinations thereof include indicators indicating user equipment that is restricted from using channel occupancy time sharing.

[0104] In one embodiment, channel occupancy time sharing is applied to user equipment that shares a destination group identifier, a destination identifier, or a combination thereof. In some embodiments, the sharing information includes information indicating whether nested channel occupancy time sharing is enabled. In some embodiments, first-level sidelink control information, second-level sidelink control information, or a combination thereof indicates the number of nested channel occupancy time sharing devices.

[0105] In various embodiments, method 900 further includes transmitting physical sidelink control channel transmissions, physical sidelink shared channel transmissions, or combinations thereof only to the device initiating channel occupancy sharing during the remaining channel occupancy. In one embodiment, the method further includes transmitting physical sidelink control channel transmissions, physical sidelink shared channel transmissions, or combinations thereof to any device within the destination identifier during the remaining channel occupancy.

[0106] In one embodiment, a method includes: determining channel occupancy time sharing for at least one user equipment; transmitting information indicating channel occupancy time sharing to at least one user equipment, wherein the channel occupancy time sharing indicates sharing information for at least one uplink communication, at least one sidelink communication, or a combination thereof; and receiving at least one uplink communication, at least one sidelink communication, or a combination thereof based on the channel occupancy time sharing.

[0107] In some embodiments, the transmit indication channel occupancy time sharing information includes a transmit interface field in the following downlink control information format, the interface field indicating channel occupancy time sharing for at least one uplink communication, at least one sidelink communication, or a combination thereof.

[0108] In some embodiments, the downlink control information format further includes the duration for sharing channel occupancy time for at least one uplink communication, at least one sidelink communication, or a combination thereof.

[0109] In various embodiments, the downlink control information format includes a unicast downlink control information format to indicate channel occupancy time sharing for at least one uplink communication, at least one sidelink communication, or a combination thereof.

[0110] In one embodiment, the sidelink license in the downlink control information format includes a destination identifier that indicates at least one user equipment to use the channel occupancy time sharing.

[0111] In some embodiments, the sidelink permission in the downlink control information initiates channel occupancy time sharing and transmits the duration for channel occupancy time sharing.

[0112] In some embodiments, the sidelink permission in the downlink control information includes a field to notify the receiver of channel occupancy time sharing information, indicating that the same channel occupancy time may be further shared with another user equipment performing sidelink communication.

[0113] In various embodiments, at least one user equipment autonomously performs sidelink transmissions based on channel occupancy time sharing and duration.

[0114] In one embodiment, an apparatus includes: a processor that determines channel occupancy time sharing for at least one user equipment; a transmitter that transmits information indicating channel occupancy time sharing to at least one user equipment, wherein the channel occupancy time sharing indicates sharing information for at least one uplink communication, at least one sidelink communication, or a combination thereof; and a receiver that receives at least one uplink communication, at least one sidelink communication, or a combination thereof based on the channel occupancy time sharing.

[0115] In some embodiments, the transmit indication channel occupancy time sharing information includes a transmit interface field in the following downlink control information format, the interface field indicating channel occupancy time sharing for at least one uplink communication, at least one sidelink communication, or a combination thereof.

[0116] In some embodiments, the downlink control information format further includes the duration for sharing channel occupancy time for at least one uplink communication, at least one sidelink communication, or a combination thereof.

[0117] In various embodiments, the downlink control information format includes a unicast downlink control information format to indicate channel occupancy time sharing for at least one uplink communication, at least one sidelink communication, or a combination thereof.

[0118] In one embodiment, the sidelink license in the downlink control information format includes a destination identifier that indicates at least one user equipment to use the channel occupancy time sharing.

[0119] In some embodiments, the sidelink permission in the downlink control information initiates channel occupancy time sharing and transmits the duration for channel occupancy time sharing.

[0120] In some embodiments, the sidelink permission in the downlink control information includes a field to notify the receiver of channel occupancy time sharing information, indicating that the same channel occupancy time may be further shared with another user equipment performing sidelink communication.

[0121] In various embodiments, at least one user equipment autonomously performs sidelink transmissions based on channel occupancy time sharing and duration.

[0122] In one embodiment, a method includes: performing a listen-before-speak procedure at a user equipment; initiating a channel occupancy time sharing (COTS) for the user equipment based on the listen-before-speak procedure at the user equipment, wherein the COTS indicates shared information to be transmitted from the user equipment for at least one uplink communication, at least one sidelink communication, or a combination thereof; and transmitting at least one uplink communication, at least one sidelink communication, or a combination thereof from the user equipment based on the COTS.

[0123] In some embodiments, the method further includes transmitting a first-level sidelink control information, a second-level sidelink control information, or a combination thereof, indicating a channel occupancy time sharing indicator, remaining duration, channel access priority level, or a combination thereof, or a channel occupancy time sharing indicator, remaining duration, channel access priority level, or a combination thereof.

[0124] In some embodiments, broadcast transmission, multicast transmission, or unicast transmission is used to transmit first-level sidelink control information, second-level sidelink control information, or a combination thereof.

[0125] In various embodiments, the first-level sidelink control information, the second-level sidelink control information, or a combination thereof, includes an indicator that restricts user equipment from using channel occupancy time sharing.

[0126] In one embodiment, channel occupancy time sharing is applied to user equipment that shares a destination group identifier, a destination identifier, or a combination thereof.

[0127] In some embodiments, the shared information includes information indicating whether nested channel occupancy time sharing is enabled.

[0128] In some embodiments, first-level sidelink control information, second-level sidelink control information, or a combination thereof, indicate the number of nested channel occupancy time sharing devices.

[0129] In various embodiments, the method further includes transmitting physical side link control channel transmissions, physical side link sharing channel transmissions, or combinations thereof only to the device initiating the channel occupancy sharing during the remaining channel occupancy.

[0130] In one embodiment, the method further includes transmitting physical side link control channel transmission, physical side link shared channel transmission, or a combination thereof to any device within the destination identifier during the remaining channel occupancy.

[0131] In one embodiment, an apparatus including a user equipment further includes: a processor that: performs a listen-before-speak process; and initiates a channel occupancy time sharing for the user equipment based on the listen-before-speak process, wherein the channel occupancy time sharing indicates shared information to be transmitted from the user equipment for at least one uplink communication, at least one sidelink communication, or a combination thereof; and a transmitter that transmits at least one uplink communication, at least one sidelink communication, or a combination thereof based on the channel occupancy time sharing.

[0132] In some embodiments, the transmitter transmits a channel occupancy time sharing indicator, remaining duration, channel access priority level, or a combination thereof, first-level sidelink control information, second-level sidelink control information, or a combination thereof.

[0133] In some embodiments, broadcast transmission, multicast transmission, or unicast transmission is used to transmit first-level sidelink control information, second-level sidelink control information, or a combination thereof.

[0134] In various embodiments, the first-level sidelink control information, the second-level sidelink control information, or a combination thereof, includes an indicator that restricts user equipment from using channel occupancy time sharing.

[0135] In one embodiment, channel occupancy time sharing is applied to user equipment that shares a destination group identifier, a destination identifier, or a combination thereof.

[0136] In some embodiments, the shared information includes information indicating whether nested channel occupancy time sharing is enabled.

[0137] In some embodiments, first-level sidelink control information, second-level sidelink control information, or a combination thereof, indicate the number of nested channel occupancy time sharing devices.

[0138] In various embodiments, the transmitter transmits physical side link control channel transmissions, physical side link sharing channel transmissions, or combinations thereof to the device that initiated the channel occupancy sharing during the remaining channel occupancy.

[0139] In one embodiment, the transmitter transmits physical side link control channel transmission, physical side link shared channel transmission, or a combination thereof to any device within the destination identifier during the remaining channel occupancy.

[0140] The embodiments may be practiced in other specific forms. The described embodiments are to be regarded in all respects as illustrative rather than restrictive. Therefore, the scope of the invention is indicated by the appended claims rather than the foregoing description. All variations within the meaning and equivalents of the claims are included within their scope.

Claims

1. A method executed by a network unit, comprising: Determine channel occupancy time sharing for at least one user equipment; Transmit information indicating channel occupancy time sharing to the at least one user equipment, wherein the channel occupancy time sharing indicates sharing information for at least one sidelink communication or a combination of at least one uplink communication and the at least one sidelink communication; as well as Based on the channel occupancy time sharing, the at least one sidelink communication or a combination of the at least one uplink communication and the at least one sidelink communication is received. The information indicating channel occupancy time sharing includes a transmit interface field in the following downlink control information format, wherein the interface field indicates the channel occupancy time sharing for the at least one sidelink communication, or a combination of the at least one uplink communication and the at least one sidelink communication. Specifically, the downlink control information includes a sidelink permission to initiate the channel occupancy time sharing and to transmit the duration of the channel occupancy time sharing.

2. The method according to claim 1, wherein, The downlink control information format further includes the duration of the channel occupancy time sharing for the at least one sidelink communication or the combination of the at least one uplink communication and the at least one sidelink communication.

3. The method according to claim 1, wherein, The downlink control information format includes a unicast downlink control information format to indicate the channel occupancy time sharing for the at least one sidelink communication or the combination of the at least one uplink communication and the at least one sidelink communication.

4. The method according to claim 1, wherein, The sidelink permission in the downlink control information format includes a destination identifier that indicates the at least one user equipment to use the channel occupancy time sharing.

5. The method according to claim 1, wherein, The sidelink permission in the downlink control information includes a field to notify the receiver of channel occupancy time sharing information, indicating that the same channel occupancy time will be further shared with another user equipment performing sidelink communication.

6. The method according to claim 1, wherein, The at least one user equipment autonomously performs sidelink transmission based on the channel occupancy time sharing and duration.

7. An apparatus including a network unit, the apparatus further comprising: A processor that determines channel occupancy time sharing for at least one user equipment; A transmitter that transmits information to the at least one user equipment indicating channel occupancy time sharing, wherein the channel occupancy time sharing indicates sharing information for at least one sidelink communication, or a combination of at least one uplink communication and the at least one sidelink communication; as well as The receiver receives the at least one sidelink communication or a combination of the at least one uplink communication and the at least one sidelink communication based on the channel occupancy time sharing. The transmitter transmits information indicating channel occupancy time sharing, which includes a transmit interface field in the following downlink control information format. This interface field indicates the channel occupancy time sharing used for the at least one sidelink communication, or a combination of the at least one uplink communication and the at least one sidelink communication. Specifically, the downlink control information includes a sidelink permission to initiate the channel occupancy time sharing and to transmit the duration of the channel occupancy time sharing.

8. A method performed by a user equipment, comprising: Perform the "listen first, speak later" process at the user's equipment. At the user equipment, a channel occupancy time sharing is initiated for the user equipment based on the listen-before-speak process, wherein the channel occupancy time sharing indicates shared information to be transmitted from the user equipment for at least one sidelink communication, or a combination of at least one uplink communication and the at least one sidelink communication; as well as Based on the channel occupancy time sharing, the user equipment transmits the at least one sidelink communication or a combination of the at least one uplink communication and the at least one sidelink communication. Transmit sidelink control information (SCI), the SCI indicating a table identifier that indicates the start of a sidelink transmission associated with the channel occupancy time sharing. Further includes, transmit indication channel occupancy time sharing indicator, remaining duration, channel access priority level, or a combination thereof, first-level sidelink control information, second-level sidelink control information, or a combination thereof.

9. The method according to claim 8, wherein, The first-level sidelink control information, the second-level sidelink control information, or a combination thereof are transmitted using broadcast, multicast, or unicast transmission.

10. The method according to claim 8, wherein, The first-level sidelink control information, the second-level sidelink control information, or a combination thereof, includes an indicator that restricts user equipment from using the channel occupancy time sharing.

11. The method according to claim 8, wherein, The channel occupancy time sharing applies to user equipment that shares a destination group identifier, a destination identifier, or a combination thereof.

12. The method according to claim 8, wherein, The shared information includes information indicating whether nested channel occupancy time sharing is enabled, such that nested channel occupancy time sharing devices that share COT with the user equipment are allowed to share the same and / or remaining COT duration as another nested channel occupancy time sharing device.

13. The method according to claim 12, wherein, The first-level sidelink control information, the second-level sidelink control information, or a combination thereof indicate the number of nested channel occupancy time sharing devices.

14. The method of claim 8, further comprising, during the remaining channel occupancy, transmitting only physical side link control channel transmission, physical side link sharing channel transmission, or a combination thereof to the device that initiated the channel occupancy sharing.

15. The method of claim 8, further comprising, during the remaining channel occupancy, transmitting a physical side-link control channel transmission, a physical side-link shared channel transmission, or a combination thereof to any device within the destination identifier.

16. An apparatus including a user equipment, the apparatus further comprising: Processor, the processor: Perform the process of listening first and then speaking; as well as Based on the aforementioned listen-before-speak process, the user equipment initiates channel occupancy time sharing, wherein the channel occupancy time sharing indicates shared information to be transmitted from the user equipment for at least one sidelink communication, or a combination of at least one uplink communication and the at least one sidelink communication; as well as A transmitter that transmits the at least one sidelink communication or a combination of the at least one uplink communication and the at least one sidelink communication based on the channel occupancy time sharing. Transmit sidelink control information (SCI), the SCI indicating a table identifier that indicates the start of a sidelink transmission associated with the channel occupancy time sharing. The transmitter transmits a channel occupancy time sharing indicator, remaining duration, channel access priority level, or a combination thereof, including first-level sidelink control information, second-level sidelink control information, or combinations thereof.

Images