Channel occupancy time sharing and power saving for reduced capability devices

Abstract

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

Description

Cross-references to applications related to channel occupancy time sharing and energy saving for devices with reduced capabilities

[0001] This application relates to and claims priority to Indian Provisional Patent Application No. 202341067047, filed on October 6, 2023, the entire contents of which are incorporated herein by reference. Technical Field

[0002] Some example embodiments typically relate to mobile or wireless telecommunications systems, such as Long Term Evolution (LTE) or 5th Generation (5G) New Radio (NR) access technologies, or 5G and above, or 6th Generation (6G) access technologies, or other communication systems. For example, some example embodiments may relate to apparatus, systems, and / or methods for Channel Occupancy Time (COT) sharing and energy saving for Capability Reduction (RedCap) devices. Background Technology

[0003] Examples of mobile or wireless telecommunications systems can include Universal Mobile Telecommunications System (UMTS) Terrestrial Radio Access Network (UTRAN), Evolved UTRAN (E-UTRAN) for Long Term Evolution (LTE), LTE-Advanced (LTE-A), MulteFire, LTE-APro, 5G or New Radio (NR) access technologies, and / or 6G radio access technologies. 5G and 6G radio systems refer to next-generation (NG) radio systems and network architectures. While 5G and 6G network technologies are primarily based on New Radio (NR) technology, 5G / 6G (or NG) networks can also be built on E-UTRAN radio. It is estimated that NR can provide bit rates of approximately 10-20 Gbit / s or higher and can at least support enhanced mobile broadband (eMBB) and ultra-reliable low-latency communication (URLLC) as well as massive machine-type communication (mMTC). NR is expected to provide extremely wideband and ultra-robust, low-latency connectivity and massive networking to support the Internet of Things (IoT). Summary of the Invention

[0004] Some example embodiments may relate to a method. This method may include receiving user equipment capabilities or user equipment service requirements from a responding user equipment. The method may also include receiving a channel occupancy time sharing range indication from a network element. The method may further include determining a channel occupancy time sharing range based on the user equipment capabilities, user equipment service requirements, or the channel occupancy time sharing range indication. Additionally, the method may include determining a channel occupancy time resource allocation for the responding user equipment. Furthermore, the method may include sending a channel occupancy time resource sharing indication to the responding user equipment based on the determined channel occupancy time sharing range and / or the determined resource allocation.

[0005] Other example embodiments may relate 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 to at least: receive user equipment capabilities or user equipment service requirements from a responding user equipment. The apparatus may also be configured to receive a channel occupancy time sharing range indication from a network element. The apparatus may further be configured to determine a channel occupancy time sharing range based on the user equipment capabilities or user equipment service requirements or the channel occupancy time sharing range indication. Additionally, the apparatus may be configured to determine a channel occupancy time resource allocation for the responding user equipment. Furthermore, the apparatus may be configured to send a channel occupancy time resource sharing indication to the responding user equipment based on the determined channel occupancy time sharing range and / or the determined resource allocation.

[0006] Other example embodiments may relate to an apparatus. The apparatus may include components for receiving user equipment capabilities or user equipment service requirements from a responding user equipment. The apparatus may also include components for receiving a channel occupancy time sharing range indication from a network element. The apparatus may further include components for determining a channel occupancy time sharing range based on the user equipment capabilities or user equipment service requirements or the channel occupancy time sharing range indication. Additionally, the apparatus may include components for determining a channel occupancy time resource allocation for the responding user equipment. Furthermore, the apparatus may include components for sending a channel occupancy time resource sharing indication to the responding user equipment based on the determined channel occupancy time sharing range and / or the determined resource allocation.

[0007] According to other example embodiments, a non-transitory computer-readable medium may be encoded with instructions that, when executed in hardware, can perform a method. The method may include receiving user equipment capabilities or user equipment service requirements from a responding user equipment. The method may also include receiving a channel occupancy time sharing range indication from a network element. The method may further include determining a channel occupancy time sharing range based on the user equipment capabilities, user equipment service requirements, or the channel occupancy time sharing range indication. Additionally, the method may include determining a channel occupancy time resource allocation for the responding user equipment. Furthermore, the method may include sending a channel occupancy time resource sharing indication to the responding user equipment based on the determined channel occupancy time sharing range and / or the determined resource allocation.

[0008] Other example embodiments may relate to a computer program product that performs a method. The method may include receiving user equipment capabilities or user equipment service requirements from a responding user equipment. The method may also include receiving a channel occupancy time sharing range indication from a network element. The method may further include determining a channel occupancy time sharing range based on the user equipment capabilities, user equipment service requirements, or the channel occupancy time sharing range indication. Additionally, the method may include determining a channel occupancy time resource allocation for the responding user equipment. Furthermore, the method may include sending a channel occupancy time resource sharing indication to the responding user equipment based on the determined channel occupancy time sharing range and / or the determined resource allocation.

[0009] Other example embodiments may involve an apparatus that may include circuitry configured to receive user equipment capabilities or user equipment service requirements from a responding user equipment. The apparatus may also include circuitry configured to receive a channel occupancy time sharing range indication from a network element. The apparatus may further include circuitry configured to determine a channel occupancy time sharing range based on the user equipment capabilities, user equipment service requirements, or the channel occupancy time sharing range indication. Additionally, the apparatus may include circuitry configured to determine a channel occupancy time resource allocation for the responding user equipment. Furthermore, the apparatus may include circuitry configured to send a channel occupancy time resource sharing indication to the responding user equipment based on the determined channel occupancy time sharing range and / or the determined resource allocation.

[0010] Some example embodiments may relate to a method. This method may include sending user equipment capabilities or user equipment service requirements to a network element or initiating user equipment. The method may also include receiving a channel occupancy time resource sharing indication from the initiating user equipment based on a determined channel occupancy time resource sharing range and / or a determined resource allocation. The method may further include determining a transmission time interval in response to the channel occupancy time resource sharing indication.

[0011] Other example embodiments may relate to an apparatus. The apparatus may include at least one processor and at least one memory storing instructions, wherein, when executed by the at least one processor, the instructions cause the apparatus to at least: transmit user equipment capabilities or user equipment service requirements to a network element or initiating user equipment. The apparatus may also be configured to receive a channel occupancy time resource sharing indication from the initiating user equipment based on a determined channel occupancy time resource sharing range and / or a determined resource allocation. The apparatus may also be configured to determine a transmission time interval in response to the channel occupancy time resource sharing indication.

