Sidelink Logical Channel Prioritization (LCP) Procedure Based on Shared Channel Occupancy Time (COT)

Abstract

Various aspects of this disclosure relate to channel occupancy time (COT) sharing for sidelink communication over unlicensed channels. For example, the systems and methods described herein enable efficient sidelink LCP procedures by implementing an LCP procedure for sidelink communication based on received COT sharing instructions. The LCP procedure may identify and utilize a sidelink logical channel of a shared COT based on a received instruction for the shared COT, and transmit data over the shared COT using a sidelink logical channel that satisfies the conditions of the LCP procedure. Furthermore, upon receiving instructions for the shared COT, a UE may implement a type 2 LBT procedure when accessing the shared channel.

Description

Technical Field

[0001] 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)", which is incorporated herein by reference in its entirety.

[0002] The present disclosure relates to wireless communication, and more particularly to sharing channel occupancy time (COT) for unlicensed sidelink channels.

Background Art

[0003] A wireless communication system may include one or more network communication devices, such as a base station, which may be known by other suitable terms, such as an eNodeB (eNB), a next-generation NodeB (gNB), etc. Each network communication device, such as a base station, may support wireless communication for one or more user communication devices, which may be known by other suitable terms, such as a user equipment (UE). 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, slots, subframes, frames, etc.) or frequency resources (e.g., subcarriers, carriers)). Additionally, a wireless communication system may support wireless communication via 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 suitable radio access technologies after 5G (e.g., sixth-generation (6G)).

[0004] In some cases, network communication devices and / or user communication devices in a wireless communication system may utilize unlicensed channels or bandwidth, such as those provided by unlicensed carriers for wireless communication. In applications of NR-U, or New Radio-Unlicensed, communication devices may access unlicensed channels for downlink and / or uplink transmission after performing a listen-before-talk (LBT) procedure.

[0005] Communication devices such as UEs may implement LBT procedures by detecting unlicensed channels for any ongoing communications within a channel (for example, by detecting the energy levels of subbands within a channel). For example, a UE (or gNB) may initiate a Channel Occupancy Time (COT) for a channel, which defines the period during which the UE can communicate over that channel by implementing an LBT procedure (for example, a Category Type 1 or Type 2 procedure) to determine that the channel is available for access. [Overview of the project] [Problems that the invention aims to solve]

[0006] In various scenarios, UEs communicate (or attempt to communicate) with other UEs via a communication link called a sidelink. As the applications of such scenarios expand to additional use cases (e.g., commercial use cases), wireless communication systems may seek to increase the data rate of sidelinks and / or support new or additional carrier frequencies for sidelinks. The use of unlicensed spectrum can help achieve these objectives, bringing increased data rates and more frequencies to the network for sidelink communication. [Means for solving the problem]

[0007] This disclosure relates to methods, apparatus, and systems that support COT sharing for sidelink communication over unlicensed channels. For example, the systems and methods described herein enable efficient sidelink LCP procedures by implementing LCP procedures for sidelink communication based on received COT sharing instructions. The LCP procedure may identify and utilize sidelink logical channels of a shared COT based on received instructions of the shared COT, and transmit data over the shared COT using sidelink logical channels that satisfy the conditions of the LCP procedure. Furthermore, by receiving instructions of the shared COT, a UE may implement a type 2 LBT procedure when accessing the shared channel.

[0008] Some implementations of the methods and apparatus described herein may further include a UE comprising at least one memory and at least one processor, the at least one processor coupled with at least one processor and configured to cause the UE to perform a logical channel prioritization (LCP) procedure comprising causing the UE to receive a shared COT instruction from a channel occupancy time (COT) initiating UE identified by a first identifier, initiating sidelink communication with a set of other UEs over a sidelink channel on unlicensed bandwidth associated with the shared COT, and generating a sidelink transport block to be transmitted to the set of other UEs over the sidelink channel, the sidelink transport block comprising a medium access channel service data unit (MAC SDU) of one or more sidelink logical channels, and the LCP procedure utilizes a sidelink logical channel of one or more sidelink logical channels having an associated CAPC value less than or equal to a channel access priority class (CAPC) threshold and an associated destination identifier matching the first identifier of the COT initiating UE.

[0009] In some implementations of the methods and apparatus described herein, the UE receives the CAPC threshold from the COT shared information in the instructions for the shared COT.

[0010] In some implementations of the methods and apparatus described herein, the sidelink logic channels considered during the LCP procedure are associated with CAPC values ​​below the CAPC threshold.

[0011] In some implementations of the methods and apparatus described herein, the UE performs the LCP procedure based at least in part on the destination identifiers of the sidelink logical channels used during the LCP procedure.

[0012] In some implementations of the methods and apparatus described herein, the sidelink logical channel used includes a sidelink traffic channel (STCH).

[0013] In some implementations of the methods and apparatus described herein, the respective associated CAPC values ​​for the logical channels are based on the delay requirements of the logical channels.

[0014] 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.

[0015] Some implementations of the methods and apparatus described herein may further include a method implemented by a UE, the method comprising: receiving instructions for 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 bandwidth associated with the shared COT; and performing a logical channel prioritization (LCP) procedure which comprises generating a sidelink transport block to be transmitted to the set of other UEs over the initiated sidelink channel, the sidelink transport block comprising MAC SDUs for one or more sidelink logical channels, and the LCP procedure utilizes a sidelink logical channel having an associated CAPC value less than or equal to a CAPC threshold and an associated destination identifier matching the first identifier of the COT initiating UE.

[0016] In some implementations of the methods and apparatus described herein, the UE receives the CAPC threshold from the COT shared information in the instructions for the shared COT.

[0017] In some implementations of the methods and apparatus described herein, the sidelink logic channels considered during the LCP procedure are associated with CAPC values ​​below the CAPC threshold.

[0018] In some implementations of the methods and apparatus described herein, the UE performs the LCP procedure based at least in part on the destination identifiers of the sidelink logical channels used during the LCP procedure.

[0019] In some implementations of the methods and apparatus described herein, the side-link logic channel used includes STCH.

[0020] In some implementations of the methods and apparatus described herein, the respective associated CAPC values ​​for the logical channels are based on the delay requirements of the logical channels.

