Channel occupancy time sharing and energy saving for reduced capability devices

Abstract

Systems, methods, apparatuses, and computer program products for channel occupancy time (COT) sharing and energy saving for reduced capability (RedCap) devices. A method may include receiving a user equipment capability or a user equipment traffic requirement from a responding user equipment. The method may also include receiving a channel occupancy time sharing scope indication from a network element. The method may further include determining a channel occupancy time sharing scope based on the user equipment capability or the user equipment traffic requirement or the channel occupancy time sharing scope indication. In addition, the method may include determining a channel occupancy time resource allocation for the responding user equipment. Further, the method may include transmitting a channel occupancy time resource sharing indication to the responding user equipment based on the determined channel occupancy time sharing scope and / or the determined resource allocation.

Description

TITLE:CHANNEL OCCUPANCY TIME SHARING AND ENERGY SAVING FOR REDUCED CAPABILITY DEVICESCROSS-REFERENCE TO RELATED APPLICATIONThis application is related to and claims the priority of India Provisional Patent Application No. 202341067047, filed October 6, 2023, the entirety of which is hereby incorporated herein by reference.FIELD:

[0001] Some example embodiments may generally relate to mobile or wireless telecommunication systems, such as Long Term Evolution (LTE) or fifth generation (5G) new radio (NR) access technology, or 5G beyond, or sixth generation (6G) access technology, or other communications systems. For example, certain example embodiments may relate to apparatuses, systems, and / or methods for channel occupancy time (COT) sharing and energy saving for reduced capability (RedCap) devices.BACKGROUND:

[0002] Examples of mobile or wireless telecommunication systems may include the Universal Mobile Telecommunications System (UMTS) Terrestrial Radio Access Network (UTRAN), Long Term Evolution (LTE) Evolved UTRAN (E-UTRAN), LTE-Advanced (LTE-A), MulteFire, LTE-A Pro, fifth generation (5G) radio access technology or new radio (NR) access technology and / or sixth generation (6G) radio access technology. Fifth generation (5G) and sixth generation (6G) wireless systems refer to the next generation (NG) of radio systems and network architecture. 5G and 6G network technology is mostly based on new radio (NR) technology, but the 5G / 6G (or NG) network can also build on E-UTRAN radio. It is estimated that NR may provide bitrates on the order of 10-20 Gbit / s or higher, and may support at least enhanced mobile broadband (eMBB) and ultra-reliable low-latency communication (URLLC) as well as massive machine-type communication (mMTC). NR is expected to deliver extreme broadband and ultra-robust, low-latency connectivityand massive networking to support the Internet of Things (loT).SUMMARY:

[0003] Some example embodiments may be directed to a method. The method may include receiving a user equipment capability or a user equipment traffic requirement from a responding user equipment. The method may also include receiving a channel occupancy time sharing scope indication from a network element. The method may further include determining a channel occupancy time sharing scope based on the user equipment capability or the user equipment traffic requirement or the channel occupancy time sharing scope indication. In addition, the method may include determining a channel occupancy time resource allocation for the responding user equipment. Further, the method may include transmitting a channel occupancy time resource sharing indication to the responding user equipment based on the determined channel occupancy time sharing scope and / or the determined resource allocation.

[0004] Other example embodiments may be directed to an apparatus. The apparatus may include at least one processor and at least one memory storing instructions, wherein the instructions, when executed by the at least one processor, cause the apparatus at least to receive a user equipment capability or a user equipment traffic requirement from a responding user equipment. The apparatus may also be caused to receive a channel occupancy time sharing scope indication from a network element. The apparatus may further be caused to determine a channel occupancy time sharing scope based on the user equipment capability or the user equipment traffic requirement or the channel occupancy time sharing scope indication. In addition, the apparatus may be caused to determine a channel occupancy time resource allocation for the responding user equipment. Further, the apparatus may be caused to transmit a channel occupancy time resource sharing indication to the responding user equipment based on the determined channel occupancy time sharing scope and / or the determined resource allocation.

[0005] Other example embodiments may be directed to an apparatus. The apparatus may include means for receiving a user equipment capability or a user equipmenttraffic requirement from a responding user equipment. The apparatus may also include means for receiving a channel occupancy time sharing scope indication from a network element. The apparatus may further include means for determining a channel occupancy time sharing scope based on the user equipment capability or the user equipment traffic requirement or the channel occupancy time sharing scope indication. In addition, the apparatus may include means for determining a channel occupancy time resource allocation for the responding user equipment. Further, the apparatus may include means for transmitting a channel occupancy time resource sharing indication to the responding user equipment based on the determined channel occupancy time sharing scope and / or the determined resource allocation.

[0006] In accordance with other example embodiments, a non-transitory computer readable medium may be encoded with instructions that may, when executed in hardware, perform a method. The method may include receiving a user equipment capability or a user equipment traffic requirement from a responding user equipment. The method may also include receiving a channel occupancy time sharing scope indication from a network element. The method may further include determining a channel occupancy time sharing scope based on the user equipment capability or the user equipment traffic requirement or the channel occupancy time sharing scope indication. In addition, the method may include determining a channel occupancy time resource allocation for the responding user equipment. Further, the method may include transmitting a channel occupancy time resource sharing indication to the responding user equipment based on the determined channel occupancy time sharing scope and / or the determined resource allocation.

[0007] Other example embodiments may be directed to a computer program product that performs a method. The method may include receiving a user equipment capability or a user equipment traffic requirement from a responding user equipment. The method may also include receiving a channel occupancy time sharing scope indication from a network element. The method may further include determining a channel occupancy time sharing scope based on the user equipment capability or the user equipment traffic requirement or the channel occupancy time sharing scope indication. In addition, the method may include determining a channel occupancytime resource allocation for the responding user equipment. Further, the method may include transmitting a channel occupancy time resource sharing indication to the responding user equipment based on the determined channel occupancy time sharing scope and / or the determined resource allocation.

[0008] Other example embodiments may be directed to an apparatus that may include circuitry configured to receive a user equipment capability or a user equipment traffic requirement from a responding user equipment. The apparatus may also include circuitry configured to receive a channel occupancy time sharing scope indication from a network element. The apparatus may further include circuitry configured to determine a channel occupancy time sharing scope based on the user equipment capability or the user equipment traffic requirement or the channel occupancy time sharing scope indication. In addition, the apparatus may include circuitry configured to determine a channel occupancy time resource allocation for the responding user equipment. Further, the apparatus may include circuitry configured to transmit a channel occupancy time resource sharing indication to the responding user equipment based on the determined channel occupancy time sharing scope and / or the determined resource allocation.

[0009] Some example embodiments may be directed to a method. The method may include transmitting a user equipment capability or a user equipment traffic requirement to a network element or an initiator user equipment. The method may also include receiving a channel occupancy time resource sharing indication from the initiator user equipment based on a determined channel occupancy time sharing scope and / or a determined resource allocation. The method may further include determining a transmission time gap in response to the channel occupancy time resource sharing indication.

[0010] Other example embodiments may be directed to an apparatus. The apparatus may include at least one processor and at least one memory storing instructions, wherein the instructions, when executed by the at least one processor, cause the apparatus at least to transmit a user equipment capability or a user equipment traffic requirement to a network element or an initiator user equipment. The apparatus may also be caused to receive a channel occupancy time resource sharing indication fromthe initiator user equipment based on a determined channel occupancy time sharing scope and / or a determined resource allocation. The apparatus may further be caused to determine a transmission time gap in response to the channel occupancy time resource sharing indication.

