Techniques for duplicating channel occupancy time sharing information

Abstract

Various aspects of the present disclosure generally relate to wireless communications. In some aspects, a first user equipment (UE) may receive COT sharing information (COT-SI) associated with a first portion of a channel occupancy time (COT) from a second UE via a sidelink. The UE may identify, based at least in part on the COT-SI, a qualified repeater UE for which the first UE is the COT-SI. The UE may transmit a communication using a first portion of the COT based at least in part on the first UE being a qualified repeater UE of the COT-SI, the communication including duplicated COT-SI. Numerous other aspects are described.

Description

TECHNICAL FIELD

[0001] Aspects of the disclosure relate generally to wireless communication, and to techniques and apparatuses for repeating channel occupancy time sharing information.

[0002] DESCRIPTION OF RELATED ART

[0003] Wireless communication systems are widely deployed to provide various telecommunication services such as telephony, video, data, messaging, and broadcasts. Typical wireless communication systems can employ multiple-access technologies capable of supporting communication with multiple users by sharing available system resources (e.g., bandwidth, transmit power, etc.). Examples of such multiple-access technologies include code division multiple access (CDMA) systems, time division multiple access (TDMA) systems, frequency division multiple access (FDMA) systems, orthogonal frequency division multiple access (OFDMA) systems, single-carrier frequency division multiple access (SC-FDMA) systems, time division synchronous code division multiple access (TD-SCDMA) systems, and long term evolution (LTE). LTE / LTE-Advanced is a set of enhancements to the Universal Mobile Telecommunications System (UMTS) mobile standard promulgated by the Third Generation Partnership Project (3 GPP).

[0004] A wireless network can include one or more network nodes that support communication for wireless communication devices, such as a user equipment (UE) or multiple UEs. A UE can communicate with a network node via downlink communications and uplink communications. “Downlink” (or “DL”) refers to

[0005] These multiple access technologies have been adopted in various telecommunication standards to provide common protocols that enable different wireless devices to communicate on a municipal, national, regional, and even global level. New Radio (NR), which can also be referred to as 5G, is a set of enhancements to the LTE mobile standard promulgated by the Third Generation Partnership Project (3GPP). NR is designed to better support mobile broadband Internet access by improving spectral efficiency, lowering costs, improving services, utilizing new spectrum, and better integrating with other open standards using orthogonal frequency division multiplexing (OFDM) with cyclic prefix (CP) (CP-OFDM) on the downlink, CP-OFDM or single-carrier frequency division multiplexing (SC-FDM) (also known as discrete Fourier transform spread OFDM (DFT-s-OFDM)) on the uplink, and support beamforming, multiple input multiple output (MIMO) antenna technology, and carrier aggregation. SUMMARY

[0006] Some aspects described herein relate to a method of wireless communication performed by a first user equipment (UE). The method can include receiving, from a second UE via a sidelink, channel occupancy time (COT) sharing information (COT-SI) associated with a first portion of a COT. The method can include identifying, based at least in part on the COT-SI, that the first UE is a qualified repeater UE of the COT-SI. The method can include transmitting, by the first UE and based at least in part on the first UE being the qualified repeater UE of the COT-SI, a communication using the first portion of the COT, the communication including a repetition of the COT-SI.

[0007] Some aspects described herein relate to a method of wireless communication performed by a first user equipment (UE). The method can include receiving, from a second UE via a sidelink, channel occupancy time (COT) sharing information (COT-SI) associated with a first portion of a COT. The method can include identifying, based at least in part on the COT-SI, that the first UE is a qualified repeater UE of the COT-SI. The method can include transmitting, by the first UE and based at least in part on the first UE being the qualified repeater UE of the COT-SI, a communication using the first portion of the COT, the communication including a repetition of the COT-SI.

[0008] Some aspects described herein relate to a first UE for wireless communication. The first UE can include a memory and one or more processors coupled to the memory. The one or more processors can be configured to receive, from a second UE via a sidelink, COT-SI associated with a first portion of a COT. The one or more processors can be configured to identify, based at least in part on the COT-SI, that the first UE is a qualified repeater UE of the COT-SI. The one or more processors can be configured to transmit, based at least in part on the first UE being the qualified repeater UE of the COT-SI, a communication using the first portion of the COT, the communication including a repetition of the COT-SI.

[0009] Some aspects described herein relate to a first UE for wireless communication. The first UE can include a memory and one or more processors coupled to the memory. The one or more processors can be configured to receive, from a second UE via a sidelink, COT-SI associated with a first portion of a COT. The one or more processors can be configured to identify, based at least in part on the COT-SI, that the first UE is a qualified repeater UE of the COT-SI. The one or more processors can be configured to transmit, based at least in part on the first UE being the qualified repeater UE of the COT-SI, a communication using the first portion of the COT, the communication including a repetition of the COT-SI.

[0010] Some aspects described herein relate to a non-transitory computer-readable medium storing a set of instructions for wireless communication by a first UE. The set of instructions, when executed by one or more processors of the first UE, can cause the first UE to receive, via a sidelink from a second UE, a COT-SI associated with a first portion of a COT. The set of instructions, when executed by the one or more processors of the first UE, can cause the first UE to identify, based at least in part on the COT-SI, that the first UE is a qualified repeater UE for the COT-SI. The set of instructions, when executed by the one or more processors of the first UE, can cause the UE to transmit, based at least in part on the first UE being the qualified repeater UE for the COT-SI, a communication using the first portion of the COT, the communication including a repeated COT-SI.

[0011] Some aspects described herein relate to a non-transitory computer-readable medium storing a set of instructions for wireless communication by a first UE. The set of instructions, when executed by one or more processors of the first UE, can cause the first UE to receive, via a sidelink from a second UE, a COT-SI associated with a first portion of a COT. The set of instructions, when executed by the one or more processors of the first UE, can cause the first UE to identify, based at least in part on the COT-SI, that the first UE is a qualified repeater UE for the COT-SI. The set of instructions, when executed by the one or more processors of the first UE, can cause the UE to transmit, based at least in part on the first UE being the qualified repeater UE for the COT-SI, a communication using the first portion of the COT, the communication including a repeated COT-SI.

[0012] Some aspects described herein relate to an apparatus for wireless communication. The apparatus can include means for receiving, via a sidelink from a UE, a COT-SI associated with a first portion of a COT. The apparatus can include means for identifying, based at least in part on the COT-SI, that the apparatus is a qualified repeater for the COT-SI. The apparatus can include means for transmitting, based at least in part on the apparatus being the qualified repeater for the COT-SI, a communication using the first portion of the COT, the communication including a repeated COT-SI.

[0013] Some aspects described herein relate to an apparatus for wireless communication. The apparatus can include means for receiving, via a sidelink from a UE, a COT-SI associated with a first portion of a COT. The apparatus can include means for identifying, based at least in part on the COT-SI, that the apparatus is a qualified repeater for the COT-SI. The apparatus can include means for transmitting, based at least in part on the apparatus being the qualified repeater for the COT-SI, a communication using the first portion of the COT, the communication including a repeated COT-SI.

[0014] Aspects generally include a method, apparatus, system, computer program product, non-transitory computer-readable medium, user equipment, base station, network entity, network node, wireless communication device, and / or processing system as substantially described herein with reference to and as illustrated by the drawings and specification.

[0015] The foregoing has outlined rather broadly the features and technical advantages of examples according to the disclosure in order that the detailed description that follows can be better understood. Additional features and advantages will be described below. The disclosed concepts and specific examples can be readily utilized as bases upon which the other structures can be built employing the principles of the disclosure. Such equivalent constructions do not depart from the scope of the claims. The characteristics of the concepts disclosed herein, both their organization and their method of operation, together with associated advantages will be better understood from the following description when considered in connection with the accompanying drawings. Each of the figures is provided for the purpose of illustration and description, and is not intended as a definition of the limits of the disclosure. BRIEF DESCRIPTION OF DRAWINGS

[0016] So that the above-recited features of the present disclosure can be understood in detail, a more particular description, which aspects, some of which are illustrated in the appended drawings, will be rendered by reference to the detailed description below. It is to be understood that the appended drawings are intended to be illustrative and not limiting of the disclosure. Like reference numerals in different drawings can identify the same or similar elements.

[0017] Figure 1 is a diagram illustrating an example of a wireless network, in accordance with the present disclosure.

[0018] Figure 2 is a diagram illustrating an example of a network node communicating with user equipment (UE) in a wireless network, in accordance with the present disclosure.

[0019] Figure 3 is a diagram illustrating an example disaggregated base station architecture, in accordance with the present disclosure.

[0020] Figure 4 is a diagram illustrating an example of sidelink and access link communications, in accordance with the present disclosure.

[0021] Figures 5A-5B is a diagram illustrating an example of sidelink communications, in accordance with the present disclosure.

[0022] Figure 6 is a diagram illustrating an example associated with sharing information of a repetition channel occupancy time, in accordance with the present disclosure.

[0023] Figure 7 is a diagram illustrating an example process performed, for example, by a first UE, in accordance with the present disclosure.

[0024] Figure 8 is a diagram illustrating an example process performed, for example, by a first UE, in accordance with the present disclosure.

[0025] Figure 9 is a diagram of an example apparatus for wireless communication, in accordance with the present disclosure. DETAILED DESCRIPTION

[0026] In some wireless communications systems, one or more network entities can communicate using unlicensed spectrum. For example, two or more user equipments (UEs) communicating via a sidelink can communicate in an unlicensed band, sometimes referred to as a sidelink unlicensed (SL-U). In such cases, a first UE, sometimes referred to as an initiating UE, an initiator UE, and / or a channel occupancy time (COT) initiator UE, can perform a listen before talk (LBT) procedure or similar procedure to contend for access to the unlicensed channel. The LBT procedure can result in the initiating UE gaining access to the unlicensed channel for a duration referred to as a COT, during which the initiating UE can perform transmissions without performing additional LBT operations. In some cases, the initiating UE can share the COT with other UEs, sometimes referred to as responding UEs, responder UEs, or COT responder UEs. To enable the responding UEs to utilize a portion of the COT, sometimes referred to as a shareable region of the COT, the initiating UE can transmit certain information about the COT (e.g., using sidelink control information (SCI)), sometimes referred to as COT sharing information (COT-SI). The COT-SI can include information such as an indication of a channel access priority class (CAPC) associated with the COT, a remaining COT duration in the shareable region of the COT, a layer 1 (L1) identifier (ID) associated with the COT (e.g., an L1 destination ID, an L1 source ID, and / or a similar L1 ID), an indication of one or more resource block (RB) sets associated with the COT, an additional ID associated with the COT (e.g., a COT sharing ID), and / or other information associated with the COT. Based at least in part on the information indicated by the COT-SI, the responding UEs can utilize resources within the shareable region of the COT for sidelink transmissions.

[0027] In some cases, one or more responding UEs can not successfully receive the COT-SI. For example, the initiating UE can transmit SCI containing the COT-SI in a first time slot of the COT, which can be missed by half-duplex UEs that are otherwise communicating (e.g., transmitting) during that time. This can result in underutilized resources, increased congestion between sidelink UEs, and / or inefficient use of network resources in other ways, as some responding UEs can perform otherwise unnecessary LBT procedures and / or reserve additional resources for sidelink communications instead of utilizing available resources in the shareable region of the COT. In such cases, it can be desirable to permit responding UEs to carry the COT-SI within their own transmitted SCI (sometimes referred to as COT-SI repetition and / or COT-SI forwarding), such as to redundantly share the COT-SI multiple times during the COT to ensure that all eligible UEs receive the COT-SI. However, COT-SI forwarding performed by multiple responding UEs can result in high signaling overhead and / or congested channels. Furthermore, responding UEs that receive the forwarded COT-SI can not be able to identify whether the UE can use the COT to respond to an initiating UE or a relay UE, resulting in communication errors, and thus high power, computation, and network resource consumption associated with correcting the communication errors.

[0028] Some techniques and apparatuses described herein enable efficient COT-SI forwarding in UE-to-UE COT sharing applications. In some aspects, a responding UE can receive a COT-SI associated with a shareable region of a COT. The responding UE can identify whether it is an eligible relay UE for the COT-SI, which can be based at least in part on whether the responding UE is a data recipient of the initiating UE, whether the responding UE is a target UE of the COT sharing, whether the responding UE is within a given range of the initiating UE, whether the responding UE is able to decode the COT-SI, or whether the responding UE satisfies other criteria. In aspects where the responding UE is an eligible relay UE for the COT-SI, the responding UE can repeat and / or forward the COT-SI when transmitting a communication in the shareable region of the COT, thereby repeating the COT-SI for certain UEs that can have otherwise missed the COT-SI from the initiating UE due to half-duplex operation or for other reasons. Thus, the repeated COT-SI can result in more eligible UEs receiving the COT-SI, which can result in more efficient use of network resources and reduced congestion between sidelink UEs. Furthermore, the COT-SI can be distributed among UEs in an efficient manner and in a manner such that the responding UEs can correctly identify the initiating UE of the COT, resulting in reduced communication errors, and thus reduced power, computation, and network resource consumption that would otherwise be required for communication errors.

[0029] Various aspects of the disclosure are described more fully below with reference to the accompanying drawings. This disclosure may, however, be embodied in many different forms and should not be construed as limited to any specific structure or function presented throughout this disclosure. Rather, these aspects are provided so that this disclosure will be thorough and complete, and will fully convey the scope of the disclosure to those skilled in the art. One skilled in the art will appreciate that the scope of the disclosure is intended to cover any aspect of the disclosure disclosed herein, whether implemented independently of or combined with any other aspect of the disclosure. For example, an apparatus can be implemented or a method can be practiced using any number of the aspects set forth herein. In addition, the scope of the disclosure is intended to cover such an apparatus or method which is practiced using other structure, functionality, or structure and functionality in addition to or other than the various aspects of the disclosure set forth herein. It will be understood that any aspect of the disclosure disclosed herein can be implemented by one or more elements of a claim.

[0030] Several aspects of telecommunication systems will now be presented with reference to various apparatus and methods. These apparatus and methods will be described in the following detailed description and illustrated in the accompanying drawings by various blocks, modules, components, circuits, steps, processes, or algorithms, among other examples (collectively referred to as “elements”). These elements can be implemented using hardware, software, or combinations thereof. Whether such elements are implemented as hardware or software depends on the particular application and design constraints imposed on the overall system.

[0031] While aspects can be described herein using terminology commonly associated with a 5G or New Radio (NR) radio access technology (RAT), aspects of the present disclosure can be applied to other RATs, such as a 3G RAT, a 4G RAT, and / or a RAT subsequent to 5G (e.g., 6G).

[0032] Figure 1is a diagram illustrating an example of a wireless network 100, in accordance with aspects of the present disclosure. The wireless network 100 can be or include elements of a 5G (e.g., NR) network or a 4G (e.g., Long Term Evolution (LTE)) network, among other examples. The wireless network 100 can include one or more network nodes 110 (shown as network node 110a, network node 110b, network node 110c, and network node 110d), one UE 120, or multiple UEs 120 (shown as UE 120a, UE 120b, UE 120c, UE 120d, and UE 120e), or other entities. The network nodes 110 are examples of network nodes that communicate with the UEs 120. As illustrated, the network nodes 110 can include one or more network nodes. For example, the network nodes 110 can be an aggregated network node, meaning that the aggregated network node is configured to utilize a radio protocol stack that is physically or logically integrated within a single RAN node (e.g., within a single device or unit). As another example, the network nodes 110 can be a disaggregated network node (sometimes referred to as a disaggregated base station), meaning that the network nodes 110 are configured to utilize a protocol stack that is physically or logically distributed across two or more nodes, such as one or more central units (CUs), one or more distributed units (DUs), or one or more radio units (RUs).

[0033] In some examples, the network nodes 110 are or include network nodes (such as RUs) that communicate with UEs 120 via radio access links. In some examples, the network nodes 110 are or include network nodes (such as DUs) that communicate with other network nodes 110 via a front-haul link or a mid-haul link. In some examples, the network nodes 110 are or include network nodes (such as CUs) that communicate with other network nodes 110 via a mid-haul link or with a core network via a backhaul link. In some examples, the network nodes 110 (such as aggregated network nodes 110 or disaggregated network nodes 110) can include multiple network nodes, such as one or more RUs, one or more CUs, and / or one or more DUs. For example, the network nodes 110 can comprise an NR base station, an LTE base station, a NodeB, an eNB (e.g., in 4G), a gNB (e.g., in 5G), an access point, a transmission reception point (TRP), a DU, a RU, a CU, a mobility element of a network, a core network node, a network element, network equipment, a RAN node, or a combination thereof. In some examples, the network nodes 110 can interconnect with each other or to one or more other network nodes 110 in the wireless network 100 using any suitable transport network, such as a direct physical connection, an air interface, or a virtual network. The transport network can further include transport interfaces of different types (wired or wireless), different generations, or a combination thereof.