[0021] 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.

[0022] Some implementations of the methods and apparatus described herein may further include a UE comprising at least one memory and at least one processor, the at least one processor coupled with at least one processor and configured to cause the UE to initiate a COT over unlicensed bandwidth for sidelink communication between sets of UEs and to send a shared COT instruction to a receiver UE of the set of UEs, the shared COT instruction comprising COT sharing information including an identifier of the UE and a CAPC threshold for a sidelink logical channel to be utilized by the receiver UE during an LCP procedure across the shared COT.

[0023] In some implementations of the methods and apparatus described herein, the UE transmits instructions for the shared COT via radio resource control (RRC) signaling.

[0024] Some implementations of the methods and apparatus described herein may further include methods implemented by a UE, the method comprising the steps of initiating a COT over unlicensed bandwidth for sidelink communication between a set of UEs, and sending a shared COT instruction to a receiving UE of the set of UEs, the shared COT instruction comprising COT sharing information including an identifier of the UE and a CAPC threshold for a sidelink logical channel to be utilized by the receiving UE during an LCP procedure across the shared COT.

[0025] In some implementations of the methods and apparatus described herein, the UE transmits instructions for the shared COT via RRC signaling.

[0026] Some implementations of the methods and apparatuses described herein may further include a processor for wireless communication comprising at least one controller, the at least one controller being coupled to at least one memory and configured to cause the processor to receive an indication of a shared COT from a COT-starting UE identified by a first identifier and initiate sidelink communication via a sidelink channel with a set of other UEs on an unlicensed band associated with the shared COT, and to perform an LCP procedure comprising generating a sidelink transport block to be transmitted to the set of other UEs via the sidelink channel, the sidelink transport block comprising MAC SDUs of one or more sidelink logical channels, the LCP procedure utilizing a sidelink logical channel having a related CAPC value below a CAPC threshold and a related destination identifier matching the first identifier of the COT-starting UE among the one or more sidelink logical channels.

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

[0028] In some implementations of the methods and apparatuses described herein, the sidelink logical channels considered during the LCP procedure are associated with CAPC values below a CAPC threshold.

[0029] In some implementations of the methods and apparatuses described herein, 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.

Brief Description of the Drawings

[0030] [Figure 1] FIG. shows an example of a wireless communication system supporting COT sharing for an unlicensed sidelink channel according to an aspect of the present disclosure. [Figure 2]This figure shows an example of a wireless communication system that supports the implementation of LCP procedures across a shared COT, according to the aspects of this disclosure. [Figure 3] This figure shows an example flowchart that supports selecting an LCP procedure for data transmission according to an aspect of this disclosure. [Figure 4] This is an example block diagram of a device that supports COT sharing for an unlicensed sidelink channel according to the aspects of this disclosure. [Figure 5] This is a flowchart illustrating a method for supporting the implementation of LCP procedures using a shared COT, according to the aspects of this disclosure. [Figure 6] This is a flowchart illustrating a method for supporting the transmission of COT shared information in the manner of this disclosure. [Modes for carrying out the invention]

[0031] When a UE uses the COT to communicate over an unlicensed channel (e.g., a sidelink), the UE may share the COT with other UEs if it does not intend to use the COT for the entire duration of the COT. In some cases, a UE using a shared COT from a COT-initiating UE may be able to perform a short LBT procedure (e.g., a type 2 procedure) to gain access to the shared COT.

[0032] However, using a shared COT for a certain transmission (e.g., a physical sidelink shared channel (PSSCH) transmission) may be based on some condition related to the UE being eligible to utilize a set of resource blocks (RBs) within the shared COT for a PSSCH transmission or other transmissions (e.g., a physical sidelink control channel (PSCCH) transmission).

[0033] For example, only PSSCH transmissions associated with a particular destination and / or Channel Access Priority Class (CAPC) may be able to use the RB set across the shared COT. Therefore, in some cases, a UE may have data available for a transmission that satisfies the shared COT conditions, but legacy Logical Channel Prioritization (LCP) procedures may prevent the use of the shared COT due to issues such as the data transmission not satisfying the destination and / or CAPC conditions.

[0034] The systems and methods described herein enable efficient sidelink LCP procedures by implementing LCP procedures for sidelink communication based on received COT shared instructions. For example, an LCP procedure can identify and utilize a sidelink logical channel of a shared COT based on received instructions of the shared COT, and transmit data through the shared COT using a sidelink logical channel that satisfies the conditions of the LCP procedure. Furthermore, by receiving instructions from the shared COT, a UE may implement a type 2 LBT procedure when accessing a shared channel.

[0035] Therefore, this system and method can realize advantages such as efficiently implementing side-link LCP procedures across shared COTs.

[0036] The aspects of this disclosure will be described in the context of wireless communication systems. The aspects of this disclosure will be further illustrated and described with reference to device diagrams and flowcharts.

[0037] Figure 1 shows an example of a wireless communication system 100 supporting COT sharing for an unlicensed sidelink channel according to an aspect of this disclosure. 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 4G and 5G networks, or other suitable radio access technologies including Institute of Electrical and Electronics Engineers (IEEE) 802.11 (Wi-Fi), IEEE 802.16 (WiMAX), and IEEE 802.20. The wireless communication system 100 may support 5G and later radio access technologies. In addition, 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).

[0038] One or more network entities 102 are distributed across a geographical area and may form a wireless communication system 100. One or more of the network entities 102 described herein may be network nodes, base stations, network elements, radio access networks (RANs), base transceiver base stations, access points, NodeBs, eNodeBs (eNBs), next-generation NodeBs (gNBs), or other appropriate terms, or may include them, or may be referred to as such. The network entities 102 and UEs 104 may communicate via a communication link 110, which may be a wireless or wired connection. For example, the network entities 102 and UEs 104 may perform wireless communication via a Uu interface (e.g., receive signaling, transmit signaling).