[0012] Other example embodiments may relate to an apparatus. The apparatus may include components for transmitting user equipment capabilities or user equipment service requirements to a network element or initiating user equipment. The apparatus may also include components for receiving a channel occupancy time resource sharing indication from the initiating user equipment based on a determined channel occupancy time resource sharing range and / or a determined resource allocation. The apparatus may further include components for determining a transmission time interval in response to the channel occupancy time resource sharing indication.

[0013] According to other example embodiments, a non-transitory computer-readable medium may be encoded with instructions that, when executed in hardware, can perform a method. The method may include sending user equipment capabilities or user equipment service requirements to a network element or initiating user equipment. The method may also include receiving a channel occupancy time resource sharing indication from the initiating user equipment based on a determined channel occupancy time resource sharing range and / or a determined resource allocation. The method may further include determining a transmission time interval in response to the channel occupancy time resource sharing indication.

[0014] Other example embodiments may relate to a computer program product that performs a method. The method may include sending user equipment capabilities or user equipment service requirements to a network element or initiating user equipment. The method may also include receiving a channel occupancy time resource sharing indication from the initiating user equipment based on a determined channel occupancy time resource sharing range and / or a determined resource allocation. The method may further include determining a transmission time interval in response to the channel occupancy time resource sharing indication.

[0015] Other example embodiments may involve an apparatus that may include circuitry configured to transmit user equipment capabilities or user equipment service requirements to a network element or initiating user equipment. The apparatus may also include circuitry configured to receive a channel occupancy time resource sharing indication from the initiating user equipment based on a determined channel occupancy time resource sharing range and / or a determined resource allocation. The apparatus may further include circuitry configured to determine a transmission time interval in response to the channel occupancy time resource sharing indication.

[0016] Some example embodiments may relate to a method. This method may include configuring a responding user equipment (UE) to share capabilities or service requirements. The method may also include receiving, based on the configuration, the responding UE's capabilities or service requirements from it. The method may further include determining a channel occupancy time (COT) sharing range based on the responding UE's capabilities and / or service requirements. Additionally, the method may include sending a COT sharing range indication to the initiating UE based on the COT sharing range.

[0017] Other example embodiments may relate 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 to at least: configure a responding user equipment to share capability or service requirements. The apparatus may also be configured to receive, based on the configuration, a responding user equipment capability or a responding user equipment service requirement from the responding user equipment. The apparatus may also be configured to determine a channel occupancy time sharing range based on the responding user equipment capability and / or the responding user equipment service requirement. Additionally, the apparatus may be configured to send a channel occupancy time sharing range indication to the initiating user equipment based on the channel occupancy time sharing range.

[0018] Other example embodiments may relate to an apparatus. The apparatus may include components for configuring a responding user equipment (UE) to share capability or service requirements. The apparatus may also include components for receiving a responding UE's capability or service requirement from the responding UE based on the configuration. The apparatus may further include components for determining a channel occupancy time (COT) sharing range based on the responding UE's capability and / or COT service requirement. Additionally, the apparatus may include components for sending a COT sharing range indication to the initiating UE based on the COT sharing range.

[0019] According to other example embodiments, a non-transitory computer-readable medium may be encoded with instructions that, when executed in hardware, can perform a method. The method may include configuring a responding user equipment (UE) to share capabilities or service requirements. The method may also include receiving, based on the configuration, a responding UE capability or a responding UE service requirement from the responding UE. The method may further include determining a channel occupancy time sharing range based on the responding UE capability and / or the responding UE service requirement. Additionally, the method may include sending a channel occupancy time sharing range indication to the initiating UE based on the channel occupancy time sharing range.

[0020] Other example embodiments may relate to a computer program product that performs a method. The method may include configuring a responding user equipment (UE) to share capabilities or service requirements. The method may also include receiving, based on the configuration, a responding UE capability or a responding UE service requirement from the responding UE. The method may further include determining a channel occupancy time sharing range based on the responding UE capability and / or the responding UE service requirement. Additionally, the method may include sending a channel occupancy time sharing range indication to the initiating UE based on the channel occupancy time sharing range.

[0021] Other example embodiments may involve an apparatus that may include circuitry configured to respond to a user equipment (UE) to share capability or service requests. The apparatus may also include circuitry configured to receive a responding UE capability or a responding UE service request from the responding UE based on the configuration. The apparatus may further include circuitry configured to determine a channel occupancy time (COT) sharing range based on the responding UE capability and / or the responding UE service request. Additionally, the apparatus may include circuitry configured to send a COT sharing range indication to the initiating UE based on the COT sharing range. Attached Figure Description

[0022] To properly understand the example embodiments, reference should be made to the accompanying drawings, in which: Figure 1 illustrates the idle channel assessment (CCA) slots.

[0023] Figure 2 shows an example of obtaining the Channel Occupied Time (COT) by the initiating device.

[0024] Figure 3 shows an example table of Channel Access Priority Classes (CAPCs) associated with services of user equipment.

[0025] Figure 4 illustrates example behavior associated with a competing window.

[0026] Figure 4B illustrates another example of behavior associated with a competition window.

[0027] Figure 4C illustrates yet another example of behavior associated with a competition window.

[0028] Figure 5A shows an example of the permissible gaps for which the Listen Before You Speak (LBT) Type 2 variant applies.

[0029] Figure 5B shows another example of the permissible gap applicable to the LBT type 2 variant.

[0030] Figure 5C shows yet another example of the permissible gap to which the LBT Type 2 variant applies.

[0031] Figure 5D shows yet another example of the permissible gap applicable to the LBT type 2 variant.

[0032] Figure 5E shows another example of the permissible gap applicable to LBT type 2 variant.

[0033] Figure 5F shows another example of the permissible gap applicable to LBT type 2 variant.

[0034] Figure 6 shows an example signal flow diagram according to some example embodiments.

[0035] Figure 7 shows an example flowchart of a method according to some example embodiments.

[0036] Figure 8 shows an example flowchart of another method according to some example embodiments.

[0037] Figure 9 shows an example flowchart of another method according to some example embodiments.