[0034] In some examples, a network node 110 can provide communication coverage for a particular geographic area. In Third Generation Partnership Project (3GPP), the term "cell" can refer to a coverage area of a network node 110 or a network node subsystem serving the coverage area, depending on the context in which the term is used. A network node 110 can be a macro cell, a pico cell, a femto cell, or another type of cell. A macro cell can cover a relatively large geographic area (e.g., a radius of several kilometers) and can allow unrestricted access by UEs 120 with service subscriptions. A pico cell can cover a relatively small geographic area (e.g., a residence) and can allow unrestricted access by UEs 120 with service subscriptions. A femto cell can cover a relatively small geographic area (e.g., a residence) and can allow restricted access by UEs 120, such as UEs 120 in an closed subscriber group (CSG). A network node 110 for a macro cell can be referred to as a macro network node. A network node 110 for a pico cell can be referred to as a pico network node. A network node 110 for a femto cell can be referred to as a femto network node or a home network node. In Figure 1 In the illustrated example, network node 110a can be a macro network node for a macro cell 102a, network node 110b can be a pico network node for a pico cell 102b, and network node 110c can be a femto network node for a femto cell 102c. A network node can support one or more (e.g., three) cells. In some examples, cells can not necessarily be stationary, and the geographic area of the cells can move according to the location of a mobile network node 110 (e.g., a mobile network node).

[0035] In some aspects, the term “base station” or “network node” can refer to an aggregated base station, a disaggregated base station, an integrated access and backhaul (IAB) node, a relay node, or one or more components thereof. For example, in some aspects, a “base station” or “network node” can refer to a CU, a DU, a RU, a near real-time (near-RT) RAN intelligent controller (RIC), or a non-RT RIC, or a combination thereof. In some aspects, the term “base station” or “network node” can refer to one device configured to perform one or more functions, such as those described herein in connection with network node 110. In some aspects, the term “base station” or “network node” can refer to multiple devices configured to perform one or more functions. For example, in some distributed systems, each of multiple different devices (which can be located in the same geographic location or different geographic locations) can be configured to perform at least a portion of a function, or to perform at least a portion of the function repeatedly, and the term “base station” or “network node” can refer to any one or more of these different devices. In some aspects, the term “base station” or “network node” can refer to one or more virtual base stations or one or more virtual base station functions. For example, in some aspects, two or more base station functions can be instantiated on a single device. In some aspects, the term “base station” or “network node” can refer to one of a base station function and not another base station function. In this way, a single device can include more than one base station.

[0036] Wireless network 100 can include one or more relay stations. A relay station is a network node that receives a transmission of data from an upstream node (e.g., a network node 110 or a UE 120) and sends a transmission of the data to a downstream node (e.g., a UE 120 or a network node 110). A relay station can be a UE 120 that can relay transmissions for other UEs 120. In Figure 1 In the illustrated example, network node 110d (e.g., a relay network node) can communicate with network node 110a (e.g., a macro network node) and UE 120d in order to facilitate communication between network node 110a and UE 120d. A network node 110 that relays communications can be referred to as a relay station, a relay base station, a relay network node, a relay node, or the like.

[0037] Wireless network 100 can be a heterogeneous network that includes network nodes 110 of different types, such as macro network nodes, pico network nodes, femto network nodes, or relay network nodes. These different types of network nodes 110 can have different transmit power levels, different coverage areas, or different impacts on interference in wireless network 100. For example, macro network nodes can have a high transmit power level (e.g., 5 to 40 watts), while pico network nodes, femto network nodes, and relay network nodes can have a lower transmit power level (e.g., 0.1 to 2 watts).

[0038] A network controller 130 can couple to or communicate with a set of network nodes 110 and can provide coordination and control for the network nodes 110. The network controller 130 can communicate with the network nodes 110 via a backhaul communication link or a metro communication link. The network nodes 110 can also communicate with one another directly via wireless backhaul communication links or indirect via wired backhaul communication links. In some aspects, the network controller 130 can be a CU or a core network device, or can include a CU or a core network device.

[0039] The UEs 120 can be dispersed throughout the wireless network 100, and each UE 120 can be stationary or mobile. A UE 120 can include, for example, an access terminal, a terminal, a mobile station or a subscriber unit. A UE 120 can be a cellular phone (e.g., a smart phone), a personal digital assistant (PDA), a wireless modem, a wireless communication device, a handheld device, a laptop computer, a cordless phone, a wireless local loop (WLL) station, a tablet, a camera, a gaming device, a netbook, a smartbook, an ultrabook, a medical device, a biometric device, a wearable device (e.g., a smart watch, smart clothing, smart glasses, a smart wristband, smart jewelry (e.g., a smart ring or a smart bracelet)), an entertainment device (e.g., a music device, a video device, or a satellite radio), a vehicular component or sensor, a smart meter / sensor, industrial manufacturing equipment, a global positioning system device, a UE function of a network node, or any other suitable device that is configured to communicate via a wireless or wired medium.

[0040] Some UEs 120 can be considered machine-type communication (MTC) or evolved or enhanced machine-type communication (eMTC) UEs. An MTC UE or eMTC UE can include, for example, a robot, a drone, a remote device, a sensor, a meter, a watchdog, or a location tag, that can communicate with a network node, another device (e.g., a remote device), or some other entity. A some UEs 120 can be considered Intemet-of-Things (IoT) devices, or can be implemented as NB-IoT (narrowband IoT) devices. Some UEs 120 can be considered customer premises equipment. A UE 120 can be included in a housing that houses components of the UE 120, such as processor components or memory components. In some examples, processor components and memory components can be coupled together. For example, a processor component (e.g., one or more processors) and a memory component (e.g., a memory) can be operatively coupled, communicatively coupled, electronically coupled, or electrically coupled.

[0041] Generally, any number of wireless networks 100 can be deployed in a given geographic area. Each wireless network 100 can support a particular RAT and can operate on one or more frequencies. A RAT can also be referred to as a radio technology, or an air interface. Frequencies can also be referred to as carriers or frequency channels. In a given geographic area, each frequency can support one RAT to avoid interference between wireless networks of different RATs. In some cases, NR or 5G RAT networks can be deployed.

[0042] In some examples, two or more UEs 120 (e.g., shown as UE 120a and UE 120e) can communicate directly using one or more sidelink channels (e.g., without using network node 110 as an intermediary to communicate with one another). For example, UEs 120 can communicate using peer-to-peer (P2P) communications, device-to-device (D2D) communications, vehicle-to-everything (V2X) protocols (which can include vehicle-to-vehicle (V2V) protocols, vehicle-to-infrastructure (V2I) protocols, or vehicle-to-pedestrian (V2P) protocols), or mesh networking. In such examples, UEs 120 can perform scheduling operations, resource selection operations, or other operations described elsewhere herein as being performed by network node 110.

[0043] Devices of wireless network 100 can use the electromagnetic spectrum for communications. The electromagnetic spectrum can be subdivided by frequency or wavelength into various classes, bands, or channels. For example, devices of wireless network 100 can communicate using one or more operating bands. In 5G NR, two initial operating bands have been identified as frequency range designations: FR1 (410 megahertz (MHz) to 7.125 gigahertz (GHz)) and FR2 (24.25 GHz to 52.6 GHz). Although a portion of FR1 is greater than 6 GHz, FR1 is often (interchangeably) referred to as a “sub-6 GHz” band in various documents and articles. A similar nomenclature issue sometimes occurs with respect to FR2, which is often (interchangeably) referred to as a “millimeter wave” band in documents and articles, despite the fact that the Extremely High Frequency (EHF) band, which is identified by the International Telecommunications Union (ITU) as the “millimeter wave” band, spans from 30 GHz to 300 GHz.

[0044] The frequencies between FR1 and FR2 are often referred to as mid-band frequencies. Recent 5G NR studies have identified operating bands for these mid-band frequencies as Frequency Range designation FR3 (7.125 GHz - 24.25 GHz). Bands that fall within FR3 can inherit FR1 characteristics or FR2 characteristics, and as such, the characteristics of FR1 or FR2 can be effectively extended into the mid-band frequencies. Furthermore, higher bands are currently being explored to extend 5G NR operations beyond 52.6 GHz. For example, three higher operating bands have been identified as Frequency Range designations FR4-a or FR4-l (52.6 GHz - 71 GHz), FR4 (52.6 GHz - 114.25 GHz), and FR5 (114.25 GHz - 300 GHz). Each of these higher bands fall within the EHF band.

[0045] With these examples in mind, unless specifically stated otherwise, if the term “sub-6 GHz” is used herein, it can refer broadly to frequencies that can be less than 6 GHz, frequencies that can be within FR1, or frequencies that can include mid-band frequencies. Further, unless specifically stated otherwise, if the term “millimeter wave” is used herein, it can broadly refer to frequencies that can include mid-band frequencies, frequencies that can be within FR2, FR4, FR4-a, or FR4-l, or FR5, or frequencies that can be within the EHF band. It is contemplated that the frequencies included in these operating bands (e.g., FR1, FR2, FR3, FR4, FR4-a, FR4-l, or FR5) can be modified, and the techniques described herein are applicable to those modified frequency ranges.

[0046] In some aspects, UE 120 can include a communication manager 140. As described in more detail elsewhere herein, the communication manager 140 can receive, from another UE via a sidelink, a COT-SI associated with a first portion of a COT, identify, based at least in part on the COT-SI, that the UE 120 is a qualified relay UE for the COT-SI, and transmit, based at least in part on the UE 120 being the qualified relay UE for the COT-SI, a communication using the first portion of the COT, the communication including a repeated COT-SI. In some other aspects, the communication manager 140 can transmit, to another UE via a sidelink, a COT-SI associated with a first portion of a COT, and indicate whether the other UE is a qualified relay UE for the COT-SI. Additionally, or alternatively, the communication manager 140 can perform one or more other operations described herein.

[0047] As indicated above, Figure 1 are provided as examples. Other examples can differ from what is described with respect to Figure 1 the examples described with respect to

[0048] Figure 2is a diagram illustrating an example 200 of a network node 110 in communication with a UE 120 in a wireless network 100, in accordance with the present disclosure. The network node 110 can be equipped with a set of antennas 234a through 234t, such as T antennas (T> 1). The UE 120 can be equipped with a set of antennas 252a through 252r, such as R antennas (R > 1). The network node 110 of example 200 includes one or more radio front end components, such as antennas 234 and modem 232. In some examples, the network node 110 can include an interface, communication component, or another component that facilitates communication with the UE 120 or another network node. Some network nodes 110 can not include radio frequency components that facilitate direct communication with UEs 120, such as one or more CUs or one or more DUs.

[0049] At the network node 110, a transmit processor 220 can receive data from a data source 212 intended for the UE 120 (or a set of UEs 120). The transmit processor 220 can select one or more modulation and coding schemes (MCSs) for the UE 120 using one or more channel quality indicators (CQIs) received from the UE 120. The network node 110 can process (e.g., encode and modulate) the data for the UE 120 using the MCSs selected for the UE 120 and can provide data symbols. The transmit processor 220 can process system information (e.g., for semi-static resource partitioning information (SRPI)) and control information (e.g., CQI requests, grants, or upper layer signaling) and provide overhead symbols and control symbols. The transmit processor 220 can generate reference symbols for reference signals (e.g., a cell-specific reference signal (CRS) or a demodulation reference signal (DMRS)) and synchronization signals (e.g., a primary synchronization signal (PSS) or a secondary synchronization signal (SSS)). A transmit (TX) multiple-input multiple-output (MIMO) processor 230 can perform spatial processing (e.g., precoding) on the data symbols, the control symbols, the overhead symbols, or the reference symbols, if applicable, and can provide a set of output symbol streams (e.g., T output symbol streams) to a corresponding set of modems 232 (e.g., T modems), shown as modems 232a through 232t. For example, each output symbol stream can be provided to a modulator component (shown as MOD) of the modems 232. Each modem 232 can use a respective modulator component to process a respective output symbol stream (e.g., for OFDM) to obtain an output sample stream. Each modem 232 can also use a respective modulator component to process (e.g., convert to analog, amplify, filter, or upconvert) the output sample stream to obtain a downlink signal. The modems 232a through 232t can transmit a set of downlink signals (e.g., T downlink signals) via a corresponding set of antennas (e.g., T antennas), shown as antennas 234a through 234t.

[0050] At the UE 120, a set of antennas 252 (shown as antennas 252a through 252r) can receive the downlink signals from network node 110 or other network nodes 110 and can provide a set of received signals (e.g., R received signals) to a set of modems 254 (e.g., R modems), shown as modems 254a through 254r. For example, each received signal can be provided to a demodulator component (shown as DEMOD) of a modem 254. Each modem 254 can condition (e.g., filter, amplify, downconvert, or digitize) a received signal to obtain input samples using a respective demodulator component. Each modem 254 can further process the input samples (e.g., for OFDM) using a demodulator component to obtain received symbols. A MIMO detector 256 can obtain received symbols from modems 254, can perform MIMO detection on the received symbols if applicable, and can provide detected symbols. A receive processor 258 can process (e.g., demodulate and decode) the detected symbols, can provide decoded data for the UE 120 to a data sink 260, and can provide decoded control information and system information to a controller / processor 280. The term “controller / processor” can refer to one or more controllers, one or more processors, or combinations thereof. A channel processor can determine reference signal received power (RSRP) parameters, received signal strength indicator (RSSI) parameters, reference signal received quality (RSRQ) parameters, or CQI parameters, among other examples. In some examples, one or more components of the UE 120 can be included in a housing 284.

[0051] A network controller 130 can include a communication unit 294, a controller / processor 290, and a memory 292. The network controller 130 can include, for example, one or more devices in a core network. The network controller 130 can communicate with the network node 110 via the communication unit 294.

[0052] One or more antennas (e.g., antennas 234a through 234t or antennas 252a through 252r) can include or be included within one or more antenna panels, one or more antenna groups, one or more sets of antenna elements, or one or more antenna arrays, among other examples. An antenna panel, antenna group, set of antenna elements, or antenna array can include one or more antenna elements (within a single housing or multiple housings), a set of co-planar antenna elements, a set of non-co-planar antenna elements, or one or more antenna elements coupled to one or more transmit or receive components (such as Figure 2 one or more components) of a device.

[0053] On the uplink, at UE 120, a transmit processor 264 can receive and process data from a data source 262 and control information (e.g., for reports comprising RSRP, RSSI, RSRQ, or CQI) from controller / processor 280. Transmit processor 264 can generate reference symbols for one or more reference signals. The symbols from transmit processor 264 can be precoded by a TX MIMO processor 266 if applicable, further processed by modems 254 (e.g., for DFT-s-OFDM or CP-OFDM), and transmitted to network node 110. In some examples, modems 254 of UE 120 can include modulators and demodulators. In some examples, UE 120 includes a transceiver. The transceiver can include any combination of antenna 252, modems 254, MIMO detector 256, receive processor 258, transmit processor 264, or TX MIMO processor 266. The transceiver can be used by a processor (e.g., controller / processor 280) and memory 282 to perform aspects of any of the processes described herein (for example, with reference to Figures 6-9 ).

[0054] At network node 110, the uplink signals from UE 120 or other UEs can be received by antennas 234, processed by modems 232 (e.g., demodulator components of modems 232, shown as DEMODs), detected by a MIMO detector 236 if applicable, and further processed by a receive processor 238 to obtain decoded data and control information transmitted by UE 120. Receive processor 238 can provide the decoded data to a data sink 239 and the decoded control information to controller / processor 240. Network node 110 can include communication unit 244 and can communicate with network controller 130 via communication unit 244. Network node 110 can include scheduler 246 to schedule one or more UEs 120 for downlink or uplink communications. In some examples, modems 232 of network node 110 can include modulators and demodulators. In some examples, network node 110 includes a transceiver. The transceiver can include any combination of antenna 234, modems 232, MIMO detector 236, receive processor 238, transmit processor 220, or TX MIMO processor 230. The transceiver can be used by a processor (e.g., controller / processor 240) and memory 242 to perform aspects of any of the processes described herein (for example, with reference to Figures 6-9 ).

[0055] In some aspects, the controller / processor 280 can be a component of a processing system. A processing system generally can be a system or series of machines or components that receives input and processes the input to produce a set of outputs (which can be delivered to other systems or components, for example, of the UE 120). For example, the processing system of the UE 120 can be a system that includes various other components or subcomponents of the UE 120.