[0039] A network entity 102 may provide a geographical coverage area 112 in which the network entity 102 can support services (e.g., voice, video, packet data, messaging, broadcast, etc.) for one or more UEs 104 located therein. For example, the network entity 102 and the UEs 104 may support wireless communication of signals relating to services (e.g., voice, video, packet data, messaging, broadcast, etc.) according to one or more radio access technologies. In some implementations, the network entity 102 may be mobile and may, for example, be a satellite associated with a non-terrestrial network. In some implementations, different geographical coverage areas 112 associated with the same or different radio access technologies may overlap, but different geographical 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 this specification may be represented by voltage, current, electromagnetic waves, magnetic fields or magnetic particles, optical fields or optical particles, or any combination thereof.

[0040] One or more UEs 104 may be distributed throughout the geographical area of ​​the wireless communication system 100. The UEs 104 may include, or be referred to as, mobile devices, wireless devices, remote devices, remote units, handheld devices, subscriber devices, or any other appropriate term. In some implementations, the UEs 104 may be referred to, for example, as units, stations, terminals, or clients. Additionally or alternatively, the UEs 104 may be referred to, for example, as Internet-of-Things (IoT) devices, Internet-of-Everything (IoE) devices, or machine-type communications (MTC) devices. In some implementations, the UEs 104 may be stationary within the wireless communication system 100. In some other implementations, the UEs 104 may be mobile within the wireless communication system 100.

[0041] One or more UE104s may be devices of different forms or with different capabilities. Several examples of UE104s are shown in Figure 1. As shown in Figure 1, a UE104 may be capable of communicating with various types of devices, such as network entities 102, other UE104s, or network equipment (e.g., core network 106, packet data network 108, relay devices, integrated access and backhaul (IAB) nodes, or other network equipment). Additionally or alternatively, a UE104 may support communication with other network entities 102 or UE104s that can act as relays in the wireless communication system 100.

[0042] UE104 may also support direct wireless communication with other UE104s via communication link 114. For example, UE104 may support direct wireless communication with another UE104 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, communication link 114 may be called a side link. For example, UE104 may support direct wireless communication with another UE104 via the PC5 interface.

[0043] A network entity 102 may support communication with the core network 106, or with another network entity 102, or both. For example, a network entity 102 may interface with the core network 106 through one or more backhaul links 116 (e.g., via S1, N2, N2, or another network interface). 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, network entities 102 may communicate directly with each other (e.g., between network entities 102). In some other implementations, 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 access network entities, which may be examples of access node controllers (ANCs). An ANC may communicate with one or more UEs 104 through one or more other access network transmitting entities, which may be called radio heads, smart radio heads, or transmit / receive points (TRPs).

[0044] In some implementations, the network entity 102 may be configured in a distributed architecture, which may be configured to utilize a protocol stack that is physically or logically distributed across two or more network entities 102, such as an Integrated Access Backhaul (IAB) network, an Open RAN (O-RAN) (e.g., a network configuration assisted 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.

[0045] RU may also be called radio head, smart radio head, remote radio head (RRH), remote radio unit (RRU), or transmit / receive point (TRP). One or more components of network entity 102 in a distributed RAN architecture may be located in the same location, or one or more components of network entity 102 may be located in distributed locations (e.g., separate physical locations). In some implementations, one or more network entities 102 in a distributed RAN architecture may be implemented as virtual units (e.g., virtual CU (VCU), virtual DU (VDU), virtual RU (VRU)).

[0046] The functional division between CU, DU, and RU may be flexible and may support different functions depending on which functions (e.g., network layer functions, protocol layer functions, baseband functions, radio frequency functions, and any combination thereof) are performed in the CU, DU, or RU. For example, a functional division of the protocol stack may be used between the CU and DU, so that the CU may support one or more layers of the protocol stack, and the DU may support one or more different layers of the protocol stack. In some implementations, the CU may host higher protocol layer functions (e.g., Layer 3 (L3), Layer 2 (L2)) and signaling (e.g., Radio Resource Control (RRC), Service Data Adaptive Protocol (SDAP), Packet Data Convergence Protocol (PDCP)). The CU may be connected to one or more DUs or RUs, which may host lower-level protocol layers such as Layer 1 (L1) (e.g., the Physical (PHY) layer) or L2 (e.g., the Radio Link Control (RLC) layer, the Media Access Control (MAC) layer) functions and signaling, each of which may be at least partially controlled by the CU160.

[0047] As an addition or alternative, a functional division of the protocol stack between DUs and RUs may be used, so that a DU may support one or more layers of the protocol stack, and a RU may support one or more different layers of the protocol stack. A DU may support one or more different cells (for example, through one or more RUs). In some implementations, the functional division between CUs and DUs, or between DUs and RUs, may be within the protocol layer (for example, some functions of the protocol layer may be performed by one of the CUs, DUs, or RUs, while other functions of the protocol layer are performed by one of the different CUs, DUs, or RUs).

[0048] A CU may be further functionally divided into CU control plane (CU-CP) and CU user plane (CU-UP) functions. A CU may be connected to one or more DUs via midhaul communication links (e.g., F1, F1-c, F1-u), and a DU may be connected to one or more RUs via fronthaul communication links (e.g., open fronthaul (FH) interfaces). In some implementations, the midhaul or fronthaul communication links may be implemented according to the interlayer interfaces (e.g., channels) of the protocol stacks supported by each network entity 102 communicating via such communication links.

[0049] 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., a mobility management entity (MME), an access and mobility management function (AMF)) and user plane entities that route packets or interconnect to external networks (e.g., a serving gateway (S-GW), a packet data network (PDN) gateway (P-GW), or a user plane function (UPF)). In some implementations, the control plane entities may manage non-access layer (NAS) functions such as mobility, authentication, and bearer management (e.g., data bearers, signal bearers, etc.) for one or more UEs 104 served by one or more network entities 102 associated with the core network 106.

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

[0051] In the wireless communication system 100, the network entities 102 and UE104 can perform various operations (e.g., wireless communication) using the resources of the wireless communication system 100 (e.g., time resources (e.g., symbols, slots, subframes, frames, etc.) or frequency resources (e.g., subcarriers, carriers)). In some implementations, the network entities 102 and UE104 may support different resource structures. For example, the network entities 102 and UE104 may support different frame structures. In some implementations, such as 4G, the network entities 102 and UE104 may support a single frame structure. In some other implementations, such as 5G and other appropriate radio access technologies, the network entities 102 and UE104 may support various frame structures (i.e., multiple frame structures). The network entities 102 and UE104 may support various frame structures based on one or more numerologies.

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