[0038] Figure 10 illustrates a collection of devices according to certain example embodiments. Detailed Implementation

[0039] It will be readily understood that, as generally described and illustrated in the accompanying drawings, components of certain example embodiments can be arranged and designed in a 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 capacity-reduced (RedCap) devices.

[0040] The features, structures, or characteristics of the exemplary embodiments described throughout this specification can be combined in any suitable manner in one or more exemplary embodiments. For example, throughout this specification, the use of the phrases "certain embodiments," "exemplary embodiments," "some embodiments," or other similar language 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. Therefore, the phrases "in some embodiments," "exemplary embodiments," "in some embodiments," "in other embodiments," or other similar language appearing throughout this specification do not necessarily refer to the same set of embodiments, and the described features, structures, or characteristics can be combined in any suitable manner in one or more exemplary embodiments. Furthermore, the terms "base station," "cell," "node," "gNB," "network," or other similar language throughout this specification are used interchangeably.

[0041] As used herein, “at least one of the following: a list of two or more elements” and “at least one of the following: a list of two or more elements” and similar wording (where a list of two or more elements is connected by “and”, “or” or “and / or”) means at least any one of the elements, or at least any two or more of the elements, or at least all of the elements.

[0042] 5G New Radio Unlicensed (NR-U) is an operating mode of the 3rd Generation Partnership Project (3GPP) Release 16, which provides the necessary technology for cellular operations to integrate unlicensed spectrum into 5G networks. In NR-U, channel access in both the downlink (DL) and uplink (UL) relies on Listen-After-Talk (LBT). The radio device or base station (BS) first senses the communication channel to determine that there is no communication before any transmission. LBT parameters (e.g., type / duration, idle channel assessment parameters, etc.) are configured by the BS.

[0043] 5G NR-U can include various types of LBT procedures, including, for example, Type 1 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 allow UE / next-generation Node B (gNB) to share a COT previously acquired by the gNB / UE. LBT Type 2 is further classified into Type 2A (25μs LBT), Type 2B (16μs LBT), and Type 2C (no LBT). COT refers to the total duration for which a particular radio device (such as an evolved Node B (eNB), gNB, or UE) participates in transmissions on a specific communication channel along with any other associated eNB / gNB / UE. This duration includes transmissions that occur after the eNB / gNB / UE has completed the necessary channel access procedures. The COT architecture reduces power consumption and channel access latency.

[0044] 3GPP has introduced a Layer 1 RedCap device, also known as NR-light. This is a category of devices that bridges the capability and complexity gap between Low Power Wide Area (LPWA) and URLCC usage in 5G by leveraging optimized designs for intermediate layer use cases. The devices operate across the FR1 and FR2 frequency ranges, adapting to both Frequency Division Duplex (FDD) and Time Division Duplex (TDD). Supporting maximum device bandwidths of 20 MHz (FR1) and 100 MHz (FR2), NR-light comprises at least one Rx antenna (FR1) and two Rx antennas (FR2) per device. NR-light targets scenarios with lower performance requirements and cost constraints, offering smaller physical sizes and longer battery life.

[0045] In unlicensed frequency bands below 7 GHz, the LBT (Low-Leaf Channel Assessment) mechanism can be used to ensure the coexistence of NR with other systems (e.g., IEEE 802.11). A UE intending to perform a side-link (SL) transmission must successfully complete an LBT check before it can initiate an SL transmission. LBT can also be referred to as the Free Channel Assessment (CCA) or the channel access procedure.

[0046] To enable the UE to pass the LBT check, the channel can be observed as available for multiple consecutive CCA slots. For example, in the sub-7 GHz range, these slots have a duration of 9 μs, as shown in Figure 1. Specifically, Figure 1 shows an example CCA slot with a duration of Tsl = 9 μs, where energy detection occurs during a 4 μs period. If the measured power (i.e., the energy collected during the CCA slot) is below a specified energy detection threshold (EDT) (which can depend on transmit power, operating band, and geographic region), the UE can consider the channel available in the CCA slot.

[0047] Figure 2 illustrates an example of an initiating device acquiring COT via LTB Type 1. When a UE initiates communication (i.e., the UE acts as the initiating device), the UE can acquire "authority" to access a channel for a specific time period, represented as COT, by applying an "extended" LBT procedure, where the channel can be considered idle for the entire duration of the contention window (CW). The "extended" LBT procedure can be referred to as LBT Type 1.

[0048] Figure 3 shows an example table of Channel Access Priority Classes (CAPCs) associated with services of the User Equipment (UE). The durations of both COT and CW can depend on the Channel Access Priority Class (CAPC) associated with the UE's services, as shown in Figure 3. Control plane services (e.g., Physical Shared Control Channel) can be transmitted using p=1, while user plane services have p>1. Figure 3 shows LBT type 1 and depicts details of the Uu UL case. However, LBT type 1 can also be used in the DL case in SL. In other cases, as further shown in Figure 3, the contention window length in the CCA slot associated with each CAPC has a minimum value (CW). min, p ) and maximum value (CW) max， p The duration of COT is determined by T. ulm cot,p Provided.

[0049] Figures 4A through 4C illustrate various example behaviors associated with contention windows. Specifically, Figure 4A shows a scenario where neither the delay time nor the countdown is interrupted (i.e., the channel is not detected as busy during the sensing slot). Figure 4B shows a scenario where the delay time is interrupted (i.e., the channel is detected as busy during the delay time sensing slot). Figure 4C shows a scenario where the contention window countdown is interrupted (i.e., the channel is detected as busy during the countdown sensing slot). As shown in Figures 4A through 4C, T d This refers to delaying the time, T sl This refers to the duration of the CCA slot, and N refers to the number of CCA slots that need to be considered idle before the contention window countdown is complete. As shown in Figures 4A to 4C, if the LBT check fails during the countdown process in the delay time or in any CCA slot, the countdown can be stopped and restarted.

[0050] Figures 5A to 5F illustrate various examples of the permissible gaps applicable to the Listen-Before-Speak (LBT) Type 2 variant. Upon successful completion of LBT Type 1 and execution of a transmission, the UE initiating the transmission (e.g., the initiating device / UE) can acquire a COT with a duration associated with the corresponding CAPC. The acquired COT can remain valid even when the initiating device suspends its transmission, although a “reduced” LBT procedure may be required if the initiating device wishes to execute a new transmission (within the COT). This “reduced” LBT procedure is referred to as LBT Type 2.