[0056] The processing system of the UE 120 can interface with one or more other components of the UE 120, can process information received from one or more other components, or can output information to one or more other components. For example, a chip or modem of the UE 120 can include a processing system, a first interface for receiving or obtaining information for the processing system, and a second interface for outputting, sending, or providing information from the processing system. In some examples, the first interface can be an interface between the processing system and a receiver of the chip or modem, such that the UE 120 can receive information or signal inputs and can pass the information to the processing system. In some examples, the second interface can be an interface between the processing system and a transmitter of the chip or modem, such that the UE 120 can send information output from the chip or modem. One of ordinary skill in the art would readily recognize that the second interface can also receive or obtain information or signal inputs, and the first interface can also output, send, or provide information.

[0057] In some aspects, the controller / processor 240 can be a component of a processing system. A processing system generally can be a system or series of machines or components that receives input and processes the input to produce a set of outputs (which can be delivered to other systems or components, for example, of the network node 110). For example, the processing system of the network node 110 can be a system that includes various other components or subcomponents of the network node 110.

[0058] The processing system of the network node 110 can interface with one or more other components of the network node 110, can process information received from one or more other components (such as inputs or signals), or can output information to one or more other components. For example, a chip or modem of the network node 110 can include a processing system, a first interface for receiving or obtaining information, and a second interface for outputting, transmitting, or providing information. In some examples, the first interface can be an interface between the processing system of the chip or modem and a receiver, such that the network node 110 can receive information or signal inputs and can pass the information to the processing system. In some examples, the second interface can be an interface between the processing system of the chip or modem and a transmitter, such that the network node 110 can transmit information output from the chip or modem. One of ordinary skill in the art will readily recognize that the second interface can also receive or obtain information or signal inputs, and the first interface can also output, transmit, or provide information.

[0059] The controller / processor 240 of the network node 110, the controller / processor 280 of the UE 120, or Figure 2 any other component of the network node 110, the UE 120, or Figure 2 The controller / processor 240 of the network node 110, the controller / processor 280 of the UE 120, or Figure 7 any other component of the network node 110, the UE 120, or Figure 8 The controller / processor 240 of the network node 110, the controller / processor 280 of the UE 120, or Figure 7 The memory 242 and the memory 282 can store data and program codes for the network node 110 and the UE 120, respectively. In some examples, the memory 242 and the memory 282 can include a non-transitory computer-readable medium storing one or more instructions (e.g., code or program code) for wireless communication. The one or more instructions, when executed (e.g., directly, or after compilation, transformation, or interpretation) by one or more processors of the network node 110 or the UE 120, can cause the one or more processors, the UE 120, or the network node 110 to perform or direct operations of, for example, Figure 8 The controller / processor 240 of the network node 110, the controller / processor 280 of the UE 120, or

[0060] In some aspects, the UE 120 can correspond to the first UE and / or the second UE described herein. In some aspects, the first UE includes means for receiving, from a second UE via a sidelink, a COT-SI associated with a first portion of a COT; means for identifying, based at least in part on the COT-SI, that the first UE is a qualified relay UE for the COT-SI; and / or means for transmitting, by the first UE and based at least in part on the first UE being the qualified relay UE for the COT-SI, a communication using the first portion of the COT, the communication including a repetition of the COT-SI. The means for the first UE to perform operations described herein can include, for example, one or more of the communication manager 140, antenna 252, modem 254, MIMO detector 256, receive processor 258, transmit processor 264, TX MIMO processor 266, controller / processor 280, or memory 282.

[0061] In some aspects, the first UE includes means for transmitting, to a second UE via a sidelink, a COT-SI associated with a first portion of a COT; and / or means for indicating whether the second UE is a qualified relay UE for the COT-SI. The means for the first UE to perform operations described herein can include, for example, one or more of the communication manager 140, antenna 252, modem 254, MIMO detector 256, receive processor 258, transmit processor 264, TX MIMO processor 266, controller / processor 280, or memory 282.

[0062] Although Figure 2 The blocks in FIG. 13 are illustrated as distinct components merely for clarity, but the functions described above in relation to these blocks can be implemented in a single hardware, software, or combined component or in various combinations of components. For example, the functions described in relation to transmit processor 264, receive processor 258, and / or TX MIMO processor 266 can be performed by controller / processor 280 or under the control of the controller / processor.

[0063] As indicated above, Figure 2 are provided as examples. Other examples can differ from what is described in relation to Figure 2 the examples described in relation to

[0064] Deployment of communication systems, such as 5G NR systems, can be arranged in a variety of ways with various components or constituent parts. In a 5G NR system or network, a network node, network entity, mobility element of a network, RAN node, core network node, network element, base station, or network equipment of a network can be implemented in an aggregated architecture or a disaggregated architecture. For example, a base station, such as a Node B (NB), an evolved NB (eNB), an NR base station, a 5G NB, an access point (AP), a TRP, or a cell, and so forth, or one or more units (or one or more components) that perform base station functionality can be implemented as an aggregated base station (also referred to as a standalone base station or a monolithic base station) or a disaggregated base station. A “network entity” or “network node” can refer to a disaggregated base station or one or more units of a disaggregated base station, such as one or more CUs, one or more DUs, one or more RUs, or a combination thereof.

[0065] An aggregated base station (e.g., an aggregated network node) can be configured to utilize a radio protocol stack that is physically or logically integrated within a single RAN node (e.g., within a single device or unit). A disaggregated base station (e.g., a disaggregated network node) can be configured to utilize a protocol stack that is physically or logically distributed between two or more units, such as one or more CUs, one or more DUs, or one or more RUs. In some examples, a CU can be implemented within a network node, and one or more DUs can be co-located with the CU or, alternatively, can be geographically or virtually spread across one or more other network nodes. The DUs can be implemented to communicate with one or more RUs. Each of the CUs, DUs, and RUs can also be implemented as virtual units, such as a virtual central unit (VCU), a virtual distributed unit (VDU), or a virtual radio unit (VRU), and so forth.

[0066] Base station type operations or network designs can take into account the aggregated nature of base station functionality. For example, a disaggregated base station can be utilized in an IAB network, an open radio access network (O-RAN (such as a network configuration initiated by the O-RAN Alliance)), or a virtualized radio access network (vRAN, also referred to as a cloud radio access network (C-RAN)) to facilitate scaling of a communication system by separating base station functionality into one or more units that can be deployed individually. A disaggregated base station can include functionality implemented across two or more units at various physical locations, as well as functionality implemented virtually for at least one unit, which can enable flexibility in network design. The various units of a disaggregated base station can be configured for wired or wireless communication with at least one other unit of the disaggregated base station.

[0067] Figure 3is a diagram illustrating an example disaggregated base station architecture 300 according to the present disclosure. The disaggregated base station architecture 300 can include a CU 310, which can communicate directly with a core network 320 via a backhaul link, or indirectly with the core network 320 through one or more disaggregated control units, such as a near-RT RIC 325 via an E2 link, or a non-RT RIC 315 associated with a service management and orchestration (SMO) framework 305, or both. The CU 310 can communicate with one or more DUs 330 via respective fronthaul links, such as over an Fl interface. Each of the DUs 330 can communicate with one or more RUs 340 via respective front-haul links. Each of the RUs 340 can communicate with one or more UEs 120 via respective radio frequency (RF) access links. In some implementations, a UE 120 can be served by multiple RUs 340 simultaneously.

[0068] Each of the units (including the CU 310, the DUs 330, the RUs 340), as well as the near-RT RIC 325, the non-RT RIC 315, and the SMO framework 305, can include or be coupled to one or more interfaces configured to receive or transmit signals, data, or information (collectively, signals) via wired or wireless transmission media. Each of the units, or an associated processor or controller providing instructions to one or more communication interfaces of the respective unit, can be configured to communicate with one or more of the other units via the transmission media. In some examples, each of the units can include a wired interface configured to receive or transmit signals to one or more of the other units over a wired transmission medium, and a wireless interface, which can include a receiver, a transmitter, or a transceiver (such as a RF transceiver) configured to receive or transmit signals to one or more of the other units over a wireless transmission medium, or both.

[0069] In some aspects, the CU 310 can host one or more higher layer control functions. Such control functions can include radio resource control (RRC) functions, packet data convergence protocol (PDCP) functions, or service data adaptation protocol (SDAP) functions, among other examples. Each control function can be implemented with an interface configured to communicate signals with other control functions hosted by the CU 310. The CU 310 can be configured to handle user plane functionality (e.g., central unit-user plane (CU-UP) functionality), control plane functionality (e.g., central unit-control plane (CU-CP) functionality), or a combination thereof. In some implementations, the CU 310 can be logically split into one or more CU-UP units and one or more CU-CP units. When implemented in an O-RAN configuration, the CU-UP units can communicate bi-directionally with the CU-CP units via an interface, such as an El interface. The CU 310 can be implemented to communicate with the DUs 330 as needed for network control and signaling.

[0070] Each DU 330 can correspond to a logical unit that includes one or more base station functions for controlling the operation of one or more RUs 340. In some aspects, the DU 330 can host one or more of a radio link control (RLC) layer, a medium access control (MAC) layer, and one or more high physical (PHY) layers, at least in part according to a functional split, such as a functional split defined by 3GPP. In some aspects, the one or more high PHY layers can be implemented by one or more modules for forward error correction (FEC) encoding and decoding, scrambling, and modulation and demodulation, among other examples. In some aspects, the DU 330 can also host one or more low PHY layers, such as implemented by one or more modules for fast Fourier transform (FFT), inverse FFT (iFFT), digital beamforming, or physical random access channel (PRACH) extraction and filtering, among other examples. Each layer (which can also be referred to as a module) can be implemented with an interface configured to communicate signals with other layers (and modules) hosted by the DU 330 or with control functions hosted by the CU 310.

[0071] Each RU 340 can implement low-layer functionality. In some deployments, the RUs 340 controlled by the DUs 330 can correspond to logical nodes that host RF processing functions or low PHY layer functions based on a functional split (e.g., a functional split defined by 3GPP), such as a low-layer functional split, such as performing FFT, performing iFFT, digital beamforming, or PRACH extraction and filtering, among other examples. In such an architecture, each RU 340 can be operated to handle over-the-air (OTA) communications with one or more UEs 120. In some implementations, real-time and non-real-time aspects of control plane and user plane communications with the RUs 340 can be controlled by the corresponding DUs 330. In some scenarios, this configuration can enable each DU 330 and CU 310 to be implemented in a cloud-based RAN architecture, such as a vRAN architecture.

[0072] The SMO framework 305 can be configured to support RAN deployment and provisioning of non-virtualized network elements and virtualized network elements. For non-virtualized network elements, the SMO framework 305 can be configured to support deployment of dedicated physical resources for RAN coverage requirements, which can be managed via an operations and maintenance interface, such as an Ol interface. For virtualized network elements, the SMO framework 305 can be configured to interact with a cloud computing platform, such as an Open Cloud (O-Cloud) platform 390, to perform network element lifecycle management, such as instantiating virtualized network elements, via a cloud computing platform interface, such as an 02 interface. Such virtualized network elements can include, but are not limited to, the CU 310, the DUs 330, the RUs 340, the non-RT RIC 315, and the near-RT RIC 325. In some implementations, the SMO framework 305 can communicate with hardware aspects of a 4G RAN, such as an Open eNB (O-eNB) 311, via an Ol interface. Additionally, in some implementations, the SMO framework 305 can directly communicate with each of the one or more RUs 340 via a respective Ol interface. The SMO framework 305 can also include the non-RT RIC 315, which is configured to support functionality of the SMO framework 305.

[0073] The non-RT RIC 315 can be configured to include logical functions that enable non-real-time control and optimization of RAN elements and resources, including model training and update, AI / ML workflow or policy-based steering of applications / features in the near-RT RIC 325. The non-RT RIC 315 can be coupled to, or communicate with, the near-RT RIC 325, such as via an Al interface. The near-RT RIC 325 can be configured to include logical functions that enable near-real-time control and optimization of RAN elements and resources via data collection and actions by interfacing, such as via an E2 interface, one or more CUs 310, one or more DUs 330, or both, and an O-eNB with the near-RT RIC 325.

[0074] In some implementations, to generate AI / ML models to be deployed in the near-RT RIC 325, the non-RT RIC 315 can receive parameters or external enrichment information from an external server. Such information can be utilized by the near-RT RIC 325 and can be received at the SMO framework 305 or the non-RT RIC 315 from non-network data sources or from network functions. In some examples, the non-RT RIC 315 or the near-RT RIC 325 can be configured to tune RAN behavior or performance. For example, the non-RT RIC 315 can monitor long-term trends and patterns of performance and employ AI / ML models to perform corrective actions through the SMO framework 305, such as reconfiguration via an Ol interface, or through creation of RAN management policies, such as Al interface policies.

[0075] As indicated above, Figure 3 are provided as examples. Other examples can differ from what is described Figure 3 with respect to the examples described with respect to

[0076] Figure 4 is a diagram illustrating an example 400 of sidelink communications and access link communications in accordance with the present disclosure.

[0077] As Figure 4As shown, transmitter (Tx) / receiver (Rx) UE 405 and Rx / Tx UE 410 can communicate with one another via a sidelink. As further shown, in some sidelink modes, network node 110 can communicate with Tx / Rx UE 405, such as via a first access link (e.g., directly or via one or more network nodes). Additionally or alternatively, in some sidelink modes, network node 110 can communicate with Rx / Tx UE 410, such as via a first access link (e.g., directly or via one or more network nodes). Tx / Rx UE 405 and / or Rx / Tx UE 410 can correspond to one or more UEs described elsewhere herein, such as UE 120 described above in connection with Figure 1 Thus, a direct link between UEs 120 (e.g., via a PC5 interface) can be referred to as a sidelink, and a direct link between a network node 110 and a UE 120 (e.g., via a Uu interface) can be referred to as an access link. Sidelink communications can be transmitted via a sidelink, and access link communications can be transmitted via an access link. An access link communication can be a downlink communication (from a network node 110 to a UE 120) or an uplink communication (from a UE 120 to a network node 110). Aspects of channels that can be conveyed via a sidelink are described in greater detail below in connection with Figure 5A

[0078] As indicated above, Figure 4 is provided as an example. Other examples can differ from what is described with respect to the example Figure 4 described with respect to the example

[0079] Figures 5A-5B is a diagram illustrating an example 500 of sidelink communications in accordance with the present disclosure.

[0080] As Figure 5A shown, a first UE 505-1 can communicate with a second UE 505-2 (and one or more other UEs 505) via one or more sidelink channels 510. First UE 505-1 and second UE 505-2 can correspond to any of the UEs described herein, such as UE 120 described above in connection with Figures 1-3 Figure 4 ​​The described Tx / Rx UE 405 or Rx / Tx UE 410. The UEs 505-1 and 505-2 can communicate using one or more sidelink channels 510 for P2P communications, D2D communications, V2X communications (e.g., which can include V2V communications, V2I communications, and / or V2P communications), and / or net mesh networking. In some aspects, the one or more sidelink channels 510 can use a PC5 interface and / or can operate in a high frequency band (e.g., a 5.9 GHz band). Additionally, or alternatively, the UEs 505 can use global navigation satellite system (GNSS) timing for synchronizing timing of transmission time intervals (TTIs) (e.g., frames, subframes, slots, or symbols).

[0081] As Figure 5A Further shown, the one or more sidelink channels 510 can include a physical sidelink control channel (PSCCH) 515, a physical sidelink shared channel (PSSCH) 520, and / or a physical sidelink feedback channel (PSFCH) 525. The PSCCH 515 can be used to convey control information, similar to a physical downlink control channel (PDCCH) and / or a physical uplink control channel (PUCCH) used for cellular communications with a network node 110 via an access link or access channel. The PSSCH 520 can be used to convey data, similar to a physical downlink shared channel (PDSCH) and / or a physical uplink shared channel (PUSCH) used for cellular communications with a network node 110 via an access link or access channel. For example, the PSCCH 515 can carry SCI 530, which can indicate various control information for a sidelink communication, such as one or more resources (e.g., time resources, frequency resources, and / or spatial resources) in which a transport block (TB) 535 can be carried on the PSSCH 520. The TB 535 can include data. The PSFCH 525 can be used to convey sidelink feedback 540, such as hybrid automatic repeat request (HARQ) feedback (e.g., acknowledgement or negative acknowledgement (ACK / NACK) information), transmit power control (TPC), and / or a scheduling request (SR).

[0082] Although shown on the PSCCH 515, in some aspects, the SCI 530 can include multiple communications in different stages, such as a first stage SCI (SCI-1) and a second stage SCI (SCI-2). The SCI-1 can be transmitted on the PSCCH 515. The SCI-2 can be transmitted on the PSSCH 520. The SCI-1 can include, for example, an indication of one or more resources (e.g., time resources, frequency resources, and / or spatial resources) on the PSSCH 520, information for decoding a sidelink communication on the PSSCH, a quality of service (QoS) priority value, a resource reservation period, a PSSCH DMRS pattern, an SCI format for the SCI-2, a beta offset for the SCI-2, a number of PSSCH DMRS ports, and / or an MCS. The SCI-2 can include information associated with a data transmission on the PSSCH 520, such as a HARQ process ID, a new data indicator (NDI), a source identifier, a destination identifier, a channel state information (CSI) report trigger, a COT-SI, or similar information.