[0011] Other example embodiments may be directed to an apparatus. The apparatus may include means for transmitting a user equipment capability or a user equipment traffic requirement to a network element or an initiator user equipment. The apparatus may also include means for receiving a channel occupancy time resource sharing indication from the initiator user equipment based on a determined channel occupancy time sharing scope and / or a determined resource allocation. The apparatus may further include means for determining a transmission time gap in response to the channel occupancy time resource sharing indication.

[0012] In accordance with other example embodiments, a non-transitory computer readable medium may be encoded with instructions that may, when executed in hardware, perform a method. The method may include transmitting a user equipment capability or a user equipment traffic requirement to a network element or an initiator user equipment. The method may also include receiving a channel occupancy time resource sharing indication from the initiator user equipment based on a determined channel occupancy time sharing scope and / or a determined resource allocation. The method may further include determining a transmission time gap in response to the channel occupancy time resource sharing indication.

[0013] Other example embodiments may be directed to a computer program product that performs a method. The method may include transmitting a user equipment capability or a user equipment traffic requirement to a network element or an initiator user equipment. The method may also include receiving a channel occupancy time resource sharing indication from the initiator user equipment based on a determined channel occupancy time sharing scope and / or a determined resource allocation. The method may further include determining a transmission time gap in response to the channel occupancy time resource sharing indication.

[0014] Other example embodiments may be directed to an apparatus that may include circuitry configured to transmit a user equipment capability or a userequipment traffic requirement to a network element or an initiator user equipment. The apparatus may also include circuitry configured to receive a channel occupancy time resource sharing indication from the initiator user equipment based on a determined channel occupancy time sharing scope and / or a determined resource allocation. The apparatus may also include circuitry configured to determine a transmission time gap in response to the channel occupancy time resource sharing indication.

[0015] Some example embodiments may be directed to a method. The method may include configuring a responding user equipment to share a capability or traffic requirement. The method may also include receiving, based on the configuration, the responding user equipment capability or the responding user equipment traffic requirement from the responding user equipment. The method may further include determining a channel occupancy time sharing scope based on the responding user equipment capability and / or the responding user equipment traffic requirement. In addition, the method may include transmitting a channel occupancy time sharing scope indication to an initiator user equipment based on the channel occupancy time sharing scope.

[0016] Other example embodiments may be directed to an apparatus. The apparatus may include at least one processor and at least one memory storing instructions, wherein the instructions, when executed by the at least one processor, cause the apparatus at least to configure a responding user equipment to share a capability or traffic requirement. The apparatus may also be caused to receive, based on the configuration, the responding user equipment capability or the responding user equipment traffic requirement from the responding user equipment. The apparatus may further be caused to determine a channel occupancy time sharing scope based on the responding user equipment capability and / or the responding user equipment traffic requirement. In addition, the apparatus may be caused to transmit a channel occupancy time sharing scope indication to an initiator user equipment based on the channel occupancy time sharing scope.

[0017] Other example embodiments may be directed to an apparatus. The apparatus may include means for configuring a responding user equipment to share a capabilityor traffic requirement. The apparatus may also include means for receiving, based on the configuration, the responding user equipment capability or the responding user equipment traffic requirement from the responding user equipment. The apparatus may further include means for determining a channel occupancy time sharing scope based on the responding user equipment capability and / or the responding user equipment traffic requirement. In addition, the apparatus may include means for transmitting a channel occupancy time sharing scope indication to an initiator user equipment based on the channel occupancy time sharing scope.

[0018] In accordance with other example embodiments, a non-transitory computer readable medium may be encoded with instructions that may, when executed in hardware, perform a method. The method may include configuring a responding user equipment to share a capability or traffic requirement. The method may also include receiving, based on the configuration, the responding user equipment capability or the responding user equipment traffic requirement from the responding user equipment. The method may further include determining a channel occupancy time sharing scope based on the responding user equipment capability and / or the responding user equipment traffic requirement. In addition, the method may include transmitting a channel occupancy time sharing scope indication to an initiator user equipment based on the channel occupancy time sharing scope.

[0019] Other example embodiments may be directed to a computer program product that performs a method. The method may include configuring a responding user equipment to share a capability or traffic requirement. The method may also include receiving, based on the configuration, the responding user equipment capability or the responding user equipment traffic requirement from the responding user equipment. The method may further include determining a channel occupancy time sharing scope based on the responding user equipment capability and / or the responding user equipment traffic requirement. In addition, the method may include transmitting a channel occupancy time sharing scope indication to an initiator user equipment based on the channel occupancy time sharing scope.

[0020] Other example embodiments may be directed to an apparatus that may include circuitry configured to configure a responding user equipment to share acapability or traffic requirement. The apparatus may also include circuitry configured to receive, based on the configuration, the responding user equipment capability or the responding user equipment traffic requirement from the responding user equipment. The apparatus may further include circuitry configured to determine a channel occupancy time sharing scope based on the responding user equipment capability and / or the responding user equipment traffic requirement. In addition, the apparatus may include circuitry configured to transmit a channel occupancy time sharing scope indication to an initiator user equipment based on the channel occupancy time sharing scope.BRIEF DESCRIPTION OF THE DRAWINGS:

[0021] For proper understanding of example embodiments, reference should be made to the accompanying drawings, wherein:

[0022] FIG. 1 illustrates a clear channel assessment (CCA) slot.

[0023] FIG. 2 illustrates an example acquisition of a channel occupancy time (COT) by an initiating device.

[0024] FIG. 3 illustrates an example table of channel access priority class (CAPC) associated with a user equipment’s traffic.

[0025] FIG. 4 illustrates an example behavior associated with contention window.

[0026] FIG. 4B illustrates another example behavior associated with contention window.

[0027] FIG. 4C illustrates a further example behavior associated with contention window..

[0028] FIG. 5A illustrates an example of allowed gaps for which listen-before-talk (LBT) type 2 variant is applicable.

[0029] FIG. 5B illustrates another example of allowed gaps for which LBT type 2 variant is applicable.

[0030] FIG. 5C illustrates a further example of allowed gaps for which LBT type 2 variant is applicable.

[0031] FIG. 5D illustrates yet another example of allowed gaps for which LBT type 2 variant is applicable.

[0032] FIG. 5E illustrates a further example of allowed gaps for which LBT type 2 variant is applicable.

[0033] FIG. 5F illustrates another example of allowed gaps for which LBT type 2 variant is applicable.

[0034] FIG. 6 illustrates an example signal flow diagram, according to certain example embodiments.

[0035] FIG. 7 illustrates an example flow diagram of a method, according to certain example embodiments.

[0036] FIG. 8 illustrates an example flow diagram of another method, according to certain example embodiments.

[0037] FIG. 9 illustrates an example flow diagram of a further method, according to certain example embodiments.

[0038] FIG. 10 illustrates a set of apparatuses, according to certain example embodiments.DETAILED DESCRIPTION:

[0039] It will be readily understood that the components of certain example embodiments, as generally described and illustrated in the figures herein, may be arranged and designed in a wide variety of different configurations. The following is a detailed description of some example embodiments of systems, methods, apparatuses, and computer program products for channel occupancy time (COT) sharing and energy saving for reduced capability (RedCap) devices.