[0051] LBT type 2 can include several variations. For example, one variation can include type 2A (25μs LBT) for SL transmissions within a COT acquired by the initiating device (when the gap between two SL transmissions is ≥25μs), and for SL transmissions following another SL transmission (see Figures 5C and 5F). In type 2B (16μs LBT), for SL transmissions within a COT acquired by the initiating device, this can be used for SL transmissions following another SL, where the gap is exactly equal to 16μs, as shown in Figures 5B and 5E. For type 2C (no LBT), this can be used for SL transmissions following another SL, where the gap is <16μs and the permissible duration of the SL transmission is ≤584μs, as shown in Figures 5A and 5D.

[0052] The initiating device can share its acquired COT with its intended receiver (the responding device). To do this, the initiating device can (e.g., via control signaling) inform the responding device of the duration of the COT. The responding device can then use this information to determine which type of LBT should be applied when performing a transmission whose intended receiver is the initiating device. If the responding device's transmission falls outside the COT, the responding device will have to use LBT type 1 with the appropriate CAPC to acquire a new COT.

[0053] In NR-U, COT sharing can be achieved from gNB to UE / from UE to gNB. Responding devices (i.e., COT-sharing devices) can transmit DL / UL transmissions with relaxed LBT requirements (Type 2A / B / C). Additionally, with the introduction of RedCap, NR devices can facilitate the expansion of the NR device ecosystem to cater to use cases such as industrial wireless sensors, video surveillance, and wearable devices. When a RedCap device or any device operates on unlicensed spectrum, it must perform LBT to access the radio channel as a regulatory requirement. Furthermore, the COT-sharing functionality for RedCap devices can serve as a catalyst for energy efficiency and enable RedCap devices to address other functionalities.

[0054] Currently, COT sharing is not supported for RedCap devices (e.g., RedCap UEs). Therefore, RedCap devices lack the ability to benefit from the energy-saving mechanisms and enhanced features facilitated by COT sharing. Consequently, power-constrained RedCap devices cannot save energy by performing reduced LBT or by not performing channel access when the Type 2C (no LBT) standard is met. For RedCap devices to utilize COT sharing functionality, the COT-initiating device or UE must be adapted to a COT sharing mechanism that gives RedCap devices an advantage over non-RedCap devices. To cover this adaptation, a comprehensive approach is needed to consider the different aspects of the COT-responding device, which are influenced by the capabilities of the RedCap device.

[0055] Connections with extreme communication requirements and limited coverage and device capabilities can be installed in locations demanding high performance, such as in vehicles, indoors, or even within the human body. This type of network is called a subnetwork and can be part of a 6G coverage network infrastructure. Devices part of a subnetwork ecosystem need to be efficient in terms of connectivity and energy consumption, as they support life-critical services in some cases. In one such example, RedCap devices and COT-sharing mechanisms are expected to be part of this subnetwork.

[0056] For RedCap devices to utilize COT sharing functionality, the COT initiating device or UE must adapt to the COT sharing mechanism, which allows RedCap devices to benefit from non-RedCap devices that may exist in the environment. This adaptation covers multiple aspects of the COT responding device, depending on the RedCap UE's capabilities. The COT initiating device needs to tune the sharing mechanism to pave the way for RedCap devices to take precedence over non-RedCap devices and meet RedCap device requirements.

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

[0058] For example, one option could involve providing COT sharing from one RedCap UE to another, prioritizing non-RedCap UEs. Another option could involve prioritizing RedCap UEs over non-RedCap UEs based on their capabilities. Yet another option could involve prioritizing the service requirements of COT responder UEs that meet COT sharing requirements. Yet another option could involve combining the prioritization of RedCap UEs with the prioritization of COT responder UEs' service requirements to select equipment for COT sharing to achieve efficient resource allocation. These options can provide a framework for optimizing COT utilization, ensuring fair distribution, and enabling RedCap equipment to efficiently access communication channels and perform critical tasks in the presence of non-RedCap equipment (e.g., non-RedCap UEs).

[0059] When both RedCap and non-RedCap devices coexist within communication range, a fair COT sharing mechanism is crucial for RedCap devices to leverage the features provided by the COTS mechanism and use energy efficiently. Therefore, when a COTS-capable UE shares its COT with another device or its communicating device, some 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 exemplary embodiments, a COT initiator (e.g., a COT-initiating UE) may share its COT with another device. For example, a COT initiator may initially be enabled to share its COT with its communicating UE (in the case of multicast or multicast services). In some exemplary embodiments, the COT-initiating UE may support the minimum bandwidth required to perform LBT. Additionally, the COT-initiating UE may determine which UE shares its COT by using at least one or more various criteria.

[0061] In some exemplary embodiments, a standard may include allowing the COT-initiating UE to share COT with one or more RedCap UEs over any other non-RedCap UE when both the COT-initiating UE and the responding UE are RedCap UEs. Under this standard, when the COT initiator itself is a RedCap UE, the initiating RedCap UE may be prioritized over non-RedCap UEs. Alternatively, according to another standard, the initiating UE may prioritize RedCap UEs over non-RedCap UEs based on reported RedCap UE capabilities. Under this standard, the COT responding UE may report its minimum bandwidth requirements, 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 standard, the COT-initiating UE may (optionally) broadcast its COT-sharing standard to the intended responding UE. Furthermore, under this standard, the initiating UE may configure a table to map the capabilities of UEs sharing COT resources. For example, an example embodiment may use principles to design the mapping table. The responding UE with limited RedCap capabilities may have the highest priority. Otherwise, the responsive UE with the highest capability can have the lowest priority in the mapping table. This mapping table can be updated if and when any UE is added to or removed from the communication device list. Additionally, under this standard, time-multiplexed COT sharing can be applied to share COT resources with multiple responsive UEs, without exceeding the COT duration.

