Sidelink logical channel prioritization (LCP) procedure based on shared channel occupancy time (COT)

Abstract

Aspects of the present disclosure relate to channel occupancy time (COT) sharing for sidelink communications on an unlicensed channel. For example, the systems and methods described herein enable an efficient sidelink LCP process by implementing an LCP process for sidelink communication based on a received COT sharing indication. The LCP process may identify and utilize a sidelink logical channel of the shared COT based on the received indication of the shared COT, and transmit data via the shared COT using the sidelink logical channel that satisfies the LCP process conditions. Further, by receiving an indication of a shared COT, the UE may perform a type 2 LBT procedure when accessing the shared channel.

Description

[0001] Related applications

[0002] This application claims priority to U.S. Provisional Patent Application No. 63 / 494,103, filed on April 4, 2023, entitled “SIDELINK LOGICAL CHANNEL PRIORITIZATION (LCP) PROCEDURE BASED ON A SHARED OCCUPANCY TIME (COT),” the entire contents of which are incorporated herein by reference. Technical Field

[0003] The present disclosure relates to wireless communications and, more particularly, to channel occupancy time (COT) of a shared unlicensed sidelink channel. Background Art

[0004] A wireless communication system may include one or more network communication devices (such as base stations), which may also be referred to as eNodeBs (eNBs), next generation NodeBs (gNBs), or other appropriate terms. Each network communication device (such as a base station) may support wireless communication for one or more user communication devices, which may also be referred to as user equipment (UEs) or other appropriate terms. A wireless communication system may support wireless communication with one or more user communication devices by utilizing resources of the wireless communication system (e.g., time resources (e.g., symbols, time slots, subframes, frames, etc.) or frequency resources (e.g., subcarriers, carriers)). Additionally, a wireless communication system may support wireless communication across various radio access technologies, including third generation (3G) radio access technology, fourth generation (4G) radio access technology, fifth generation (5G) radio access technology, and other appropriate radio access technologies beyond 5G (e.g., sixth generation (6G)).

[0005] In some cases, network communication devices and / or user communication devices of a wireless communication system may utilize unlicensed channels or frequency bands, such as channels or frequency bands provided by an unlicensed carrier for wireless communication. Under NR-U or New Radio Unlicensed applications, a communication device may access an unlicensed channel for downlink and / or uplink transmission after performing a listen-before-talk (LBT) procedure.

[0006] A communication device (such as a UE) may perform a LBT procedure by sensing any unlicensed channels within the channel that are communicating (e.g., detecting the energy level of a subband within the channel). For example, a UE (or gNB) may initiate a channel occupation time (COT) for a channel by performing an LBT procedure (e.g., a Category Type 1 or Type 2 procedure) and determining that the channel is available for access. The COT defines the time period during which the UE may communicate on the channel.

[0007] In various scenarios, a UE communicates (or intends to communicate) with other UEs via a communication link known as a sidelink. As the use of such scenarios expands to additional use cases (e.g., commercial use cases), wireless communication systems may seek to increase sidelink data rates and / or support new or additional carrier frequencies for the sidelink. Utilization of unlicensed spectrum can help achieve these goals, providing a network with increased data rates and additional frequencies for sidelink communications. Summary of the Invention

[0008] The present disclosure relates to methods, apparatus, and systems for supporting COT sharing for sidelink communications on unlicensed channels. For example, the systems and methods described herein enable an efficient sidelink LCP process by implementing an LCP process for sidelink communications based on a received COT sharing indication. The LCP process can identify and utilize a sidelink logical channel of a shared COT based on a received indication of a shared COT, and transmit data via the shared COT using the sidelink logical channel that meets the LCP process conditions. In addition, by receiving an indication of a shared COT, the UE can perform a Type 2 LBT process when accessing a shared channel.

[0009] Some implementations of the methods and apparatus described herein may also include a UE comprising at least one memory and at least one processor coupled to the at least one processor and configured to cause the UE to: receive an indication of a shared channel occupancy time (COT) from a COT initiating UE identified by a first identifier; initiate sidelink communication with a set of other UEs via a sidelink channel on an unlicensed band associated with the shared COT; and perform a logical channel prioritization (LCP) procedure, the LCP procedure comprising: generating a sidelink transport block to be sent to the set of other UEs via the sidelink channel, wherein the sidelink transport block comprises a media access channel service data unit (MAC SDU) of one or more sidelink logical channels; and wherein the LCP procedure utilizes a sidelink logical channel of the one or more sidelink logical channels having: an associated channel access priority (CAPC) value equal to or less than a threshold CAPC value, and an associated destination identifier that matches the first identifier of the COT initiating UE.

[0010] In some implementations of the methods and apparatus described herein, the UE receives the threshold CAPC value from COT sharing information within an indication of a shared COT.

[0011] In some implementations of the methods and apparatus described herein, a sidelink logical channel considered during the LCP procedure is associated with a CAPC value that is equal to or less than a threshold CAPC value.

[0012] In some implementations of the methods and apparatus described herein, the UE performs an LCP procedure based at least in part on a destination identifier of a sidelink logical channel utilized during the LCP procedure.

[0013] In some implementations of the methods and apparatus described herein, the sidelink logical channel utilized comprises a Sidelink Traffic Channel (STCH).

[0014] In some implementations of the methods and apparatus described herein, each associated CAPC value for a logical channel is based on a delay requirement of the logical channel.

[0015] In some implementations of the methods and apparatus described herein, a UE initiates a sidelink channel with a set of other UEs by selecting a sidelink grant.

[0016] Some implementations of the methods and apparatus described herein may also include a method performed by a UE, the method comprising: receiving an indication of a shared COT from a COT-initiating UE identified by a first identifier; initiating sidelink communication with a set of other UEs over a sidelink channel on an unlicensed band associated with the shared COT; and performing a logical channel prioritization (LCP) procedure, the LCP procedure comprising: generating a sidelink transport block to be sent to the set of other UEs over the initiated sidelink channel, wherein the sidelink transport block comprises a MAC SDU of one or more sidelink logical channels; and wherein the LCP procedure utilizes a sidelink logical channel of the one or more sidelink logical channels having: an associated CAPC value that is equal to or less than a threshold CAPC value, and an associated destination identifier that matches the first identifier of the COT-initiating UE.

[0017] In some implementations of the methods and apparatus described herein, the UE receives the threshold CAPC value from COT sharing information within an indication of a shared COT.

[0018] In some implementations of the methods and apparatus described herein, a sidelink logical channel considered during the LCP procedure is associated with a CAPC value that is equal to or less than a threshold CAPC value.

[0019] In some implementations of the methods and apparatus described herein, the UE performs an LCP procedure based at least in part on a destination identifier of a sidelink logical channel utilized during the LCP procedure.

[0020] In some implementations of the methods and apparatus described herein, the utilized sidelink logical channels include (multiple) STCHs.

[0021] In some implementations of the methods and apparatus described herein, each associated CAPC value for a logical channel is based on a delay requirement of the logical channel.

[0022] In some implementations of the methods and apparatus described herein, a UE initiates a sidelink channel with a set of other UEs by selecting a sidelink grant.

[0023] Some implementations of the methods and apparatus described herein may also include a UE comprising at least one memory and at least one processor, the at least one processor being coupled to the at least one processor and configured to cause the UE to: initiate a COT on an unlicensed band, the COT being used for sidelink communication between a set of UEs; and send an indication of a shared COT to a receiving UE in the set of UEs, wherein the indication of the shared COT includes COT sharing information, the COT sharing information including: an identifier of the UE, and a threshold CAPC value for a sidelink logical channel utilized by the receiving UE during an LCP procedure on the shared COT.