[0083] In some aspects, the one or more sidelink channels 510 can use a resource pool. For example, a scheduling assignment (e.g., included in the SCI 530) can be transmitted in a subchannel using a particular RB across time. In some aspects, a data transmission associated with the scheduling assignment (e.g., on the PSSCH 520) can occupy adjacent RBs in the same subframe as the scheduling assignment (e.g., using frequency division multiplexing). In some aspects, the scheduling assignment and the associated data transmission are not transmitted on adjacent RBs.

[0084] In some aspects, the UE 505 can operate using a sidelink transmission mode (e.g., mode 1), in which resource selection and / or scheduling is performed by a network node 110 (e.g., a base station, a CU, or a DU). For example, the UE 505 can receive a grant (e.g., in downlink control information (DCI) or in an RRC message, such as for a configured grant) from the network node 110 (e.g., directly or via one or more network nodes) for sidelink channel access and / or scheduling. In some aspects, the UE 505 can operate using a transmission mode (e.g., mode 2), in which resource selection and / or scheduling is performed by the UE 505 (e.g., instead of the network node 110). In some aspects, the UE 505 can perform resource selection and / or scheduling by sensing channel availability for transmission. For example, the UE 505 can measure an RSSI parameter (e.g., a sidelink-RSSI (S-RSSI) parameter) associated with various sidelink channels, can measure an RSRP parameter (e.g., a PSSCH-RSRP parameter) associated with various sidelink channels, and / or can measure an RSRQ parameter (e.g., a PSSCH-RSRQ parameter) associated with various sidelink channels, and can select a channel for transmitting a sidelink communication based at least in part on the measurements.

[0085] Additionally or alternatively, the UE 505 can perform resource selection and / or scheduling using SCI 530 received in the PSCCH 515, which can indicate occupied resources and / or channel parameters. Additionally or alternatively, the UE 505 can perform resource selection and / or scheduling by determining a channel busy ratio (CBR) associated with various sidelink channels, which can be used for rate control (e.g., by indicating a maximum number of resource blocks that the UE 505 can use for a particular set of subframes).

[0086] In a transmission mode in which resource selection and / or scheduling is performed by the UE 505, the UE 505 can generate a sidelink grant and can transmit the grant in SCI 530. The sidelink grant can indicate, for example, one or more parameters (e.g., transmission parameters) to be used for an upcoming sidelink transmission, such as one or more resource blocks to be used for the upcoming sidelink transmission (e.g., for a TB 535), one or more subframes to be used for the upcoming sidelink transmission, and / or an MCS to be used for the upcoming sidelink transmission on the PSSCH 520. In some aspects, the UE 505 can generate a sidelink grant indicating one or more parameters for semi-persistent scheduling (SPS), such as a periodicity of sidelink transmissions. Additionally or alternatively, the UE 505 can generate a sidelink grant for event-driven scheduling, such as for on-demand sidelink messages.

[0087] Further, in some aspects, the sidelink communications can be transmitted via a sidelink, and / or the access link communications can be transmitted via an access link in a licensed RF spectrum, an unlicensed RF spectrum, and / or any suitable combination thereof.

[0088] For example, to accommodate growing demand for traffic, various efforts have been made to improve spectral efficiency, and thereby improve network capacity, in wireless networks (e.g., via use of higher order modulation, advanced MIMO antenna techniques, multi-cell coordination techniques, etc.). Another potential way to improve network capacity is to expand the system bandwidth. However, there can be a limited amount of available spectrum in lower frequency bands that has traditionally been licensed or otherwise allocated to mobile network operators.

[0089] Accordingly, various techniques have been developed to enable operation of cellular RATs in unlicensed or other shared spectrum. For example, License Assisted Access (LAA) uses carrier aggregation on the downlink to combine LTE in a licensed band with LTE in an unlicensed band (e.g., the 2.4 and / or 5 GHz band already occupied by wireless local area network (WLAN) or “Wi-Fi” devices). In other examples, Enhanced LAA (eLAA) and further Enhanced LAA (feLAA) techniques enable both uplink and downlink LTE operation in unlicensed spectrum, MulteFire is an LTE-based technology operating in unlicensed and shared spectrum in a standalone mode, NR Unlicensed (NR-U) enables NR operation in unlicensed spectrum, etc. Generally, one challenge that arises when operating a cellular RAT in unlicensed spectrum (e.g., using LAA, eLAA, feLAA, MulteFire, and / or NR-U) is the need to ensure fair coexistence with incumbent (e.g., WLAN) systems that can operate in that unlicensed spectrum.

[0090] For example, a transmitting device (e.g., a network node 110, a UE 120, a Tx / Rx UE 405, a Rx / Tx UE 410, a UE 505, etc.) can need to perform an LBT procedure to contend for access to an unlicensed channel before gaining access to and / or transmitting on the unlicensed channel. An LBT procedure can generally include a clear channel assessment (CCA) procedure that is performed in order to determine whether an unlicensed channel is available (e.g., not occupied by other transmitters). In particular, a CCA procedure can include detecting an energy level on the unlicensed channel and determining whether the energy level satisfies (e.g., is less than or equal to) a threshold (sometimes referred to as an energy detection threshold, etc.). When the energy level satisfies (e.g., is not equal to or exceeds) the threshold, the CCA procedure is considered successful, and the transmitting device can gain access to the unlicensed channel for a duration that can be referred to as a COT, during which the transmitting device can perform transmissions without performing additional LBT operations. When the energy level does not satisfy the threshold, the CCA procedure is unsuccessful, and the contention for access to the unlicensed channel can be considered unsuccessful.

[0091] When a CCA procedure results in a determination that an unlicensed channel band is not available (e.g., due to an energy level detected on the unlicensed channel indicating that another device is already using the channel), the CCA procedure can be performed again later. In environments where a transmitting device can gain limited access to an unlicensed channel (e.g., due to WLAN activity or transmissions by other devices), an extended CCA (eCCA) procedure can be employed to increase the likelihood that the transmitting device will successfully gain access to the unlicensed channel.

[0092] For example, a transmitting device performing an eCCA procedure can perform a random number of CCA procedures (from 1 to q) according to an eCCA counter. In cases where and / or when the transmitting device senses that the channel has become clear, the transmitting device can initiate a random wait period based on the eCCA counter, and if the channel remains clear for the random wait period, begin transmitting.

[0093] Accordingly, while wireless networks can be configured to use unlicensed spectrum to achieve faster data rates, provide a more responsive user experience, offload traffic from licensed spectrum, etc., the need to ensure fair coexistence with existing systems (e.g., WLAN devices) can hinder efficient use of unlicensed spectrum. For example, the LBT procedure to ensure that no other device is already using the channel introduces a delay before a transmission can begin, which can degrade the user experience, cause unacceptable performance for latency-sensitive or delay-sensitive applications, etc., even when there is no interference. Moreover, these problems can be exacerbated when the initial CCA procedure is unsuccessful, as the transmitting device can only transmit on the channel after performing an additional number of CCA procedures and determining that the channel has become and remains clear for a random wait period. Furthermore, in some cases, the channel occupancy time obtained by a transmitting device can have a longer duration than is necessary for the transmitting device to perform a desired transmission, which can result in inefficient use of the unlicensed channel.

[0094] Accordingly, in some cases, a wireless network can cause a COT obtained by a transmitting device to be shared with other nodes to improve access, efficiency, etc., for unlicensed channels. For example, in downlink-to-uplink channel occupancy time sharing on an access link, a network node 110 can obtain a COT with an eCCA, and the COT can be shared with one or more UEs (e.g., UEs 120, Tx / Rx UE 405, Rx / Tx UE 410, UE 505, etc.) that can then transmit uplink signals within the COT obtained by the network node 110. In this case, a UE attempting to initiate an uplink transmission within the COT shared with the network node 110 can perform the uplink transmission without having to perform an LBT procedure, or the UE can perform the uplink transmission after a single CCA with a shorter LBT procedure (e.g., a Category 2 LBT procedure when the downlink-to-uplink gap duration is between 16 and 25 µs, a Category 1 LBT procedure when the downlink-to-uplink gap duration is less than or equal to 16 µs, etc.).

[0095] Additionally or alternatively, a wireless network can support uplink-to-downlink channel occupancy time sharing on an access link. In this case, a UE-initiated COT (e.g., for a configured grant PUSCH or a scheduled uplink transmission) can be shared with a network node 110. In this way, the network node 110 can be allowed to transmit control and / or broadcast signals and / or channels for any UEs served by the network node 110 so long as the transmissions include downlink signals, channels, and / or other transmissions (e.g., PDSCH, PDCCH, reference signals, etc.) intended to be received by the UE that initiated the channel occupancy.

[0096] Additionally or alternatively, the wireless network can support UE-to-UE COT sharing over sidelink. For example, as shown in Figure 5B FIG. 5B and by reference number 545, a COT obtained by an initiator UE (e.g., Tx / Rx UE 405, UE 505-1, which can be a UE that initially performs a Type 1 channel access procedure to obtain a COT) can be shared in a frequency division multiplexing (FDM) mode by dividing the COT into multiple interlaces (e.g., time periods during which one or more UEs can perform transmission operations). For example, as shown in Figure 5B FIG. 5B, the initiator UE can use one or more sidelink resources (e.g., time and frequency resources) to transmit in a first interlace after the COT has been obtained, and a responder UE (e.g., Rx / Tx UE 410, UE 505-2) can use sidelink frequency resources that do not overlap with the sidelink frequency resources used by the initiator UE to perform transmission operations in a subsequent interlace (e.g., the responder UE can respond using a Type 2 channel access procedure by sharing the COT obtained by the initiator UE). Thus, as shown in Figure 5B FIG. 5B, FDM or interlace-based COT sharing can introduce a short transmission gap between interlaces to allow other UEs to perform transmission operations in subsequent interlaces during the shared COT, and sidelink control information transmitted by the initiator UE can carry information to support interlace-based COT sharing.

[0097] Additionally or alternatively, as shown by reference number 550, UE-to-UE COT sharing can be implemented in a time division multiplexing (TDM) mode. In this case, the total COT can be divided into an initial time period during which an initiating UE can perform transmissions, which can include one or more SCI transmissions indicating when the initial transmissions will end, a remaining duration of the COT that is available for sharing, and / or the like. In some examples, the information associated with COT sharing contained within the SCI can be referred to as COT-SI. Thus, one or more responder UEs can monitor the SCI transmitted by other UEs (e.g., the initiating UE) to recover the COT-SI that is available for performing transmissions during the time period corresponding to the shared COT (e.g., that is available to enable the responder UEs to use a Type 2 channel access procedure). In some examples, the COT-SI can include an indication of a CAPC associated with the shared COT, a remaining COT duration in the shared COT (e.g., a number of sidelink slots remaining in the shared COT, a number of milliseconds (ms) remaining in the shared COT, or a similar indication), an Ll ID associated with the shared COT (e.g., an Ll destination ID, an Ll source ID, and / or a similar Ll ID), an indication of one or more RB sets associated with the shared COT, an additional ID associated with the shared COT (e.g., a COT sharing ID), and / or other information associated with the shared COT (e.g., a communication range, additional information regarding time and / or frequency resources, a starting offset associated with the shared COT and / or transmissions by the responder UEs, a channel access type associated with the shared COT, or similar information).

[0098] In some examples, if an Ll ID contained in the initiating’s transmissions (e.g., a logical source / destination ID pair for a unicast PSCCH / PSSCH transmission, or a logical destination ID for a groupcast or broadcast PSCCH / PSSCH transmission) matches a logical ID known at the receiving UE, a UE receiving the SCI containing the COT-SI (e.g., a responder UE) can identify that the UE is a target of the COT sharing (e.g., a target of the COT-SI). Additionally or alternatively, if an additional ID contained in the initiating’s transmissions (e.g., a COT sharing ID) matches a logical ID known at the receiving UE, the UE receiving the SCI containing the COT-SI can identify that the UE is a target of the COT sharing.

[0099] Additionally or alternatively, if a COT sharing ID is received at a responding UE and a COT sharing ID / logical ID mapping has been constructed at the responding UE, a UE receiving a SCI containing a COT-SI can identify that the UE is a target of COT sharing. In such cases, an initiating UE can provide support for mapping any given COT sharing ID to a set of allowable logical IDs. A COT sharing ID can be recorded by a responding UE that is a target of COT sharing, where the responding UE associates the COT sharing ID with a known logical ID used by the initiating UE in transmissions carrying such a COT sharing ID (e.g., upon receiving a transmission carrying a COT sharing ID, the responding UE can map the COT sharing ID to one or more logical IDs associated with the initiating UE). In such examples, whenever the responding UE receives a transmission including a COT sharing ID, the mapping can indicate a set of logical IDs that can be used in response.

[0100] For example, a first UE UE1 (which can be an initiating UE) can transmit a unicast communication to a second UE UE2 (which can be a responding UE) that includes a first source / destination ID pair (e.g., a first source ID and a first destination ID) and a COT sharing ID. Accordingly, UE2 can associate the first source ID and / or the first destination ID with the COT sharing ID. Similarly, UE1 can transmit a unicast communication to a third UE UE3 (which can be another responding UE) that includes a second source / destination ID pair (e.g., a second source ID and a second destination ID) and the COT sharing ID. Accordingly, UE3 can associate the second source ID and / or the second destination ID with the COT sharing ID. UE1 can also transmit a groupcast / broadcast communication to a group including UE3 and a fourth UE (UE4) (which can be another responding UE) that includes a third destination ID and the COT sharing ID. Accordingly, UE3 and UE4 can associate the third destination ID with the COT sharing ID. Thus, in the shared COT, UE2 can respond with a unicast communication using the first source / destination ID pair, as in this example UE2 associates the shared COT (e.g., via the COT sharing ID) with the first source / destination ID pair. Similarly, UE3 can respond with a unicast communication using the second source / destination ID pair or with a groupcast / broadcast communication using the third destination ID, as in this example UE3 associates the shared COT with the second source / destination ID pair and the third destination ID. Further, UE4 can respond with a groupcast / broadcast communication using the third destination ID, as in this example UE4 associates the shared COT with the third destination ID.

[0101] In some examples, it can be desirable to configure UEs to repeat and / or forward the COT-SI in order to ensure that the COT-SI is received by all eligible and / or intended responding UEs. For example, in some examples, the COT-SI can be transmitted in a first slot of the COT, and thus certain half-duplex UEs can miss the COT-SI due to the UEs otherwise communicating (e.g., transmitting) in the first slot of the COT, which can result in underutilized resources, increased congestion between sidelink UEs, and / or inefficient use of network resources in other ways. In such cases, it can be desirable to permit responding UEs to carry the COT-SI within their own transmitted SCI, such as to redundantly share the COT-SI multiple times during the COT to ensure that all eligible UEs receive the COT-SI. However, COT-SI forwarding performed by multiple responding UEs can result in high signaling overhead and / or congested channels. Moreover, responding UEs receiving the repeated COT-SI can be unable to identify whether the UEs can use the COT to respond to an initiator UE or a relay UE, resulting in communication errors and thus high power, computation, and network resource consumption associated with correcting the communication errors.

[0102] Some techniques and apparatuses described herein enable efficient COT-SI forwarding in UE-to-UE COT sharing applications. In some aspects, a responding UE can receive a COT-SI associated with a shareable region of a COT. The responding UE can identify whether it is an eligible relay UE for the COT-SI, which can be based at least in part on whether the responding UE is a data recipient of the initiating UE, whether the responding UE is a target UE of the COT sharing, whether the responding UE is within a given range of the initiating UE, whether the responding UE is able to decode the COT-SI, or whether the responding UE satisfies other criteria. In aspects where the responding UE is an eligible relay UE for the COT-SI, the responding UE can repeat and / or forward the COT-SI when transmitting a communication in the shareable region of the COT, thereby repeating the COT-SI for certain UEs that can have otherwise missed the COT-SI from the initiating UE due to half-duplex operation, etc. Thus, the repeated COT-SI can result in more eligible UEs receiving the COT-SI, which can result in more efficient use of network resources and reduced congestion between sidelink UEs. Moreover, the COT-SI can be distributed among UEs in an efficient manner and in a manner such that the responding UEs can correctly identify the initiator UE, resulting in reduced communication errors and thus reduced power, computation, and network resource consumption that would otherwise be needed for the communication errors.

[0103] As indicated above, Figures 5A-5B are provided by way of example. Other examples can differ from what is described Figures 5A-5B without departing from the spirit of the disclosure.