[0040] The features, structures, or characteristics of example embodiments described throughout this specification may be combined in any suitable manner in one or more example embodiments. For example, the usage of the phrases “certain embodiments,” “an example embodiment,” “some embodiments,” or other similar language, throughout this specification refers to the fact that a particular feature, structure, or characteristic described in connection with an embodiment may be included in at least one embodiment. Thus, appearances of the phrases “in certain embodiments,” “an example embodiment,” “in some embodiments,” “in other embodiments,” or other similar language, throughout this specification do notnecessarily refer to the same group of embodiments, and the described features, structures, or characteristics may be combined in any suitable manner in one or more example embodiments. Further, the terms “base station”, “cell”, “node”, “gNB”, “network” or other similar language throughout this specification may be used interchangeably.

[0041] As used herein, “at least one of the following: ” and “at least one of ” and similar wording, where the list of two or more elements are joined by “and”, “or” or “and / or,” mean at least any one of the elements, or at least any two or more of the elements, or at least all the elements.

[0042] 5G new radio-unlicensed (NR-U) is a third generation partnership project (3GPP) release 16 mode of operation that provides the necessary technology for cellular operations to integrate unlicensed spectrum into 5G networks. In NR-U, channel access in both downlink (DL) and uplink (UL) relies on listen-before-talk (LBT). A wireless device or a base station (BS) first senses the communications channel to determine that there is no communications prior to any transmission. The LBT parameters (e.g., type / duration, clear channel assessment parameters, etc.) are configured by the BS.

[0043] 5G NR-U may include various types of LBT procedures including, for example, Type 1 channel access procedures and Type 2 channel access procedures. Type 1 channel access procedures are used to acquire a channel in a new COT, while Type 2 channel access procedures are used to allow the UE / next generation node B (gNB) to share the COT previously acquired by the gNB / UE. LBT Type 2 is further categorized into Type 2A (25 ps LBT), Type 2B (16 ps LBT), and Type 2C (no LBT). COT refers to the overall duration during which a specific wireless device, such as an evolved NodeB (eNB), gNB, or UE, along with any other associated eNB / gNB / UE(s), engages in transmissions on a particular communication channel. This time duration encompasses the transmissions that occur after an eNB / gNB / UE completes the necessary channel access procedures. The COT structure reduces power consumption and channel access delay.

[0044] 3GPP has introduced a tier of RedCap devices, also known as NR-light. It isa device category that bridges the capability and complexity gap between low-power wide-area (LPWA) and URLCC uses in 5G with an optimized design for mid-tier use cases. The devices operate across both FR1 and FR2 frequency ranges, accommodating frequency division duplex (FDD) and time division duplex (TDD). With support for a maximum device bandwidth of 20MHz (FR1) and 100MHz (FR2), NR-light includes a minimum of 1 Rx antenna (FR1) and 2 Rx antennas (FR2) per device. NR-light targets scenarios with lower performance requirements and cost constraints, are smaller in physical size and have longer battery life.

[0045] In sub-7GHz unlicensed bands, NR coexistence with other systems (e.g., IEEE 802.11) may be ensured via a LBT channel access mechanism where a UE intending to perform a sidelink (SL) transmission needs first to successfully complete an LBT check before being able to initiate that SL transmission. LBT may also be referred to as clear channel assessment (CCA) or channel access procedure.

[0046] For a UE to pass an LBT check, it may observe the channel as available for a number of consecutive CCA slots. For instance, in sub-7 GHz, the duration of these slots is 9 ps, as illustrated in FIG. 1. In particular, FIG. 1 illustrates an example CCA slot with a duration of Tsl = 9 ps, where the energy detection takes place during 4 ps. The UE may deem the channel as available in a CCA slot if the measured power (i.e., the collected energy during the CCA slot) is below a regulatory specified energy detection threshold (EDT), which can depend on the transmit power, operating band, and geographical region.

[0047] FIG. 2 illustrates an example acquisition of the COT by an initiating device via LTB Type 1. When a UE initiates the communication (i.e., the UE takes the role of an initiating device), the UE may acquire the “right” to access the channel for a certain period of time denoted as COT, by applying an “extended” LBT procedure where the channel may be deemed as free for the entire duration of the contention window (CW). The “extended” LBT procedure may be known as LBT Type 1.

[0048] FIG. 3 illustrates an example table of channel access priority class (CAPC) associated with a user equipment’ s traffic. The duration of both the COT and CW may depend on the channel access priority class (CAPC) associated with the UE’s traffic, as illustrated in FIG. 3. The control plane traffic (e.g., physical shared controlchannel) may be transmitted with p=l, while user plane traffic has p>l. In FIG. 3, the LBT Type 1 is illustrated, and depicts details for the Uu UL case. However, the DL case LBT Type 1 may also be adopted in SL. In other cases, as further illustrated in FIG. 3, the contention window length in CCA slots associated with each CAPC has a minimum (CW™n, p) and maximum (CWmax,, p). The duration of the COT is given by Tuim cot,p-

[0049] FIGs. 4A-4C illustrate various example behavior associated with contention windows. In particular, FIG. 4A illustrates a scenario when neither the defer time nor the countdown are disrupted (i.e., the channel is not detected as busy during a sensing slot). FIG. 4B illustrates a scenario where the defer time is disrupted (i.e., the channel is detected as busy during a defer time sensing slot). FIG. 4C illustrates a scenario where the contention window countdown is disrupted (i.e., the channel is detected as busy during a sensing slot of the countdown). As illustrated in FIGs. 4A- 4C, Ta refers to the defer time, Tsirefers to the CCA slot duration, and N refers to the number of CCA slots required to be deemed as free before the contention window countdown is complete. As illustrated in FIGs. 4A-4C, if during the countdown procedure the LBT check fails in defer time or any CCA slot, then the countdown may stop and restart.

[0050] FIGs. 5A-5F illustrate various examples of allowed gaps for which listen- before-talk (LBT) type 2 variant is applicable. The UE initiating the transmission (e.g., initiating device / UE) upon successfully completing the LBT Type 1 and performing a transmission, may acquire the COT with a duration associated with the corresponding CAPC. The acquired COT may be valid even when the initiating device pauses its transmission, although if the initiating device wants to perform a new transmission (within the COT), it may be required to perform a “reduced” LBT procedure. This “reduced” LBT procedure is known as LBT Type 2.

[0051] LBT Type 2 may include multiple variants. For example, one variant may include Type 2A (25 ps LBT) for SL transmissions within the initiating device acquired COT (when the gap between two SL transmissions is > 25 ps, as well for SL transmission following another SL transmission (see FIGs. 5C and 5F). In Type 2B (16 ps LBT), for SL transmission within the initiating device acquired COT, canbe used for SL transmission following another SL with gap exactly equal to 16 ps), as illustrated in FIGs. 5B and 5E. For Type 2C (no LBT), this may be used for SL transmission(s) following another SL, with a gap < 16 ps and the allowed duration of the SL transmission < 584 ps), as illustrated in FIGs. 5A and 5D.

[0052] The initiating device can share its acquired COT with its intended receiver (the responding device). For this purpose, the initiating device may inform (e.g., via control signaling) the responding device about the duration of this COT. The responding device may then use this information to decide which type of LBT it should apply upon performing a transmission for which the intended receiver is the initiating device. In case the responding device transmission falls outside the COT, then the responding device will have to acquire a new COT using the LBT Type 1 with the appropriate CAPC.