[0024] In some implementations of the methods and apparatus described herein, the UE sends an indication of the shared COT via radio resource control (RRC) signaling.

[0025] Some implementations of the methods and apparatus described herein may also include a method performed by a UE, the method comprising: initiating a COT on an unlicensed band, the COT being used for sidelink communication between a set of UEs; and sending an indication of a shared COT to a receiving UE in the set of UEs, wherein the indication of the shared COT includes COT sharing information, the COT sharing information including: an identifier of the UE, and a threshold CAPC value for a sidelink logical channel utilized by the receiving UE during an LCP procedure on the shared COT.

[0026] In some implementations of the methods and apparatus described herein, the UE sends an indication of the shared COT via RRC signaling.

[0027] Some implementations of the methods and apparatus described herein may also include a processor for wireless communications, the processor comprising at least one controller coupled to at least one memory and configured to cause the processor to: receive an indication of a shared COT from a COT-initiating UE identified by a first identifier; initiate sidelink communications with a set of other UEs over a sidelink channel on an unlicensed band associated with the shared COT; and perform an LCP process comprising: generating a sidelink transport block to be sent to the set of other UEs over the sidelink channel, wherein the sidelink transport block comprises a MAC SDU of one or more sidelink logical channels; and wherein the LCP process utilizes a sidelink logical channel of the one or more sidelink logical channels having: an associated CAPC value that is equal to or less than a threshold CAPC value, and an associated destination identifier that matches the first identifier of the COT-initiating UE.

[0028] In some implementations of the methods and apparatus described herein, the processor receives the threshold CAPC value from COT sharing information within the indication of the shared COT.

[0029] In some implementations of the methods and apparatus described herein, a sidelink logical channel considered during the LCP procedure is associated with a CAPC value that is equal to or less than a threshold CAPC value.

[0030] In some implementations of the methods and apparatus described herein, the processor performs the LCP procedure based at least in part on a destination identifier of a sidelink logical channel utilized during the LCP procedure. BRIEF DESCRIPTION OF THE DRAWINGS

[0031] Figure 1 An example of a wireless communication system supporting COT sharing for an unlicensed sidelink channel according to aspects of the present disclosure is illustrated.

[0032] Figure 2 An example of a wireless communication system supporting LCP procedures on a shared COT according to aspects of the present disclosure is illustrated.

[0033] Figure 3 Illustrated is an example of a flow diagram supporting a process of selecting an LCP for data transmission according to aspects of the present disclosure.

[0034] Figure 4 Illustrated is an example of a block diagram of a device supporting COT sharing for an unlicensed sidelink channel according to aspects of the present disclosure.

[0035] Figure 5 A flow chart illustrating a method for supporting the use of a shared COT to perform an LCP process according to aspects of the present disclosure is shown.

[0036] Figure 6 A flowchart of a method supporting sending COT sharing information according to aspects of the present disclosure is illustrated. DETAILED DESCRIPTION

[0037] When a UE utilizes a COT to communicate on an unlicensed channel (e.g., a sidelink), the UE may share the COT with other UEs when the UE does not intend to utilize the COT for the entire duration of the COT. In some cases, a UE using the COT to initiate a shared COT may be able to perform a short LBT procedure (e.g., a Type 2 procedure) to gain access to the shared COT.

[0038] However, use of the shared COT for certain transmissions (e.g., physical sidelink shared channel (PSSCH) transmissions) may be based on certain conditions associated with the UE being eligible to utilize a set of resource blocks (RBs) within the shared COT for PSSCH transmissions, etc. (e.g., physical sidelink control channel (PSCCH) transmissions).

[0039] For example, only PSSCH transmissions associated with a specific destination and / or channel access priority level (CAPC) can use RB sets on the shared COT. Therefore, in some cases, a UE may have data available for transmission that meets the shared COT conditions, but the traditional logical channel prioritization (LCP) process may prevent the use of the shared COT due to data transmission not meeting the destination and / or CAPC conditions, as well as other issues.

[0040] The systems and methods described herein enable an efficient sidelink LCP procedure by implementing an LCP procedure for sidelink communications based on a received COT sharing indication. For example, the LCP procedure can identify and utilize a sidelink logical channel sharing the COT based on the received indication of the shared COT, and transmit data via the shared COT using the sidelink logical channel that meets the LCP procedure conditions. In addition, by receiving an indication of the shared COT, the UE can perform a Type 2 LBT procedure when accessing the shared channel.

[0041] Thus, among other benefits, the system and method may enable an efficient sidelink LCP process over a shared COT.

[0042] Aspects of the present disclosure are described in the context of a wireless communication system.Aspects of the present disclosure are further illustrated and described with reference to device diagrams and flow charts.

[0043] Figure 1An example of a wireless communication system 100 supporting COT sharing for unlicensed sidelink channels according to aspects of the present disclosure is illustrated. The wireless communication system 100 may include one or more network entities 102, one or more UEs 104, a core network 106, and a packet data network 108. The wireless communication system 100 may support various radio access technologies. In some implementations, the wireless communication system 100 may be a 4G network, such as an LTE network or an LTE-Advanced (LTE-A) network. In some other implementations, the wireless communication system 100 may be a 5G network, such as an NR network. In other implementations, the wireless communication system 100 may be a combination of a 4G network and a 5G network, or other suitable radio access technologies, including Institute of Electrical and Electronics Engineers (IEEE) 802.11 (Wi-Fi), IEEE 802.16 (WiMAX), or IEEE 802.20. The wireless communication system 100 may support radio access technologies other than 5G. Additionally, the wireless communication system 100 may support technologies such as time division multiple access (TDMA), frequency division multiple access (FDMA), or code division multiple access (CDMA).

[0044] One or more network entities 102 may be dispersed throughout a geographic area to form the wireless communication system 100. One or more of the network entities 102 described herein may be, include, or be referred to as a network node, a base station, a network element, a radio access network (RAN), a base transceiver station, an access point, a NodeB, an eNodeB (eNB), a next generation NodeB (gNB), or other suitable terminology. The network entity 102 and the UE 104 may communicate via a communication link 110, which may be a wireless or wired connection. For example, the network entity 102 and the UE 104 may perform wireless communication (e.g., receive signaling, send signaling) over a Uu interface.

[0045] The network entity 102 may provide a geographic coverage area 112 for which it supports services (e.g., voice, video, packet data, messaging, broadcast, etc.) for one or more UEs 104 within the geographic coverage area 112. For example, the network entity 102 and the UEs 104 may support wireless communication of signals associated with the services (e.g., voice, video, packet data, messaging, broadcast, etc.) based on one or more radio access technologies. In some implementations, the network entity 102 may be mobile, such as a satellite associated with a non-terrestrial network. In some implementations, different geographic coverage areas 112 associated with the same or different radio access technologies may overlap, but different geographic coverage areas 112 may be associated with different network entities 102. The information and signals described herein may be represented using any of a variety of different technologies and techniques. For example, data, instructions, commands, information, signals, bits, symbols, and chips that may be referenced throughout the description may be represented by voltages, currents, electromagnetic waves, magnetic fields or particles, optical fields or particles, or any combination thereof.