[0062] In other example embodiments, service requirements of COT responders that meet COT requirements can be given priority. For example, minimum bandwidth requirements can be used to determine one or more responding devices to share the COT. In some example embodiments, a COT responder can successfully complete its transmission within the available COT duration. In this example embodiment, a COT responder that cannot meet the COT requirements may not participate in COT sharing. In other example embodiments, a table can be configured by the COT initiator to map the service requirements of COT responders. For example, mapping can be used to design a mapping table. Additionally, COT responders with higher CAPC (CAPC associated with the UE's service) can receive the highest priority. Otherwise, COT responders with the lowest CAPC can receive the lowest priority in the mapping table.

[0063] According to some example embodiments, the initiating UE prioritizes RedCap UEs over non-RedCap UEs, and the prioritization of COT responders' service requirements can be combined. Additionally, this combination may include the ability to create a mapping table containing the RedCap UE capabilities and service requirements of the COT responders. If the COT initiator has both UE capability and service requirement information, COT resource allocation for the COT initiator may be more efficient. In this example embodiment, if the COT responder UE has critical service requirements and lower RedCap capabilities compared to another RedCap device, the responder UE may receive COT resources prior to other RedCap UEs. Otherwise, if only one option is considered (e.g., UE priority of RedCap UEs over non-RedCap UEs, or priority of COT responder's service requirements), the responder UE selected by this method may not have been prioritized. Furthermore, in some example embodiments, allocating COT resources to RedCap UEs with stringent requirements (such as energy-constrained or bandwidth-constrained) may be more efficient. In some exemplary embodiments, when the COT initiator has information including, for example, RedCap capabilities and / or the COT responder's service requirements, a first option prioritizing RedCap UEs over non-RedCap UEs based on the reported RedCap capabilities, a second option prioritizing the COT responder's service requirements, and a third option combining the first and second options can be applied. This information can be shared directly between the COT responder and the COT initiator via SL UE auxiliary information or via BS Radio Resource Control (RRC) signaling, as described below with respect to Figure 6.

[0064] Figure 6 illustrates an example signaling flow diagram according to certain example embodiments. As shown in Figure 6, the signaling flow involves COT responder 600, COT initiator 605, and BS 610. At 615, a PC5 link can be established between COT responder 600 and COT initiator 605. At 620, UEs (e.g., COT responder 600 and / or COT initiator 606) can be configured by BS 610 to share COT sharing capabilities / service requirements for SL communication. At 625, BS 610 can determine the COT sharing scope based on the capabilities / service requirements of COT responder 600 (e.g., RedCap UE) according to any one or more of the above options. For example, BS 610 can prioritize RedCap UEs based on their capabilities (e.g., a UE with minimal equipment capabilities is prioritized over a UE with better equipment capabilities). Similar criteria can also be applied when service requirements are considered to prioritize one RedCap UE over another. In some example embodiments, after BS 610 / COT initiator 605 checks whether COT responder 600 can actually be serviced by COT sharing based on the received service requirements / equipment capabilities of COT responder 600, the COT sharing scope may include a prioritized list of COT responders. At 630, BS 610 may send a COT sharing scope indication to COT initiator 605 based on the determined COT sharing scope. For example, in some example embodiments, BS 610 may indicate a list of UEs preferentially used for COT sharing based on the determined COT sharing scope.

[0065] At 635, COT initiator 605 can acquire the COT. For example, at 635, when COT initiator 605 performs LBT (as a regulatory requirement) to acquire a radio channel, COT initiator 605 can share its COT with another UE. At 640, COT initiator 605 can determine the COT sharing range based on RedCap UE capabilities / service requirements and / or the COT sharing range indication received from BS 610, according to any one or more of the above options. For example, in some example embodiments, the COT responder with the least equipment capability can be given first priority, and the COT responder with the highest equipment capability can be given last priority. In some example embodiments, the equipment capability / service requirements of the COT responder can be shared with BS 610 and COT initiator 605. Therefore, at 640, COT initiator 605 can perform substantially the same operation as BS 610 at 625. However, the difference between the COT sharing range determined at BS 610 and the COT sharing range determined at COT initiator 605 could be that BS 610 determines the range in the case of SL mode 1 communication, while COT initiator 605 determines the COT sharing range in the case of SL mode 2 communication. Therefore, it can be seen that the difference between these two operating modes is that in mode 1, the resources used by the UE-to-UE link can be allocated by BS 605; in mode 2, public (pre-configured) resources can be shared autonomously between UEs without the intervention of BS 610. Therefore, in some example embodiments, at least for SL mode 2 communication, steps 625 and 630 can be skipped / omitted.

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

[0067] Figure 7 illustrates an example flowchart of a method according to certain example embodiments. In example embodiments, the method of Figure 7 can be performed by a network entity or a group of multiple network elements in a 3GPP system such as LTE or 5G-NR. For example, in an example embodiment, the method of Figure 7 can be performed by a COT initiating device (e.g., a UE), similar to one of the apparatus 10 or 20 shown in Figure 10.

[0068] As shown in Figure 7, the method may include: at 700, receiving user equipment capabilities or user equipment service requirements from the responding user equipment. The method may also include: at 705, receiving a channel occupancy time sharing range indication from a network element. The method may further include: at 710, determining a channel occupancy time sharing range based on the user equipment capabilities, user equipment service requirements, or the channel occupancy time sharing range indication. Additionally, the method may include: at 715, determining a channel occupancy time resource allocation for the responding user equipment. In some example embodiments, the resource allocation is determined based on the determined channel occupancy time sharing range. Furthermore, the method may include: at 720, sending a channel occupancy time resource sharing indication to the responding user equipment based on the determined channel occupancy time sharing range and / or the determined resource allocation.

[0069] According to some example embodiments, determining the channel occupancy time sharing range may include: determining the channel occupancy time sharing priority. In some example embodiments, the COT sharing priority may include a list of priority COT responders. According to some example embodiments, the determination of the channel occupancy time sharing range is based on whether both the channel occupancy time initiator and the responding user equipment are degraded user equipments. According to some example embodiments, channel occupancy time sharing can be provided from one degraded user equipment to another. According to other example embodiments, the determination of the channel occupancy time sharing range is based on: prioritizing degraded user equipment over non-degraded user equipment based on the capabilities of the degraded user equipment.

[0070] In some example embodiments, the determination of the channel occupancy time sharing range is based on: prioritizing channel occupancy time responders with service requirements that satisfy the channel occupancy time sharing requirements. In some example embodiments, the determination of the channel occupancy time sharing range is based on: prioritizing capability-reduced user equipment (User Equipment) over non-capability-reduced User Equipment (User Equipment) based on the capability of the capability-reduced User Equipment; and prioritizing channel occupancy time responders with service requirements that satisfy the channel occupancy time sharing requirements.