[0104] Figure 6is a diagram of an example 600 associated with a repeated COT-SI according to the present disclosure. As shown Figure 6 The network node 605 (e.g., network node 110, CU, DU, and / or RU), initiating UE 610 (e.g., UE 120, Tx / Rx UE 405, UE 505-1), and responding UE 615 (e.g., UE 120, Rx / Tx UE 410, UE 505-2) can communicate with one another, in some aspects, the network node 605, initiating UE 610, and responding UE 615 can be part of a wireless network (e.g., wireless network 100). The network node 605, initiating UE 610, and responding UE 615 can have established a wireless connection prior to the operations shown. For example, the network node 605 can have established an access link connection with the initiating UE 610 and / or responding UE 615, such as the access link connection described above in connection with Figure 6 For example, the network node 605 can have established an access link connection with the initiating UE 610 and / or responding UE 615, such as the access link connection described above in connection with Figure 4 For example, the network node 605 can have established an access link connection with the initiating UE 610 and / or responding UE 615, such as the access link connection described above in connection with Figure 4 For example, the network node 605 can have established an access link connection with the initiating UE 610 and / or responding UE 615, such as the access link connection described above in connection with Figure 5A In some aspects, the initiating UE 610 and responding UE 615 can be capable of communicating in unlicensed spectrum (e.g., SL-U), such as by using a Type 1 channel access procedure and / or a Type 2 channel access procedure described above in connection with Figures 5A-5B In some aspects, the initiating UE 610 and responding UE 615 can be capable of communicating in unlicensed spectrum (e.g., SL-U), such as by using a Type 1 channel access procedure and / or a Type 2 channel access procedure described above in connection with

[0105] As shown by reference number 620, the network node 605 can transmit configuration information, and the initiating UE 610 and / or responding UE 615 can receive the configuration information. For example, the initiating UE 610 and / or responding UE 615 can receive the configuration from the network node 605 via a respective access link, such as the access link described above in connection with Figure 4 In some aspects, the initiating UE 610 and / or responding UE 615 can receive the configuration information via one or more of RRC signaling, one or more MAC control elements (MAC-CEs), and / or DCI, among other examples. In some aspects, the configuration information can include an indication of one or more configuration parameters (e.g., already known to the initiating UE 610 and / or responding UE 615 and / or previously indicated by the network node 605 or other network device) for the initiating UE 610 and / or responding UE 615 to select and / or explicit configuration information for the initiating UE 610 and / or responding UE 615 to use to configure the initiating UE 610 and / or responding UE 615, among other examples.

[0106] In some aspects, the configuration information can configure repetition of the COT-SI (sometimes referred to as COT-SI forwarding). For example, such as when a responding UE utilizes a shareable region of a COT, the configuration information can configure parameters and / or conditions associated with the responding UE (e.g., responding UE 615) repeating the COT-SI. In this regard, when so configured, upon receiving an indication of the COT-SI associated with a COT (e.g., COT 625, described in greater detail below) from an initiating UE 610, the responding UE 615 can identify whether one or more conditions and / or parameters are satisfied, and if so, can repeat the COT-SI when responding in a shareable region (e.g., shareable region 630) of the COT, described in greater detail below in connection with reference number 640.

[0107] In some aspects, the configuration information can be associated with a resource pool used by the initiating UE 610 and / or the responding UE 615 to transmit communications using a COT. In other words, in some aspects, the enabling of COT-SI forwarding and / or repetition can be RRC configured at a resource pool level. In such aspects, the network node 605, via the configuration information, can enable COT-SI forwarding for a first resource pool, can disable COT-SI sharing for a second resource pool, and so on. Thus, if the responding UE 615 performs a transmission in the first resource pool, the responding UE 615 can repeat the COT-SI, and if the responding UE 615 performs a transmission in the second resource pool, the responding UE 615 can refrain from repeating the COT-SI based at least in part on the configuration information. In some other aspects, the enabling of COT-SI forwarding and / or repetition can be PC5 RRC configured per sidelink. In such aspects, if the responding UE 615 performs a transmission using a sidelink that has COT-SI forwarding enabled, the responding UE 615 can repeat the COT-SI, and if the responding UE 615 performs a transmission using a sidelink that has COT-SI forwarding disabled, the responding UE 615 can refrain from repeating the COT-SI.

[0108] The initiating UE 610 and / or the responding UE 615 can configure themselves based at least in part on the configuration information. In some aspects, the initiating UE 610 and / or the responding UE 615 can be configured to perform one or more operations described herein based at least in part on the configuration information.

[0109] As shown by reference number 635, the initiating UE 610 can transmit (e.g., via a sidelink, such as via a sidelink described above in connection with reference number 605), an indication of a COT-SI associated with a COT (e.g., COT 625, described in greater detail below). In some aspects, the COT-SI can be associated with a COT (e.g., COT 625) that is configured to be shared by one or more UEs (e.g., the responding UE 615). In some aspects, the COT-SI can be associated with a COT (e.g., COT 625) that is configured to be shared by one or more UEs (e.g., the responding UE 615) in a resource pool (e.g., resource pool 620, described in greater detail below in connection with reference number 640). Figures 4-5BThe COT-SI described above can be associated with a COT 625 and / or a shareable region 630 of the COT 625. For example, the COT-SI can be associated with a COT 625 and / or a shareable region 630 of the COT 625 based at least in part on the COT-SI being transmitted by a responding UE 615 in response to a communication transmitted by an initiating UE 610. In some aspects, the COT-SI can be associated with a COT 625 and / or a shareable region 630 of the COT 625 based at least in part on the COT-SI being transmitted by an initiating UE 610 in response to a COT 625 being detected by the initiating UE 610. In some aspects, the COT-SI can be associated with a COT 625 and / or a shareable region 630 of the COT 625 based at least in part on the COT-SI being transmitted by an initiating UE 610 in response to a COT 625 being detected by the initiating UE 610 and a communication being transmitted by a responding UE 615 in response to the COT 625. Figure 5B As described above, the COT-SI can include information associated with the COT 625 and / or the shareable region 630 of the COT 625, such as an indication of a CAPC associated with the shareable region 630 of the COT 625, a remaining COT duration (e.g., a number of sidelink slots in the shareable region 630 of the COT 625, a number of ms remaining in the shareable region 630 of the COT 625, or a similar indication), an LI ID associated with the shareable region 630 of the COT 625 (e.g., an LI destination ID, an LI source ID, and / or a similar LI ID), an indication of one or more RB sets associated with the shareable region 630 of the COT 625, an additional ID associated with the shareable region 630 of the COT 625 (e.g., a COT sharing ID), and / or other information associated with the shareable region 630 of the COT 625 (e.g., a communication range, additional information regarding time and / or frequency resources, a starting offset associated with the shareable region 630 of the COT 625 and / or a transmission of the responding UE, a channel access type associated with the shareable region 630 of the COT 625, or similar information).

[0110] In some aspects, the communication shown in association with reference number 635 can be a data communication transmitted to the responding UE 615, and / or the COT-SI can be associated with a data communication transmitted to the responding UE 615. In such aspects, the responding UE 615 can be referred to as a data recipient of the initiating UE 610. Additionally, or alternatively, in some aspects, the communication shown in association with reference number 635 can include, and / or be associated with, an indication that the COT-SI is to be repeated in a communication transmitted by the responding UE 615 using the shareable region 630 of the COT 625. For example, in some aspects, the COT-SI can include a one-bit indicator that indicates whether the COT-SI is to be repeated and / or forwarded by the responding UE 615. In such aspects, when the one-bit indicator indicates one of “0” or “1,” the responding UE 615 is to repeat the COT-SI (e.g., COT-SI forwarding is enabled), and when the one-bit indicator indicates the other of “0” or “1,” the responding UE 615 is not to repeat the COT-SI (e.g., COT-SI forwarding is disabled), which is described in more detail below in association with reference number 640.

[0111] In some aspects, the initiating UE 610 and / or the responding UE 615 can receive configuration information from the network node 605 that configures repetition of the COT-SI (as described above in association with reference number 620), and once configured, the initiating UE 610 can indicate, via an indication (e.g., a one-bit indication) associated with the COT-SI, whether the responding UE 615 is to repeat the COT-SI. In other words, if the network node 605 enables COT-SI forwarding in a certain resource pool or otherwise, the COT-SI transmitted via the communication shown in association with reference number 635 can include one additional bit to indicate the enabling of COT-SI forwarding, such that the initiating UE 610 indicates in the COT-SI whether the responding UE 615 should forward the COT-SI.

[0112] In some aspects, the initiating UE 610 can make a determination of whether the responding UEs 615 are to repeat the COT-SI based at least in part on the priority levels sent by the responding UEs. For example, the initiating UE 610 can receive an indication of respective priority levels associated with the reserved resources of the responding UEs. If the average priority level and / or the highest priority level satisfies a priority level threshold, the initiating UE 610 can enable COT-SI. If the average priority level and / or the highest priority level does not satisfy the priority level threshold, the initiating UE 610 can disable COT-SI. For example, the initiating UE 610 can be configured with, designated with, hard-coded with, or otherwise associated with a priority level threshold, such as a priority level threshold equal to “2.” Further, a transmission of a first responding UE having a reserved resource associated with the shareable region 630 of the COT 625 can be associated with a priority level of “1” (e.g., the highest priority level), a transmission of a second responding UE having a reserved resource associated with the shareable region 630 of the COT 625 can be associated with a priority level of “3,” and a transmission of a third responding UE having a reserved resource associated with the shareable region 630 of the COT 625 can be associated with a priority level of “2.” In some aspects, the initiating UE 610 can enable COT-SI forwarding (e.g., can set a one-bit indicator) because the average priority level (2) satisfies the priority level threshold (2). In some other aspects, the initiating UE 610 can enable COT-SI forwarding (e.g., can set a one-bit indicator) because the highest priority level (1) satisfies the priority level threshold (2).

[0113] As indicated by reference 640, the responding UE 615 can identify that the responding UE 615 is a qualified relay UE for the COT-SI based at least in part on the COT-SI. In some aspects, the responding UE 615 can identify that the responding UE 615 is a qualified relay UE for the COT-SI based at least in part on whether the responding UE 615 is a data recipient of the initiating UE 610 (e.g., in some aspects, a qualified relay UE is a data recipient of a COT initiator). In this regard, the responding UE 615 can identify that the responding UE 615 is a qualified relay UE for the COT-SI when an ID (e.g., a source / destination ID pair for a unicast transmission, a destination ID for a groupcast or broadcast transmission) contained in a communication including the COT-SI (e.g., the communication described above in connection with reference 635) matches a logical ID known to the responding UE 615. In such aspects, the responding UE 615 can receive a data communication associated with the COT-SI from the initiating UE 610 via a sidelink, and the responding UE 615 can identify that the responding UE 615 is a qualified relay UE for the COT-SI based at least in part on the responding UE 615 receiving the data communication (e.g., based at least in part on the responding UE 615 being a data recipient of the initiating UE 610).

[0114] Additionally or alternatively, the responding UE 615 can identify that the responding UE 615 is a qualified relay UE for the COT-SI based at least in part on the responding UE 615 identifying that the responding UE 615 is a target UE for the COT-SI. In some aspects, the responding UE 615 can identify that the responding UE 615 is a target UE for the COT-SI based at least in part on at least one ID contained within the COT-SI. For example, the at least one ID can be at least one L1 ID (e.g., a source / destination ID pair for a unicast transmission, or a destination ID for a groupcast or broadcast transmission) contained within a source ID field and / or a destination ID field of the COT-SI. In some other aspects, the at least one ID can be an ID indicated by an additional ID field of the COT-SI, such as a COT sharing ID contained within the additional ID field. In such aspects, if the responding UE 615 identifies that one or more IDs of the COT-SI match a logical ID known at the responding UE 615 (e.g., stored in a layer 2 mapping, etc.), the responding UE 615 can identify that the responding UE 615 is a target of the COT-SI and thus a qualified relay UE for the COT-SI.

[0115] Additionally, or alternatively, the responding UE 615 can identify that the responding UE 615 is a qualified relay UE for COT-SI based at least in part on the responding UE 615 identifying that the responding UE 615 is within a particular range of the initiating UE 610. In some aspects, the responding UE 615 can identify that the responding UE 615 is within the particular range (and thus is a qualified relay UE) based at least in part on an RSRP associated with communications (e.g., the communications described above in connection with reference number 635) between the responding UE 615 and the initiating UE 610 satisfying an RSRP threshold. More specifically, the responding UE 615 can measure an RSRP of the communications carrying the COT-SI, and if the RSRP satisfies the RSRP threshold, the responding UE 615 can determine that it is close to the initiating UE 610 (e.g., within the particular range of the initiating UE 610) and thus is a qualified relay UE.

[0116] Additionally, or alternatively, the responding UE 615 can identify that the responding UE 615 is within the particular range (and thus is a qualified relay UE) based at least in part on the responding UE 615 being associated with a same zone identifier as the initiating UE 610. More specifically, in some aspects, the responding UE 615 can be configured to determine a zone ID (sometimes referred to as Zone_id) associated with a zone in which it is located using a formula. More specifically, the responding UE 615 can be configured to determine the zone ID via a sidelink zone configuration information element (IE) (sometimes referred to as sl-ZoneConfig), which can be part of the configuration information described above in connection with reference number 620. In some aspects, the responding UE 615 can determine the zone ID based at least in part on the formula Zone_id = y1 x 64 + xi, where xi = Floor(x / L) Mod 64, yi = Floor(y / L) Mod 64, L is a value of a zone length parameter (sometimes referred to as sl-ZoneLength) indicated by the sidelink zone configuration IE (e.g., sl-ZoneConfig), x is a geodetic distance in meters between a current location and geographic coordinates (0, 0) of the responding UE 615 according to a World Geodetic System 1984 (WGS84) model, and y is a geodetic distance in meters between the current location and the geographic coordinates (0, 0) of the responding UE 615 according to the WGS84 model. In this regard, the zone ID can be used as an identification that represents a location of a UE, where a granularity of the zone ID depends on the configured value of L. In such aspects, if the initiating UE 610 and the responding UE 615 share the same zone ID (e.g., determined according to the formula described above), the responding UE 615 can identify that it is a qualified relay UE for COT-SI.

[0117] Additionally or alternatively, responsive UE 615 can identify, based at least in part on responsive UE 615 decoding the COT-SI, that responsive UE 615 is a qualified relay UE for the COT-SI. In other words, in some aspects, any responsive UE that is able to decode the COT-SI can be a qualified relay UE, and thus can repeat the COT-SI when responding in the shareable region 630 of COT 625.

[0118] As shown by reference number 645, responsive UE 615 can transmit a communication using a first portion of COT 625 (e.g., the shareable region 630 of COT 625), and initiating UE 610 and / or another UE can receive the communication using the first portion. For example, using the parameters indicated by the COT-SI, responsive UE 615 can utilize COT 625 (more specifically, the shareable region 630 of COT 625) to transmit a communication in a sidelink. Further, in aspects where responsive UE 615 identifies that responsive UE 615 is a qualified relay UE for the COT-SI (as described above in connection with reference number 640), responsive UE 615 can repeat the COT-SI in the communication (e.g., in SCI associated with the communication). In other words, in some aspects, the communication shown in connection with reference number 645 can include the repeated COT-SI based at least in part on responsive UE 615 identifying that responsive UE 615 is a qualified relay UE for the COT-SI.

[0119] In some aspects, the responding UE 615 can indicate the repeated COT-SI is from the responding UE 615 and not the COT initiator (e.g., the initiating UE 610). This can be because, upon receiving the COT-SI, the responding UE (e.g., the responding UE 615 and / or one or more other responding UEs) can map a logical identifier associated with the COT-SI (e.g., a COT sharing ID included in an additional ID field of the COT-SI, etc.) to a logical ID associated with the transmitting UE. Thus, in examples in which the responding UE 615 repeats the COT-SI (e.g., includes the repeated COT-SI in the communication indicated by reference number 645) without an indication that the responding UE 615 is repeating the COT-SI, another responding UE can mistakenly associate the COT-SI with the responding UE 615 (e.g., can map the COT sharing ID to a logical ID associated with the responding UE 615). Accordingly, in some aspects, the COT-SI and / or the repeated COT-SI can include an indicator indicating whether the COT-SI was transmitted by the COT initiator (e.g., the initiating UE 610) or a responding UE (e.g., the responding UE 615). For example, the COT-SI can include a one-bit indicator that is set to one of “0” or “1” when the COT-SI originates from the COT initiator (e.g., the initiating UE 610) and is set to the other of “0” or “1” when the COT-SI originates from the responding UE (e.g., the responding UE 615). Thus, in such aspects, the COT-SI transmitted by the initiating UE 610 (e.g., the COT-SI included with the communication described above in connection with reference number 635) can include an indication that the COT-SI was transmitted by the initiating UE 610 and / or the repeated COT-SI transmitted by the responding UE 615 (e.g., the COT-SI included with the communication described above in connection with reference number 645) can include an indication that the repeated COT-SI was not transmitted by the initiating UE 610. In such cases, a UE receiving the repeated COT-SI can identify that certain IDs associated with the repeated COT-SI (e.g., a source / destination ID pair for unicast transmissions, a destination ID for groupcast and / or broadcast transmissions, etc.) corresponding to the responding UE 615 can not be used to determine whether the UE is a target of the COT-SI.