[0046] One or more UEs 104 may be dispersed throughout the geographic area of ​​the wireless communication system 100. UE 104 may include or may be referred to as a mobile device, wireless device, remote device, remote unit, handheld device, subscriber device, or some other suitable terminology. In some implementations, UE 104 may be referred to as a unit, station, terminal, or client, etc. Additionally or alternatively, UE 104 may be referred to as an Internet of Things (IoT) device, an Internet of Everything (IoE) device, or a Machine Type Communication (MTC) device, etc. In some implementations, UE 104 may be stationary within the wireless communication system 100. In some other implementations, UE 104 may be mobile within the wireless communication system 100.

[0047] One or more UEs 104 may be devices in different forms or with different capabilities. Figure 1 Some examples of UE 104 are shown in FIG. Figure 1 As shown, the UE 104 may be capable of communicating with various types of devices, such as a network entity 102, other UEs 104, or a network device (e.g., a core network 106, a packet data network 108, a relay device, an integrated access and backhaul (IAB) node, or another network device). Additionally or alternatively, the UE 104 may support communication with other network entities 102 or UEs 104 that may act as relays in the wireless communication system 100.

[0048] The UE 104 may also be capable of supporting wireless communications directly with other UEs 104 via a communication link 114. For example, the UE 104 may support wireless communications directly with another UE 104 via a device-to-device (D2D) communication link. In some implementations, such as vehicle-to-vehicle (V2V) deployments, vehicle-to-everything (V2X) deployments, or cellular V2X deployments, the communication link 114 may be referred to as a side link. For example, the UE 104 may support wireless communications directly with another UE 104 via a PC5 interface.

[0049] The network entities 102 may support communication with the core network 106 or with another network entity 102, or both. For example, the network entities 102 may interface with the core network 106 via one or more backhaul links 116 (e.g., via S1, N2, N2, or another network interface). The network entities 102 may communicate with each other via the backhaul links 116 (e.g., via X2, Xn, or another network interface). In some implementations, the network entities 102 may communicate directly with each other (e.g., between the network entities 102). In some other implementations, the network entities 102 may communicate with each other or indirectly (e.g., via the core network 106). In some implementations, one or more network entities 102 may include subcomponents, such as an access network entity, which may be an example of an access node controller (ANC). The ANC may communicate with one or more UEs 104 via one or more other access network transport entities, which may be referred to as radio heads, smart radio heads, or transmission reception points (TRPs)).

[0050] In some implementations, the network entity 102 may be configured in a decomposed architecture that may be configured to utilize a protocol stack that is physically or logically distributed between two or more network entities 102, such as an integrated access backhaul (IAB) network, an open RAN (O-RAN) (e.g., a network configuration sponsored by the O-RAN Alliance), or a virtualized RAN (vRAN) (e.g., a cloud RAN (C-RAN)). For example, the network entity 102 may include one or more of the following: a central unit (CU), a distributed unit (DU), a radio unit (RU), a RAN intelligent controller (RIC) (e.g., a near real-time RIC (near RT RIC), a non-real-time RIC (non-RT RIC)), a service management and orchestration (SMO) system, or any combination thereof.

[0051] The RU may also be referred to as a radio head, smart radio head, remote radio head (RRH), remote radio unit (RRU), or transmission reception point (TRP). In a disaggregated RAN architecture, one or more components of the network entity 102 may be collocated, or one or more components of the network entity 102 may be located in distributed locations (e.g., separate physical locations). In some implementations, one or more network entities 102 of the disaggregated RAN architecture may be implemented as virtual units (e.g., virtual CU (VCU), virtual DU (VDU), virtual RU (VRU)).

[0052] The functional split between the CU, DU, and RU can be flexible, and different functions can be supported depending on the functions performed at the CU, DU, or RU (e.g., network layer functions, protocol layer functions, baseband functions, radio frequency functions, and any combination thereof). For example, a functional split of the protocol stack can be adopted between the CU and the DU, such that the CU can support one or more layers of the protocol stack, and the DU can support one or more different layers of the protocol stack. In some implementations, the CU can host upper protocol layer (e.g., Layer 3 (L3), Layer 2 (L2)) functions and signaling (e.g., Radio Resource Control (RRC), Service Data Adaptation Protocol (SDAP), Packet Data Convergence Protocol (PDCP)). The CU can be connected to one or more DUs or RUs, and one or more DUs or RUs can host lower protocol layers, such as Layer 1 (L1) (e.g., physical (PHY) layer) or L2 (e.g., radio link control (RLC) layer, media access control (MAC) layer) functions and signaling, and each DU or RU can be at least partially controlled by the CU 160.

[0053] Additionally or alternatively, a functional split of the protocol stack may be employed between the DU and the RU such that the DU may support one or more layers of the protocol stack and the RU may support one or more different layers of the protocol stack. The DU may support one or more different cells (e.g., via one or more RUs). In some implementations, the functional split between the CU and the DU or between the DU and the RU may be within the protocol layer (e.g., some functions of the protocol layer may be performed by one of the CU, DU, or RU, while other functions of the protocol layer may be performed by different ones of the CU, DU, or RU).

[0054] The CU can be further functionally split into CU control plane (CU-CP) and CU user plane (CU-UP) functions. The CU can be connected to one or more DUs via a medium-range communication link (e.g., F1, F1-c, F1-u), and the DU can be connected to one or more RUs via a fronthaul communication link (e.g., an open fronthaul (FH) interface). In some implementations, the medium-range communication link or the fronthaul communication link can be implemented according to the interface (e.g., channel) between the layers of the protocol stack supported by the corresponding network entity 102 communicating via such a communication link.

[0055] The core network 106 may support user authentication, access authorization, tracking, connectivity, and other access, routing, or mobility functions. The core network 106 may be an evolved packet core (EPC) or a 5G core (5GC), which may include control plane entities that manage access and mobility (e.g., mobility management entity (MME), access and mobility management function (AMF)), and user plane entities that route packets or interconnections to external networks (e.g., serving gateway (S-GW), packet data network (PDN) gateway (P-GW), or user plane function (UPF)). In some implementations, the control plane entities may manage non-access stratum (NAS) functions, such as mobility, authentication, and bearer management (e.g., data bearer, signaling bearer, etc.) for one or more UEs 104 served by one or more network entities 102 associated with the core network 106.

[0056] The core network 106 can communicate with the packet data network 108 via one or more backhaul links 116 (e.g., via S1, N2, N2, or another network interface). The packet data network 108 can include an application server 118. In some implementations, one or more UEs 104 can communicate with the application server 118. The UE 104 can establish a session (e.g., a protocol data unit (PDU) session, etc.) with the core network 106 via the network entity 102. The core network 106 can use the established session (e.g., the established PDU session) to route traffic (e.g., control information, data, etc.) between the UE 104 and the application server 118. The PDU session can be an example of a logical connection between the UE 104 and the core network 106 (e.g., one or more network functions of the core network 106).

[0057] In the wireless communication system 100, the network entity 102 and the UE 104 may use the resources of the wireless communication system 100 (e.g., time resources (e.g., symbols, time slots, subframes, frames, etc.) or frequency resources (e.g., subcarriers, carriers)) to perform various operations (e.g., wireless communications). In some implementations, the network entity 102 and the UE 104 may support different resource structures. For example, the network entity 102 and the UE 104 may support different frame structures. In some implementations, such as in 4G, the network entity 102 and the UE 104 may support a single frame structure. In some other implementations, such as in 5G and other suitable radio access technologies, the network entity 102 and the UE 104 may support various frame structures (i.e., multiple frame structures). The network entity 102 and the UE 104 may support various frame structures based on one or more digital technologies.