[0071] Figure 8 illustrates an example flowchart of a method according to certain example embodiments. In example embodiments, the method of Figure 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 example, in an example embodiment, the method of Figure 8 may be performed by a COT responder device (e.g., UE), similar to one of the apparatus 10 or 20 shown in Figure 10.

[0072] As shown in Figure 8, the method may include: at 800, sending user equipment capabilities or user equipment service requirements to the network element or the initiating user equipment. The method may further include: at 805, receiving a channel occupancy time resource sharing indication from the initiating user equipment based on the determined channel occupancy time sharing range and / or the determined resource allocation. The method may further include: at 810, determining a transmission time interval in response to the received channel occupancy time resource sharing indication. According to some example embodiments, the method may further include determining a listen-before-speak type based on the transmission time interval.

[0073] Figure 9 illustrates an example flowchart of another method according to certain example embodiments. In the example embodiments, the method of Figure 9 can be performed by a network entity or a group of multiple network elements in a 3GPP system such as LTE or 5G-NR. For example, in the example embodiments, the method of Figure 9 can be performed by a BS, gNB, or network, similar to one of the devices 10 or 20 shown in Figure 10.

[0074] As shown in Figure 9, the method may include: at 900, configuring the responding user equipment to share capabilities or service requirements. The method may further include: at 905, receiving the responding user equipment's capabilities or service requirements from the responding user equipment based on the configuration. The method may further include: at 910, determining the channel occupancy time sharing range based on the responding user equipment's capabilities and / or service requirements. Additionally, the method may include: at 915, sending a channel occupancy time sharing range indication to the initiating user equipment based on the channel occupancy time sharing range.

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

[0076] In some example embodiments, devices 10 and 20 may include one or more processors, one or more computer-readable storage media (e.g., memory, storage device, etc.), one or more radio access components (e.g., modems, transceivers, etc.), and / or user interfaces. In some example embodiments, devices 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 technology. It should be noted that those skilled in the art will understand that devices 10 and 20 may include components or features not shown in FIG. 10.

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

[0078] Processors 12 and 22 can perform functions associated with the operation of devices 10 and 20, including, for example, precoding of antenna gain / phase parameters, encoding and decoding of individual bits forming communication messages, formatting of information, and overall control of devices 10 and 20, including the processes and examples shown in Figures 1 through 9.

[0079] Devices 10 and 20 may also include or be coupled to memories 14 and 24 (internal or external), which may be coupled to processors 12 and 24, respectively, for storing information and instructions that can be executed by processors 12 and 24. Memories 14 and 24 may be one or more memories of any type suitable for the local application environment and may be implemented using any suitable volatile or non-volatile data storage technology, such as semiconductor-based memory devices, magnetic memory devices and systems, optical memory devices and systems, fixed memory, and / or removable memory. For example, memories 14 and 24 may include any combination of random access memory (RAM), read-only memory (ROM), static storage devices such as disks or optical discs, hard disk drives (HDDs), or any other type of non-transitory machine or computer-readable medium. Instructions stored in memories 14 and 24 may include program instructions or computer program code that, when executed by processors 12 and 22, enable devices 10 and 20 to perform the tasks described herein.

[0080] In some exemplary embodiments, devices 10 and 20 may also include or be coupled to an (internal or external) drive or port configured to accept and read external computer-readable storage media, such as an optical disc, USB drive, flash drive, or any other storage media. For example, the external computer-readable storage media may store computer programs or software executed by processors 12 and 22 and / or devices 10 and 20 to perform any of the methods and examples shown in Figures 1 through 9.

[0081] In some example embodiments, devices 10 and 20 may further include or be coupled to one or more antennas 15 and 25 for receiving downlink signals and for transmitting from devices 10 and 20 via UL. Devices 10 and 20 may also include transceivers 18 and 28 configured to transmit and receive information. Transceivers 18 and 28 may also include radio interfaces (e.g., modems) coupled to antennas 15 and 25. The radio interface may correspond to a variety 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, etc. The radio interface may include other components such as filters, converters (e.g., digital-to-analog converters, etc.), symbol demappers, signal shaping components, inverse fast Fourier transform (IFFT) modules, etc., to process symbols carried by the downlink or UL, such as OFDMA symbols.

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

[0083] In some example embodiments, memories 14 and 34 store software modules that provide functionality when executed by processors 12 and 22. These modules may include, for example, an operating system that provides operating system functionality for devices 10 and 20. The memories may also store one or more functional modules, such as applications or programs, to provide additional functionality to devices 10 and 20. Components of devices 10 and 20 may be implemented in hardware or as any suitable combination of hardware and software. According to some example embodiments, devices 10 and 20 may optionally be configured to communicate with each other via a wireless or wired communication link 70 (in any combination) based on any radio access technology, such as NR.

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

[0085] For example, in some example embodiments, apparatus 10 may be controlled by memory 14 and processor 12 to receive user equipment capabilities or user equipment service requirements from a responding user equipment. Apparatus 10 may also be controlled by memory 14 and processor 12 to receive a channel occupancy time sharing range indication from a network element. Apparatus 10 may also be controlled by memory 14 and processor 12 to determine a channel occupancy time sharing range based on user equipment capabilities or user equipment service requirements or the channel occupancy time sharing range indication. Furthermore, apparatus 10 may be controlled by memory 14 and processor 12 to determine a channel occupancy time resource allocation for the responding user equipment. Additionally, apparatus 10 may be controlled by memory 14 and processor 12 to send a channel occupancy time resource sharing indication to the responding user equipment based on the determined channel occupancy time sharing range and / or the determined resource allocation.

[0086] In other example embodiments, device 10 may be controlled by memory 14 and processor 12 to send user equipment capabilities or user equipment service requirements to network elements or initiating user equipment. Device 10 may also be controlled by memory 14 and processor 12 to receive a channel occupancy time resource sharing indication from the initiating user equipment based on a determined channel occupancy time resource sharing range and / or a determined resource allocation. Device 10 may also be controlled by memory 14 and processor 12 to determine a transmission time interval in response to the channel occupancy time resource sharing indication.