[0120] Additionally or alternatively, a responding UE 615 can update certain information associated with a COT-SI, such as information associated with a remaining COT duration, information regarding time resources and / or frequency resources, or the like, in response to repeating and / or forwarding the COT-SI. In this regard, in some aspects, a COT-SI transmitted by the initiating UE 610 (e.g., a COT-SI included with the communication described above in connection with reference number 635) can include an indication of time resources and / or frequency resources associated with the shareable region 630 of the COT 625, and a repeated COT-SI transmitted by the responding UE 615 (e.g., a COT-SI included with the communication described above in connection with reference number 645) can include an indication of time resources and / or frequency resources associated with a portion of the shareable region 630 of the COT 625 that remains after the communication in which the repeated COT-SI is transmitted (e.g., the communication described above in connection with reference number 645) is transmitted.

[0121] Additionally or alternatively, a COT-SI can include an indication of an offset between an initial COT-SI reception time (e.g., a reception time associated with a COT-SI transmitted by a COT initiator, such as the initiating UE 610) and a COT-SI forwarding time (e.g., a time at which a COT-SI is forwarded and / or repeated by a qualified repeater UE, such as the responding UE 615). In such aspects, if the offset is equal to zero, a responding UE receiving a COT-SI can identify that the COT-SI is a COT-SI transmitted by a COT initiator (e.g., the initiating UE 610), and if the offset is greater than zero, a responding UE receiving a COT-SI can identify that the COT-SI is a repeated COT-SI transmitted by another responding UE (e.g., the responding UE 615). Thus, in some aspects, a COT-SI transmitted by the initiating UE 610 (e.g., a COT-SI included with the communication described above in connection with reference number 635) can include an indication of a zero offset between an initial COT-SI reception time and a COT-SI forwarding time, and a repeated COT-SI transmitted by the responding UE 615 (e.g., a COT-SI included with the communication described above in connection with reference number 645) can include an indication of an offset greater than zero between an initial COT-SI reception time and a COT-SI forwarding time.

[0122] Additionally or alternatively, in some aspects, when repeating the COT-SI, the responding UE 615 can indicate additional information associated with the COT initiator (e.g., the initiating UE 610) such that other responding UEs receiving the repeated COT-SI can map the COT initiator to the COT-SI. For example, in some aspects, the responding UE 615 can transmit a third stage SCI (SCI-3) indicating one or more logical IDs associated with the initiating UE 610 with a communication using the shareable region 630 of the COT 625 (e.g., the communication described above in connection with reference number 645). In such aspects, the SCI-3 can not be transmitted if the COT-SI is from the initiating UE 610 (e.g., as described above in connection with reference number 635). Thus, a UE receiving the COT-SI (e.g., the responding UE 615 and / or one or more other responding UEs) can map the COT share ID associated with the COT 625 to a logical ID (e.g., a source ID and / or a destination ID contained in the SCI-2) from the COT initiator (e.g., the initiating UE 610). On the other hand, the SCI-3 can be transmitted if the COT-SI is from the responding UE 615 or another eligible relay UE (e.g., as described above in connection with reference number 645). Thus, a UE receiving the repeated COT-SI (e.g., one or more other responding UEs) can map the COT share ID associated with the COT 625 to a logical ID (e.g., a source ID and / or a destination ID) contained in the SCI-3.

[0123] In some aspects, an eligible relay UE (e.g., the responding UE 615) can only repeat the COT-SI if certain other conditions are met. In other words, in some aspects, not all eligible relay UEs will repeat the COT-SI when responding in a COT. For example, in some aspects, when an eligible relay UE (e.g., the responding UE 615) receives a COT-SI from another UE, the eligible relay UE can only forward and / or repeat the COT-SI if a portion of the COT’s shareable region to be used by the eligible relay UE is located at a front portion of the COT’s shareable region. In some aspects, the front portion of the COT’s shareable region can be defined according to a percentage parameter of first occurrence (sometimes referred to as X). For example, in some aspects, if the eligible relay UE is transmitting a communication in the COT’s shareable region in the first X% of slots, the eligible relay UE can only repeat the COT-SI.

[0124] In Figure 6In the illustrated example, a front portion of the shareable region of the COT is indicated by reference number 650. As shown, the communication including the repeated COT-SI (e.g., the communication described above in connection with reference number 645) occurs within the front portion of the shareable region of the COT. Thus, in some aspects, the responding UE 615 can include the repeated COT-SI in the communication using the shareable region of the COT based at least in part on the communication being transmitted in the front of the shareable region of the COT. Moreover, in some aspects, the front portion of the shareable region of the COT can be associated with a percentage (e.g., X%) of the first occurrence of the shareable region of the COT, as described above. Additionally or alternatively, the responding UE 615 can receive configuration information from the network node 605 via the access link indicating the percentage of the first occurrence of the shareable region of the COT (e.g., the responding UE 615 can receive an indication of the percentage value of the first occurrence via the configuration information described above in connection with reference number 620). In this regard, and as indicated by reference number 655, in some aspects, the responding UE 615 can transmit a communication in the shareable region 630 of the COT 625 that occurs after the front portion (e.g., after the first X% of the slot) in some aspects, the responding UE 615 can omit the COT-SI from the communication (e.g., can not repeat the COT-SI), despite the responding UE 615 being a qualified relay UE, because the communication occurs after the front portion of the shareable region 630 of the COT 625.

[0125] In some aspects, upon receiving the COT-SI from another UE (e.g., the initiating UE 610), a qualified relay UE (e.g., the responding UE 615) can forward and / or repeat the COT-SI once within the shareable region 630 of the COT 625 and / or within the configured portion of the shareable region 630 of the COT 625. In this regard, the responding UE 615 can repeat the COT-SI for any other responding UEs that can have missed the initial transmission of the COT-SI from the initiating UE 610, but the responding UE 615 can refrain from repeating the COT-SI multiple times in order to reduce the overhead associated with the repetition of the COT-SI. For example, as shown, the responding UE 615 can transmit a communication including the COT-SI within the configured portion of the shareable region 630 of the COT 625. In this regard, the responding UE 615 can transmit the communication including the COT-SI within the configured portion of the shareable region 630 of the COT 625 in order to provide the COT-SI to any other responding UEs that can have missed the initial transmission of the COT-SI from the initiating UE 610. Figure 6In some aspects, the responding UE 615 can transmit, in the shareable region 630 of the COT 625, a first communication including a repeated COT-SI (e.g., the communication shown in connection with reference number 645), and the responding UE 615 can transmit, in the shareable region 630 of the COT 625, a second communication omitting the repeated COT-SI (e.g., the communication shown in connection with reference number 655). In other words, in some aspects, the responding UE 615 can include the repeated COT-SI in a communication (e.g., the communication shown in connection with reference number 645) using the shareable region 630 of the COT 625 based at least in part on the communication being a first occurrence of the multiple transmissions performed by the responding UE 615 during the shareable region 630 of the COT 625.

[0126] Based at least in part on the responding UE 615 identifying whether the responding UE 615 is a qualified relay UE for the COT-SI and repeating the COT-SI accordingly, the responding UE 615, the initiating UE 610, the network node 605, and / or other responding UEs can conserve computational, power, network, and / or communication resources that would have otherwise been consumed in a communication scheme in which the COT-SI is transmitted by the initiating UE 610 only a single time. For example, based at least in part on the responding UE 615 identifying whether the responding UE 615 is a qualified relay UE for the COT-SI and repeating the COT-SI accordingly, more responding UEs can receive the COT-SI and thus utilize the shareable region 630 of the COT 625, thereby improving resource utilization and leading to more efficient use of network resources.

[0127] As indicated above, Figure 6 are provided as examples. Other examples can differ from what is described Figure 6 with respect to the examples described in this regard.

[0128] Figure 7 is a diagram illustrating an example process 700 performed, for example, by a first UE, in accordance with the present disclosure. Example process 700 is an example where the first UE (e.g., a responding UE 615) performs operations associated with techniques for repeating a COT-SI.

[0129] As Figure 7 indicated above, in some aspects, process 700 can include receiving, from a second UE (e.g., an initiating UE 610) via a sidelink, a COT-SI associated with a first portion of a COT (block 710). For example, the first UE (e.g., using reception component 902 and / or communication manager 906, depicted in FIG. 9) can receive, from a second UE via a sidelink, a COT-SI associated with a first portion of a COT, as described above. Figure 9

[0130] As​Figure 7 Further, as shown, in some aspects, process 700 can include identifying, based at least in part on the COT-SI, that the first UE is a qualified repeater UE for the COT-SI (block 720). For example, the first UE (e.g., using transmission component 904 and / or communication manager 906, depicted in FIG. 9) can identify, based at least in part on the COT-SI, that the first UE is a qualified repeater UE for the COT-SI, as described above. Figure 9 The communication manager 906, depicted in FIG. 9, can identify, based at least in part on the COT-SI, that the first UE is a qualified repeater UE for the COT-SI, as described above.

[0131] As Figure 7 Further, as shown, in some aspects, process 700 can include transmitting, based at least in part on the first UE being a qualified repeater UE for the COT-SI, a communication using the first portion of the COT, the communication including the repeated COT-SI (block 730). For example, the first UE (e.g., using transmission component 904 and / or communication manager 906, depicted in FIG. 9) can transmit, based at least in part on the first UE being a qualified repeater UE for the COT-SI, a communication using the first portion of the COT, the communication including the repeated COT-SI, as described above. Figure 9 The communication manager 906, depicted in FIG. 9, can identify, based at least in part on the COT-SI, that the first UE is a qualified repeater UE for the COT-SI, as described above.

[0132] Process 700 can include additional aspects, such as any single aspect or any combination of aspects described below and / or in connection with one or more other processes described elsewhere herein.

[0133] In a first aspect, process 700 includes receiving, via a sidelink from a second UE, a data communication associated with a COT-SI, where the identification of the first UE being a qualified repeater UE for the COT-SI is based at least in part on the first UE receiving the data communication.

[0134] In a second aspect, alone or in combination with the first aspect, the identification of the first UE being a qualified repeater UE for the COT-SI is based at least in part on the first UE identifying that at least one logical identifier associated with the COT-SI corresponds to the first UE.

[0135] In a third aspect, alone or in combination with one or more of the first and second aspects, the identification of the first UE being a qualified repeater UE for the COT-SI is based at least in part on the first UE identifying that the first UE is a target UE for the COT-SI.

[0136] In a fourth aspect, alone or in combination with one or more of the first through third aspects, the identification of the first UE being a qualified repeater UE for the COT-SI is based at least in part on an RSRP associated with communications between the first UE and the second UE satisfying an RSRP threshold.

[0137] In a fifth aspect, alone or in combination with one or more of the first through fourth aspects, the identification of the first UE as a qualified relay UE of the COT-SI is based at least in part on the first UE being associated with a same zone identifier as a zone identifier of the second UE.

[0138] In a sixth aspect, alone or in combination with one or more of the first through fifth aspects, the identification of the first UE as a qualified relay UE of the COT-SI is based at least in part on the first UE decoding the COT-SI.

[0139] In a seventh aspect, alone or in combination with one or more of the first through sixth aspects, the process 700 includes receiving configuration information configuring repetition of the COT-SI.

[0140] In an eighth aspect, alone or in combination with one or more of the first through seventh aspects, the configuration information is received from a network node via an access link.

[0141] In a ninth aspect, alone or in combination with one or more of the first through eighth aspects, the configuration information is associated with a resource pool used by the first UE to transmit a communication using the first portion of the COT.

[0142] In a tenth aspect, alone or in combination with one or more of the first through ninth aspects, the configuration information is received from the second UE via a sidelink.

[0143] In an eleventh aspect, alone or in combination with one or more of the first through tenth aspects, the process 700 includes receiving, from the second UE via a sidelink, an indication that the COT-SI is to be repeated in a communication transmitted by the first UE using the first portion of the COT.

[0144] In a twelfth aspect, alone or in combination with one or more of the first through eleventh aspects, the indication that the COT-SI is to be repeated is a one-bit indicator associated with the COT-SI.

[0145] In a thirteenth aspect, alone or in combination with one or more of the first through twelfth aspects, the indication that the COT-SI is to be repeated is based at least in part on at least one of: an average priority level of one or more responding UEs associated with the first portion of the COT satisfying a priority level threshold, or a highest priority level of one or more responding UEs associated with the first portion of the COT satisfying a priority level threshold.

[0146] In a fourteenth aspect, alone or in combination with one or more of the first through thirteenth aspects, process 700 includes receiving, from the network node via the access link, configuration information configuring repetition of the COT-SI, and receiving, from the second UE via the sidelink, an indication that the COT-SI is to be repeated in a communication transmitted by the first UE using a first portion of the COT.

[0147] In a fifteenth aspect, alone or in combination with one or more of the first through fourteenth aspects, including the repeated COT-SI in the communication using the first portion of the COT is based at least in part on the communication being transmitted in a front portion of the first portion of the COT.

[0148] In a sixteenth aspect, alone or in combination with one or more of the first through fifteenth aspects, the front portion of the first portion of the COT is associated with a percentage of a first occurrence of the first portion of the COT.

[0149] In a seventeenth aspect, alone or in combination with one or more of the first through sixteenth aspects, process 700 includes receiving, from the network node via the access link, configuration information indicating the percentage of the first occurrence of the first portion of the COT.

[0150] In an eighteenth aspect, alone or in combination with one or more of the first through seventeenth aspects, including the repeated COT-SI in the communication using the first portion of the COT is based at least in part on the communication being a first occurrence of a transmission by the first UE performed during the first portion of the COT of a plurality of transmissions.

[0151] In a nineteenth aspect, alone or in combination with one or more of the first through eighteenth aspects, the COT-SI includes an indication that the COT-SI is transmitted by the second UE, and the repeated COT-SI includes an indication that the repeated COT-SI is not transmitted by the second UE.

[0152] In a twentieth aspect, alone or in combination with one or more of the first through nineteenth aspects, the COT-SI includes an indication of at least one of a time resource or a frequency resource associated with the first portion of the COT, and the repeated COT-SI includes an indication of at least one of a time resource or a frequency resource associated with a second portion of the first portion of the COT remaining after the communication including the repeated COT-SI is transmitted.

[0153] In a twenty-first aspect, alone or in combination with one or more of the first through twentieth aspects, the COT-SI includes an indication of a zero offset between an initial COT-SI reception time and a COT-SI forwarding time, and the repeated COT-SI includes an indication of an offset greater than zero between the initial COT-SI reception time and the COT-SI forwarding time.

[0154] In a twenty-second aspect, alone or in combination with one or more of the first through twenty-first aspects, the process 700 includes transmitting, with the communication using the first portion of the COT, third sidelink control information indicating one or more logical identifiers associated with the second UE.

[0155] Although Figure 7 Example blocks of the process 700 are illustrated, but in some aspects, the process 700 can include additional blocks, fewer blocks, different blocks, or differently arranged blocks than those depicted in FIG. 8. Additionally, or alternatively, two or more of the blocks of the process 700 can be performed in parallel. Figure 7

[0156] Figure 8 is a diagram illustrating an example process 800 performed, for example, by a first UE, in accordance with the present disclosure. Example process 800 is an example where the first UE (e.g., initiating UE 610) performs operations associated with techniques for repeated COT-SI.

[0157] As Figure 8 further shown, in some aspects, the process 800 can include transmitting, to the second UE via a sidelink, a COT-SI associated with a first portion of a COT (block 810). For example, the first UE (e.g., using transmission component 904 and / or communication manager 906) can transmit, to the second UE via a sidelink, a COT-SI associated with a first portion of a COT, as described above. Figure 9

[0158] As Figure 8 further shown, in some aspects, the process 800 can include indicating whether the second UE is a qualified relay UE for the COT-SI (block 820). For example, the first UE (e.g., using communication manager 906) can indicate whether the second UE is a qualified relay UE for the COT-SI, as described above. Figure 9

[0159] Process 800 can include additional aspects, such as any single aspect or any combination of aspects described below and / or in connection with one or more other processes described elsewhere herein.