[0053] In NR-U, a COT can be shared from / to the gNB to / from the UE. The responding device (i.e., COT shared device) can transmit a DL / UL transmission with relaxed LBT requirement (type 2A / B / C). Additionally, at the introduction of RedCap, NR devices may facilitate the expansion of the NR device ecosystem to cater to the use cases such as Industrial wireless sensors, video surveillance, and wearables. When a RedCap device or any device operates over unlicensed spectrum, it must perform LBT to access the wireless channel as a regulatory requirement. Furthermore, COT sharing functionality for RedCap devices can serve as a catalyst for energy efficiency and enable RedCap devices to serve other functional problems.

[0054] Currently, COT sharing for RedCap devices (e.g., RedCap UEs) is not supported. Thus, RedCap devices lack the ability to benefit from energy-saving mechanisms and enhanced functionalities facilitated by COT sharing. As a result, power-limited RedCap devices cannot save energy by performing a reduced LBT or by not performing channel access in case of meeting Type 2C (no LBT) criteria. To enable RedCap devices to use the COT sharing functionalities, the COT initiating device, or the UE must adapt a COT sharing mechanism that would benefit RedCap devices over the non-RedCap devices. To cover such adaptation, a thorough approach is needed that considers different aspects of the COT responding device, which is influenced by the capabilities of RedCap devices.

[0055] Connectivity for extreme communication requirements with limited coverage and with limited device capability may be installed in locations where the high- performance requirements are demanded, such as in-vehicle, in-house, or even in human bodies. This type of network is termed as subnetworks and can be part of the 6G overlay network infrastructure. Devices that are part of the subnetwork ecosystem need to be highly efficient in terms of connectivity and energy consumption as they are in some cases supporting life critical services. RedCap devices and COT sharing mechanism are expected to be part of this subnetwork in one such example.

[0056] To enable RedCap devices to use the COT sharing functionalities, the COT initiating device, or the UE, would have to adapt a COT sharing mechanism that would benefit RedCap device over the non-RedCap devices that may be present in the environment. Such adaptation covers multiple aspects of the COT responding device which is dependent on the RedCap UE capabilities. The COT initiating device needs to tune the sharing mechanism to pave the way to prioritize and fulfil the requirements of RedCap device over non-RedCap devices.

[0057] In view of the drawbacks exhibited by the current state of technology, certain example embodiments address the need to prioritize and support COT sharing for RedCap devices, including, for example, in scenarios where both RedCap and non- RedCap devices coexist and provide critical communication services. Certain example embodiments may also introduce alternative options based on the COT initiating device determining to allocate its COT resources to one or more devices.

[0058] For instance, one option may involve offering COT sharing from one RedCap UE to another RedCap UE, prioritizing over non-RedCap UE. Another option may involve prioritizing RedCap UE over non-RedCap UE based on the RedCap UE capability. A further option may involve prioritizing traffic requirements of COT responder UEs that meet COT sharing requirements. Yet another option may involve combining the prioritization of RedCap UEs and prioritizing traffic requirements of COT responder UEs for selecting devices for COT sharing to achieve efficient resource allocation. These options may provide a framework to optimize COT utilization, ensuring fair distribution, and enabling RedCap devices to efficientlyaccess communication channels and perform critical tasks in the presence of non- RedCap devices (e.g., non-RedCap UEs).

[0059] When both RedCap devices and non-RedCap devices coexist within a communication range, a fair COT sharing mechanism is critical for RedCap devices to take advantages of the features that COTS mechanism offers, and use energy efficiently. Thus, when a COTS-capable UE share its COT with another device or with its communicating device, certain example embodiments introduce options such as those described above, based on the COT initiating device determining to allocate its COT resources to one or more devices.

[0060] According to certain example embodiments, the COT initiator (e.g., COT initiating UE) may share its COT with another device. For instance, the COT initiator may be initially enabled to share its COT with its communicating UEs (in case of groupcast or groupcast services). In some example embodiments, the COT initiating UE may support a minimum bandwidth required to perform LBT. Additionally, the COT initiating UE may determine which UE to share its COT by using at least one or more various criteria.

[0061] In certain example embodiments, one criteria may include when both the COT initiating UE and the responding UE are RedCap UEs, the COT initiating UE may prioritize sharing the COT with one or more RedCap UEs over any other non- RedCap UE. Under this criteria, the prioritization of RedCap UEs over non-RedCap UEs may be initiated when the COT initiator itself is a RedCap UE. Alternatively, according to another criteria, the initiating UE may prioritize the RedCap UE over non-RedCap UEs based on a reported RedCap UE capability. Under this criteria, the COT responding UE may report its minimum bandwidth requirement, minimum number of receive branches (e.g., 1 , 2, or 4), and / or minimum number of DL multiple input multiple output (MIMO) layers (e.g., 1 or 2) to the COT initiating UE. Additionally, under this criteria, the COT initiating UE may broadcast (optionally) its COT sharing criteria to intended responding UEs. Furthermore, under this criteria, a table may be configured by the initiating UE to map the UE capability to share COT resources. For instance, one example embodiment may use a principle to design a mapping table. The responding UE having limited RedCap capabilitymay have the highest priority. Otherwise, the responding UE having the highest capability can have the least priority in the mapping table. This mapping table may be updated if and when any UE is added or deleted from the communicating device list. Additionally, under this criteria, the time multiplex COT sharing may be applied to share the COT resources with multiple responding UEs while not exceeding the COT duration.

[0062] In other example embodiments, the COT responder’s traffic requirements that meet COT requirements may be prioritized. For example, a minimum bandwidth requirement may be used to determine one or more responding devices to share COT. In some example embodiments, the COT responder may complete its transmission successfully within an available COT duration. In this example embodiment, the COT responder that cannot meet the COT requirements may not participate in COT sharing. In other example embodiments, a table may be configured by the COT initiator to map the COT responder’s traffic requirements. For instance, the mapping may be used to design a mapping table. Additionally, the COT responder that has a higher CAPC (CAPC associated with the UE’s traffic) may obtain the highest priority. Otherwise, the COT responder having the lowest CAPC may obtain the least priority in the mapping table.

[0063] According to certain example embodiments, the initiating UE prioritizing the RedCap UE over non-RedCap UEs, and the prioritization of COT responder’s traffic requirements may be combined. Additionally, this combination may include the ability to create a mapping table accordingly, containing COT responder’s RedCap UE capability and traffic requirements. If the COT initiator has UE capability along with the traffic requirements information, then the COT resource allocation for the COT initiator may be more efficient. In this example embodiment, if a COT responder UE has critical traffic requirements and has a lower RedCap capability as compared to another RedCap device, the responder UE may be prioritized to obtain the COT resources over other RedCap UE. Otherwise, the selected responder UE through this method may not have been prioritized if only one option (e.g., UE prioritization of RedCap UEs over non-RedCap UEs or prioritization of COT responder’s traffic requirements) is considered. Further, in some exampleembodiments, it may be more effective to allocate COT resources to RedCap UEs having stringent requirements such as energy limited, or bandwidth limited. In certain example embodiments, a first option of prioritization of RedCap UEs over non-RedCap UEs based on the reported RedCap capability, a second option of prioritizing COT responder’s traffic requirements, and a third option of combining the first and second options may be applied when the COT initiator has information including, for example, RedCap capability and / or traffic requirements of the COT responder. This information may be directly shared with the COT initiator by the COT responder via SL UE assistance information or via BS radio resource control (RRC) signaling as described below with respect to FIG. 6.