[0087] In other example embodiments, device 20 may be controlled by memory 24 and processor 22 to configure a responding user equipment to share capabilities or service requirements. Device 20 may also be controlled by memory 24 and processor 22 to receive responding user equipment capabilities or service requirements from the responding user equipment based on the configuration. Device 20 may also be controlled by memory 24 and processor 22 to determine a channel occupancy time sharing range based on the responding user equipment capabilities or service requirements. Furthermore, device 20 may be controlled by memory 24 and processor 22 to send a channel occupancy time sharing range indication to the initiating user equipment based on the channel occupancy time sharing range.

[0088] In some example embodiments, the apparatus (e.g., apparatus 10 and / or apparatus 20) may include components for performing the methods, processes, or any variations discussed herein. Examples of such components may include one or more processors, memory, controllers, transmitters, receivers, and / or computer program code for inducing the execution of operations.

[0089] Some example embodiments may relate to an apparatus including components for performing any of the methods described herein, including, for example, components for receiving user equipment capabilities or user equipment service requirements from a responding user equipment. The apparatus may also include components for receiving a channel occupancy time sharing range indication from a network element. The apparatus may further include components for determining a channel occupancy time sharing range based on the user equipment capabilities or user equipment service requirements or the channel occupancy time sharing range indication. The apparatus may also include components for determining a channel occupancy time resource allocation for the responding user equipment. Additionally, the apparatus may include components for sending a channel occupancy time resource sharing indication to the responding user equipment based on the determined channel occupancy time sharing range and / or the determined resource allocation.

[0090] Other example embodiments may relate to an apparatus including components for performing any of the methods described herein, including, for example, components for transmitting user equipment capabilities or user equipment service requirements to a network element or initiating user equipment. The apparatus may further include components for receiving a channel occupancy time resource sharing indication from the initiating user equipment based on a determined channel occupancy time resource sharing range and / or a determined resource allocation. The apparatus may also include components for determining a transmission time interval in response to the channel occupancy time resource sharing indication.

[0091] Other example embodiments may relate to an apparatus including components for performing any of the methods described herein, including, for example, components for configuring a responding user equipment (UE) to share capabilities or service requirements. The apparatus may also include components for receiving UE capabilities or UE service requirements from the responding UE based on the configuration. The apparatus may further include components for determining a channel occupancy time (COT) sharing range based on the UE capabilities or UE service requirements. Additionally, the apparatus may include components for sending a COT sharing range indication to the initiating UE based on the COT sharing range.

[0092] Certain example embodiments described herein provide several technical improvements, enhancements, and / or advantages regarding UE power efficiency by performing shorter LBTs (e.g., different LBT types). For example, in some example embodiments, a framework can be provided for optimizing 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-executable components configured to perform some example embodiments during program runtime. The one or more computer-executable components may be at least one piece of software code or a portion thereof. Modifications and configurations required to implement the functionality of certain example embodiments may be executed as routines, which may be implemented as added or updated software routines. The software routines may be downloaded to the device.

[0094] As an example, software or computer program code, or portions thereof, may be in the form of source code, object code, or some intermediate form, and may be stored in some carrier, distribution medium, or computer-readable medium, which may be any entity or device capable of carrying the program. Such a carrier may include, for example, recording media, computer memory, read-only memory, photoelectric and / or electrical carrier signals, telecommunication signals, and software distribution packages. Depending on the required processing power, the computer program may be executed in a single electronic digital computer or may be distributed across multiple computers. The computer-readable medium or computer-readable storage medium may be a non-transitory medium.

[0095] In other example embodiments, the function may be performed by hardware or circuitry included in the device (e.g., device 10 or device 20), for example by using 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 function may be implemented as a signal, a non-tangible component that may be carried by an electromagnetic signal downloaded from the Internet or other networks.

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

[0097] It will be readily understood by those skilled in the art that the present disclosure as described above can be practiced with processes of a different sequence and / or with hardware elements in a configuration different from the disclosed configuration. Therefore, although the present disclosure has been described based on these exemplary embodiments, it will be apparent to those skilled in the art that certain modifications, variations, and alternative constructions will be readily apparent while remaining within the spirit and scope of the exemplary embodiments. While the above embodiments relate to 5G NR and LTE technologies, the above embodiments can also be applied to any other current or future 3GPP technologies, such as LTE-Advanced and / or fourth-generation (4G) technologies.

[0098] Partial Glossary: ​​3GPP Third Generation Partnership Project, 5G 5th Generation, 5GCN, 5G Core Network, 5GS, 5G System, BS Base Station, CAPC Channel Access Priority Class, CCA Idle Channel Assessment, COT Channel Occupancy Time, CWS Contention Window Size, DL Downlink, eNB Enhanced Node, BE-UTRAN Evolution, UTRAN gNB, 5G or Next Generation Node, BGP Protection Period, IQ In-phase and Quadrature Phase, LBT Listen-After-Speak, LTE Long Term Evolution, ML Machine Learning, NR New Radio, PQ, IPC5 QoS Identifier, PSCCH Physical Side Link Control Channel, PSFCH Physical Side Link Feedback Channel, PSSCH Physical Side Link Shared Channel, RAT Radio Access Technology, RedCap Capability Reduction, RP Resource Pool, UE User Equipment, UL Uplink

Claims

1. A method comprising: From receiving user equipment capabilities or user equipment service requirements in response to user equipment; from receiving channel occupancy time sharing range indications from network elements; The channel occupancy time sharing range is determined based on the user equipment capabilities, user equipment service requirements, or the channel occupancy time sharing range indication; the channel occupancy time resource allocation for the responding user equipment is determined. And based on the determined channel occupancy time sharing range and / or the determined resource allocation, send a channel occupancy time resource sharing indication to the responding user equipment.

2. The method according to claim 1, wherein the determination of the channel occupancy time sharing range includes: Determine the priority of channel occupancy time sharing.

3. The method according to claim 1, wherein the determination of the channel occupancy time sharing range is based on whether both the channel occupancy time initiator and the responding user equipment are degraded user equipments, wherein the sharing of channel occupancy time is provided from one degraded user equipment to another degraded user equipment.

4. The method of claim 1, wherein the determination of the channel occupancy time sharing range is based on: prioritizing the degraded user equipment over the non-degraded user equipment based on the capabilities of the degraded user equipment.