[0058] One or more digital technologies may be supported in the wireless communication system 100, and the digital technologies may include subcarrier spacing and cyclic prefixes. A first digital technology (e.g., μ = 0) may be associated with a first subcarrier spacing (e.g., 15 kHz) and a normal cyclic prefix. In some implementations, the first digital technology (e.g., μ = 0) associated with the first subcarrier spacing (e.g., 15 kHz) may utilize one slot per subframe. A second digital technology (e.g., μ = 1) may be associated with a second subcarrier spacing (e.g., 30 kHz) and a normal cyclic prefix. A third digital technology (e.g., μ = 2) may be associated with a third subcarrier spacing (e.g., 60 kHz) and a normal cyclic prefix or an extended cyclic prefix. A fourth digital technology (e.g., μ = 3) may be associated with a fourth subcarrier spacing (e.g., 120 kHz) and a normal cyclic prefix. A fifth digital technology (e.g., μ = 4) may be associated with a fifth subcarrier spacing (e.g., 240 kHz) and a normal cyclic prefix.

[0059] The time intervals of resources (e.g., communication resources) can be organized according to frames (also called radio frames). Each frame can have a duration, for example, a duration of 10 milliseconds (ms). In some implementations, each frame can include multiple subframes. For example, each frame can include 10 subframes, and each subframe can have a duration, for example, a duration of 1 ms. In some implementations, each frame can have the same duration. In some implementations, each subframe of a frame can have the same duration.

[0060] Additionally or alternatively, the time intervals of resources (e.g., communication resources) can be organized according to time slots. For example, a subframe can include a certain number (e.g., quantity) of time slots. The number of time slots in each subframe can also depend on one or more digital technologies supported in the wireless communication system 100. For example, a first digital technology, a second digital technology, a third digital technology, a fourth digital technology, and a fifth digital technology (i.e., μ=0, μ=1, μ=2, μ=3, μ=4) associated with corresponding subcarrier spacings of 15kHz, 30kHz, 60kHz, 120kHz, and 240kHz can utilize one time slot per subframe, two time slots per subframe, four time slots per subframe, eight time slots per subframe, and 16 time slots per subframe, respectively. Each time slot can include a certain number (e.g., quantity) of symbols (e.g., OFDM symbols). In some implementations, the number (e.g., quantity) of time slots for a subframe can depend on the digital technology. For a conventional cyclic prefix, a time slot can include 14 symbols. For an extended cyclic prefix (e.g., for a 60 kHz subcarrier spacing), a slot may include 12 symbols. For both a normal cyclic prefix and an extended cyclic prefix, the relationship between the number of symbols per slot, the number of slots per subframe, and the number of slots per frame may depend on the digital technology. It should be understood that references to a first digital technology (e.g., μ = 0) associated with a first subcarrier spacing (e.g., 15 kHz) may be used interchangeably between subframes and slots.

[0061] In the wireless communication system 100, the electromagnetic (EM) spectrum can be divided into various categories, frequency bands, frequency channels, etc. based on frequency or wavelength. For example, the wireless communication system 100 can support one or more operating frequency bands, such as the frequency range designations FR1 (410 MHz-7.125 GHz), FR2 (24.25 GHz-52.6 GHz), FR3 (7.125 GHz-24.25 GHz), FR4 (52.6 GHz-114.25 GHz), FR4a or FR4-1 (52.6 GHz-71 GHz), and FR5 (114.25 GHz-300 GHz). In some implementations, the network entity 102 and the UE 104 can perform wireless communications on one or more operating frequency bands. In some implementations, FR1 can be used by the network entity 102 and the UE 104, as well as other devices or apparatuses, for cellular communication traffic (e.g., control information, data). In some implementations, FR2 can be used by the network entity 102 and the UE 104, as well as other devices or apparatuses, for short-range, high data rate capabilities.

[0062] FR1 may be associated with one or more digital technologies (e.g., at least three digital technologies). For example, FR1 may be associated with a first digital technology (e.g., μ = 0) including a subcarrier spacing of 15 kHz, a second digital technology (e.g., μ = 1) including a subcarrier spacing of 30 kHz, and a third digital technology (e.g., μ = 2) including a subcarrier spacing of 60 kHz. FR2 may be associated with one or more digital technologies (e.g., at least two digital technologies). For example, FR2 may be associated with a third digital technology (e.g., μ = 2) including a subcarrier spacing of 60 kHz, and a fourth digital technology (e.g., μ = 3) including a subcarrier spacing of 120 kHz.

[0063] As described herein, in some embodiments, a UE may utilize an enhanced or modified LCP procedure when transmitting data (e.g., PSSCH or PSCCH transmissions) over a shared COT. For example, when a UE determines that the highest priority data available for transmission in its buffer has a priority higher than a predefined threshold priority, the UE may employ a conventional LCP procedure in which the destination of the sidelink transmission is selected based on the highest priority data.

[0064] However, when the highest priority of the data available for transmission is below a predefined threshold priority, the UE may use an enhanced LCP procedure, as described herein. In some cases, the enhanced LCP procedure is based on COT sharing information received from the initiating UE (e.g., information within an indication of a shared COT). Using the enhanced LCP procedure, the UE may access the shared COT and maximize the use of the shared COT.

[0065] For example, the UE may determine the highest priority as the highest priority among the priorities of logical channels that have available data and can be multiplexed in a transport block / media access control (TB / MAC) protocol data unit (PDU) according to mapping restrictions (e.g., restrictions described in TS 38.321 Section 5.4.3.1.2). In some cases, the network (e.g., gNB) may configure a predefined threshold priority for the UE via radio resource control (RRC) signaling.

[0066] In some cases, a responding UE using resources on a shared COT (e.g., after a Type 2 LBT procedure accessing the shared COT) may be a UE directed by a COT-initiating UE with a PSCCH / PSSCH transmission. For example, when a COT-initiating UE performs a unicast transmission, the UE may be a responding UE when the source ID and destination ID within the indication of the shared COT match the corresponding destination ID and source ID at the receiving UE. As another example, when a COT-initiating UE performs a multicast or broadcast transmission, the UE may be a responding UE when the source ID and destination ID within the indication of the shared COT match the destination ID known by the receiving UE.