[0053] The time intervals of resources (for example, communication resources) can be organized according to frames (also called wireless frames). Each frame may have a time length, for example, 10 milliseconds (ms). In some implementations, each frame may contain multiple subframes. For example, each frame may contain 10 subframes, each subframe may have a time length, for example, 1 ms. In some implementations, each frame may have the same time length. In some implementations, each subframe of a frame may have the same time length.

[0054] As an addition or alternative, the time intervals of resources (e.g., communication resources) may be organized according to slots. For example, a subframe may contain a number (e.g., quantity) of slots. The number of slots in each subframe may also depend on one or more numerologies supported in the wireless communication system 100. For example, the first, second, third, fourth, and fifth numerologies (i.e., μ=0, μ=1, μ=2, μ=3, μ=4) associated with the respective subcarrier intervals of 15kHz, 30kHz, 60kHz, 120kHz, and 240kHz may utilize 1 slot per subframe, 2 slots per subframe, 4 slots per subframe, 8 slots per subframe, and 16 slots per subframe, respectively. Each slot may contain a number (e.g., quantity) of symbols (e.g., OFDM symbols). In some implementations, the number (e.g., quantity) of slots for a subframe may depend on the numerology. For a typical cyclic prefix, a slot may contain 14 symbols. In an extended cyclic prefix (e.g., applicable to a 60 kHz subcarrier interval), a slot may contain 12 symbols. The relationship between the number of symbols per slot, the number of slots per subframe, and the number of slots per frame for ordinary and extended cyclic prefixes may depend on the numerology. It should be understood that references to a first numerology (e.g., μ=0) associated with a first subcarrier interval (e.g., 15 kHz) may be interchangeable between subframes and between slots.

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

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

[0057] As described herein, in some embodiments, a UE may utilize an improved or modified LCP procedure when transmitting data across a shared COT (e.g., a PSSCH or PSCCH transmission). For example, a UE may utilize the legacy LCP procedure when it determines that the highest-priority data in the UE's buffer available for transmission has a higher priority than a predetermined threshold, in which case the destination for the sidelink transmission is selected based on the highest-priority data.

[0058] However, when the highest priority of data available for transmission is lower than a predetermined threshold priority, the UE may use an improved LCP procedure, as described herein. In some cases, the improved LCP procedure is based on COT sharing information received from the initiating UE (e.g., information in the shared COT instructions). Using the improved LCP procedure, the UE can access the shared COT and maximize its utilization.

[0059] For example, a UE may determine the highest priority among 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 constraints (e.g., constraints described in section 5.4.3.1.2 of TS 38.321). In some cases, a network (e.g., a gNB) may configure the UE using predetermined threshold priorities via radio resource control (RRC) signaling.

[0060] In some cases, a corresponding responding UE using resources across a shared COT (for example, after accessing the shared COT via a type 2 LBT procedure) may be a UE targeted / targeted by the COT initiating UE for a PSCCH / PSSCH transmission. For example, when a COT initiating UE performs a unicast transmission, the UE may be a responding UE if the source ID and destination ID in the shared COT instruction match the corresponding destination ID and source ID in the receiving UE. As another example, when a COT initiating UE performs a groupcast or broadcast transmission, the UE may be a responding UE if the source ID and destination ID in the shared COT instruction match a destination ID known to the receiving UE.