[0160] ​​​In a first aspect, the process 800 includes transmitting, via a sidelink, a data communication associated with the COT-SI to the second UE, where the indication of whether the second UE is an eligible relay UE for the COT-SI is based at least in part on transmitting the data communication to the second UE.

[0161] In a second aspect, alone or in combination with the first aspect, the indication of whether the second UE is an eligible relay UE for the COT-SI is based at least in part on including, in the COT-SI, at least one logical identifier corresponding to the second UE.

[0162] In a third aspect, alone or in combination with one or more of the first and second aspects, the indication of whether the second UE is an eligible relay UE for the COT-SI is based at least in part on the second UE being a target UE for the COT-SI.

[0163] In a fourth aspect, alone or in combination with one or more of the first through third aspects, the indication of whether the second UE is an eligible relay UE for the COT-SI is based at least in part on an RSRP associated with communications between the second UE and the first UE satisfying an RSRP threshold.

[0164] In a fifth aspect, alone or in combination with one or more of the first through fourth aspects, the indication of whether the second UE is an eligible relay UE for the COT-SI is based at least in part on the second UE being associated with a zone identifier that is the same as a zone identifier of the first UE.

[0165] In a sixth aspect, alone or in combination with one or more of the first through fifth aspects, the indication of whether the second UE is an eligible relay UE for the COT-SI is based at least in part on the second UE being capable of decoding the COT-SI.

[0166] In a seventh aspect, alone or in combination with one or more of the first through sixth aspects, the process 800 includes receiving, via an access link from a network node, configuration information configuring repetition of the COT-SI.

[0167] In an eighth aspect, alone or in combination with one or more of the first through seventh aspects, the configuration information is associated with a resource pool used by the first UE to transmit the COT-SI.

[0168] In a ninth aspect, alone or in combination with one or more of the first through eighth aspects, the process 800 includes transmitting, via a sidelink, an indication to the second UE that the COT-SI is to be repeated in a communication transmitted by the second UE using a first portion of a COT.

[0169] In a tenth aspect, alone or in combination with one or more of the first through ninth aspects, the indication that the COT-SI is to be repeated is a one-bit indicator associated with the COT-SI.

[0170] In an eleventh aspect, alone or in combination with one or more of the first through tenth aspects, the indication that the COT-SI is to be repeated is based at least in part on at least one of: an average priority level of one or more responding UEs associated with the first portion of the COT satisfying a priority level threshold, or a highest priority level of one or more responding UEs associated with the first portion of the COT satisfying a priority level threshold.

[0171] In a twelfth aspect, alone or in combination with one or more of the first through eleventh aspects, the process 800 includes receiving, from the network node via an access link, configuration information configuring repetition of the COT-SI, and transmitting, to the second UE via a sidelink, an indication that the COT-SI is to be repeated in a communication transmitted by the second UE using the first portion of the COT.

[0172] In a thirteenth aspect, alone or in combination with one or more of the first through twelfth aspects, the COT-SI includes an indication that the COT-SI is transmitted by the first UE.

[0173] In a fourteenth aspect, alone or in combination with one or more of the first through thirteenth aspects, the COT-SI includes an indication of a zero offset between an initial COT-SI reception time and a COT-SI forwarding time.

[0174] Although Figure 8 An example block of the process 800 is shown, but in some aspects, the process 800 can include additional blocks, fewer blocks, different blocks, or differently arranged blocks than those depicted in Figure 8 In aspects, one or more of the following features can be included in the process 800. In aspects, the process 800 includes one or more of the following features.

[0175] Figure 9 is a diagram of an example apparatus 900 for wireless communication in accordance with the present disclosure. The apparatus 900 can be a first UE (e.g., an initiating UE 610, a responding UE 615), or a first UE can include the apparatus 900. In some aspects, the apparatus 900 includes a reception component 902, a transmission component 904, and / or a communication manager 906, which can communicate with one another via one or more buses and / or one or more other components. In some aspects, the communication manager 906 is the communication manager 706. Figure 1The described communication manager 140. As shown, apparatus 900 can communicate with another apparatus 908, such as a second UE (e.g., initiating UE 610, responding UE 615) or a network node (such as a CU, DU, RU, or base station), using a reception component 902 and a transmission component 904.

[0176] In some aspects, the apparatus 900 can be configured to perform one or more operations described herein based on a UE 120. Additionally or alternatively, the apparatus 900 can be configured to perform one or more processes described herein, such as process 700 of FIG. 7, Figure 6 Figure 7 In some aspects, the apparatus 900 can be configured to perform one or more operations described herein based on a UE 120. Additionally or alternatively, the apparatus 900 can be configured to perform one or more processes described herein, such as process 700 of FIG. 7, Figure 8 Figure 9 In some aspects, the apparatus 900 and / or one or more components thereof can include one or more components of the UE 120 described in connection with FIG. 2. Additionally or alternatively, one or more components of the apparatus 900 shown can be implemented within one or more components of the UE 120 described in connection with FIG. 2. Additionally or alternatively, one or more components of the apparatus 900 can be implemented at least in part as software stored in a memory. For example, a component (or a portion of a component) can be implemented as instructions or code stored in a non-transitory computer-readable medium and executable by a controller or a processor to perform the functions or operations of the component. Figure 2 Figure 9 The reception component 902 can receive communications, such as reference signals, control information, data communications, or a combination thereof, from the apparatus 908. The reception component 902 can provide received communications to one or more other components of the apparatus 900. In some aspects, the reception component 902 can perform signal processing on the received communications (such as filtering, amplification, demodulation, analog-to-digital conversion, demultiplexing, deinterleaving, de-mapping, equalization, interference cancellation, or decoding, among other examples), and can provide the processed signals to one or more other components of the apparatus 900. In some aspects, the reception component 902 can include one or more antennas, a modem, a demodulator, a MIMO detector, a receive processor, a controller / processor, a memory, or a combination thereof, of the UE 120 described in connection with FIG. 2. Figure 2

[0177] The reception component 902 can receive communications, such as reference signals, control information, data communications, or a combination thereof, from the apparatus 908. The reception component 902 can provide received communications to one or more other components of the apparatus 900. In some aspects, the reception component 902 can perform signal processing on the received communications (such as filtering, amplification, demodulation, analog-to-digital conversion, demultiplexing, deinterleaving, de-mapping, equalization, interference cancellation, or decoding, among other examples), and can provide the processed signals to one or more other components of the apparatus 900. In some aspects, the reception component 902 can include one or more antennas, a modem, a demodulator, a MIMO detector, a receive processor, a controller / processor, a memory, or a combination thereof, of the UE 120 described in connection with FIG. 2. Figure 2

[0178] ​​​​​The transmission component 904 can transmit communications, such as reference signals, control information, data communications, or a combination thereof, to the apparatus 908. In some aspects, one or more other components of the apparatus 900 can generate communications and can provide the generated communications to the transmission component 904 for transmission to the apparatus 908. In some aspects, the transmission component 904 can perform signal processing on the generated communications (such as filtering, amplification, modulation, digital-to-analog conversion, multiplexing, interleaving, mapping, or encoding, among other examples), and can transmit the processed signals to the apparatus 908. In some aspects, the transmission component 904 can include one or more antennas, a modem, a modulator, a transmit MIMO processor, a transmit processor, a controller / processor, a memory, or a combination thereof, of the described UE 120. In some aspects, the transmission component 904 can be co-located with the reception component 902 in a transceiver. Figure 2 The transmission component 904 can transmit communications, such as reference signals, control information, data communications, or a combination thereof, to the apparatus 908. In some aspects, one or more other components of the apparatus 900 can generate communications and can provide the generated communications to the transmission component 904 for transmission to the apparatus 908. In some aspects, the transmission component 904 can perform signal processing on the generated communications (such as filtering, amplification, modulation, digital-to-analog conversion, multiplexing, interleaving, mapping, or encoding, among other examples), and can transmit the processed signals to the apparatus 908. In some aspects, the transmission component 904 can include one or more antennas, a modem, a modulator, a transmit MIMO processor, a transmit processor, a controller / processor, a memory, or a combination thereof, of the described UE 120. In some aspects, the transmission component 904 can be co-located with the reception component 902 in a transceiver.

[0179] The communication manager 906 can support the operations of the reception component 902 and / or the transmission component 904. For example, the communication manager 906 can receive information associated with configuring reception of communications by the reception component 902 and / or transmission of communications by the transmission component 904. Additionally, or alternatively, the communication manager 906 can generate control information and / or provide control information to the reception component 902 and / or the transmission component 904 to control the reception and / or transmission of communications.

[0180] The reception component 902 can receive, from a second UE via a sidelink, a COT-SI associated with a first portion of a COT. The communication manager 906 can identify that the first UE is a qualified relay UE for the COT-SI based at least in part on the COT-SI. The transmission component 904 can transmit, using the first portion of the COT, a communication that includes a repetition of the COT-SI based at least in part on the first UE being the qualified relay UE for the COT-SI.

[0181] The reception component 902 can receive, from a second UE via a sidelink, a data communication associated with a COT-SI, where an identification that the first UE is a qualified relay UE for the COT-SI is based at least in part on the first UE receiving the data communication. The reception component 902 can receive configuration information configuring a repetition of the COT-SI. The reception component 902 can receive, from the second UE via the sidelink, an indication that the COT-SI is to be repeated in a communication transmitted by the first UE using the first portion of the COT. The reception component 902 can receive, from a network node via an access link, configuration information configuring the repetition of the COT-SI. The reception component 902 can receive, from the network node via the access link, configuration information indicating a percentage of a first occurrence of the first portion of the COT.

[0182] The transmission component 904 can transmit, with a communication using a first portion of a COT, a third level sidelink control information indicating one or more logical identifiers associated with a second UE. The transmission component 904 can transmit, to the second UE via a sidelink, a COT-SI associated with the first portion of the COT. The communication manager 906 can indicate whether the second UE is a qualified relay UE for the COT-SI. The transmission component 904 can transmit, to the second UE via the sidelink, a data communication associated with the COT-SI, where the indication of whether the second UE is a qualified relay UE for the COT-SI is based at least in part on transmitting the data communication to the second UE.

[0183] The reception component 902 can receive, from a network node via an access link, configuration information configuring repetition of a COT-SI. The transmission component 904 can transmit, to a second UE via a sidelink, an indication that the COT-SI is to be repeated in a communication transmitted by the second UE using a first portion of a COT.

[0184] Figure 9 The number and arrangement of components shown is provided as an example. In practice, there can be additional components, fewer components, different components, or differently arranged components than those shown. Figure 9 than those shown. Additionally or alternatively, some of the components shown can be implemented by one or more other components not specifically shown in the figure. The components shown can be implemented in hardware, software, or a combination of both hardware and software. Figure 9 Two or more components illustrated can be implemented within a single component, or Figure 9 A single component illustrated can be implemented as multiple, distributed components. Additionally or alternatively, Figure 9 A set of one or more components illustrated can perform one or more functions described as being performed by another set of one or more components illustrated. Figure 9 Another set of components illustrated can perform one or more functions described as being performed by the set of one or more components illustrated.

[0185] An overview of some aspects of the present disclosure is provided below:

[0186] Aspect 1 : A method of wireless communication performed by a first UE, the method comprising: receiving, from a second UE via a sidelink, a COT-SI associated with a first portion of a COT; identifying, based at least in part on the COT-SI, that the first UE is a qualified relay UE for the COT-SI; and transmitting, by the first UE and based at least in part on the first UE being the qualified relay UE for the COT-SI, a communication using the first portion of the COT, the communication including a repeated COT-SI.

[0187] Aspect 2: The method of Aspect 1, further comprising: receiving, from the second UE via the sidelink, a data communication associated with the COT-SI, wherein the identification that the first UE is a qualified relay UE for the COT-SI is based at least in part on the first UE receiving the data communication.

[0188] Aspect 3: The method of any of aspects 1-2, wherein the identification of the first UE as a qualified repeater UE of the COT-SI is based at least in part on the first UE identifying that a correspondence of at least one logical identifier associated with the COT-SI corresponds to the first UE.

[0189] Aspect 4: The method of any of aspects 1-3, wherein the identification of the first UE as a qualified repeater UE of the COT-SI is based at least in part on the first UE identifying that the first UE is a target UE of the COT-SI.

[0190] Aspect 5: The method of any of aspects 1-4, wherein the identification of the first UE as a qualified repeater UE of the COT-SI is based at least in part on a RSRP associated with a communication between the first UE and the second UE satisfying a RSRP threshold.

[0191] Aspect 6: The method of any of aspects 1-5, wherein the identification of the first UE as a qualified repeater UE of the COT-SI is based at least in part on the first UE being associated with a same zone identifier as a zone identifier of the second UE.

[0192] Aspect 7: The method of any of aspects 1-6, wherein the identification of the first UE as a qualified repeater UE of the COT-SI is based at least in part on the first UE decoding the COT-SI.

[0193] Aspect 8: The method of any of aspects 1-7, further comprising: receiving configuration information configuring repetition of the COT-SI.

[0194] Aspect 9: The method of aspect 8, wherein the configuration information is received from a network node via an access link.

[0195] Aspect 10: The method of aspect 9, wherein the configuration information is associated with a resource pool used by the first UE to transmit the communication using the first portion of the COT.

[0196] Aspect 11: The method of aspect 8, wherein the configuration information is received from the second UE via the sidelink.

[0197] Aspect 12: The method of any of aspects 1-11, further comprising: receiving, from the second UE via the sidelink, an indication that the COT-SI is to be repeated in the communication transmitted by the first UE using the first portion of the COT.

[0198] Aspect 13: The method of aspect 12, wherein the indication that the COT-SI is to be repeated is a one-bit indicator associated with the COT-SI.

[0199] Aspect 14: The method of aspect 12, wherein the indication that the COT-SI is to be repeated is based at least in part on at least one of: an average priority level of one or more responding UEs associated with the first portion of the COT satisfies a priority level threshold, or a highest priority level of the one or more responding UEs associated with the first portion of the COT satisfies the priority level threshold.

[0200] Aspect 15: The method of any one of aspects 1 through 14, further comprising: receiving, from a network node via an access link, configuration information configuring repetition of the COT-SI; and receiving, from the second UE via the sidelink, an indication that the COT-SI is to be repeated in the communication transmitted by the first UE using the first portion of the COT.

[0201] Aspect 16: The method of any one of aspects 1 through 15, wherein including the repeated COT-SI in the communication using the first portion of the COT is based at least in part on the communication being transmitted in a front portion of the first portion of the COT.

[0202] Aspect 17: The method of aspect 16, wherein the front portion of the first portion of the COT is associated with a percentage of a first occurrence of the first portion of the COT.

[0203] Aspect 18: The method of aspect 17, comprising: receiving, from a network node via an access link, configuration information indicating the percentage of the first occurrence of the first portion of the COT.

[0204] Aspect 19: The method of any one of aspects 1 through 18, wherein including the repeated COT-SI in the communication using the first portion of the COT is based at least in part on the communication being a first occurring transmission of a plurality of transmissions performed by the first UE during the first portion of the COT.

[0205] Aspect 20: The method of any one of aspects 1 through 19, wherein the COT-SI includes an indication that the COT-SI is transmitted by the second UE, and wherein the repeated COT-SI includes an indication that the repeated COT-SI is not transmitted by the second UE.

[0206] Aspect 21 : The method of any of aspects 1-20, wherein the COT-SI comprises an indication of at least one of a time resource or a frequency resource associated with the first portion of the COT, and wherein the repeated COT-SI comprises an indication of at least one of a time resource or a frequency resource associated with a second portion of the first portion of the COT that remains after the communication comprising the repeated COT-SI is transmitted.

[0207] Aspect 22: The method of any of aspects 1-21, wherein the COT-SI comprises an indication of a zero offset between an initial COT-SI reception time and a COT-SI forwarding time, and wherein the repeated COT-SI comprises an indication of an offset greater than zero between the initial COT-SI reception time and the COT-SI forwarding time.

[0208] Aspect 23: The method of any of aspects 1-22, further comprising transmitting, with the communication using the first portion of the COT, a third level of sidelink control information indicating one or more logical identifiers associated with the second UE.

[0209] Aspect 24: A method of wireless communication performed by a first UE, the method comprising: transmitting, to a second UE via a sidelink, a COT-SI associated with a first portion of a COT; and indicating whether the second UE is a qualified relay UE for the COT-SI.

[0210] Aspect 25: The method of aspect 24, further comprising: transmitting, to the second UE via the sidelink, a data communication associated with the COT-SI, wherein the indication of whether the second UE is a qualified relay UE for the COT-SI is based at least in part on transmitting the data communication to the second UE.

[0211] Aspect 26: The method of any of aspects 24-25, wherein the indication of whether the second UE is a qualified relay UE for the COT-SI is based at least in part on including, in the COT-SI, at least one logical identifier corresponding to the second UE.