[0067] In some cases, the COT sharing information may include an additional ID that maps to or matches an ID for the responding UE to satisfy a destination condition for sending data via the shared COT. Furthermore, the COT sharing information may include a CAPC value (e.g., a threshold) for sending data via the shared COT. Thus, when the destination condition is satisfied and when the data / transport block / MAC PDU to be sent by the responding UE via the sidelink (e.g., data within the UE's buffer) has a CAPC value equal to or less than the CAPC value indicated in the COT sharing information, the responding UE may send data using the shared COT.

[0068] Figure 2 FIG2 illustrates an example of a wireless communication system 200 that supports performing an LCP process on a shared COT according to aspects of the present disclosure. The wireless communication system 200 may implement Figure 1 For example, the wireless communication system 200 may include a base station 102 and a UE 104, which may be as described in reference Figure 1 Examples of base stations and UE 104 are described.

[0069] The responding UE 210 receives an indication of a shared COT (e.g., COT sharing indication 240) from the COT initiating UE 220, which initiates the COT 230 on an unlicensed channel for sidelink communication. As described herein, the COT sharing indication 240 may include, among other information, destination information and / or a CAPC value for data to be sent by the responding UE 210 via the shared COT 230.

[0070] A responding UE 210 having data to transmit that meets the conditions for the LCP procedure using the shared COT 230 may perform the LCP procedure 250 using the shared COT 230. For example, the responding UE 210 may determine that the highest priority data available for transmission in its buffer has a priority less than a predefined threshold priority.

[0071] Based on this determination, responding UE 210 utilizes only logical channels (LCHs) that meet the CAPC condition during LCP procedure 250. Thus, responding UE 210 uses logical channels that have associated CAPC values ​​that are less than or equal to the CAPC value identified within the COT sharing information (e.g., contained in COT sharing indication 240).

[0072] In addition, the responding UE 210 may utilize a logical channel that also satisfies the destination condition. For example, during the LCP procedure 250, the responding UE 210 utilizes a logical channel having a source ID and a destination ID that match the destination ID(s) and source ID(s) of the PSSCH / PSCCH of the COT initiating UE, or a logical channel having a source ID and a destination ID that are included in the COT sharing indication 240.

[0073] In some embodiments, the responding UE 210 may determine whether any data available for transmission in its buffer meets the destination conditions for use with the shared COT. For example, whether the responding UE 210 has PSSCH / PSCCH transmission(s) for the COT initiating UE 220, e.g., whether the source ID and destination ID contained in the sidelink control information (SCI) of the COT initiator match the corresponding destination ID and source ID associated with the same unicast at the receiving UE.

[0074] In some cases, when no logical channel has data available for transmission that meets the destination conditions for the shared COT, the responding UE 210 may use a conventional LCP procedure. For example, the responding UE 210 generates a TB and performs an LBT type 1 access procedure for transmission of the generated TB (e.g., without using any (plural) RB sets corresponding to the shared COT 230).

[0075] In other cases, when at least one logical channel includes data available for transmission that meets the destination condition (e.g., transmission to the destination is indicated as being in the shared COT 230), the responding UE 210 determines whether the delay budget associated with the logical channels having data available for transmission that does not meet the destination condition can be met even if the shared COT 230 cannot be used for transmission of such data.

[0076] For example, the responding UE 210 determines whether the remaining delay budget of the logical channels that do not meet the destination condition is greater than a predefined threshold delay budget (e.g., the duration of the shared COT 230). When the responding UE 210 determines that the latency requirement of the data can be met, the responding UE 210 considers only those LCHs that are part of the LCP process for sidelink transmission that meet the destination condition (e.g., transmission to the destination ID is indicated as being in the shared COT) when determining the destination. In some cases, the responding UE 210 may only consider logical channels that meet the CAPC condition during destination selection (e.g., when the CAPC value associated with the logical channel is equal to or less than the CAPC value indicated within the COT sharing information of the COT sharing indication 240).

[0077] In some embodiments, as part of the destination selection of the LCP procedure, the responding UE 210 may select / consider only logical channels that meet the CAPC condition (e.g., logical channels having a CAPC value less than or equal to a threshold CAPC value). For example, the responding UE 210 may determine whether the selected destination (e.g., the highest priority logical channel among the logical channels that meet the destination selection condition) meets the destination condition.

[0078] When the destination conditions are not met, the responding UE 210 can utilize the conventional LCP procedure (e.g., performing an LBT type 1 procedure on the PSSCH for transmission of the generated TB). However, when the selected destination meets the destination conditions of the shared COT 230, the responding UE 210 generates a TB based on a logical channel that meets the CAPC conditions (and other conditions, such as LCH mapping restrictions). The responding UE 210 can then use LBT type 2 for the generated TB and thereby perform an enhanced LCP procedure for data transmission via the shared COT 230.

[0079] In some embodiments, during the LCP procedure, the responding UE 210 selects / considers a logical channel that meets a destination condition (e.g., the corresponding PSSCH / PSCCH transmission is for the COT initiating UE 220) for a first sidelink transmission (e.g., a PSSCH / PSCCH transmission) within the shared COT 230. For example, the responding UE 210 may apply a destination restriction only for the first PSSCH / PSCCH transmission within the shared COT 230.

[0080] In addition, the responding UE 210 may select / consider logical channels that meet the CAPC conditions only for the first PSSCH / PSCCH transmission within the shared COT 230. For any remaining or subsequent PSSCH / PSCCH transmissions within the shared COT 230, the responding UE 210 may follow the traditional LCP procedure (e.g., using logical channels that do not meet the destination conditions). In some cases, the responding UE 210 may also apply the CAPC conditions / restrictions to subsequent PSSCH / PSCCH transmissions within the shared COT 230.

[0081] In doing so, when at least one PSSCH / PSCCH transmission is for the COT initiating UE 220 (such as the first PSSCH / PSCCH transmission), the responding UE 210 may utilize the shared COT 230 (eg, the PSSCH / PSCCH transmission utilizes the RB set of the shared COT 230).

[0082] Furthermore, in some cases, the responding UE 320 may determine whether there is data available for transmission to the COT initiating UE 220 before determining whether to use the shared COT 230 (via LBT Type 2) or to initiate a new COT (via LBT Type 1). When the first PSSCH / PSCCH transmission is to the COT initiating UE 220, the responding UE 210 may utilize the shared COT 230, and the responding UE 210 may perform subsequent transmissions to other UEs.

[0083] In some embodiments, when the delay budget of a logical channel or transport block is about to expire and the CAPC constraints / conditions do not allow transmission of the transport block or logical channel using the shared COT 230, the responding UE 210 may increase the CAPC value of the logical channel or transport block. To ensure that the responding UE 210 can transmit a TB within its delay budget using the shared COT 230 (via LBT Type 2), in some cases the responding UE 210 may increase the CAPC priority of the logical channel or TB. For example, when the priority (e.g., CAPC value) of the logical channel or TB is greater than a predefined threshold CAPC value, the responding UE 210 may only increase the CAPC priority of the logical channel or TB to satisfy the CAPC conditions of the shared COT 230.

[0084] In some embodiments, the buffer of the responding UE 210 has data for the sidelink logical channel available for transmission. However, when the sidelink logical channel has a CAPC value greater than the CAPC value indicated in the COT sharing information, such as when the MAC PDU contains (multiple) MAC SDUs and / or (multiple) MAC CEs of a sidelink logical channel with a high CAPC priority (e.g., SRB), or when the TB contains (multiple) MAC SDUs of a sidelink logical channel for which the delay budget is about to expire and cannot be met without sharing the COT 230, the responding UE 210 may not multiplex the MAC service data unit (MAC SDU(s)) into the MAC PDU.

[0085] To prevent the responding UE 210 from transmitting a MAC PDU using a low CAPC value (e.g., a higher CAPC value than indicated in the shared COT information) and, therefore, using LBT type 1 for PSSCH / PSCCH transmission, the responding UE 210 may multiplex padding into the MAC PDU instead of data of a logical channel with a low CAPC priority (e.g., a high CAPC value). In some cases, the lowest priority CAPC of the logical channel(s) with the MAC SDU multiplexed in the TB may be used for transmission of the TB, regardless of whether the TB contains a sidelink MAC CE in addition to the MAC SDU.

[0086] In some cases, the responding UE 210 may implement multiplexing stuffing into the MAC PDU only when the amount of data with the highest CAPC priority within the MAC PDU exceeds or is greater than a certain size threshold, such as a value or percentage (e.g., configured via higher layer signaling).

[0087] In some embodiments, as described herein, responding UE 210 may perform a series of determinations when selecting an LCP procedure for data transmission. Figure 3 Illustrated is an example of a flow chart 300 that supports a process of selecting an LCP for data transmission according to aspects of the present disclosure.

[0088] The responding UE 210 receives the COT share information 310 and performs COT share selection 312. First, the responding UE performs a destination matching operation 314 and determines whether its cache contains data that meets the destination conditions of the COT share information 310 and is available for transmission.

[0089] When there is no data available for transmission that meets the destination condition, the responding UE 210 follows the legacy LCP procedure 316 and performs LBT Type 1 for the corresponding PSSCH / PSCCH transmission(s). When there is data in the UE buffer that meets the destination condition of the COT sharing information 310, in operation 320, the responding UE 210 determines whether the selected destination (when using the legacy LCP / destination selection based on the highest priority data) meets the destination condition of the shared COT.

[0090] When the selected destination satisfies the destination conditions of the shared COT, the responding UE 210 determines whether the PSSCH / PSCCH transmission satisfies the CAPC conditions in operation 322. When the responding UE 210 uses only logical channels during the LCP procedure, the responding UE 210 is eligible to use the shared COT for the selected destination that also satisfies the CAPC conditions, and performs LBT Type 2 in operation 324. When the responding UE 210 does not apply additional CAPC restrictions during the LCP procedure, the resulting TB may not satisfy the CAPC conditions of the shared COT, and the responding UE 210 performs LBT Type 1 in operation 326.

[0091] When the selected destination does not satisfy the destination condition of the shared COT, the responding UE 210 determines whether to change the destination selection during the LCP procedure in operation 330. The responding UE 210 may determine whether to change the destination selection based on the priority of the highest priority data in its cache.

[0092] When the responding UE 210 selects a destination that does not satisfy the destination conditions of the shared COT, the responding UE 210 initiates its own COT for the corresponding PSSCH / PSCCH transmission and performs an LBT Type 1 procedure. When the responding UE 210 determines to change the destination selection procedure (e.g., to use only logical channels that satisfy the destination conditions of the shared COT), in operation 340, the responding UE 210 determines whether CAPC restrictions are applied to determine eligibility for using the shared COT.

[0093] When the responding UE 210 uses only logical channels during the LCP procedure in operation 340, the responding UE 210 is eligible to use the shared COT for the selected destination that also satisfies the CAPC condition and performs LBT Type 2 in operation 344. When the responding UE 210 does not apply additional CAPC restrictions during the LCP procedure, the responding UE 210 performs LBT Type 1 in operation 342, as described herein.

[0094] Furthermore, in some cases, when the responding UE 210 receives multiple COT sharing information from different COT initiating UEs and the responding UE 210 has data that meets multiple COT sharing conditions, the responding UE 210 may maximize high priority transmission and follow the traditional destination selection principle based on the highest priority.

[0095] In some embodiments, the responding UE 210 may enter a discontinuous reception state (e.g., a DRX state) in which the responding UE 210 does not monitor the PSCCH(SCI) / PSSCH for a source-destination pair when the responding UE 210 is using a shared COT for a destination. For example, when the COT-initiating UE 220 is sharing its COT (e.g., COT 230, and the responding UE 210 is using a shared COT), the responding UE 210 may stop monitoring the PSCCH / PSSCH from the COT-initiating UE 220.

[0096] In some cases, the responding UE 210 may stop monitoring the PSCCH / PSSCH when using the shared COT because the COT initiating UE 220 is sharing its COT and therefore has no data available for transmission to the responding UE 210. In some cases, when the responding UE 210 uses the shared COT and stops monitoring the PSCCH / PSSCH, the responding UE 210 may stop or suspend all DRX-related timers (e.g., DRX-related timers for the source-destination pair for which it is using the shared COT).

[0097] Thus, in some embodiments, when a UE (eg, responding UE 210) receives a COT sharing indication from a COT initiating UE (eg, COT initiating UE 220) and uses a shared COT (eg, COT 230), the UE may implement or enter a DRX state.

[0098] As described herein, in various embodiments, the systems and methods enable a UE to utilize an enhanced LCP procedure when performing data transmission using a sidelink over an unlicensed spectrum.

[0099] In some cases, the system and method may enable the UE to only consider using logical channels that meet the CAPC restrictions during the LCP procedure, such as when the selected destination meets the destination conditions, the UE uses a shared COT for (multiple) PSSCH transmissions, otherwise the UE initiates its own COT.

[0100] In some cases, the systems and methods can implement criteria / rules that control whether a UE uses a shared COT with a modified or enhanced LCP procedure, or whether a UE initiates its own COT. For example, based on the priority of its highest priority data, when the highest priority data exceeds a predefined priority threshold, the UE determines whether the use of a shared COT is appropriate, and the UE can use the new COT to send the high priority data. Another example is that based on the delay budget of the sidelink logical channel or transport block, the UE determines whether to change the LCP procedure to use a shared COT for (multiple) PSSCH transmissions.

[0101] In some cases, the systems and methods can enable enhanced destination selection based on a shared COT for initial sidelink transmissions of the shared COT without any restrictions on subsequent transmissions.

[0102] In some cases, when the delay budget is about to expire and shared COT usage is not allowed based on the current CAPC value, the system and method can enable the UE to increase the CAPC priority of the transport block or logical channel, or include padding.

[0103] In some cases, the systems and methods may enable a UE to stop DRX active time based on COT sharing information / usage, such as when responding to a UE using a shared COT (where DRX occurs during use of the shared COT and / or DRX-related timers are stopped while using the shared COT).

[0104] Figure 4 An example of a block diagram 400 of a device 402 supporting COT sharing for an unlicensed sidelink channel according to aspects of the present disclosure is illustrated. The device 402 may be an example of a network entity 102 or a UE 104 as described herein. The device 402 may support wireless communications with one or more network entities 102, UEs 104, or any combination thereof. The device 402 may include components for bidirectional communication, including components for sending and receiving communications (such as a processor 404, a memory 406, a transceiver 408, and an I / O controller 410). These components may be in electronic communication or otherwise coupled (e.g., operatively, communicatively, functionally, electronically, electrically) via one or more interfaces (e.g., a bus).

[0105] The processor 404, memory 406, transceiver 408, or various combinations thereof, or various components thereof, may be examples of means for performing various aspects of the present disclosure described herein. For example, the processor 404, memory 406, transceiver 408, or various combinations thereof, or components thereof, may support a method for performing one or more of the operations described herein.

[0106] In some implementations, the processor 404, memory 406, transceiver 408, or various combinations or components thereof may be implemented in hardware (e.g., in a communications management circuit system). The hardware may include a 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 of components configured to or otherwise support the functions described in this disclosure. In some implementations, the processor 404 and the memory 406 coupled to the processor 404 may be configured to perform one or more functions described herein (e.g., execution of instructions stored in the memory 406 by the processor 404).

[0107] For example, according to examples disclosed herein, the processor 404 can support wireless communications at the device 402. The processor 404 can be configured to or otherwise support components for: receiving an indication of a shared COT from a COT-initiating UE identified by a first identifier; initiating sidelink communications with a set of other UEs over a sidelink channel on an unlicensed band associated with the shared COT; and performing an LCP procedure, the LCP procedure comprising: generating a sidelink transport block to be sent to the set of other UEs over the initiated sidelink channel, wherein the sidelink transport block comprises a MAC SDU of one or more sidelink logical channels, and wherein the LCP procedure utilizes a sidelink logical channel of the one or more sidelink logical channels having an associated CAPC value that is equal to or less than a threshold CAPC value and an associated destination identifier that matches the first identifier of the COT-initiating UE.

[0108] As another example, according to examples disclosed herein, the processor 404 can support wireless communications at the device 402. The processor 404 can be configured to or otherwise support means for: initiating a COT on an unlicensed band, the COT being used for sidelink communications between a set of UEs; and sending an indication of a shared COT to a receiving UE in the set of UEs, wherein the indication of the shared COT includes COT sharing information including an identifier of the UE and a threshold CAPC value for a sidelink logical channel to be utilized by the receiving UE during an LCP procedure on the shared COT.

[0109] The processor 404 may include an intelligent hardware device (e.g., a general-purpose processor, a DSP, a CPU, a microcontroller, an ASIC, an FPGA, a programmable logic device, discrete gate or transistor logic components, discrete hardware components, or any combination thereof). In some implementations, the processor 404 may be configured to operate a memory array using a memory controller. In some other implementations, the memory controller may be integrated into the processor 404. The processor 404 may be configured to execute computer-readable instructions stored in a memory (e.g., memory 406) to cause the device 402 to perform various functions of the present disclosure.

[0110] The memory 406 may include random access memory (RAM) and read-only memory (ROM). The memory 406 may store computer-readable computer executable code, which includes instructions that, when executed by the processor 404, cause the device 402 to perform the various functions described herein. The code may be stored in a non-transitory computer-readable medium such as system memory or another type of memory. In some implementations, the code may not be directly executed by the processor 404, but may cause a computer (e.g., when compiled and executed) to perform the functions described herein. In some implementations, the memory 406 may also include a basic I / O system (BIOS), which may control basic hardware or software operations, such as interaction with peripheral device components or devices.

[0111] I / O controller 410 can manage input and output signals for device 402. I / O controller 410 can also manage peripheral devices that are not integrated into device 402. In some implementations, I / O controller 410 can represent a physical connection or port to an external peripheral device. In some implementations, I / O controller 410 can utilize an operating system, such as MS or another known operating system. In some implementations, I / O controller 410 may be implemented as part of a processor such as processor 2406. In some implementations, a user may interact with device 402 via I / O controller 410 or via hardware components controlled by I / O controller 410.

[0112] In some implementations, the device 402 may include a single antenna 412. However, in some other implementations, the device 402 may have more than one antenna 412 (i.e., multiple antennas), including multiple antenna panels or antenna arrays, which are capable of concurrently sending or receiving multiple wireless transmissions. The transceiver 408 can communicate bidirectionally via one or more antennas 412, wired or wireless links, as described herein. For example, the transceiver 408 can represent a wireless transceiver and can communicate bidirectionally with another wireless transceiver. The transceiver 408 can also include a modem for modulating packets, providing the modulated packets to one or more antennas 412 for transmission, and demodulating packets received from the one or more antennas 412.

[0113] Figure 5 A flow chart of a method 500 for supporting the execution of an LCP process using a shared COT according to aspects of the present disclosure is illustrated. The operations of the method 500 may be implemented by the apparatus described herein or components thereof. For example, the operations of the method 500 may be implemented by reference to Figures 1 to 3 The UE 104 described herein performs. In some implementations, the device may execute a set of instructions to control the functional elements of the device to perform the described functions. Additionally or alternatively, the device may use dedicated hardware to perform aspects of the described functions.

[0114] At 505, method 500 may include receiving an indication of a shared COT from a COT initiating UE identified by a first identifier. The operations of 505 may be performed according to examples described herein. In some implementations, aspects of the operations of 505 may be described with reference to Figure 1 The device is used to perform the above.

[0115] At 510, method 500 may include initiating sidelink communications with a set of other UEs over a sidelink channel on an unlicensed frequency band associated with a shared COT. The operations of 510 may be performed according to examples described herein. In some implementations, aspects of the operations of 510 may be described with reference to Figure 1 The device is used to perform the above.

[0116] At 515, method 500 may include performing an LCP process, the LCP process comprising: generating a sidelink transport block to be sent to the set of other UEs via the initiated sidelink channel, wherein the sidelink transport block comprises a MAC SDU of one or more sidelink logical channels, and wherein the LCP process utilizes a sidelink logical channel of the one or more sidelink logical channels having an associated CAPC value that is equal to or less than a threshold CAPC value and an associated destination identifier that matches a first identifier of the COT initiating UE. The operations of 515 may be performed according to examples described herein. In some implementations, aspects of the operations of 515 may be performed by reference to Figure 1 The device is used to perform the above.

[0117] Figure 6 FIGURE 6 illustrates a flow chart of a method 600 for supporting sending COT shared information according to aspects of the present disclosure. The operations of the method 600 may be implemented by the apparatus described herein or components thereof. For example, the operations of the method 600 may be implemented by reference to Figures 1 to 3 The UE 104 described herein performs. In some implementations, the device may execute a set of instructions to control the functional elements of the device to perform the described functions. Additionally or alternatively, the device may use dedicated hardware to perform aspects of the described functions.

[0118] At 605, method 600 may include initiating a COT on an unlicensed band for sidelink communications between a set of UEs. The operations of 605 may be performed according to examples described herein. In some implementations, aspects of the operations of 605 may be described with reference to Figure 1 The device is used to perform the above.

[0119] At 610, method 600 may include sending an indication of a shared COT to a receiving UE in the set of UEs, wherein the indication of the shared COT includes COT sharing information, the COT sharing information including: an identifier of the UE, and a threshold CAPC value for a sidelink logical channel utilized by the receiving UE during an LCP procedure on the shared COT. The operations of 610 may be performed according to the examples described herein. In some implementations, aspects of the operations of 610 may be implemented by reference to Figure 1 The device is used to perform the above.

[0120] It should be noted that the methods described herein describe possible implementations, and that the operations and steps may be rearranged or otherwise modified, and other implementations are possible. Furthermore, aspects from two or more methods may be combined.

[0121] The various illustrative blocks and components described in conjunction with the disclosure herein may be implemented or executed using a general purpose processor, a DSP, an ASIC, a CPU, an 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. A general purpose processor may be a microprocessor, but in the alternative, the processor may be any processor, controller, microcontroller, or state machine. A processor may also be implemented as a combination of computing devices (e.g., a DSP and a microprocessor, a plurality of microprocessors, a combination of one or more microprocessors in conjunction with a DSP core, or any other such configuration).

[0122] The functions described herein may be implemented in hardware, software executed by a processor, firmware, or any combination thereof. If implemented in software executed by a processor, the functions may be stored as one or more instructions or codes on or transmitted via a computer-readable medium. Other examples and implementations are within the scope of this disclosure and the appended claims. For example, due to the nature of software, the functions described herein may be implemented using software executed by a processor, hardware, firmware, hardwiring, or any combination thereof. Features that implement the functions may also be physically located in various locations, including being distributed so that portions of the functions are implemented at different physical locations.

[0123] Computer readable medium includes non-transient computer storage medium and communication medium, and communication medium includes any medium that promotes that computer program is transferred from one place to another place.Non-transient storage medium can be any available medium that can be accessed by general-purpose or special-purpose computer.As an example and not limitation, non-transient computer readable medium can include RAM, ROM, electrically erasable programmable ROM (EEPROM), flash memory, compact disc (CD) ROM or other optical disc storage device, magnetic disk storage device or other magnetic storage device, or can be used for carrying or storing desired program code components in the form of instruction or data structure and can be by general-purpose or special-purpose computer, or any other non-transient medium that general-purpose or special-purpose processor accesses.

[0124] Any connection may be appropriately referred to as a computer-readable medium. For example, if the software is sent from a website, server, or other remote source using a coaxial cable, fiber optic cable, twisted pair, digital subscriber line (DSL), or wireless technology (such as infrared, radio, and microwave), the coaxial cable, fiber optic cable, twisted pair, DSL, or wireless technology (such as infrared, radio, and microwave) is included in the definition of computer-readable medium. Disks and optical discs as used herein include CDs, laser discs, optical discs, digital versatile discs (DVDs), floppy disks, and Blu-ray discs, where disks typically reproduce data magnetically, while optical discs reproduce data optically using lasers. Combinations of the above are also included within the scope of computer-readable media.

[0125] As used herein (including in the claims), "or" used in a list of items (e.g., a list of items beginning with a phrase such as "at least one of" or "one or more of" or "one or both of") represents an inclusive list, so that, for example, a list of at least one of A, B, or C represents A or B or C or AB or AC or BC or ABC (i.e., A and B and C). Furthermore, as used herein, the phrase "based on" should not be interpreted as a reference to a set of closed conditions. For example, an example step described as "based on condition A" can be based on both condition A and condition B without departing from the scope of this disclosure. In other words, as used herein, the phrase "based on" should be interpreted in the same manner as the phrase "based at least in part on." Furthermore, as used herein (including in the claims), a "set" may include one or more elements.

[0126] When referring to a network entity, the terms "send," "receive," or "transmit" may refer to any part of a network entity of the RAN (e.g., base station, CU, DU, RU) that communicates with another device (e.g., directly or via one or more other network entities).

[0127] The description herein, in conjunction with the accompanying drawings, describes example configurations and does not represent all possible examples that may be implemented or within the scope of the claims. The term "example" as used herein means "serving as an example, instance, or illustration," rather than "preferred" or "superior to other examples." For the purpose of providing an understanding of the described techniques, the detailed description includes specific details. However, these techniques can be practiced without these specific details. In some cases, known structures and devices are shown in block diagram form to avoid obscuring the concepts of the described examples.

[0128] The description herein is provided to enable one of ordinary skill in the art to make or use the present disclosure. Various modifications to the present disclosure will be readily apparent to one of ordinary skill in the art, and the general principles defined herein may be applied to other variations without departing from the scope of the present disclosure. Therefore, the present disclosure is not limited to the examples and designs described herein, but should be construed in the widest sense consistent with the principles and novel features disclosed herein.

Claims

1. A user equipment (UE), comprising: at least one memory; as well as at least one processor, coupled to the at least one processor and configured to cause the UE to: Initiating, from a channel occupancy time (COT) identified by a first identifier, a UE receives an indication of a shared COT; Initiating sidelink communications with a set of other UEs over a sidelink channel in an unlicensed frequency band associated with the shared COT; as well as performing a Logical Channel Prioritization (LCP) procedure, the LCP procedure comprising: generating a sidelink transport block to be sent to the set of other UEs via the sidelink channel, wherein the sidelink transport block comprises a media access channel service data unit (MAC SDU) of one or more sidelink logical channels; and wherein the LCP process utilizes a sidelink logical channel of the one or more sidelink logical channels having: an associated Channel Access Priority (CAPC) value that is equal to or less than a threshold CAPC value, and An associated destination identifier that matches the first identifier of the COT initiating UE. 2 . The UE of claim 1 , wherein the UE receives the threshold CAPC value from COT sharing information within the indication of the shared COT.

3. The UE of claim 1 , wherein the sidelink logical channel considered during the LCP procedure is associated with a CAPC value that is equal to or less than the threshold CAPC value.

4. The UE of claim 1 , wherein the UE performs the LCP procedure based at least in part on the destination identifier of the sidelink logical channel utilized during the LCP procedure.

5. The UE of claim 1, wherein the utilized sidelink logical channel comprises a Sidelink Traffic Channel (STCH).

6. The UE of claim 1 , wherein each associated CAPC value for a logical channel is based on a delay requirement of the logical channel.

7. The UE of claim 1, wherein the UE initiates the sidelink channel with the set of other UEs by selecting a sidelink grant.

8. A method performed by a user equipment (UE), the method comprising: Initiating, from a channel occupancy time (COT) identified by a first identifier, a UE receives an indication of a shared COT; Initiating sidelink communications with a set of other UEs over a sidelink channel in an unlicensed frequency band associated with the shared COT; as well as performing a logical channel prioritization (LCP) procedure, the LCP procedure comprising: generating a sidelink transport block to be sent to the set of other UEs over the initiated sidelink channel, wherein the sidelink transport block comprises a media access channel service data unit (MAC SDU) of one or more sidelink logical channels; and wherein the LCP process utilizes a sidelink logical channel of the one or more sidelink logical channels having: an associated Channel Access Priority (CAPC) value that is equal to or less than a threshold CAPC value, and An associated destination identifier that matches the first identifier of the COT initiating UE.

9. The method of claim 8, wherein the UE receives the threshold CAPC value from COT sharing information within the indication of the shared COT.

10. The method of claim 8, wherein the sidelink logical channel considered during the LCP procedure is associated with a CAPC value that is equal to or less than the threshold CAPC value.

11. The method of claim 8, wherein the UE performs the LCP procedure based at least in part on the destination identifier of the sidelink logical channel utilized during the LCP procedure.

12. The method of claim 8, wherein the utilized sidelink logical channel comprises a Sidelink Traffic Channel (STCH).

13. The method of claim 8, wherein each associated CAPC value for a logical channel is based on a delay requirement of the logical channel.

14. The method of claim 8, wherein the UE initiates the sidelink channel with the set of other UEs by selecting a sidelink grant.

15. A user equipment (UE), comprising: at least one memory; as well as at least one processor, coupled to the at least one processor and configured to cause the UE to: Initiating a channel occupation time (COT) on an unlicensed band, the COT being used for sidelink communications between the set of UEs; and sending an indication of sharing the COT to a receiving UE in the set of UEs, The indication of sharing the COT includes COT sharing information, and the COT sharing information includes: an identifier of the UE; as well as A threshold channel access priority (CAPC) value for a sidelink logical channel utilized by the recipient UE during a logical channel prioritization (LCP) procedure on the shared COT. 16 . The UE of claim 15 , wherein the UE sends the indication of the shared COT via radio resource control (RRC) signaling.

17. A processor for wireless communication, comprising: at least one controller coupled to the at least one memory and configured to cause the processor to: Initiating, from a channel occupancy time (COT) identified by a first identifier, a UE receives an indication of a shared COT; Initiating sidelink communications with a set of other UEs over a sidelink channel in an unlicensed frequency band associated with the shared COT; as well as performing a Logical Channel Prioritization (LCP) procedure, the LCP procedure comprising: generating a sidelink transport block to be sent to the set of other UEs via the sidelink channel, wherein the sidelink transport block comprises a media access channel service data unit (MAC SDU) of one or more sidelink logical channels; and wherein the LCP process utilizes a sidelink logical channel of the one or more sidelink logical channels having: an associated Channel Access Priority (CAPC) value that is equal to or less than a threshold CAPC value, and An associated destination identifier that matches the first identifier of the COT initiating UE.

18. The processor of claim 17, wherein the processor receives the threshold CAPC value from COT sharing information within the indication of the shared COT.

19. The processor of claim 17, wherein the sidelink logical channel considered during the LCP procedure is associated with a CAPC value that is equal to or less than the threshold CAPC value.

20. The processor of claim 17, wherein the processor performs the LCP procedure based at least in part on the destination identifier of the sidelink logical channel utilized during the LCP procedure.

Images