[0064] FIG. 6 illustrates an example signal flow diagram, according to certain example embodiments. As illustrated in FIG. 6, the signal flow involves a COT responder(s) 600, COT initiator 605, and BS 610. At 615, a PC5 link may be established between the COT responder(s) 600 and the COT initiator 605. At 620, the UEs (e.g., COT responder(s) 600 and / or COT initiator 606) may be configured by the BS 610 to share the capability / traffic requirements for COT sharing in SL communications. At 625, the BS 610 may determine the COT sharing scope based on the COT responder(s) 600 (e.g., RedCap UE) capability / traffic requirements according to any one or more options described above. For example, the BS 610 may prioritize the RedCap UEs based on their capability (e.g., UE having least device capability is prioritized over UE having better device capability). Similar criterion may also be applied when considering the traffic requirements to prioritize a RedCap UE over another RedCap UE. In certain example embodiments, the COT sharing scope may comprise a list of prioritized COT responder(s) after the BS 610 / COT initiator 605 checks whether the COT responder(s) 600 can actually be served by the COT sharing or not based on the received traffic requirements / device capability of the COT responder(s) 600. At 630, the BS 610 may transmit a COT sharing scope indication to the COT initiator 605 based on the determined COT sharing scope. For instance, in some example embodiments, the BS 610 may indicate a list of UEs prioritized for COT sharing based on the determined COT sharing scope.

[0065] At 635, the COT initiator 605 may acquire the COT. For instance, at 635, when COT initiator 605 performs LBT, as a regulatory requirement(s), to acquire a wireless channel, the COT initiator 605 may share its COT with another UE. At 640, the COT initiator 605 may determine the COT sharing scope based on the RedCap UE capability / traffic requirements according to any one or more options described above, and / or the received COT sharing scope indication from the BS 610. For instance, in some example embodiments, the COT responder with the least device capability may be given first priority, and the COT responder with the highest device capability may be given a last priority. In some example embodiments, the COT responders’ device capability / traffic requirements may be shared with both the BS 610 and the COT initiator 605. As such, at 640, the COT initiator 605 may perform essentially the same job as the BS 610 at 625. However, a difference between the COT sharing scope determined at the BS 610 and the COT sharing scope determined at the COT initiator 605 may be that the BS 610 determines the scope in the case of SL mode 1 communication, whereas the COT initiator 605 determines the COT sharing scope in the case of SL mode 2 communication. Thus, it may be seen that a difference between these two operational modes is that in mode 1, the resources used by the UE-to-UE link may be allocated by the BS 605; in mode 2, a common (preconfigured) resource may be autonomously shared between the UEs without the intervention of the BS 610. Therefore, in some example embodiments, the steps 625 and 630 may be skipped / omitted at least for SL mode 2 communication.

[0066] At 645, the COT initiator 605 may determine a COT resource allocation for one or more COT responder(s) 600. At 650, the COT initiator 605 may transmit a COT resource sharing indication to the COT responder(s) 600. In some example embodiments, the COT resource sharing indication may indicate the sharing, the COT sharing scope (e.g., a list of prioritized COT responder(s)), and / or the resource allocation (e.g., the time / frequency resources of at least part of the COT). In some example embodiments, the list of COT responder(s) may be indicated to all COT responders of the COT initiator 605. At 655, the COT responder(s) 600 may calculate a transmission time gap in response to the COT resource sharing indication. At 660, the COT responder(s) 600 may determine a LBT type based on thetransmission time gap. For instance, in response to the COT resource sharing indication, the COT responder(s) 600 may determine the transmission gap. This transmission gap may decide the LBT type, which may represent a regulator requirement. At 665, the COT responder(s) 600 may optionally perform SL Tx with the COT initiator 605 based on the LBT determination.

[0067] FIG. 7 illustrates an example flow diagram of a method, according to certain example embodiments. In an example embodiment, the method of FIG. 7 may be performed by a network entity, or a group of multiple network elements in a 3GPP system, such as LTE or 5G-NR. For instance, in an example embodiment, the method of FIG. 7 may be performed by a COT initiator device such as, for example, a UE, similar to one of apparatuses 10 or 20 illustrated in FIG. 10.

[0068] As illustrated in FIG. 7, the method may include, at 700, receiving a user equipment capability or a user equipment traffic requirement from a responding user equipment. The method may also include, at 705, receiving a channel occupancy time sharing scope indication from a network element. The method may further include, at 710, determining a channel occupancy time sharing scope based on the user equipment capability or the user equipment traffic requirement or the channel occupancy time sharing scope indication. Additionally, the method may include, at 715, determining a channel occupancy time resource allocation for the responding user equipment. In certain example embodiments, the resource allocation is determined based on the determined channel occupancy time sharing scope. Further, the method may include, at 720, transmitting a channel occupancy time resource sharing indication to the responding user equipment based on the determined channel occupancy time sharing scope and / or the determined resource allocation.

[0069] According to certain example embodiments, the determination of the channel occupancy time sharing scope may include determining a channel occupancy time sharing priority. In certain example embodiments, the COT sharing priority may comprise a list of prioritized COT responder(s). According to some example embodiments, the determination of the channel occupancy time sharing scope is based on whether both a channel occupancy time initiator and the responding user equipment are reduced capability user equipment. According to some exampleembodiments, sharing of the channel occupancy time may be offered from one reduced capability user equipment to another reduced capability user equipment. According to other example embodiments, the determination of the channel occupancy time sharing scope is based on prioritizing a reduced capability user equipment over a non-reduced capability user equipment based on a capability of the reduced capability user equipment.

[0070] In certain example embodiments, the determination of the channel occupancy time sharing scope is based on prioritizing channel occupancy time responders with traffic requirements that satisfy channel occupancy time sharing requirements. In some example embodiments, the determination of the channel occupancy time sharing scope is based on prioritizing a reduced capability user equipment over a non-reduced capability user equipment based on a capability of the reduced capability user equipment, and prioritizing channel occupancy time responders with traffic requirements that satisfy channel occupancy time sharing requirements.

[0071] FIG. 8 illustrates an example flow diagram of a method, according to certain example embodiments. In an example embodiment, the method of FIG. 8 may be performed by a network entity, or a group of multiple network elements in a 3GPP system, such as LTE or 5G-NR. For instance, in an example embodiment, the method of FIG. 8 may be performed by a COT responder device such as, for example, a UE, similar to one of apparatuses 10 or 20 illustrated in FIG. 10.

[0072] As illustrated in FIG. 8, the method may include, at 800, transmitting a user equipment capability or a user equipment traffic requirement to a network element or an initiator user equipment. The method may also include, at 805, receiving a channel occupancy time resource sharing indication from the initiator user equipment based on a determined channel occupancy time sharing scope and / or a determined resource allocation. The method may further include, at 810, determining a transmission time gap in response to the received channel occupancy time resource sharing indication. According to certain example embodiments, the method may also include determining a listen-before-talk type based on the transmission time gap.

[0073] FIG. 9 illustrates an example flow diagram of another method, according tocertain example embodiments. In an example embodiment, the method of FIG. 9 may be performed by a network entity, or a group of multiple network elements in a 3GPP system, such as LTE or 5G-NR. For instance, in an example embodiment, the method of FIG. 9 may be performed by a BS, gNB, or network, similar to one of apparatuses 10 or 20 illustrated in FIG. 10.