[0061] In some cases, COT shared information may include additional IDs that are mapped to or match the ID of the responding UE in order to satisfy the destination conditions for sending data across the shared COT. Furthermore, COT shared information may include a CAPC value (e.g., a threshold) for sending data across the shared COT. Thus, a responding UE can send data using the shared COT when the destination conditions are met and the data / transport block / MAC PDU to be sent by the responding UE via the sidelink (e.g., data in the UE's buffer) has a CAPC value less than or equal to the CAPC value indicated in the COT shared information.

[0062] Figure 2 shows an example of a wireless communication system 200 that supports the implementation of LCP procedures across a shared COT, according to an aspect of the present disclosure. The wireless communication system 200 implements, or may implement, an aspect of the wireless communication system 100, as described in Figure 1. For example, the wireless communication system 200 may include a base station 102 and a UE 104, which may be an example of a base station and UE 104 as described with reference to Figure 1.

[0063] The responding UE210 receives a shared COT instruction (e.g., COT sharing instruction 240) from the COT initiating UE220, and the COT initiating UE220 initiates COT230 over an unlicensed channel for sidelink communication. As described herein, the COT sharing instruction 240 may include information such as destination information and / or CAPC values ​​for data to be transmitted over the shared COT230 by the responding UE210.

[0064] A response UE210 having data to be transmitted that satisfies the LCP procedure conditions for using a shared COT230 can perform the LCP procedure 250 using the shared COT230. For example, a response UE210 may determine that the highest priority data in the UE210's buffer available for transmission has a lower priority than a predetermined threshold priority.

[0065] Based on this decision, the response UE210 utilizes only logical channels (LCHs) that satisfy the CAPC condition during the LCP procedure 250. Therefore, the response UE210 uses logical channels with relevant CAPC values ​​less than or equal to the CAPC value identified in the COT shared information (for example, included in the COT shared instruction 240).

[0066] Furthermore, the response UE 210 may utilize a logical channel that also satisfies the destination conditions. For example, during the LCP procedure 250, the response UE 210 may use a logical channel that has a source ID and destination ID that match the destination ID and source ID of the PSSCH / PSCCH of the COT initiation UE, or one that is included in the COT shared instruction 240.

[0067] In some embodiments, the responding UE210 may determine whether any data in the UE210's buffer available for transmission satisfies the destination conditions for shared COT use. For example, whether the responding UE210 has a PSSCH / PSCCH transmission addressed to the COT initiating UE220, for instance, whether the source ID and destination ID included in the COT initiator's sidelink control information (SCI) match the corresponding destination ID and source ID related to the destination ID and source ID unicast at the receiving UE.

[0068] In some cases, when the logical channel does not have data available for transmission that satisfies the destination conditions for sharing the COT, the response UE210 may use the legacy LCP procedure. For example, the response UE210 may generate a TB and perform the LBT type 1 access procedure for transmission of the generated TB (e.g., without using any RB set corresponding to the shared COT230).

[0069] In other cases, if at least one logical channel contains data available for transmissions that satisfy the destination condition (for example, indicating that a transmission to a destination occurs within the shared COT230), the response UE210 determines whether the delay budget associated with the logical channel containing such data can be satisfied even if the shared COT230 cannot be used for transmitting data available for transmissions that do not satisfy the destination condition.

[0070] For example, the response UE210 determines whether the remaining delay budget of a logical channel that does not satisfy the destination condition is greater than a predetermined threshold delay budget (e.g., the time length of the shared COT230). When the response UE210 determines that the data latency requirements can be met, the response UE210 considers such a LCH only when determining the destination as part of an LCP procedure for a sidelink transmission that satisfies the destination condition (e.g., indicating that the transmission to the destination ID occurs within the shared COT). In some cases, the response UE210 may consider a logical channel only during destination selection that satisfies the CAPC condition (e.g., when the CAPC value associated with the logical channel is less than or equal to the CAPC value indicated in the COT sharing information of the COT sharing instruction 240).

[0071] In some embodiments, the response UE210 may select / consider only logical channels that satisfy the CAPC condition (e.g., logical channels with a CAPC value less than or equal to the CAPC threshold) as part of the destination selection in the LCP procedure. For example, the response UE210 may determine whether the selected destination (e.g., the logical channel with the highest priority among the logical channels eligible for destination selection) satisfies the destination condition.

[0072] When the destination conditions are not met, the response UE210 may utilize the legacy LCP procedure (for example, by implementing LBT type 1 for transmitting the generated TB on the PSSCH). However, when the selected destination satisfies the destination conditions of the shared COT230, the response UE210 generates a TB based on a logical channel that satisfies the CAPC conditions (and other conditions such as LCH mapping constraints). The response UE210 then may use LBT type 2 for the generated TB and thus implement the improved LCP procedure for transmitting data over the shared COT230.

[0073] In some embodiments, the response UE210 selects / considers a logical channel that satisfies the destination condition (e.g., the corresponding PSSCH / PSCCH transmission is destined for the COT initiation UE220) for a first sidelink transmission (e.g., a PSSCH / PSCCH transmission) within the shared COT230 during the LCP procedure. For example, the response UE210 may apply only the destination constraint for the first PSSCH / PSCCH transmission within the shared COT230.

[0074] Furthermore, the response UE210 may select / consider only logical channels that satisfy the CAPC conditions for the first PSSCH / PSCCH transmission within the shared COT230. For any remaining or subsequent PSSCH / PSCCH transmissions within the shared COT230, the response UE210 may follow the legacy LCP procedure (e.g., using logical channels that do not satisfy the destination condition). In some cases, the response UE210 may also apply CAPC conditions / constraints for subsequent PSSCH / PSCCH transmissions within the shared COT230.

[0075] When doing so, if at least one PSSCH / PSCCH transmission, such as the first PSSCH / PSCCH transmission, is addressed to the COT initiation UE220, the response UE210 can utilize the shared COT230 (for example, the PSSCH / PSCCH transmission utilizes the RB set of the shared COT230).

[0076] Furthermore, in some cases, the responding UE320 may determine whether there is data available for a transmission addressed to the COT initiating UE220 before deciding whether to use the shared COT230 (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 UE220, the responding UE210 can utilize the shared COT230 and carry out subsequent transmissions to other UEs.

[0077] In some embodiments, the response UE210 may increase the CAPC value of a logical channel or transport block when the delay budget for the logical channel or transport block is about to expire and CAPC constraints / conditions do not allow transmission of the transport block or logical channel using the shared COT230. To ensure that the response UE210 can transmit the TB within the delay budget by using the shared COT230 (via LBT type 2), the response UE210 may, in some cases, increase the CAPC priority of the logical channel or TB. For example, the response UE210 may increase the CAPC priority of a logical channel or TB to satisfy the CAPC condition of the shared COT230 only when the priority of the logical channel or TB (e.g., the CAPC value) is greater than a predetermined CAPC threshold.

[0078] In some embodiments, the buffer of the response UE210 contains data for the sidelink logical channel available for transmission. However, the response UE210 does not need to multiplex the MAC SDU to the MAC PDU when the sidelink logical channel has a CAPC value greater than the CAPC value indicated in the COT shared information, such as when the TB contains MAC SDUs for a sidelink logical channel whose MAC PDU has a high CAPC priority (e.g., SRB) and / or MAC CE, or when the TB contains MAC SDUs for a sidelink logical channel whose delay budget is about to expire and cannot be met without the shared COT230.

[0079] To avoid the response UE210 using a low CAPC value (e.g., a higher CAPC value than indicated in the shared COT information) for transmitting MAC PDUs, and therefore using LBT type 1 for PSSCH / PSCCH transmissions, the response UE210 may implement multiplex padding to MAC PDUs instead of data on logical channels with lower CAPC priority (e.g., higher CAPC values). In some cases, regardless of whether the TB also includes sidelink MAC CEs in addition to MAC SDUs, the CAPC of the lowest priority logical channel on which the MAC SDU is multiplexed in the TB may be used for transmitting the TB.

[0080] In some cases, the response UE210 may perform multiple padding to the MAC PDU only when the amount of data with the highest CAPC priority in the MAC PDU exceeds or is greater than a threshold of some magnitude, such as a value or percentage (e.g., configured via higher-layer signaling).

[0081] In some embodiments, as described herein, the response UE210 may make a series of decisions when selecting an LCP procedure for data transmission. Figure 3 shows an example of a flowchart 300 supporting the selection of an LCP procedure for data transmission according to an aspect of this disclosure.

[0082] The responding UE 210 receives the COT shared information 310 and performs the COT shared selection 312. First, the responding UE performs the destination matching operation 314 and determines whether its buffer contains data available for transmission that satisfies the destination conditions of the COT shared information 310.

[0083] When there is no data available for a transmission that satisfies the destination conditions, the response UE210 performs LBT type 1 for the corresponding PSSCH / PSCCH transmission according to legacy LCP procedure 316. When there is data in the UE buffer that satisfies the destination conditions of the COT shared information 310, the response UE210 performs operation 320, determining whether the selected destination (using legacy LCP / destination selection based on the highest priority data) satisfies the destination conditions of the shared COT.

[0084] When the selected destination satisfies the destination conditions of the shared COT, the response UE210 determines in operation 322 whether the CAPC conditions are met for PSSCH / PSCCH transmission. When the response UE210 uses only logical channels during the LCP procedure, for selected destinations that also satisfy the CAPC conditions, the response UE210 is eligible to use the shared COT and performs LBT type 2 in operation 324. When the response UE210 does not apply additional CAPC constraints during the LCP procedure, the resulting TB may not satisfy the CAPC conditions of the shared COT, and the response UE210 performs LBT type 1 in operation 326.

[0085] If the selected destination does not satisfy the destination conditions of the shared COT, the response UE210 determines in operation 330 whether to change the destination selection during the LCP procedure. The response UE210 may decide whether to change the destination selection based on the priority of the highest-priority data in its buffer.

[0086] When the responding UE210 selects a destination that does not satisfy the destination conditions of the shared COT, the responding UE210 initiates its own COT for the corresponding PSSCH / PSCCH transmission and performs the LBT type 1 procedure. When the responding UE210 modifies the destination selection procedure (for example, when it decides to use only logical channels that satisfy the destination conditions of the shared COT, the responding UE210, in operation 340, determines whether CAPC constraints apply to determine eligibility to use the shared COT).

[0087] If the response UE210 uses only logical channels during the LCP procedure in operation 340, the response UE210 is eligible to use the shared COT for selected destinations that also satisfy the CAPC conditions, and in operation 344, it implements LBT type 2. If the response UE210 does not apply any additional CAPC constraints during the LCP procedure, the response UE210 implements LBT type 1 in operation 342, as described herein.

[0088] Furthermore, in some cases, when the responding UE210 receives multiple COT sharing information from different COT initiating UEs and has data that satisfies multiple COT sharing conditions, the responding UE210 may maximize the transmission of high priority and follow the conventional principles of destination selection based on the highest priority.

[0089] In some embodiments, the response UE210 may enter a discontinuous receive state (e.g., a DRX state) in which the response UE210 does not monitor PSCCH(SCI) / PSSCH for a given source-destination pair when using a shared COT for its destination. For example, the response UE210 may stop monitoring PSCCH / PSSCH from the COT-starting UE220 when the COT-starting UE220 shares its COT (e.g., COT230) and the response UE210 is using the shared COT.

[0090] In some cases, the response UE210 may stop monitoring the PSCCH / PSSCH while using the shared COT, because the COT initiating UE220 is sharing its COT and therefore there is no data available to send to the response UE210. In some cases, when the response UE210 is using the shared COT and stops monitoring the PSCCH / PSSCH, the response UE210 may stop or interrupt all drx-related timers (for example, drx-related timers for source and destination pairs where the response UE210 is using the shared COT).

[0091] Therefore, in some embodiments, a UE (e.g., a response UE210) may implement or enter a DRX state when it receives a COT sharing instruction from a COT initiating UE (e.g., a COT initiating UE220) and uses a shared COT (e.g., a COT230).

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

[0093] In some cases, the system and method may allow the UE to consider only using a logical channel that satisfies the CAPC constraint during the LCP procedure, such as when the selected destination satisfies the destination conditions, and the UE uses a shared COT for PSSCH transmission; otherwise, the UE initiates its own unique COT.

[0094] In some cases, the system and methods may implement criteria / rules governing whether the UE uses a shared COT with a modified or improved LCP procedure, or whether the UR initiates its own COT. For example, depending on the priority of its highest-priority data, the UE may determine whether it is appropriate to use a shared COT when the highest-priority data exceeds a predetermined priority threshold, and the UE may use a new COT to transmit the higher-priority data. As another example, depending on the delay budget of a sidelink logical channel or transport block, the UE may decide whether to modify the LCP procedure to use a shared COT for PSSCH transmissions.

[0095] In some cases, the system and method can implement improved destination selection based on the shared COT for the initial sidelink transmission of the shared COT, without any constraints on subsequent transmissions.

[0096] In some cases, the system and methods may allow the UE to increase the CAPC priority of a transport block or logical channel, or to include padding when the delay budget is about to expire and the use of shared COT is not permissible based on the current CAPC value.

[0097] In some cases, the system and methods may allow the UE to stop drx ActiveTime based on COT sharing information / usage, such as when the responding UE is using a shared COT (when DRX occurs during the use of a shared COT, and / or when drx-related timers are stopped when using a shared COT).

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

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

[0100] In some implementations, the processor 404, memory 406, transceiver 408, or various combinations or components thereof, may be implemented in hardware (for example, in a communication management circuit). 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 gates or transistor logic, discrete hardware components, or any combination thereof that constitutes, or otherwise supports, the functions described herein. In some implementations, the processor 404 and the memory 406 coupled to the processor 404 may be configured to perform one or more of the functions described herein (for example, having the processor 404 execute instructions stored in memory 406).

[0101] For example, the processor 404 may support wireless communication in device 402 according to examples such as those disclosed herein. The processor 404 may be configured, or may support otherwise, for performing an LCP procedure comprising receiving instructions for a shared COT from a COT initiating UE identified by a first identifier, initiating sidelink communication with a set of other UEs over an unlicensed band associated with the shared COT via a sidelink channel, and generating a sidelink transport block to be transmitted to the set of other UEs via the initiated sidelink channel, wherein the sidelink transport block comprises a MAC SDU for one or more sidelink logical channels, and the LCP procedure utilizes a sidelink logical channel having an associated CAPC value less than or equal to a CAPC threshold and an associated destination identifier matching the first identifier of the COT initiating UE.

[0102] As another example, the processor 404 may support wireless communication in device 402 in accordance with examples such as those disclosed herein. The processor 404 is configured, or may otherwise support, for initiating a COT over unlicensed bandwidth for sidelink communication between sets of UEs and sending a shared COT instruction to a receiver UE of the set of UEs, the shared COT instruction comprising COT sharing information including UE identifiers and CAPC thresholds for sidelink logical channels to be utilized by the receiver UE during LCP procedures across the shared COT.

[0103] The processor 404 may include intelligent hardware devices (e.g., general-purpose processors, DSPs, CPUs, microcontrollers, ASICs, FPGAs, programmable logic devices, 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 memory (e.g., memory 406) in order to cause device 402 to perform various functions of this disclosure.

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

[0105] The I / O controller 410 can manage input and output signals for device 402. The I / O controller 410 can also manage peripherals not integrated into device M02. In some implementations, the I / O controller 410 may represent physical connections or ports to external peripherals. In some implementations, the I / O controller 410 may utilize an operating system such as iOS®, ANDROID®, MS-DOS®, MS-WINDOWS®, OS / 2®, UNIX®, LINUX®, or another known operating system. In some implementations, the I / O controller 410 may be implemented as part of a processor, such as processor M06. In some implementations, a user may interact with device 402 via the I / O controller 410 or via hardware components controlled by the I / O controller 410.

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

[0107] Figure 5 shows a flowchart of Method 500, which supports performing an LCP procedure using a shared COT, according to an aspect of this disclosure. The operation of Method 500 may be performed by a device or component thereof, as described herein. For example, the operation of Method 500 may be performed by UE104, as described with reference to Figures 1 to 3. In some implementations, the device may execute a set of instructions to control a functional element of the device to perform the described function. In addition or alternatively, the device may perform aspects of the described function using dedicated hardware.

[0108] In 505, method 500 may include the step of receiving instructions for a shared COT from a COT-initiated UE identified by a first identifier. The operation of 505 may be carried out according to examples such as those described herein. In some implementations, the operation of 505 may be carried out by a device as described with reference to Figure 1.

[0109] In 510, method 500 may include the step of initiating sidelink communication with another set of UEs via a sidelink channel over an unlicensed bandwidth associated with a shared COT. The operation of 510 may be carried out according to examples such as those described herein. In some implementations, the mode of operation of 510 may be carried out by a device as described with reference to Figure 1.

[0110] In 515, method 500 may include the step of performing an LCP procedure comprising generating a sidelink transport block to be sent to a set of other UEs via an initiated sidelink channel, the sidelink transport block comprising a MAC SDU of one or more sidelink logical channels, and the LCP procedure utilizes a sidelink logical channel having an associated CAPC value less than or equal to a CAPC threshold and an associated destination identifier matching a first identifier of the COT initiated UE. The operation of 515 may be performed according to examples such as those described herein. In some implementations, the operation of 515 may be performed by a device such as those described with reference to Figure 1.

[0111] Figure 6 shows a flowchart of Method 600 supporting the transmission of COT shared information according to an aspect of this disclosure. The operation of Method 600 may be carried out by a device or component thereof, as described herein. For example, the operation of Method 600 may be carried out by UE104 as described with reference to Figures 1 to 3. In some implementations, the device may execute a set of instructions to control the functional elements of the device to perform the described functions. In addition or alternatively, the device may use dedicated hardware to perform aspects of the described functions.

[0112] In 605, method 600 may include the step of initiating a COT over an unlicensed band for sidelink communication between sets of UEs. The operation of 605 may be carried out according to examples such as those described herein. In some implementations, the operation of 605 may be carried out by a device as described with reference to Figure 1.

[0113] In 610, method 600 may include the step of sending a shared COT instruction to a receiving UE from a set of UEs, the shared COT instruction comprising COT sharing information including an identifier for the UE and a CAPC threshold for a sidelink logical channel to be used by the receiving UE during the LCP procedure across the shared COT. The operation of 610 may be carried out according to examples such as those described herein. In some implementations, the operation of 610 may be carried out by a device as described with reference to Figure 1.

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

[0115] Blocks and components for various descriptions related to the disclosure herein may be implemented or performed in general-purpose processors, DSPs, ASICs, CPUs, FPGAs, or other programmable logic devices, discrete gates 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 alternatively, a processor may be any processor, controller, microcontroller, or state machine. A processor may also be implemented as a combination of computing devices (for example, a combination of a DSP and a microprocessor, multiple microprocessors, one or more microprocessors working with a DSP core, or any other such configuration).

[0116] The functions described herein may be implemented in hardware, software executed by a processor, firmware, or any combination thereof. When implemented in software executed by a processor, the functions may be stored as one or more instructions or codes on a computer-readable medium, or transmitted through them. Other examples and implementations are within the scope of this disclosure and the accompanying claims. For example, depending on the nature of the software, the functions described herein may be implemented using software executed by a processor, hardware, firmware, hardwiring, or any combination thereof. Features implementing the functions may also be physically located in various locations, including being distributed so that some of the functions are implemented in different physical locations.

[0117] Computer-readable media include both non-temporary computer storage media and communication media, including any media that facilitates the transfer of computer programs from one location to another. Non-temporary storage media can be any available media that can be accessed by a general-purpose computer or a dedicated computer. Non-temporary computer-readable media can include, but are not limited to, RAM, ROM, electrically erasable programmable ROM (EEPROM), flash memory, compact disk (CD) ROM or other optical disk storage, magnetic disk storage or other magnetic storage devices, or any other non-temporary media that can be used to carry or store desired program code means in the form of instructions or data structures, and that can be accessed by a general-purpose computer or a dedicated computer or a general-purpose processor or a dedicated processor.

[0118] Any connection can appropriately be called a computer-readable medium. For example, if software is transmitted from a website, server, or other remote source using coaxial cable, fiber optic cable, twisted pair, digital subscriber line (DSL), or wireless technologies such as infrared, radio, and microwave, then coaxial cable, fiber optic cable, twisted pair, DSL, or wireless technologies such as infrared, radio, and microwave are included in the definition of a computer-readable medium. In this specification, disk and disc include CD, laserdisc, optical disc, digital versatile disc (DVD), floppy disk, and Blu-ray® disc, where disk usually reproduces data magnetically and disc uses a laser to reproduce data optically. Any combination of the above is also included in the scope of a computer-readable medium.

[0119] In this specification, as used in enumerations of items (for example, enumerations of items followed by phrases such as “at least one of” or “one or more of” or “one or both of”), including in the claims, “or” indicates an inclusive enumeration, such as when the enumeration of at least one of A, B, or C means A or B or C or AB or AC or BC or ABC (i.e., A and B and C). Also in this specification, the phrase “based on” should not be interpreted as referring to a closed set of conditions. For example, an exemplary step described as “based on condition A” may be based on both condition A and condition B without departing from the scope of this disclosure. In other words, in this specification, the phrase “based on” shall be interpreted in the same way as the phrase “based on at least part of.” Furthermore, in this specification, including in the claims, “set” may include one or more elements.

[0120] The terms “transmit,” “receive,” or “communicate” may refer to any part of a RAN network entity (e.g., base station, CU, DU, RU) that is communicating with another device (e.g., directly or through one or more other network entities) when referring to a network entity.

[0121] The descriptions herein, along with the accompanying drawings, describe exemplary configurations and do not represent all examples that may be implemented or that fall within the scope of the claims. The term “example” as used herein means “serving as an example, case, or illustration,” and does not mean “preferred” or “advantageous over other examples.” The modes for carrying out the invention include specific details for the purpose of providing an understanding of the techniques described. However, these techniques may be practiced without these specific details. In some cases, known structures and devices are shown in the form of block diagrams to avoid obscuring the concepts of the examples described.

[0122] The descriptions herein are provided to enable those skilled in the art to create or use this disclosure. Various modifications to this disclosure will be apparent to those skilled in the art, and the general principles defined herein may be applied to other modifications without departing from the scope of this disclosure. Accordingly, this disclosure is not limited to the examples and designs described herein and should be recognized as encompassing the broadest possible scope of principles and novel features disclosed herein without inconsistency. [Explanation of Symbols]

[0123] 100 Wireless Communication Systems 102 Network Entities 104 UE 106 Core Network 108 Packet Data Network 110 Communication Link 112 Geographic Coverage Areas 114 Communication Link 116 Backhaul Link 118 Application Server 200 Wireless Communication Systems 210 UE 220 COT start UE 230 Shared COT 240 COT sharing instructions 250 LCP Procedures 402 Device 404 Processor 406 memory 408 Transceiver 410 I / O Controllers 412 Antenna

Claims

1. At least one memory, A user device (UE) comprising at least one processor, wherein the at least one processor is coupled with the UE, The system receives a COT instruction from the Shared Channel Occupancy Time (COT) initiation UE, which is identified by the first identifier. Initiate sidelink communication with another set of UEs via a sidelink channel on the unlicensed bandwidth associated with the shared COT, The system is configured to perform a logical channel prioritization (LCP) procedure, which includes 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) for one or more sidelink logical channels. The LCP procedure is performed in one or more of the side-link logical channels. Related CAPC values ​​below the Channel Access Priority Class (CAPC) threshold, A related destination identifier that matches the first identifier of the COT start UE and A UE that utilizes a sidelink logical channel.

2. The UE according to claim 1, wherein the UE receives the CAPC threshold from the COT sharing information in the instructions of the shared COT.

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

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

5. The UE according to claim 1, wherein the sidelink logical channel used includes a sidelink traffic channel (STCH).

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

7. The UE according to 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 user equipment (UE), The steps include receiving a shared COT instruction from a shared channel occupancy time (COT) initiation UE identified by a first identifier, The steps include: initiating sidelink communication with another set of UEs via a sidelink channel on the unlicensed bandwidth associated with the shared COT; The procedure comprises the steps of performing a logical channel prioritization (LCP) procedure which involves generating a sidelink transport block to be sent to the set of other UEs via the initiated sidelink channel, The sidelink transport block comprises a media access channel service data unit (MAC SDU) for one or more sidelink logical channels. The LCP procedure is performed in one or more of the side-link logical channels. Related CAPC values ​​below the Channel Access Priority Class (CAPC) threshold, A related destination identifier that matches the first identifier of the COT start UE and A method that utilizes a sidelink logical channel having

9. The method according to claim 8, wherein the UE receives the CAPC threshold from the COT sharing information in the instruction of the shared COT.

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

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

12. The method according to claim 8, wherein the sidelink logical channel used includes a sidelink traffic channel (STCH).

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

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

15. At least one memory, A user device (UE) comprising at least one processor, wherein the at least one processor is coupled with the UE, To initiate shared channel occupancy time (COT) over unlicensed bandwidth for sidelink communication between sets of UEs, The UE is configured to send instructions for the shared COT to the recipient UE of the aforementioned set, The aforementioned instruction of the shared COT, The identifier of the aforementioned UE, During the logical channel prioritization (LCP) procedure across the shared COT, the channel access priority class (CAPC) threshold for the sidelink logical channel used by the receiver UE and A UE that includes COT shared information.

16. The UE according to claim 15, wherein the UE transmits the instructions of the shared COT via radio resource control (RRC) signaling.

17. A processor for wireless communication comprising at least one controller, wherein the at least one controller is coupled with at least one memory, and the processor, The Shared Channel Occupancy Time (COT) instruction is received from the Shared Channel Occupancy Time (COT) Initiation UE, identified by the first identifier. Initiate sidelink communication with another set of UEs via a sidelink channel on the unlicensed bandwidth associated with the shared COT, It is configured to perform a logical channel prioritization (LCP) procedure, which includes generating a sidelink transport block to be sent to the set of other UEs via the sidelink channel, The sidelink transport block comprises a media access channel service data unit (MAC SDU) for one or more sidelink logical channels. The LCP procedure is performed in one or more of the side-link logical channels. Related CAPC values ​​below the Channel Access Priority Class (CAPC) threshold, A related destination identifier that matches the first identifier of the COT start UE and A processor that utilizes side-link logical channels.

18. The processor according to claim 17, wherein the processor receives the CAPC threshold from the COT sharing information in the instruction of the shared COT.

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

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

Images