[0212] Aspect 27: The method of any of aspects 24-26, wherein the indication of whether the second UE is a qualified relay UE for the COT-SI is based at least in part on the second UE being a target UE for the COT-SI.

[0213] Aspect 28: The method of any one of aspects 24 through 27, wherein the indication of whether the second UE is a qualified repeater UE of the COT-SI is based at least in part on a RSRP associated with communications between the second UE and the first UE satisfying a RSRP threshold.

[0214] Aspect 29: The method of any one of aspects 24 through 28, wherein the indication of whether the second UE is a qualified repeater UE of the COT-SI is based at least in part on the second UE being associated with a same zone identifier as a zone identifier of the first UE.

[0215] Aspect 30: The method of any one of aspects 24 through 29, wherein the indication of whether the second UE is a qualified repeater UE of the COT-SI is based at least in part on the second UE being capable of decoding the COT-SI.

[0216] Aspect 31 : The method of any one of aspects 24 through 30, further comprising: receiving, from a network node via an access link, configuration information configuring repetition of the COT-SI.

[0217] Aspect 32: The method of aspect 31, wherein the configuration information is associated with a resource pool used by the first UE to transmit the COT-SI.

[0218] Aspect 33: The method of any one of aspects 24 through 32, further comprising: transmitting, to the second UE via the sidelink, an indication that the COT-SI is to be repeated in a communication transmitted by the second UE using the first portion of the COT.

[0219] Aspect 34: The method of aspect 33, wherein the indication that the COT-SI is to be repeated is a one-bit indicator associated with the COT-SI.

[0220] Aspect 35: The method of aspect 33, wherein the indication that the COT-SI is to be repeated is based at least in part on at least one of: an average priority level of one or more responding UEs associated with the first portion of the COT satisfying a priority level threshold, or a highest priority level of the one or more responding UEs associated with the first portion of the COT satisfying the priority level threshold.

[0221] Aspect 36: The method of any of aspects 24 through 35, further comprising: receiving, from a network node via an access link, configuration information configuring repetition of the COT-SI; and transmitting, to the second UE via the sidelink, an indication that the COT-SI is to be repeated in a communication transmitted by the second UE using the first portion of the COT.

[0222] Aspect 37: The method of any of aspects 24 through 36, wherein the COT-SI comprises an indication that the COT-SI is transmitted by the first UE.

[0223] Aspect 38: The method of any of aspects 24 through 37, wherein the COT-SI comprises an indication of a zero offset between an initial COT-SI reception time and a COT-SI forwarding time.

[0224] Aspect 39: An apparatus for wireless communication at a device, the apparatus comprising: a processor; memory coupled with the processor; and instructions stored in the memory and executable by the processor to cause the apparatus to perform the method of one or more of aspects 1 through 38.

[0225] Aspect 40: A device for wireless communication, the device comprising: memory; and one or more processors coupled to the memory, the one or more processors configured to perform the method of one or more of aspects 1 through 38.

[0226] Aspect 41: An apparatus for wireless communication, the apparatus comprising at least one means for performing the method of one or more of aspects 1 through 38.

[0227] Aspect 42: A non-transitory computer-readable medium storing code for wireless communication, the code comprising instructions executable by a processor to perform the method of one or more of aspects 1 through 38.

[0228] Aspect 43: A non-transitory computer-readable medium storing a set of instructions for wireless communication, the set of instructions comprising one or more instructions that, when executed by one or more processors of a device, cause the device to perform the method of one or more of aspects 1 through 38.

[0229] While the foregoing disclosure provides examples and descriptions, it is not intended to be exhaustive or to limit the aspects to the precise form disclosed. Modifications and variations are possible in light of the above disclosure or from practice of the aspects.

[0230] As used herein, the term “component” is intended to be broadly interpreted to include hardware, firmware, or a combination of hardware and software. As used herein, a processor is implemented in hardware, firmware, or a combination of hardware and software. As used herein, the phrase “based on” is intended to be broadly interpreted to mean “based, at least in part, on.” As used herein, depending on the context, “satisfies a threshold” can refer to a value being greater than a threshold, greater than or equal to a threshold, less than a threshold, less than or equal to a threshold, equal to a threshold, not equal to a threshold, and the like. As used herein, a phrase referring to “at least one of’ a list of items means any combination of those items, including single members. As an example, “at least one of a, b, or c” is intended to cover a, b, c, a-b, a-c, b-c, and a-b-c.

[0231] Also, as used herein, the articles “a” and “an” are intended to include one or more items, and can be used interchangeably with “one or more.” Furthermore, as used herein, the article “the” is intended to include the item(s), zero or one or more item and can be used interchangeably with “the one or more.” Also, as used herein, the terms “set” and “group” are intended to include one or more items (for example, related items, unrelated items, or a combination of related and unrelated items), and can be used interchangeably with “one or more.” Where only one item is intended, the phrase “only one” or similar language can be used. Also, as used herein, the term “has” and its variants are intended to be broad terms of inclusion, and are not limited to direct and tangible possession. Also, as used herein, the term “or” is intended to be inclusive, and can be used interchangeably with “and / or,” unless expressly stated otherwise (e.g., in an exception).

[0232] The various illustrative logics, logical blocks, modules, circuits and algorithm processes described in connection with the aspects disclosed herein can be implemented as electronic hardware, computer software, or combinations of both. The interchangeability of hardware and software has been described generally, in terms of functionality, and illustrated in the various illustrative components, blocks, modules, circuits and processes described herein. Whether such functionality is implemented in hardware or software depends on the particular application and design constraints imposed on the overall system.

[0233] The hardware and data processing apparatus used to implement the various illustrative logics, logical blocks, modules and circuits described in connection with the aspects disclosed herein can be implemented or performed with a general purpose single- or multi-chip processor, a digital signal processor (DSP), an application specific integrated circuit (ASIC), a field programmable gate array (FPGA) or other programmable logic device, discrete gate or transistor logic, discrete hardware components, or any combination thereof designed to perform the functions described herein. The general purpose processor can be a microprocessor, or, any conventional processor, controller, microcontroller, or state machine. A processor can also be implemented as a combination of computing devices, e.g., a combination of a DSP and a microprocessor, a plurality of microprocessors, one or more microprocessors in conjunction with a DSP core, or any other such configuration. In some aspects, particular processes and methods can be performed by an FPGA or ASIC.

[0234] In one or more aspects, the functions described can be implemented in hardware, digital electronic circuitry, computer software, firmware, including the structures disclosed in this specification and their structural equivalents, or in any combination thereof. Aspects of the subject matter described in this specification also can be implemented as one or more computer programs, e.g., one or more modules of computer program instructions, encoded on a computer storage medium for execution by, or to control the operation of, data processing apparatus.

[0235] If implemented in software, the functions can be stored on or transmitted over as one or more instructions or code on a computer-readable medium. The processes of a method or algorithm disclosed herein can be implemented in a processor-executable software module which can reside on a computer-readable medium. Computer-readable media includes both computer storage media and communication media including any medium that can be enabled to transfer a computer program from one place to another. Storage media can be any available media that can be accessed by a computer. By way of example, and not limitation, such computer-readable media can include RAM, ROM, EEPROM, CD-ROM or other optical disk storage, magnetic disk storage or other magnetic storage devices, or any other medium that can be used to store desired program code in the form of instructions or data structures and that can be accessed by a computer. Also, any connection is properly termed a computer-readable medium. Disk and disc, as used herein, includes compact discs (CDs), laser discs, optical discs, digital versatile discs (DVDs), floppy disks and blu-ray discs where disks usually reproduce data magnetically, while discs reproduce data optically with lasers. Combinations of the above should also be included within the scope of computer-readable media. Additionally, the methods or algorithms described herein can be embodied in a computer-readable medium that can be resident in the memory of one or more computer processors, such as a computer-readable medium encoding an executable program of instructions for execution by or to control the operation of that processor, or, alternatively, a computer program product including a computer-readable medium.

[0236] Various modifications to aspects described herein will be readily apparent to those skilled in the art, and the generic principles defined herein can be applied to other aspects. Thus, the claims are not intended to be limited to the aspects presented herein, but are to be accorded the full scope consistent with the disclosure, the principles and novel features disclosed herein. The claims are not intended to be limited to the aspects shown herein, but are to be accorded the full scope consistent with the disclosure, the principles and novel features disclosed herein.

[0237] Additionally, those of ordinary skill in the art will readily recognize that the terms "upper" and "lower" are sometimes used for ease of description in relation to the drawings and indicate relative positions on a properly oriented page as they correspond with the orientation of the drawings, and can not reflect the proper orientation of any device as implemented.

[0238] Certain features described in the context of separate aspects in this specification can also be implemented in combination in a single aspect. Conversely, various features described in the context of a single aspect can also be implemented in multiple aspects separately or in any suitable sub-combination. Moreover, although features can be described above as acting in certain combinations and even initially claimed as such, one or more features from a claimed combination can in some cases be excised from the combination and the claimed combination can be directed to a sub-combination or variations of a sub-combination.

[0239] Similarly, while operations are depicted in the drawings in a particular order, this should not be understood as requiring such an order, or that all illustrated operations be performed, to achieve desirable results. Additionally, the drawings can schematically depict one more example processes in the form of a flowchart. However, other operations that are not depicted can be incorporated in the example processes that are schematically illustrated. For example, one or more additional operations can be performed before, after, simultaneously with, or between any of the illustrated operations. In certain circumstances, multitasking and parallel processing can be advantageous. Moreover, the separation of various system components in the aspects described herein should not be understood as requiring such separation in all aspects, and it should be understood that the described program components and systems can generally be integrated in a single software product or packaged into multiple software products. Additionally, other aspects fall within the scope of the appended claims. In some cases, the actions recited in the claims can be performed in a different order and still achieve desirable results.

Claims

1. A first user equipment (UE) for wireless communication, the first user equipment (UE) comprising: Memory; and One or more processors, said one or more processors being coupled to the memory and configured to: Receive COT-Signal (COT-SI) from the second UE via a side link, which is associated with the first part of the Channel Occupancy Time (COT). The first UE is identified as a qualified repeater UE of the COT-SI, at least in part, based on the COT-SI; and The first part of the COT is used to transmit communication, which includes repeated COT-SI, based at least in part on the fact that the first UE is a qualified repeater UE of the COT-SI.

2. The first UE according to claim 1, wherein the one or more processors are further configured to: receive data communication associated with the COT-SI from the second UE via the side link, wherein in order to identify the first UE as a qualified repeater UE of the COT-SI, the one or more processors are further configured to: identify the first UE as a qualified repeater UE of the COT-SI based at least in part on the first UE receiving the data communication.

3. The first UE according to claim 1, wherein, in order to identify the first UE as a qualified repeater UE of the COT-SI, the one or more processors are further configured to: identify the first UE as a qualified repeater UE of the COT-SI at least in part based on the first UE identifying that at least one logical identifier associated with the COT-SI corresponds to the first UE.

4. The first UE according to claim 1, wherein, in order to identify the first UE as a qualified repeater UE of the COT-SI, the one or more processors are further configured to: identify the first UE as a qualified repeater UE of the COT-SI at least in part based on the first UE identifying the first UE as a target UE of the COT-SI.

5. The first UE of claim 1, wherein, in order to identify the first UE as a qualified repeater UE of the COT-SI, the one or more processors are further configured to: identify the first UE as a qualified repeater UE of the COT-SI based at least in part on the reference signal received power (RSRP) associated with communication between the first UE and the second UE satisfying an RSRP threshold.

6. The first UE of claim 1, wherein, in order to identify the first UE as a qualified repeater UE of the COT-SI, the one or more processors are further configured to: identify the first UE as a qualified repeater UE of the COT-SI based at least in part on the association of the first UE with a region identifier that is the same as the region identifier of the second UE.

7. The first UE according to claim 1, wherein, in order to identify the first UE as a qualified repeater UE of the COT-SI, the one or more processors are further configured to: identify the first UE as a qualified repeater UE of the COT-SI by decoding the COT-SI based at least in part on the first UE.

8. The first UE according to claim 1, wherein the one or more processors are further configured to receive repeated configuration information configuring the COT-SI.

9. The first UE according to claim 8, wherein the one or more processors are further configured to receive the configuration information from a network node via an access link.

10. The first UE of claim 9, wherein the configuration information is associated with a resource pool used by the first UE to transmit the communication using the first portion of the COT.

11. The first UE of claim 8, wherein the one or more processors are further configured to receive the configuration information from the second UE via the side link.

12. The first UE of claim 1, wherein the one or more processors are further configured to: receive from the second UE via the side link an indication that the COT-SI will be repeated in the communication sent by the first UE using the first portion of the COT.

13. The first UE of claim 12, wherein the indication that the COT-SI will be repeated is a one-bit indicator associated with the COT-SI.

14. The first UE of claim 12, wherein the indication to be repeated by the COT-SI is based at least in part on at least one of the following: The average priority level of one or more responding UEs associated with the first part of the COT meets the priority level threshold, or The highest priority level of the one or more responding UEs associated with the first part of the COT satisfies the priority level threshold.

15. The first UE according to claim 1, wherein the one or more processors are further configured to: Receive repeated configuration information configuring the COT-SI from the network node via the access link; and The COT-SI received from the second UE via the side link is an indication that will be repeated in the communication sent by the first UE using the first part of the COT.

16. The first UE of claim 1, wherein, in order to include the repeated COT-SI in the communication using the first part of the COT, the one or more processors are further configured to include the repeated COT-SI in the communication using the first part of the COT, at least in part based on the fact that the communication is sent in the pre-part of the first part of the COT.

17. The first UE of claim 16, wherein the front portion of the first part of the COT is associated with the percentage of the first occurrence of the first part of the COT.

18. The first UE of claim 17, wherein the one or more processors are further configured to: receive configuration information from a network node via an access link indicating the percentage of the first occurrence of the first portion of the COT.

19. The first UE of claim 1, wherein, in order to include the repeated COT-SI in the communication using the first portion of the COT, the one or more processors are further configured to include the repeated COT-SI in the communication using the first portion of the COT at least in part based on the fact that the communication is the first transmission performed by the first UE during the first portion of the COT among a plurality of transmissions.

20. The first UE of claim 1, wherein the COT-SI includes an indication that the COT-SI is sent by the second UE, and wherein the repeated COT-SI includes an indication that the repeated COT-SI is not sent by the second UE.

21. The first UE of claim 1, wherein the COT-SI includes an indication of at least one of time resources or frequency resources associated with the first portion of the COT, and wherein the repeated COT-SI includes an indication of at least one of time resources or frequency resources associated with the second portion of the first portion of the COT remaining after the communication including the repeated COT-SI has been sent.

22. The first UE of claim 1, wherein the COT-SI includes an indication of a zero offset between the initial COT-SI reception time and the COT-SI forwarding time, and wherein the repeated COT-SI includes an indication of a greater than zero offset between the initial COT-SI reception time and the COT-SI forwarding time.

23. The first UE of claim 1, wherein the one or more processors are further configured to: transmit third-level sidelink control information indicating one or more logical identifiers associated with the second UE, together with the communication using the first part of the COT.

24. A first user equipment (UE) for wireless communication, the first user equipment (UE) comprising: Memory; and One or more processors, said one or more processors being coupled to the memory and configured to: Transmit COT-Signal (COT-SI) associated with the first part of the Channel Occupancy Time (COT) to the second UE via a side link; and Indicates whether the second UE is a qualified repeater UE of the COT-SI.

25. The first UE of claim 24, wherein the one or more processors are further configured to: Receive repeated configuration information configuring the COT-SI from the network node via the access link; and The COT-SI is sent to the second UE via the side link as an indication that it will be repeated in the communication sent by the second UE using the first part of the COT.

26. The first UE of claim 24, wherein the COT-SI includes an indication that the COT-SI is sent by the first UE.

27. A method for wireless communication performed by a first user equipment (UE), the method comprising: Receive COT-Signal (COT-SI) from the second UE via a side link, which is associated with the first part of the Channel Occupancy Time (COT). The first UE is identified as a qualified repeater UE of the COT-SI, at least in part, based on the COT-SI. as well as The first UE transmits communication using the first portion of the COT, at least in part based on the first UE being a qualified repeater UE of the COT-SI, the communication including repeated COT-SI.

28. The method of claim 27, further comprising: Along with the communication using the first part of the COT, third-level sidelink control information indicating one or more logical identifiers associated with the second UE is sent.

29. A method for wireless communication performed by a first user equipment (UE), the method comprising: Transmit COT-Signal (COT-SI) associated with the first part of the Channel Occupancy Time (COT) to the second UE via a side link; and Indicates whether the second UE is a qualified repeater UE of the COT-SI.

30. The method of claim 29, wherein the COT-SI includes an indication that the COT-SI is sent by the first UE.

Images