5. The method according to claim 1, wherein the determination of the channel occupancy time sharing range is based on: prioritizing channel occupancy time responders that meet the service requirements for channel occupancy time sharing.

6. The method of claim 1, wherein the determination of the channel occupancy time sharing range is based on: prioritizing the degraded user equipment over the non-degraded user equipment according to the capabilities of the degraded user equipment, and prioritizing the channel occupancy time responders with service requirements that meet the channel occupancy time sharing requirements.

7. A method comprising: Send user equipment capabilities or user equipment service requirements to the network element or the initiating user equipment; Based on the determined channel occupancy time sharing range and / or the determined resource allocation, receive the channel occupancy time resource sharing indication from the initiating user equipment; And determine the transmission time gap in response to the channel occupancy time resource sharing indication.

8. The method according to claim 7, further comprising: The "listen first, speak later" type is determined based on the transmission time gap.

9. A method comprising: Configure the responding user equipment to share capabilities or service requirements; based on the configuration, receive the responding user equipment capabilities or the responding user equipment service requirements from the responding user equipment; The channel occupancy time sharing range is determined based on the capabilities of the responding user equipment and / or the service requirements of the responding user equipment; and a channel occupancy time sharing range indication is sent to the initiating user equipment based on the channel occupancy time sharing range.

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 to at least: receive user equipment capabilities or user equipment service requirements from a responding user equipment; receive a channel occupancy time sharing range indication from a network element; determine a channel occupancy time sharing range based on the user equipment capabilities or the user equipment service requirements or the channel occupancy time sharing range indication; and determine a channel occupancy time resource allocation for the responding user equipment. And based on the determined channel occupancy time sharing range and / or the determined resource allocation, send a channel occupancy time resource sharing indication to the responding user equipment.

11. The apparatus of claim 10, wherein the determination of the channel occupancy time sharing range comprises: Determine the priority of channel occupancy time sharing.

12. The apparatus of claim 10, wherein the determination of the channel occupancy time sharing range is based on whether both the channel occupancy time initiator and the responding user equipment are degraded user equipments, wherein the sharing of channel occupancy time is provided from one degraded user equipment to another.

13. The apparatus of claim 10, wherein the determination of the channel occupancy time sharing range is based on prioritizing the degraded user equipment over the non-degraded user equipment according to the capabilities of the degraded user equipment.

14. The apparatus of claim 10, wherein the determination of the channel occupancy time sharing range is based on: prioritizing channel occupancy time responders that meet the service requirements for channel occupancy time sharing.

15. The apparatus of claim 10, wherein the determination of the channel occupancy time sharing range is based on: prioritizing the degraded user equipment over the non-degraded user equipment according to the capabilities of the degraded user equipment, and prioritizing the channel occupancy time responders having service requirements that satisfy the 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 device to at least: send user equipment capabilities or user equipment service requirements to a network element or initiating user equipment; and receive a channel occupancy time resource sharing indication from the initiating user equipment based on a determined channel occupancy time sharing range and / or a determined resource allocation. And determine the transmission time gap in response to the channel occupancy time resource sharing indication.

17. The apparatus of claim 7, wherein the instructions, when executed by the at least one processor, cause the apparatus to at least: determine a listen-before-speak 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 device to at least: configure a responsive user equipment to share capabilities or service requirements; and, based on the configuration, receive the responsive user equipment capabilities and / or the responsive user equipment service requirements from the responsive user equipment; The channel occupancy time sharing range is determined based on the capabilities of the responding user equipment or the service requirements of the responding user equipment; and a channel occupancy time sharing range indication is sent to the initiating user equipment based on the channel occupancy time sharing range.

19. An apparatus comprising: Components used to receive user equipment capabilities or user equipment service requests from user equipment in response; A component used to receive a channel occupancy time sharing range indication from network elements; Components for determining the channel occupancy time sharing range based on the user equipment capabilities, the user equipment service requirements, or the channel occupancy time sharing range indication; Components used to determine the allocation of channel occupancy time resources for the responding user equipment; And a component for sending a channel occupancy time resource sharing indication to the responding user equipment based on the determined channel occupancy time sharing range and / or the determined resource allocation.

20. The apparatus of claim 19, wherein the determination of the channel occupancy time sharing range comprises: Determine the priority of channel occupancy time sharing.

21. The apparatus of claim 19, wherein the determination of the channel occupancy time sharing range is based on whether both the channel occupancy time initiator and the responding user equipment are degraded user equipments, wherein the sharing of channel occupancy time is provided from one degraded user equipment to another.

22. The apparatus of claim 19, wherein the determination of the channel occupancy time sharing range is based on prioritizing the degraded user equipment over the non-degraded user equipment according to the capabilities of the degraded user equipment.

23. The apparatus of claim 19, wherein the determination of the channel occupancy time sharing range is based on: prioritizing channel occupancy time responders that meet the service requirements for channel occupancy time sharing.

24. The apparatus of claim 19, wherein the determination of the channel occupancy time sharing range is based on: prioritizing the degraded user equipment over the non-degraded user equipment according to the capabilities of the degraded user equipment, and prioritizing the channel occupancy time responder having service requirements that satisfy the channel occupancy time sharing requirements.

25. An apparatus comprising: Components used to send user equipment capabilities or user equipment service requirements to network elements or initiating user equipment; A component for receiving a channel occupancy time resource sharing indication from the initiating user equipment based on the determined channel occupancy time sharing range and / or the determined resource allocation; And components for determining transmission time gaps in response to the channel occupancy time resource allocation indication.

26. The apparatus of claim 25, further comprising: A component used to determine the "listen first, speak later" type based on the transmission time gap.

27. An apparatus comprising: Components used to configure user equipment to share capabilities or service requirements; Based on the configuration, receive the capabilities of the responding user equipment or the service requirements of the responding user equipment from the responding user equipment; The channel occupancy time sharing range is determined based on the capabilities of the responding user equipment and / or the service requirements of the responding user equipment; and a channel occupancy time sharing range indication is sent to the initiating user equipment based on the channel occupancy time sharing range.

28. A non-transitory computer-readable medium comprising program instructions that, when executed by a processor, cause a device to perform the method according to any one of claims 1 to 9.

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

Images