[0074] As illustrated in FIG. 9, the method may include, at 900, configuring a responding user equipment to share a capability or traffic requirement. The method may also include, at 905, receiving, based on the configuration, the responding user equipment capability or the responding user equipment traffic requirement from the responding user equipment. The method may further include, at 910, determining a channel occupancy time sharing scope based on the responding user equipment capability and / or the responding user equipment traffic requirement. In addition, the method may include, at 915, transmitting a channel occupancy time sharing scope indication to an initiator user equipment based on the channel occupancy time sharing scope.

[0075] FIG. 10 illustrates a set of apparatuses 10 and 20 according to certain example embodiments. In certain example embodiments, apparatuses 10 and 20 may be elements in a communications network or associated with such a network. For example, apparatus 10 may be a COT responder (e.g., UE) or a COT initiator (e.g., UE), or other similar radio communication computer device, and apparatus 20 may be a BS, gNB, network, or other similar computing device.

[0076] In some example embodiments, apparatuses 10 and 20 may include one or more processors, one or more computer-readable storage medium (for example, memory, storage, or the like), one or more radio access components (for example, a modem, a transceiver, or the like), and / or a user interface. In some example embodiments, apparatuses 10 and 20 may be configured to operate using one or more radio access technologies, such as GSM, LTE, LTE-A, NR, 5G, 6G, WLAN, WiFi, NB-IoT, Bluetooth, NFC, MulteFire, and / or any other radio access technologies. It should be noted that one of ordinary skill in the art would understand that apparatuses 10 and 20 may include components or features not shown in FIG. 10.

[0077] As illustrated in the example of FIG. 10, apparatuses 10 and 20 may includeor be coupled to a processors 12 and 22 for processing information and executing instructions or operations. Processors 12 and 22 may be any type of general or specific purpose processor. In fact, processors 12 and 22 may include one or more of general-purpose computers, special purpose computers, microprocessors, DSPs, field-programmable gate arrays (FPGAs), application-specific integrated circuits (ASICs), and processors based on a multi-core processor architecture, as examples. While a single processors 12 and 22 is shown in FIG. 10, multiple processors may be utilized according to other example embodiments. For example, it should be understood that, in certain example embodiments, apparatuses 10 and 20 may include two or more processors that may form a multiprocessor system (e.g., in this case processors 12 may represent a multiprocessor) that may support multiprocessing. According to certain example embodiments, the multiprocessor system may be tightly coupled or loosely coupled (e.g., to form a computer cluster).

[0078] Processors 12 and 22 may perform functions associated with the operation of apparatuses 10 and 20 including, as some examples, precoding of antenna gain / phase parameters, encoding and decoding of individual bits forming a communication message, formatting of information, and overall control of the apparatuses 10 and 20, including processes and examples illustrated in FIGs. 1-9.

[0079] Apparatuses 10 and 20 may further include or be coupled to a memories 14 and 24 (internal or external), which may be respectively coupled to processors 12 and 24 for storing information and instructions that may be executed by processors 12 and 24. Memories 14 and 24 may be one or more memories and of any type suitable to the local application environment, and may be implemented using any suitable volatile or nonvolatile data storage technology such as a semiconductorbased memory device, a magnetic memory device and system, an optical memory device and system, fixed memory, and / or removable memory. For example, memories 14 and 24 can be comprised of any combination of random access memory (RAM), read only memory (ROM), static storage such as a magnetic or optical disk, hard disk drive (HDD), or any other type of non-transitory machine or computer readable media. The instructions stored in memories 14 and 24 may include program instructions or computer program code that, when executed by processors 12 and 22,enable the apparatuses 10 and 20 to perform tasks as described herein.

[0080] In certain example embodiments, apparatuses 10 and 20 may further include or be coupled to (internal or external) a drive or port that is configured to accept and read an external computer readable storage medium, such as an optical disc, USB drive, flash drive, or any other storage medium. For example, the external computer readable storage medium may store a computer program or software for execution by processors 12 and 22 and / or apparatuses 10 and 20 to perform any of the methods and examples illustrated in FIGs. 1-9.

[0081] In some example embodiments, apparatuses 10 and 20 may also include or be coupled to one or more antennas 15 and 25 for receiving a downlink signal and for transmitting via an UL from apparatuses 10 and 20. Apparatuses 10 and 20 may further include a transceivers 18 and 28 configured to transmit and receive information. The transceivers 18 and 28 may also include a radio interface (e.g., a modem) coupled to the antennas 15 and 25. The radio interface may correspond to a plurality of radio access technologies including one or more of GSM, LTE, LTE- A, 5G, NR, 6G, WLAN, NB-IoT, Bluetooth, BT-LE, NFC, RFID, UWB, and the like. The radio interface may include other components, such as filters, converters (for example, digital-to-analog converters and the like), symbol demappers, signal shaping components, an Inverse Fast Fourier Transform (IFFT) module, and the like, to process symbols, such as OFDMA symbols, carried by a downlink or an UL.

[0082] For instance, transceivers 18 and 28 may be configured to modulate information on to a carrier waveform for transmission by the antennas 15 and 25 and demodulate information received via the antenna 15 and 25 for further processing by other elements of apparatuses 10 and 20. In other example embodiments, transceivers 18 and 28 may be capable of transmitting and receiving signals or data directly. Additionally or alternatively, in some example embodiments, apparatus 10 may include an input and / or output device (I / O device). In certain example embodiments, apparatuses 10 and 20 may further include a user interface, such as a graphical user interface or touchscreen.

[0083] In certain example embodiments, memories 14 and 34 store software modules that provide functionality when executed by processors 12 and 22. Themodules may include, for example, an operating system that provides operating system functionality for apparatuses 10 and 20. The memory may also store one or more functional modules, such as an application or program, to provide additional functionality for apparatuses 10 and 20. The components of apparatuses 10 and 20 may be implemented in hardware, or as any suitable combination of hardware and software. According to certain example embodiments, apparatuses 10 and 20 may optionally be configured to communicate each other (in any combination) via a wireless or wired communication links 70 according to any radio access technology, such as NR.

[0084] According to certain example embodiments, processors 12 and 22 and memories 14 and 24 may be included in or may form a part of processing circuitry or control circuitry. In addition, in some example embodiments, transceivers 18 and 28 may be included in or may form a part of transceiving circuitry.

[0085] For instance, in certain example embodiments, apparatus 10 may be controlled by memory 14 and processor 12 to receive a user equipment capability or a user equipment traffic requirement from a responding user equipment. Apparatus 10 may also be controlled by memory 14 and processor 12 to receive a channel occupancy time sharing scope indication from a network element. Apparatus 10 may further be controlled by memory 14 and processor 12 to determine a channel occupancy time sharing scope based on the user equipment capability or the user equipment traffic requirement or the channel occupancy time sharing scope indication. In addition, apparatus 10 may be controlled by memory 14 and processor 12 to determine a channel occupancy time resource allocation for the responding user equipment. Further, apparatus 10 may be controlled by memory 14 and processor 12 to transmit a channel occupancy time resource sharing indication to the responding user equipment based on the determined channel occupancy time sharing scope and / or the determined resource allocation.

[0086] In other example embodiments, apparatus 10 may be controlled by memory 14 and processor 12 to transmit a user equipment capability or a user equipment traffic requirement to a network element or an initiator user equipment. Apparatus 10 may also be controlled by memory 14 and processor 12 to receive a channeloccupancy time resource sharing indication from the initiator user equipment based on a determined channel occupancy time sharing scope and / or a determined resource allocation. Apparatus 10 may further be controlled by memory 14 and processor 12 to determine a transmission time gap in response to the channel occupancy time resource sharing indication.

[0087] In other example embodiments, apparatus 20 may be controlled by memory 24 and processor 22 to configure a responding user equipment to share a capability or traffic requirement. Apparatus 20 may also be controlled by memory 24 and processor 22 to receive, based on the configuration, the responding user equipment capability or the responding user equipment traffic requirement from the responding user equipment. Apparatus 20 may further be controlled by memory 24 and processor 22 to determine a channel occupancy time sharing scope based on the responding user equipment capability or the responding user equipment traffic requirement. In addition, apparatus 20 may be controlled by memory 24 and processor 22 to transmit a channel occupancy time sharing scope indication to an initiator user equipment based on the channel occupancy time sharing scope.

[0088] In some example embodiments, an apparatus (e.g., apparatus 10 and / or apparatus 20) may include means for performing a method, a process, or any of the variants discussed herein. Examples of the means may include one or more processors, memory, controllers, transmitters, receivers, and / or computer program code for causing the performance of the operations.

[0089] Certain example embodiments may be directed to an apparatus that includes means for performing any of the methods described herein including, for example, means for receiving a user equipment capability or a user equipment traffic requirement from a responding user equipment. The apparatus may also include means for receiving a channel occupancy time sharing scope indication from a network element. The apparatus may also include means for determining a channel occupancy time sharing scope based on the user equipment capability or the user equipment traffic requirement or the channel occupancy time sharing scope indication. The apparatus may further include means for determining a channel occupancy time resource allocation for the responding user equipment. In addition,the apparatus may include means for transmitting a channel occupancy time resource sharing indication to the responding user equipment based on the determined channel occupancy time sharing scope and / or the determined resource allocation.

[0090] Other example embodiments may be directed to an apparatus that includes means for performing any of the methods described herein including, for example, means for transmitting a user equipment capability or a user equipment traffic requirement to a network element or an initiator user equipment. The apparatus may also include means for receiving a channel occupancy time resource sharing indication from the initiator user equipment based on a determined channel occupancy time sharing scope and / or a determined resource allocation. The apparatus may further include means for determining a transmission time gap in response to the channel occupancy time resource sharing indication.

[0091] Other example embodiments may be directed to an apparatus that includes means for performing any of the methods described herein including, for example, means for configuring a responding user equipment to share a capability or traffic requirement. The apparatus may also include means for receiving, based on the configuration, the responding user equipment capability or the responding user equipment traffic requirement from the responding user equipment. The apparatus may further include means for determining a channel occupancy time sharing scope based on the responding user equipment capability or the responding user equipment traffic requirement. In addition, the apparatus may include means for transmitting a channel occupancy time sharing scope indication to an initiator user equipment based on the channel occupancy time sharing scope.

[0092] Certain example embodiments described herein provide several technical improvements, enhancements, and / or advantages in respect to UE energy saving by performing shorter LBT (e.g., different LBT Type). For instance, in some example embodiments, it may be possible to provide a framework for optimized COT utilization, ensuring fair distribution, and enabling RedCap devices to efficiently access communication channels and perform critical tasks in the presence of non- RedCap UEs.

[0093] A computer program product may include one or more computer-executablecomponents which, when the program is run, are configured to carry out some example embodiments. The one or more computer-executable components may be at least one software code or portions of it. Modifications and configurations required for implementing functionality of certain example embodiments may be performed as routine(s), which may be implemented as added or updated software routine(s). Software routine(s) may be downloaded into the apparatus.

[0094] As an example, software or a computer program code or portions of it may be in a source code form, object code form, or in some intermediate form, and it may be stored in some sort of carrier, distribution medium, or computer readable medium, which may be any entity or device capable of carrying the program. Such carriers may include a record medium, computer memory, read-only memory, photoelectrical and / or electrical carrier signal, telecommunications signal, and software distribution package, for example. Depending on the processing power needed, the computer program may be executed in a single electronic digital computer or it may be distributed amongst a number of computers. The computer readable medium or computer readable storage medium may be a non-transitory medium.

[0095] In other example embodiments, the functionality may be performed by hardware or circuitry included in an apparatus (e.g., apparatus 10 or apparatus 20), for example through the use of an application specific integrated circuit (ASIC), a programmable gate array (PGA), a field programmable gate array (FPGA), or any other combination of hardware and software. In yet another example embodiment, the functionality may be implemented as a signal, a non-tangible means that can be carried by an electromagnetic signal downloaded from the Internet or other network.

[0096] According to certain example embodiments, an apparatus, such as a node, device, or a corresponding component, may be configured as circuitry, a computer or a microprocessor, such as single-chip computer element, or as a chipset, including at least a memory for providing storage capacity used for arithmetic operation and an operation processor for executing the arithmetic operation.

[0097] One having ordinary skill in the art will readily understand that the disclosure as discussed above may be practiced with procedures in a different order, and / or withhardware elements in configurations which are different than those which are disclosed. Therefore, although the disclosure has been described based upon these example embodiments, it would be apparent to those of skill in the art that certain modifications, variations, and alternative constructions would be apparent, while remaining within the spirit and scope of example embodiments. Although the above embodiments refer to 5G NR and LTE technology, the above embodiments may also apply to any other present or future 3GPP technology, such as LTE-advanced, and / or fourth generation (4G) technology.

[0098] Partial Glossary:

[0099] 3GPP 3rd Generation Partnership Project

[0100] 5G 5th Generation

[0101] 5GCN 5G Core Network

[0102] 5GS 5G System

[0103] BS Base Station

[0104] CAPC Channel Access Priority Class

[0105] CCA Clear Channel Assessment

[0106] COT Channel Occupancy Time

[0107] CWS Contention Window Size

[0108] DL Downlink

[0109] eNB Enhanced Node B

[0110] E-UTRAN Evolved UTRAN

[0111] gNB 5G or Next Generation NodeB

[0112] GP Guard Period

[0113] IQ In-phase and Quadrature-phase

[0114] LBT Listen-B efore-T alk

[0115] LTE Long Term Evolution

[0116] ML Machine Learning

[0117] NR New Radio

[0118] PQI PC5 QoS Identifier

[0119] PSCCH Physical Sidelink Control Channel

[0120] PSFCH Physical Sidelink Feedback Channel

[0121] PSSCH Physical Sidelink Shared Channel

[0122] RAT Radio Access Technology

[0123] RedCap Reduced Capability

[0124] RP Resource Pool

[0125] UE User Equipment

[0126] UL Uplink

Claims

WE CLAIM:

1. A method comprising: receiving a user equipment capability or a user equipment traffic requirement from a responding user equipment; receiving a channel occupancy time sharing scope indication from a network element; determining a channel occupancy time sharing scope based on the user equipment capability or the user equipment traffic requirement or the channel occupancy time sharing scope indication; determining a channel occupancy time resource allocation for the responding user equipment; and transmitting a channel occupancy time resource sharing indication to the responding user equipment based on the determined channel occupancy time sharing scope and / or the determined resource allocation.

2. The method according to claim 1 , wherein the determination of the channel occupancy time sharing scope comprises determining a channel occupancy time sharing priority.

3. The method according to claim 1, wherein the determination of the channel occupancy time sharing scope is based on: whether both a channel occupancy time initiator and the responding user equipment are reduced capability user equipment, wherein sharing of the channel occupancy time is offered from one reduced capability user equipment to another reduced capability user equipment.

4. The method according to claim 1 , wherein the determination of the channel occupancy time sharing scope is based on: prioritizing a reduced capability user equipment over a non-reduced capability user equipment based on a capability of the reduced capability userequipment.

5. The method according to claim 1, wherein the determination of the channel occupancy time sharing scope is based on: prioritizing channel occupancy time responders with traffic requirements that satisfy channel occupancy time sharing requirements.

6. The method according to claim 1 , wherein the determination of the channel occupancy time sharing scope is based on: prioritizing a reduced capability user equipment over a non-reduced capability user equipment based on a capability of the reduced capability user equipment, and prioritizing channel occupancy time responders with traffic requirements that satisfy channel occupancy time sharing requirements.

7. A method, comprising: transmitting a user equipment capability or a user equipment traffic requirement to a network element or an initiator user equipment; receiving a channel occupancy time resource sharing indication from the initiator user equipment based on a determined channel occupancy time sharing scope and / or a determined resource allocation; and determining a transmission time gap in response to the channel occupancy time resource sharing indication.

8. The method according to claim 7, further comprising: determining a listen-before-talk type based on the transmission time gap.

9. A method, comprising: configuring a responding user equipment to share a capability or traffic requirement; receiving, based on the configuration, the responding user equipmentcapability or the responding user equipment traffic requirement from the responding user equipment; determining a channel occupancy time sharing scope based on the responding user equipment capability and / or the responding user equipment traffic requirement; and transmitting a channel occupancy time sharing scope indication to an initiator user equipment based on the channel occupancy time sharing scope.

10. An apparatus, comprising: at least one processor; and at least one memory storing instructions, wherein the instructions, when executed by the at least one processor, cause the apparatus at least to receive a user equipment capability or a user equipment traffic requirement from a responding user equipment; receive a channel occupancy time sharing scope indication from a network element; determine a channel occupancy time sharing scope based on the user equipment capability or the user equipment traffic requirement or the channel occupancy time sharing scope indication; determine a channel occupancy time resource allocation for the responding user equipment; and transmit a channel occupancy time resource sharing indication to the responding user equipment based on the determined channel occupancy time sharing scope and / or the determined resource allocation.

11. The apparatus according to claim 10, wherein the determination of the channel occupancy time sharing scope comprises determining a channel occupancy time sharing priority.

12. The apparatus according to claim 10, wherein the determination of the channel occupancy time sharing scope is based on:whether both a channel occupancy time initiator and the responding user equipment are reduced capability user equipment, wherein sharing of the channel occupancy time is offered from one reduced capability user equipment to another reduced capability user equipment.

13. The apparatus according to claim 10, wherein the determination of the channel occupancy time sharing scope is based on: prioritizing a reduced capability user equipment over a non-reduced capability user equipment based on a capability of the reduced capability user equipment.

14. The apparatus according to claim 10, wherein the determination of the channel occupancy time sharing scope is based on: prioritizing channel occupancy time responders with traffic requirements that satisfy channel occupancy time sharing requirements.

15. The apparatus according to claim 10, wherein the determination of the channel occupancy time sharing scope is based on: prioritizing a reduced capability user equipment over a non-reduced capability user equipment based on a capability of the reduced capability user equipment, and prioritizing channel occupancy time responders with traffic requirements that satisfy channel occupancy time sharing requirements.

16. An apparatus, comprising: at least one processor; and at least one memory storing instructions, wherein the instructions, when executed by the at least one processor, cause the apparatus at least to transmit a user equipment capability or a user equipment traffic requirement to a network element or an initiator user equipment; receive a channel occupancy time resource sharing indication from theinitiator user equipment based on a determined channel occupancy time sharing scope and / or a determined resource allocation; and determine a transmission time gap in response to the channel occupancy time resource sharing indication.

17. The apparatus according to claim 7, wherein the instructions, when executed by the at least one processor, cause the apparatus at least to: determine a listen-before-talk type based on the transmission time gap.

18. An apparatus, comprising: at least one processor; and at least one memory storing instructions, wherein the instructions, when executed by the at least one processor, cause the apparatus at least to configure a responding user equipment to share a capability or traffic requirement; receive, based on the configuration, the responding user equipment capability and / or the responding user equipment traffic requirement from the responding user equipment; determine a channel occupancy time sharing scope based on the responding user equipment capability or the responding user equipment traffic requirement; and transmit a channel occupancy time sharing scope indication to an initiator user equipment based on the channel occupancy time sharing scope.

19. An apparatus, comprising: means for receiving a user equipment capability or a user equipment traffic requirement from a responding user equipment; means for receiving a channel occupancy time sharing scope indication from a network element; means for determining a channel occupancy time sharing scope based on the user equipment capability or the user equipment traffic requirement or the channel occupancy time sharing scope indication;means for determining a channel occupancy time resource allocation for the responding user equipment; and means for transmitting a channel occupancy time resource sharing indication to the responding user equipment based on the determined channel occupancy time sharing cope and / or the determined resource allocation.

20. The apparatus according to claim 19, wherein the determination of the channel occupancy time sharing scope comprises determining a channel occupancy time sharing priority.

21. The apparatus according to claim 19, wherein the determination of the channel occupancy time sharing scope is based on: whether both a channel occupancy time initiator and the responding user equipment are reduced capability user equipment, wherein sharing of the channel occupancy time is offered from one reduced capability user equipment to another reduced capability user equipment.

22. The apparatus according to claim 19, wherein the determination of the channel occupancy time sharing scope is based on: prioritizing a reduced capability user equipment over a non-reduced capability user equipment based on a capability of the reduced capability user equipment.

23. The apparatus according to claim 19, wherein the determination of the channel occupancy time sharing scope is based on: prioritizing channel occupancy time responders with traffic requirements that satisfy channel occupancy time sharing requirements.

24. The apparatus according to claim 19, wherein the determination of the channel occupancy time sharing scope is based on: prioritizing a reduced capability user equipment over a non-reducedcapability user equipment based on a capability of the reduced capability user equipment, and prioritizing channel occupancy time responders with traffic requirements that satisfy channel occupancy time sharing requirements.

25. An apparatus, comprising: means for transmitting a user equipment capability or a user equipment traffic requirement to a network element or an initiator user equipment; means for receiving a channel occupancy time resource sharing indication from the initiator user equipment based on a determined channel occupancy time sharing scope and / or a determined resource allocation; and means for determining a transmission time gap in response to the channel occupancy time resource allocation indication.

26. The apparatus according to claim 25, further comprising: means for determining a listen-before-talk type based on the transmission time gap.

27. An apparatus, comprising: means for configuring a responding user equipment to share a capability or traffic requirement; receiving, based on the configuration, the responding user equipment capability or the responding user equipment traffic requirement from the responding user equipment; determining a channel occupancy time sharing scope based on the responding user equipment capability and / or the responding user equipment traffic requirement; and transmitting a channel occupancy time sharing scope indication to an initiator user equipment based on the channel occupancy time sharing scope.

28. A non-transitory computer readable medium comprising programinstructions that, when executed by a processor, cause an apparatus to perform a method according to any of claims 1-9.

29. An apparatus comprising circuitry configured to cause the apparatus to perform the process according to any of claims 1-9.

Images