Channel configuration based on logical channel conditions

Abstract

Aspects of the present disclosure relate to methods, apparatuses, and systems for supporting logical channel condition-based channel configuration. For example, a wireless channel for data transmission, e.g., a PSSCH allocation for sidelink transmission, is configured with different logical channel conditions. In accordance with an implementation, the UE applies a first logical channel condition to a first PSSCH allocation in a set of consecutive PSSCH allocations, and applies a second logical channel condition to the remaining PSSCH allocations. For example, the second logical channel condition specifies certain conditions to be mapped to high priority data allocated by a subsequent PSSCH.

Description

[0001] CROSS-REFERENCE TO RELATED APPLICATIONS

[0002] This application claims priority to U.S. patent application serial number 63 / 358,631, filed on July 6, 2022, entitled “CHANNEL CONFIGURATION BASEDON LOGICAL CHANNEL CONDITIONS,” the entire contents of which are incorporated herein by reference. Technical Field

[0003] The present disclosure relates to wireless communications, and more particularly to wireless channel configuration. Background Art

[0004] A wireless communication system may include one or more network communication devices (such as base stations), which may be referred to as eNodeB (eNB), next generation NodeB (gNB), or other suitable terms. Each network communication device (such as a base station) may support wireless communication of one or more user communication devices, which may also be referred to as user equipment (UE) or other suitable terms. A wireless communication system may support wireless communication with one or more user communication devices by utilizing resources of a wireless communication system (e.g., time resources (e.g., symbols, time slots, subframes, frames, etc.) or frequency resources (e.g., subcarriers, carriers)). In addition, 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 suitable radio access technologies beyond 5G (e.g., sixth generation (6G)).

[0005] Some wireless communication systems provide methods for configuring wireless channels for data transmission, such as for physical sidelink shared channel (PSSCH) configuration. However, some technologies apply static data configurations for wireless channels, which may not be able to adapt to certain failures related to channel conditions. Summary of the invention

[0006] The present disclosure relates to methods, devices, and systems that support channel configuration based on logical channel conditions. For example, different logical channel conditions are used to configure a wireless channel for data transmission, for example, a PSSCH allocation for sidelink transmission. According to the implementation, the UE applies a first logical channel condition to the first PSSCH allocation in a continuous PSSCH allocation set. For example, the first PSSCH allocation is immediately after a clear channel assessment (CCA) process (e.g., a listen-before-talk (LBT) process). For example, the first logical channel condition specifies that high priority data will not be mapped to the first PSSCH allocation in a continuous PSSCH allocation set. In addition, high priority data can be mapped to subsequent PSSCH allocations in a continuous PSSCH allocation set that meets certain second logical channel conditions, such as by applying a second logical channel condition to the remaining PSSCH allocations. For example, the second logical channel condition specifies certain conditions for high priority data that will be mapped to subsequent PSSCH allocations, such as subsequent PSSCH allocations that do not include a physical sidelink feedback channel (PSFCH), or a sidelink positioning reference signal (SL-PRS).

[0007] By utilizing the technology, delays and / or failures in the transmission of high-priority data can be reduced. For example, the technology can reduce delays that may occur in wireless transmission of high-priority data and improve the reliability of data transmission.

[0008] Some implementations of the methods and apparatus described herein may also include generating, for a PSSCH allocation set, a first set of media access control (MAC) protocol data units (PDUs) for a first subset of PSSCH allocations in the PSSCH allocation set based at least in part on a first logical channel condition associated with a logical channel priority ranking; and generating, for the PSSCH allocation set, a second set of MAC PDUs for a second subset of PSSCH allocations in the PSSCH allocation set based at least in part on a second logical channel condition associated with a logical channel priority ranking.

[0009] Some implementations of the methods and apparatus described herein may further include: determining a PSSCH allocation set based on at least one predefined criterion; wherein at least one predefined criterion includes: a second subset of PSSCH allocations does not include PSFCH; wherein at least one predefined criterion includes: a second subset of PSSCH allocations does not include sidelink PRS; wherein a first subset of PSSCH allocations starts from a first PSSCH allocation in the PSSCH allocation set; performing a listen-before-talk process before the first subset of PSSCH allocations; as part of logical channel priority sorting, preventing high priority data from being mapped to the first subset of PSSCH allocations; wherein the first logical channel condition is different from the second logical channel condition; wherein the PSSCH allocation set includes: consecutive PSSCH allocations; wherein the first logical channel condition includes: data below a threshold priority is mapped to the first subset of PSSCH allocations.

[0010] Some implementations of the methods and apparatus described herein may further include: wherein the first logical channel condition comprises: data with a priority higher than a threshold is not mapped to a first subset of a PSSCH allocation; wherein the second logical channel condition comprises: an indication that data with a priority higher than a threshold is mapped to a second subset of a PSSCH allocation; wherein the second logical channel condition comprises: when data with a priority higher than a threshold is mapped to PSSCH resources of a second subset of a PSSCH allocation, one or more of the following items: the PSSCH resources do not include a PSFCH; the PSFCH timing is not delayed; the PSSCH resources do not include a sidelink PRS; the PSSCH resources are within the discontinuous reception (DRX) time of the destination UE; or the modulation and coding scheme (MCS) to be used for transmission on the PSSCH resources is not a specified level higher than the MCS previously selected for the PSSCH resources; and also includes sending data via one or more of a first group of MAC PDUs or a second group of MAC PDUs; and also includes sending data via one or more of a first subset of a PSSCH allocation or a second subset of a PSSCH allocation.

[0011] Some implementations of the methods and apparatus described herein may also include generating a notification that, for a PSSCH allocation set, specifies: a first logical channel condition associated with a logical channel priority ranking for a first subset of PSSCH allocations in the PSSCH allocation set; and a second logical channel condition associated with a logical channel priority ranking for a second subset of PSSCH allocations in the PSSCH allocation set; and sending the notification to a UE.

[0012] Some implementations of the methods and apparatus described herein may also include: wherein the notification specifies that: the first subset of PSSCH allocations will start from the first PSSCH allocation in the PSSCH allocation set; wherein the first logical channel condition is different from the second logical channel condition; wherein the first logical channel condition specifies that: high priority data will not be mapped to the first subset of PSSCH allocations; wherein the second logical channel condition includes: an indication that data above a threshold priority will be mapped to a second subset of PSSCH allocations; wherein the second logical channel condition includes: when data above a threshold priority is mapped to the PSSCH resources of the second subset of PSSCH allocations, one or more of the following items: the PSSCH resources will not include PSFCH; the PSFCH timing will not be delayed; the PSSCH resources will not include sidelink PRS; the PSSCH resources will be within the DRX time of the destination UE; or the MCS to be used for transmission on the PSSCH resources will not be a specified level higher than the MCS previously selected for the PSSCH resources.

[0013] Some implementations of the methods and apparatus described herein may also include: performing, by the UE, a listen-before-talk procedure on a first sidelink resource to be used for a sidelink transmission; autonomously selecting, by the UE at least in part based on a failure of the listen-before-talk procedure, a second sidelink resource to be used for the sidelink transmission; and sending the sidelink transmission using the second sidelink resource.

[0014] Some implementations of the methods and apparatus described herein may further include: receiving an indication of a failure of a listen-before-talk procedure from a physical layer (PHY); wherein the second sidelink resource includes: the next time slot after the first sidelink resource; selecting the second sidelink resource as the sidelink resource so that one or more of the following items: the second sidelink resource does not include PSFCH: the PSFCH timing is not delayed due to the selection of the second sidelink resource; the second sidelink resource does not include a sidelink PRS; the second sidelink resource is within the DRX time of the destination UE; or the MCS to be used for transmission on the second sidelink resource is not a specified level higher than the MCS previously selected for the first sidelink resource; wherein the sidelink transmission on the first sidelink resource includes: a transport block in a hybrid automatic repeat request (HARQ) buffer, and using the second sidelink resource to send the sidelink transmission includes: HARQ retransmissions of the transport block; wherein the UE is configured with a maximum number of HARQ transmissions, and the UE is configured to exceed the maximum number in the event of HARQ retransmissions of the transport block. BRIEF DESCRIPTION OF THE DRAWINGS

[0015] Figure 1 An example of a wireless communication system supporting channel configuration based on logical channel conditions according to aspects of the present disclosure is illustrated.

[0016] Figure 2 Different channel occupation times (COTs) and idle periods between COTs are illustrated.

[0017] Figure 3 An implementation is illustrated where different COT initiators are used for different physical uplink shared channel (PUSCH) transmissions and / or repetitions.

[0018] Figure 4 An implementation is illustrated where the UE initiates the COT.

[0019] Figure 5 Implementations supporting channel configuration based on logical channel conditions according to aspects of the present disclosure are illustrated.

[0020] Figure 6 Implementations supporting channel configuration based on logical channel conditions according to aspects of the present disclosure are illustrated.

[0021] Figure 7 An example of time slots supporting channel configuration based on logical channel conditions according to aspects of the present disclosure is illustrated.

[0022] Figure 8 and Fig. 9 An example of a block diagram of a device supporting channel configuration based on logical channel conditions according to aspects of the present disclosure is illustrated.

[0023] Figures 10 to 12 A flow chart of a method for supporting channel configuration based on logical channel conditions according to aspects of the present disclosure is illustrated. DETAILED DESCRIPTION

[0024] In some wireless communication systems, a method for logical channel prioritization (LCP) is provided, wherein in a scenario where the UE has a set of consecutive PSSCH allocations, the UE multiplexes high priority data to the first PSSCH allocation. However, when operating in a shared spectrum with multiple PSSCH allocations, the first SL allocation may have the highest probability of CCA failure, where the UE will perform CCA to initiate a sidelink transmission sequence. Therefore, mapping the high priority data to the first PSSCH immediately after the CCA process may result in an increased delay in the transmission of the high priority data due to the resulting HARQ retransmissions.

[0025] For example, in some wireless communication systems, for scenarios involving multiple transmission time interval (TTI) grants, high priority data may be placed in the first transport block (TB), respectively, and may therefore be sent within the first PUSCH allocation. However, when operating in a shared spectrum, following this principle for multi-TTI grants may result in a situation where the UE is unable to send high priority data and / or MAC control elements (CEs) due to a CCA failure, and / or part of the transmission is lost due to a later access to the channel, making the corresponding TB undecodable without further (e.g., later) retransmissions. For example, the UE performs CCA to initiate an uplink (UL) transmission sequence within a multi-TTI grant, and the first UL grant is the most likely scenario in which a UL transmission failure may occur due to a CCA failure. Therefore, mapping the high priority data in the first PUSCH immediately after the CCA process may result in an increased delay in the transmission of the high priority data due to the necessary HARQ retransmissions.

[0026] Therefore, the present disclosure provides a technology that supports channel configuration based on logical channel conditions. For example, different logical channel conditions are used to configure a wireless channel for data transmission, for example, a PSSCH allocation for sidelink transmission. According to the implementation, the UE applies a first logical channel condition to the first PSSCH allocation in a continuous PSSCH allocation set. For example, the first PSSCH allocation is immediately after a CCA process (e.g., an LBT process). For example, the first logical channel condition specifies that high priority data will not be mapped to the first PSSCH allocation in a continuous PSSCH allocation set. In addition, high priority data can be mapped to subsequent PSSCH allocations in a continuous PSSCH allocation set that meets certain second logical channel conditions, such as by applying a second logical channel condition to the remaining PSSCH allocations. For example, the second logical channel condition specifies certain conditions for high priority data that will be mapped to subsequent PSSCH allocations, such as subsequent PSSCH allocations that do not include PSFCH or SL-PRS.

[0027] The present disclosure also provides a technique that enables a UE to trigger selection of new SL resources when SL transmission is not performed due to a CCA failure. For example, in response to receiving a CCA (e.g., LBT) failure indication for a transmission attempt for a TB and / or PSSCH from a PHY layer, a UE configured for resource allocation mode 2 selects new additional SL resources for transmission of the TB. For example, a CCA failure event is used as a trigger for SL resource selection (e.g., reselection).

[0028] Thus, by utilizing the techniques, the risk of delaying the transmission of high priority data and / or MAC CE due to CCA failure, such as the risk that a CCA failure of the first PSSCH allocation in a set of consecutive PSSCH allocations may occur, is mitigated. In addition, the UE-autonomous selection of sidelink resources in response to CCA failure may reduce latency and signaling overhead compared to some conventional resource selection procedures. Thus, the techniques may reduce data transmission latency and provide higher data transmission reliability, such as for the transmission of high priority data using sidelink resources.

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

[0030] Figure 1 An example of a wireless communication system 100 that supports channel configuration based on logical channel conditions according to various 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 advanced LTE (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 the Institute of Electrical and Electronics Engineers (IEEE) 802.11 (Wi-Fi), IEEE 802.16 (WiMAX), IEEE 802.20. The wireless communication system 100 may support radio access technologies other than 5G. 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).

[0031] One or more network entities 102 may be dispersed throughout a geographic area to form a wireless communication system 100. One or more of the network entities 102 described herein may be or include or may 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 terms. 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.

[0032] The network entity 102 may provide a geographic coverage area 112 for which the network entity 102 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 UE 104 may support wireless communications of signals associated with 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, for example, 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.

[0033] 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, a wireless device, a remote device, a remote unit, a handheld device, a subscriber device, or some other suitable term. In some implementations, UE 104 may be referred to as a unit, a station, a terminal, or a 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 in the wireless communication system 100. In some other implementations, UE 104 may be mobile in the wireless communication system 100.

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

[0035] 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, V2X deployments, or cellular V2X deployments, the communication link 114 may be referred to as a sidelink. For example, the UE 104 may support wireless communications directly with another UE 104 via a PC5 interface.

[0036] The network entity 102 may support communication with the core network 106 or with another network entity 102 or both. For example, the network entity 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 access network entities, which may be examples of access node controllers (ANCs). 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 transport reception points (TRPs)).

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

[0038] The RU may also be referred to as a radio head, a smart radio head, a remote radio head (RRH), a remote radio unit (RRU), or a transmission reception point (TRP). In a decomposed 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 at distributed locations (e.g., separate physical locations). In some implementations, one or more network entities 102 of the decomposed RAN architecture may be implemented as virtual units (e.g., virtual CU (VCU), virtual DU (VDU), virtual RU (VRU)).

[0039] The functional split between CU, DU, and RU can be flexible, and different functions can be supported according to 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 a protocol stack can be adopted between a CU and a DU, so 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., PHY layer) or L2 (e.g., Radio Link Control (RLC) layer, MAC layer) functions and signaling, and each can be at least partially controlled by the CU.

[0040] 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, the DU, or the RU, while other functions of the protocol layer are performed by a different one of the CU, the DU, or the RU).

[0041] The CU may be further functionally split into CU control plane (CU-CP) and CU user plane (CU-UP) functions. The CU may be connected to one or more DUs via a medium-range communication link (e.g., F1, F1-c, F1-u), and the DU may 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 may be implemented according to interfaces (e.g., channels) between layers of a protocol stack supported by a corresponding network entity 102 communicating via such a communication link.

[0042] The core network 106 may support user authentication, access authorization, tracking, connection, 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 entity may manage non-access stratum (NAS) functions, such as mobility, authentication, and bearer management (e.g., data bearer, signal bearer, etc.) of one or more UEs 104 served by one or more network entities 102 associated with the core network 106.

[0043] The core network 106 may 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 may include an application server 118. In some implementations, one or more UEs 104 may communicate with the application server 118. The UE 104 may establish a session (e.g., a PDU session, etc.) with the core network 106 via the network entity 102. The core network 106 may 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 may 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).

[0044] 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 communication). 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.

[0045] 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., 15kHz) and a normal cyclic prefix. A first digital technology (e.g., μ = 0) associated with a first subcarrier spacing (e.g., 15kHz) may utilize one slot per subframe. A second digital technology (e.g., μ = 1) may be associated with a second subcarrier spacing (e.g., 30kHz) and a normal cyclic prefix. A third digital technology (e.g., μ = 2) may be associated with a third subcarrier spacing (e.g., 60kHz) 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., 120kHz) and a normal cyclic prefix. A fifth digital technology (e.g., μ = 4) may be associated with a fifth subcarrier spacing (e.g., 240kHz) and a normal cyclic prefix.

[0046] The time intervals of resources (e.g., communication resources) can be organized according to frames (also referred to as 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.

[0047] Additionally or alternatively, the time intervals of resources (e.g., communication resources) can be organized according to time slots. For example, a subframe may include a certain number (e.g., quantity) of time slots. Each time slot may include a certain number (e.g., quantity) of symbols (e.g., orthogonal frequency division multiplexing (OFDM) symbols). In some implementations, the number (e.g., quantity) of time slots of a subframe may depend on the digital technology. For a normal cyclic prefix, a time slot may include 14 symbols. For an extended cyclic prefix (e.g., applicable to a 60kHz subcarrier spacing), a time slot may include 12 symbols. For a normal cyclic prefix and an extended cyclic prefix, the relationship between the number of symbols per time slot, the number of time slots per subframe, and the number of time 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., 15kHz) may be used interchangeably between subframes and time slots.

[0048] 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 frequency range names 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 and other equipment or devices for cellular communication services (e.g., control information, data). In some implementations, FR2 can be used by the network entity 102 and the UE 104 and other equipment or devices for short-range, high data rate capabilities.

[0049] 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; 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 2 digital technologies). For example, FR2 may be associated with a third digital technology (e.g., μ=2) including a subcarrier spacing of 60 kHz; a fourth digital technology (e.g., μ=3) including a subcarrier spacing of 120 kHz.

[0050] In accordance with the implementation of channel configuration based on logical channel conditions, network entity 102 generates a prioritization notification 120 and sends the prioritization notification 120 to UE 104(1). For example, prioritization notification 120 includes various parameters for mapping data to sidelink resources used by UE 104(1), such as for configuring a PSSCH allocation used by UE 104(1). For example, prioritization notification 120 includes different logical channel conditions for performing LCP, such as based on different data priorities and / or data types. Examples of different logical channel conditions are described throughout this disclosure.

[0051] Thus, based at least in part on the prioritization notification 120, the UE 104(1) performs a prioritization process 122 to map data to wireless resources, such as a subset of different PSSCH allocations for sidelink transmissions, as part of COT sharing. For example, as described in detail herein, after the CCA process, the prioritization process 122 maps high priority data to subsequent PSSCH allocations that occur after the initial PSSCH allocation. In addition, the mapping of high priority data to subsequent PSSCH allocations may depend on certain logical channel conditions, examples of which are provided throughout the present disclosure. Based at least in part on the prioritization process 122, the UE 104(1) performs a data transmission 124 of the mapped data using the PSSCH allocation determined by the prioritization process 122. For example, the data transmission 124 utilizes a PSSCH allocation obtained as part of COT sharing with a different UE 104 (such as with UE 104(2) and / or other UEs 104).

[0052] In some wireless communication systems, a device (e.g., UE, network node (e.g., gNB), etc.) may operate in an unlicensed spectrum and may perform CCA (e.g., via LBT and / or channel sensing) before being able to transmit in the unlicensed spectrum. If the device performing the CCA does not detect the presence of other signals in the channel, the channel may be considered available for transmission. In a frame-based device (FBE) operating mode, the device may perform CCA during idle periods, and when the channel is acquired, the device may communicate during non-idle time of a fixed frame period duration, referred to as COT). In some current specifications and / or regulations, the idle time is no shorter than the maximum of 5% of the fixed frame period (FFP) and 100 microseconds.

[0053] Additionally, the determination of ownership of the COT for UL transmissions at both the gNB and the UE (e.g., which device has initiated the COT) is used to determine:

[0054] 1) Whether another UE can send another UL transmission within the COT.

[0055] 2) Which idle periods (gNB's or UE's) should be observed (e.g., no UL transmissions are allowed during the observed idle periods).

[0056] 3) Energy Detection (ED) threshold (which can be different, e.g. in case of gNB-shared UE-COT or UE-initiated COT, or if the ED threshold is determined based on UE transmit power and / or gNB transmit power)

[0057] Furthermore, in some wireless communication systems, for the case where a sidelink is operated on a cell configured with a shared spectrum, corresponding UE actions upon detecting a CCA failure for a sidelink transmission are not defined.

[0058] Figure 2 200 different COTs and idle periods between the COTs are illustrated. In addition, a FFP 202 including a specific COT and an idle period is illustrated.

[0059] The UE may perform channel sensing, and if the UE senses that the channel is idle, the UE may access the channel. UE initiated channel occupation (CO) is particularly useful in low latency applications where UL data is allowed to be sent in the configured granted resources to initiate CO.

[0060] A single downlink control information (DCI) can schedule several TBs, called multi-PUSCH transmission. According to Technical Specification (TS) 38.214 V16.5.0:

[0061] If the pusch-TimeDomainAllocationListForMultiPUSCH in pusch-Config contains a row indicating resource allocations for two to eight consecutive PUSCHs, K2 indicates the time slot in which the UE should send the first PUSCH of multiple PUSCHs. Each PUSCH has a separate start and length indicator value (SLIV) and mapping type. The number of scheduled PUSCHs is signaled by the number of valid SLIVs indicated in the row of pusch-TimeDomainAllocationListForMultiPUSCH signaled in DCI format 0_1.

[0062] For the COT initiator determination of Configuration Grant (CG) transmission, it has been specified that:

[0063] When the configured UL transmission starts after the UE FFP boundary and is

[0064] Before the idle period of the associated UE FFP ends:

[0065] If the UE has initiated UE FFP, the UE assumes that the configured UL transmission corresponds to the UE initiating COT

[0066] Otherwise, if before the idle period of the gNB FFP, the transmission was confined to the gNB FFP and if the UE has determined that the gNB has initiated the gNB FFF, the UE may assume that the configured UL transmission corresponds to a gNB-initiated COT.

[0067] Figure 3 An implementation 300 is illustrated in which different COT initiators are used for different PUSCH transmissions and / or repetitions. In implementation 300, u-FFP refers to UE-FFP (FFP associated with and / or configured for UE-initiated COT), g-FFP refers to gNB-FFP (FFP associated with or configured for gNB-initiated COT), PUSCH-g refers to PUSCH transmissions sent based on the gNB being the COT initiator, and PUSCH-u refers to PUSCH transmissions sent based on the UE being the COT initiator.

[0068] Additionally, at 300, the DCI schedules PUSCH-g and PUSCH-u. The gNB has already initiated COT in G-FFP1 (e.g., to serve other UEs or schedule UEs). The UE has not yet initiated COT in U-FFP1. PUSCH-g is not aligned with the u-FFP boundary and is transmitted based on the gNB being the COT initiator. PUSCH-u may be transmitted during g-IDLE (if the COT initiator indicating PUSCH-u is the UE) because the gNB does not have any other data to initiate g-COT in G-FFP2. Additionally, g-IDLE may be longer than u-IDLE, and / or the overlap with g-IDLE and PUSCH-u may also be longer than the overlap of PUSCH-g and u-IDLE. LBT / gap may be implemented between PUSCH-g and PUSCH-u of the UE, for example, where the PUSCH-g end and / or PUSCH-g symbols overlapping with u-IDLE are treated as invalid symbols before u-IDLE.

[0069] Figure 4An implementation 400 is illustrated in which the UE initiates a COT. For example, at 400, UE1 has initiated a COT due to a first CG-PUSCH transmission, e.g., when the CG-PUSCH is aligned with the U-FFP1 boundary. The gNB knows that a second CG-PUSCH is coming and wishes to schedule an UL transmission immediately after the second CG-PUSCH. The second CG-PUSCH is sent in accordance with the UE-COT (e.g., in the case of a CG transmission, based on an agreed-upon UE behavior for determining the initiator of the COT), and sending PUSCH-u in accordance with the UE-COT can avoid LBT before the PUSCH-u transmission; whereas if PUSCH-u is PUSCH-g, LBT may be required because it will be sent assuming g-COT. In addition, the gNB wishes to schedule a PUSCH for UE2. To enable the gNB to do this, UE1's PUSCH-g will be sent assuming g-COT. LBT / gap may be required between UE1's PUSCH-u and PUSCH-g.

[0070] The channel assessment procedure based on semi-static channel occupancy described in TS 37.213 is applicable to environments where no other techniques can be assumed, such as according to regulatory levels, private venue policies, etc. If the gNB provides the higher layer parameter ChannelAccessMode-r16 = 'semistatic' to the UE(s) via System Information Block (SIB) 1 or dedicated configuration, the gNB may x Initiate periodic channel occupation, from i·T x x·T x The even-indexed radio frame starts at , and the maximum channel occupancy time T y =0.95T x , where T x =period T x =Periodin ms, which is a high-level parameter provided in SemiStaticChannelAccessConfig,

[0071] In the procedures of this section, when the gNB or UE performs sensing for assessing channel availability, the sensing may be performed for at least the sensing slot duration T sl = 9us. Clauses 4.1.5 and 4.2.3 describe the corresponding X for sensing performed by the gNB or UE, respectively. Thresh adjust.

[0072] Channel occupation initiated by the gNB and shared with (multiple) UEs is to meet the following requirements:

[0073] - After the channel is sensed to be idle for at least the sensing time slot duration T sl = 9us later, the gNB will immediately send a downlink (DL) transmission burst from the start of the channel occupancy time. If the channel is sensed as busy, the gNB does not perform any transmission during the current period.

[0074] - If the gap between the DL transmission burst(s) and any previous transmission burst is greater than 16us, then sl =9us later, the gNB may immediately send (multiple) DL transmission bursts within the channel occupancy time.

[0075] - If the gap between DL transmission burst and UL transmission burst is at most 16us, the gNB can send (multiple) DL transmission burst after (multiple) UL transmission burst within the channel occupancy time without sensing the channel.

[0076] - The UE may send a signal after detecting (multiple DL transmission bursts) during the channel occupancy period

[0077] Send (multiple) UL transmission bursts as follows:

[0078] - If the gap between the UL transmission burst and the DL transmission burst is at most 16 us, the UE can send (multiple) UL transmission bursts after (multiple) DL transmission bursts within the channel occupancy time without sensing the channel.

[0079] - If the gap between the UL transmission burst and the DL transmission burst is greater than 16us, then within the 25us interval ending immediately before the transmission, the channel is sensed to be idle for at least the sensing time slot duration T sl =9us later, the UE may send (multiple) UL transmission bursts after (multiple) DL transmission bursts within the channel occupancy time.

[0080] - Before the next period starts, the gNB and UE will be z =max(0.05T x , no transmission is sent in a set of consecutive symbols within a duration of 100us).

[0081] If the UE fails to access the channel(s) before the expected UL transmission to the gNB, Layer 1 informs higher layers of the channel access failure.

[0082] In order to improve the challenges existing in the configuration of wireless channels in some wireless communication systems, the present disclosure details a channel configuration solution based on logical channel conditions. In the following discussion, the terms eNB and / or gNB are used to refer to base stations, but they can be replaced with any other radio access nodes, such as base stations (BS), eNBs, gNBs, access points (APs), NRDU / CUs, relays, etc. In addition, the implementation is mainly described in the context of 5G NR. However, the described implementation is also applicable to other mobile communication systems that support the configuration of service cells and carriers in unlicensed spectrum, such as LTE mobile wireless and / or cellular telecommunication systems. It should be noted that throughout the document, the term "multiple PSSCH transmission" may refer to a situation in which a device has one or more SL grants, each SL grant scheduling one or more SL resources, allocations, and / or transmissions, resulting in SL transmissions in at least two SL (e.g., PSSCH and / or physical sidelink control channel (PSCCH)) resources. It should also be noted that one SL resource may include multiple transport blocks and / or PSSCHs, for example, for single-user multiple-input multiple-output (SU-MIMO) transmission. In addition, one SL resource can correspond to one time slot, part of a time slot, or a mini time slot, respectively.

[0083] In the implementations described herein, a use case is considered in which a UE may be implemented to perform a CCA procedure before being allowed to perform a set of multiple (e.g., consecutive) PSSCH and / or PSCCH transmissions. In this scenario, the proposed UE behavior disclosed in various implementations is beneficial.

[0084] According to one or more implementations, channel occupancy is initiated by a first UE and is shared with one or more other UEs for sidelink transmission in the shared spectrum. If the gap between SL transmission bursts of the first UE and the other UEs is greater than a predefined gap duration (e.g., 16us), the one or more other UEs may sense that the channel is idle for at least the predefined sensing slot duration, e.g., within a 25us interval ending immediately before the transmission. sl =9us, send (multiple) SL transmission bursts.

[0085] In at least some implementations, the UE does not map high priority data to the first x PSSCH resources in an LCP process immediately following a CCA (e.g., LBT) process, e.g., the first x PSSCH resources occupied by the channel for which the UE implements the CCA process. Instead, the high priority data may be mapped to (x+1) and / or later resources.

[0086] For example, the UE ensures that the PSFCH group / timing is not delayed when multiplexing high priority data to later PSSCH resources, for example, the PSFCH transmission is not moved to a later time slot. For example, if the PSFCH transmission timing is not affected, the UE is only allowed to delay the multiplexing and / or transmission of high priority data to later PSSCH resources. Otherwise, for example, due to delayed HARQ feedback, the delay of high priority data may be impaired. The restriction / condition of not delaying the PSFCH transmission timing may conform to an implementation that depends on the PSFCH period. For example, for the case where the PSFCH period is 1 (for example, PSFCH resources are configured in each time slot), when high priority data is sent on a later PSSCH resource, the condition of not delaying the PSFCH timing may not be met. Therefore, it should be understood that the standard may only apply to certain configurations, for example, the standard only applies to specific PSFCH configurations.

[0087] Figure 5 An implementation 500 that supports channel configuration based on logical channel conditions in accordance with various aspects of the present disclosure is illustrated. For example, implementation 500 depicts PSFCH timing and resource handling (e.g., carrying HARQ feedback) for different PSSCH and PSCCH transmissions. As shown, each PSSCH / PSCCH is associated with a PSFCH resource. According to various implementations of channel configuration based on logical channel conditions, it is ensured that PSFCH timing is not delayed and / or changed when high priority data is multiplexed on a later PSSCH (e.g., not on the first PSSCH after CCA).

[0088] In one example, the UE considers the logical channel priority of a logical channel (LCH) to be lower than the configured threshold for the first x PSSCH / PSCCH resources in the LCP process immediately following the CCA. Therefore, an implementation may provide LCH channel conditions (e.g., rules) for the first x PSSCH / PSCCH resources. In at least some implementations, for the remaining PSSCH resources in the set of multiple PSSCH resources (e.g., x+1 PSSCHs and subsequent PSSCH resources), the UE may use traditional LCH restriction rules, e.g., considering all LCHs regardless of their associated priorities.

[0089] In implementation 500 , a physical resource block (PRB) set 502 is used to generate HARQ feedback from PSSCH 2 , and a PRB set 504 is used to generate HARQ feedback for PSSCH 6 .

[0090] Figure 6An implementation 600 supporting channel configuration based on logical channel conditions in accordance with aspects of the present disclosure is illustrated. Implementation 600 includes an example implementation of PRB sets 502, 504. As shown, PRB sets 502, 504 each include 5 PRBs, with 2 cyclic pairs per PRB.

[0091] In at least some implementations, if a UE is authorized and / or has selected two or more contiguous SL resources in time (e.g., whether as a result of multiple individual SL grants, (multiple) multiple PSSCH grants, a CG, or a combination thereof), then for the first of such two SL resources, the UE will undergo CCA, while for the second SL resource, if the transmission in the previous first SL resource is allowed and performed based on the CCA, no additional LBT may be required.

[0092] In at least some scenarios of multiple PSSCH allocations, the first SL allocation has the highest probability of LBT failure. In a specific implementation of this embodiment, x is equal to 1, for example, the UE does not map the high priority data to the first SL resource and / or PSSCH allocation immediately after the CCA process, but instead maps the high priority data to the second SL resource and / or PSSCH allocation after the CCA process. Therefore, the UE can use a different LCH restriction configuration for the first PSSCH resource when generating a TB compared to the LCP process performed on the second PSSCH resource.

[0093] According to at least one implementation, the UE:

[0094] During the LCP procedure after the CCA / LBT procedure, when the first x TBs are mapped to the first x SL resources / PSSCH allocations, the first LCH condition configuration is used to generate the TB / LCP procedure, and

[0095] During the LCP process after the CCA / LBT process, when the TB is not mapped to the first x SL resources / PSSCH allocations, a second LCH condition configuration is used to generate the TB / LCP process, i.e., mapped to x+1 and subsequent SL resources / PSSCH allocations.

[0096] According to at least one implementation, the UE does not multiplex (multiple) MAC CEs to the first x SL resource allocations immediately after the CCA procedure. Alternatively, for the case where the UE does not perform high priority data mapping, the UE may be allowed to multiplex (multiple) low priority MAC CEs, such as MAC CEs for recommended bit rate queries and MAC CEs for buffer status reports (BSRs), included for filling into the first x SL allocations.

[0097] According to at least one implementation, the UE is only allowed to multiplex high priority data (e.g., MAC CE) to later subsequent SL resources (e.g., not the first 'x' PSSCH resources immediately after CCA) in a set of multiple SL resources if the associated acknowledgement / negative acknowledgement (ACK / NACK) timing on the physical uplink control channel (PUCCH) is not affected by delayed / postponed transmission of high priority data and / or (multiple) MAC CEs. For example, even if the PSFCH transmission associated with the high priority data may be delayed, the UE should still have sufficient processing time to generate the corresponding ACK / NACK and send it to the gNB on the PUCCH.

[0098] According to at least one implementation, the UE does not map high priority data to the first x PSSCH resources in the LCP process immediately following the CCA process, such as the case where the first x PSSCH resources occupied by the channel on which the UE undergoes the CCA process. Instead, the high priority data may be mapped to (x+1) and / or later SL resources. Certain criteria may be used to define whether a subsequent / later PSSCH / PSCCH is eligible to carry high priority data, for example, whether the UE is allowed to delay mapping / transmission of high priority data to a specific PSSCH / PSCCH time slot. According to at least one implementation, if the MCS used for a later PSSCH / PSCCH time slot is y levels higher than the MCS used by the UE for the first PSSCH time slot immediately after the CCA process, the UE does not multiplex the high priority data into a later PSSCH time slot. In one example, y is a predefined threshold.

[0099] Figure 7 An example of a time slot 700 that supports channel configuration based on logical channel conditions in accordance with various aspects of the present disclosure is illustrated. In this particular example, the time slot 700 includes 14 sidelink symbols allocated for different purposes, including automatic gain control (AGC), PSSCH, PSCCH, demodulation reference signal (DMRS), protection symbols, and PSFCH. In at least some implementations where high priority data is delayed, certain adjustments may be made. For example, considering that in time slot 700, high priority data is delayed from PSSCH so that the data is consistent with PSFCH. In such a scenario, the MCS may be modified (e.g., as described above) to account for fewer symbols / PRBs used for PSSCH transmission.

[0100] In at least some implementations, the UE does not map high priority data to the first x PSSCH resources during the LCP process immediately following the CCA process, but is mapped to later, for example, x+1 PSSCHs in a scenario where the PSSCH / PSCCH resources do not contain PSFCH. According to at least one implementation, the UE does not multiplex high priority data to a later PSSCH time slot containing PSFCH. In addition, in at least some implementations, the UE may only map high priority data to a later PSSCH / PSCCH time slot that does not contain PSFCH. Since the PSSCH time slot containing PSFCH has fewer PSSCH symbols, the reliability of the TB containing high priority data may be affected because the MCS can be higher than that of a time slot without PSFCH. The restriction / condition of not multiplexing high priority data to a PSSCH time slot containing PSFCH may conform to an implementation that depends on the PSFCH period. For example, for a case where the PSFCH period is 1 (e.g., PSFCH resources are configured in each time slot), such a condition may not be met. Therefore, it should be understood that the criterion may only apply to certain configurations, for example, the criterion only applies to specific PSFCH configurations.

[0101] In at least some implementations, the UE does not map high priority data to the first x PSSCH resources during the LCP process immediately following the CCA process, but instead maps to later (e.g., x+1) PSSCH resources in a scenario where the PSSCH / PSCCH resources do not contain a sidelink positioning reference symbol (SL-PRS). According to at least one implementation, the UE is not allowed to multiplex high priority data to PSSCH resources (e.g., later resources) consisting of SL-PRS. For example, the UE is only allowed to move and / or multiplex high priority data (e.g., (multiple) MAC CEs) to later PSSCH / PSCCH time slots that do not contain SL-PRS.

[0102] In at least some implementations, the UE is not allowed to delay multiplexing / transmission of high priority data (e.g., (multiple) MAC CEs) beyond a configured maximum delay. For example, certain criteria are provided that define whether a subsequent PSSCH / PSCCH is eligible to carry high priority data, for example, whether the UE is allowed to delay mapping and / or transmission of high priority data to that PSSCH / PSCCH time slot. In at least one example, the UE does not multiplex high priority data to a subsequent PSSCH time slot that is n time slots and / or t ms later than the first PSSCH / PSCCH time slot immediately after a CCA process. In one example, n and / or t correspond to respective predefined thresholds. In another or alternative example, the UE multiplexes high priority data only to a later time slot that still meets the delay constraints (e.g., packet delay budget (PDB)) of the data, for example for mode 2.

[0103] In at least some implementations, the UE is not allowed to delay the multiplexing and / or transmission of high priority data (e.g., (multiple) MAC CEs) to PSSCH resources that are not within the DRX activation time of the corresponding receiving UE. For example, a criterion for defining whether a subsequent PSSCH / PSCCH is eligible to carry high priority data can be provided, for example, whether the UE is allowed to delay the mapping and / or transmission of high priority data to a PSSCH / PSCCH time slot. In at least one example, the UE is only allowed to multiplex high priority data to a later PSSCH time slot that is within the DRX activity time of a selected destination (e.g., a receiving UE destination).

[0104] In at least some implementations, if the UE knows that at least one SL resource and / or PSSCH allocation is available for transmission immediately after the first such SL resource, the UE will not map high priority data to the first PSSCH allocation immediately after the CCA procedure. For example, consider that the UE has SL grants for two SL transmissions in resource r1 and resource r2, and the UE will undergo a CCA procedure before transmitting in resource r1. In addition, in the case where another LBT is successful so that the UE can transmit in resource r1, and in the case where resource r2 is not immediately after resource r1. The UE may apply traditional LCH mapping / restriction behavior during the LCP process. However, if resource r2 is immediately after resource r1, or has a gap of up to a first predefined gap duration, which is short enough that a new CCA procedure does not need to be performed for transmission in resource r2, then in at least some implementations, the UE may not map high priority data for transmission in resource r1. For example, in such a scenario, the UE may autonomously decide whether to apply the described mapping behavior, for example, whether to map higher priority data to a TB, based on its knowledge of whether CCA is required for transmission in resource r2 due to the gap.

[0105] In at least some implementations, if the UE has lower priority data (and / or other SL transmissions) to send in the first PSSCH allocation, the UE does not map high priority data to the first PSSCH allocation immediately after the CCA process. In one example, the UE is allowed to move and / or multiplex high priority data to later PSSCH resources only if the first p PSSCH transmissions of the first x PSSCH resources and / or the TB does not contain padding.

[0106] In at least some implementations, the UE does not map high priority data to the first PSSCH allocation immediately after the CCA procedure if the first PSSCH allocation consists of a number of symbols less than a threshold. In one example, the threshold is signaled via higher layers and / or the physical layer, and / or depends on UE processing, such as processing capability 1 or 2 defined in TS 38.214.

[0107] In at least some implementations, the UE does not map high priority data to the first PSSCH allocation immediately after the CCA procedure if the first PSSCH allocation consists of a number of symbols greater than a threshold. In one example, the threshold is large enough to accommodate multiple non-overlapping CCAs, or large enough to perform at least two CCAs so that their CCA failure events can be assumed to be independent with high probability.

[0108] In at least some implementations, the UE is configured to allow different LCP restriction configurations to be applied to SL transmissions immediately after the CCA process (e.g., mapping of high priority data of (multiple) LCHs and / or (multiple) MAC CEs to PSSCH resources). Such configuration may be performed through higher layer signaling (such as RRC signaling). In at least one example, the UE may be allowed to move and / or multiplex high priority data to later PSSCH resources only for specific propagation types. For example, the UE may be allowed to multiplex high priority data on later PSSCH resources only for unicast services.

[0109] In at least some implementations, the UE is only allowed to move and / or multiplex high priority data (e.g., (multiple) MAC CEs) to a later PSSCH resource that has the same DMRS configuration that the UE would use for the original PSSCH / PSCCH slot, e.g., the first SL resource immediately after the CCA procedure. For example, the UE uses the same DMRS configuration for high priority data in a later PSSCH / PSCCH slot that the UE would use for the original PSSCH / PSCCH slot, e.g., the first SL resource immediately after the CCA procedure.

[0110] The various implementations described herein may be applicable to scenarios where the UE has multiple (e.g., consecutive) SL resources, and has generated a TB for transmission on a PSSCH resource (e.g., the first PSSCH resource among multiple PSSCH resources), and CCA fails in the corresponding transmission attempt. In such a scenario, the UE may move the already generated TB to a HARQ process associated with a subsequent PSSCH resource that satisfies the above conditions. Examples of this condition include: the PSSCH resource does not contain a PSFCH and / or the PSSCH is selected so that the PSFCH timing is not delayed. Based on such conditions, the UE may perform a transmission attempt on a later PSSCH resource. This can ensure that high priority data is not delayed due to a CCA failure, such as a CCA failure that may occur when high priority data is multiplexed on the first x PSSCH resources among multiple PSSCH resources.

[0111] In at least some implementations, for scenarios where SL transmission is not performed due to LBT failure, the UE can trigger selection of new SL resources (e.g., new selection and / or reselection). For example, in at least one implementation, a UE configured for autonomous resource allocation mode (e.g., mode 2) selects new SL resources for transmission of a TB in response to receiving an LBT failure indication from the PHY layer for a transmission attempt for a TB and / or PSSCH. For example, the LBT failure event represents a new trigger for SL resource (re)selection. For example, in contrast to the operation of the NR Uu interface on unlicensed spectrum, the UE is allowed to retransmit pending TBs in the HARQ buffer immediately (e.g., in the next time slot without delay). For example, a timer (e.g., a CG retransmission timer (CGRT) timer) is not applied, which defines when the UE is allowed to autonomously retransmit a TB in a pending HARQ process. In at least one example, the UE has selected SL resources for the initial transmission of the TB, and two HARQ retransmissions are used, such as blind HARQ retransmissions.

[0112] For example, in a scenario where an initial transmission cannot be performed due to LBT failure, the UE can autonomously select additional SL resources for autonomous retransmission of the initial transmission. For example, the UE selects SL resources that occur before the original first HARQ retransmission. Even if the initial transmission of the TB is postponed due to LBT failure, the UE can ensure that the PDB is still satisfied. In at least some implementations, the UE only selects SL resources that meet certain criteria described in the above implementations for autonomous retransmission, for example, the selected PSSCH resources will not contain PSFCH or SL-PRS.

[0113] In at least some implementations, in the event of a LBT failure for a HARQ (re)transmission, the UE is allowed to make additional transmission attempts, e.g., to support autonomous retransmissions for the HARQ (re)transmission. For example, the UE does not need to consider the minimum time gap between the SL resources selected for the original transmission attempt for the TB and the additional SL resources triggered by the LBT failure. In at least one example, the UE selects the additional SL resources such that, from a processing delay perspective, the receiving UE can still send the PSFCH if the PSFCH is configured for the resource pool.

[0114] In at least some implementations, if the PDB associated with the TB is still satisfied, the UE is allowed to exceed the allowed number of HARQ transmissions (e.g., such as configured by RRC, such as sl-MaxTxTransNumPSSCH) in a scenario where HARQ transmissions cannot be performed due to LBT failure. For example, the parameter sl-MaxTxTransNumPSSCH allocates the maximum number of HARQ transmissions that the UE is allowed to perform, rather than the maximum number of HARQ transmission attempts and / or transmission opportunities.

[0115] Figure 8 An example of a block diagram 800 of a device 802 (e.g., an apparatus) supporting channel configuration based on logical channel conditions in accordance with aspects of the present disclosure is illustrated. The device 802 may be an example of a UE 104 as described herein. The device 802 may support wireless communications with one or more network entities 102, UEs 104, or any combination thereof. The device 802 may include components for bidirectional communications, including components for sending and receiving communications (such as a processor 804, a memory 806, a transceiver 808, and an I / O controller 810). 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).

[0116] The processor 804, the memory 806, the transceiver 808, 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 804, the memory 806, the transceiver 808, or various combinations thereof or components thereof may support methods for performing one or more of the operations described herein.

[0117] In some implementations, the processor 804, the memory 806, the transceiver 808, or various combinations or components thereof may be implemented in hardware (e.g., in a communication 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 thereof, which is configured to or otherwise supports components for performing the functions described in the present disclosure. In some implementations, the processor 804 and the memory 806 coupled to the processor 804 may be configured to perform one or more functions described herein (e.g., by executing instructions stored in the memory 806 by the processor 804). For example, in the context of the UE 104, the transceiver 808 and the processor 804 coupled to the transceiver 808 are configured to cause the UE 104 to perform various described operations and / or combinations thereof.

[0118] For example, according to examples disclosed herein, the processor 804 and / or the transceiver 808 may support wireless communications at the device 802. For example, the processor 804 and / or the transceiver 808 may be configured to or otherwise support a component for: for a PSSCH allocation set, based at least in part on a first logical channel condition associated with a logical channel prioritization, generating a first set of MAC PDUs for a first subset of PSSCH allocations in the PSSCH allocation set; and for the PSSCH allocation set, based at least in part on a second logical channel condition associated with the logical channel prioritization, generating a second set of MAC PDUs for a second subset of PSSCH allocations in the PSSCH allocation set.

[0119] In addition, in some implementations, the processor 804 and / or the transceiver 808 can be configured to or otherwise support a component for determining a PSSCH allocation set based on at least one predefined criterion; wherein at least one predefined criterion includes: a second subset of the PSSCH allocation does not include a PSFCH; wherein at least one predefined criterion includes: a second subset of the PSSCH allocation does not include a sidelink PRS; wherein the first subset of the PSSCH allocation starts from the first PSSCH allocation in the PSSCH allocation set; a listen-before-talk process is performed before the first subset of the PSSCH allocation; as part of logical channel prioritization, high priority data is prevented from being mapped to the first subset of the PSSCH allocation; wherein the first logical channel condition is different from the second logical channel condition; wherein the PSSCH allocation set includes consecutive PSSCH allocations.

[0120] In addition, in some implementations, the first logical channel condition includes: data with a priority lower than a threshold is mapped to a first subset of the PSSCH allocation; wherein the first logical channel condition includes: data with a priority higher than a threshold is not mapped to the first subset of the PSSCH allocation; wherein the second logical channel condition includes: an indication that data with a priority higher than a threshold is mapped to a second subset of the PSSCH allocation; wherein the second logical channel condition includes: when data with a priority higher than a threshold is mapped to PSSCH resources of the second subset of the PSSCH allocation, one or more of the following items: the PSSCH resources do not include PSFCH; the PSFCH timing is not delayed; the PSSCH resources do not include a sidelink PRS; the PSSCH resources are within the DRX time of the destination UE; or the MCS to be used for transmission on the PSSCH resources is not a specified level higher than the MCS previously selected for the PSSCH resources; support for a component for sending data through one or more of the first group of MAC PDUs or the second group of MAC PDUs; support for a component for sending data through one or more of the first subset of the PSSCH allocation or the second subset of the PSSCH allocation.

[0121] In another example, according to examples disclosed herein, the processor 804 and / or the transceiver 808 can support wireless communications at the device 802. For example, the processor 804 and / or the transceiver 808 can be configured to or otherwise support a component for: performing a listen-before-talk procedure on a first sidelink resource to be used for a sidelink transmission; autonomously selecting, by the UE at least in part based on a failure of the listen-before-talk procedure, a second sidelink resource to be used for the sidelink transmission; and sending the sidelink transmission using the second sidelink resource.

[0122] In addition, in some implementations, the processor 804 and / or the transceiver 808 may be configured to or otherwise support a component for: receiving an indication of a failure of a listen-before-talk process from the PHY layer; wherein the second sidelink resource includes a next time slot after the first sidelink resource; selecting the second sidelink resource as the sidelink resource so that one or more of the following items: the second sidelink resource does not include a PSFCH: the PSFCH timing is not delayed due to the selection of the second sidelink resource; the second sidelink resource does not include a sidelink PRS; the second sidelink resource is within the DRX time of the destination UE; or the MCS to be used for transmission on the second sidelink resource is not a specified level higher than the MCS previously selected for the first sidelink resource; wherein the sidelink transmission on the first sidelink resource includes: a transport block in a HARQ buffer, and wherein using the second sidelink resource to send the sidelink transmission includes: a HARQ retransmission of the transport block; wherein the UE is configured with a maximum number of HARQ transmissions, and the UE is configured to exceed the maximum number in the event of HARQ retransmissions of the transport block.

[0123] The processor 804 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, a discrete gate or transistor logic component, a discrete hardware component, or any combination thereof). In some implementations, the processor 804 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 804. The processor 804 may be configured to execute computer-readable instructions stored in a memory (e.g., a memory 806) to cause the device 802 to perform various functions of the present disclosure.

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

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

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

[0127] Fig. 9 An example of a block diagram 900 of a device 902 (e.g., an apparatus) supporting channel configuration based on logical channel conditions in accordance with aspects of the present disclosure is illustrated. The device 902 may be an example of a network entity 102 as described herein. The device 902 may support wireless communications with one or more network entities 102, UEs 104, or any combination thereof. The device 902 may include components for bidirectional communications, including components for sending and receiving communications (such as a processor 904, a memory 906, a transceiver 908, and an I / O controller 910). 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).

[0128] The processor 904, the memory 906, the transceiver 908, 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 904, the memory 906, the transceiver 908, or various combinations thereof or components thereof may support methods for performing one or more of the operations described herein.

[0129] In some implementations, the processor 904, memory 906, transceiver 908, or various combinations or components thereof may be implemented in hardware (e.g., in a communication 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 thereof, which is configured to or otherwise supports components for performing the functions described in the present disclosure. In some implementations, the processor 904 and the memory 906 coupled to the processor 904 may be configured to perform one or more functions described herein (e.g., by executing instructions stored in the memory 906 by the processor 904). For example, in the context of the network entity 102, the transceiver 908 and the processor 904 coupled to the transceiver 908 are configured to cause the network entity 102 to perform various described operations and / or combinations thereof.

[0130] For example, according to examples disclosed herein, the processor 904 and / or the transceiver 908 may support wireless communications at the device 902. For example, the processor 904 and / or the transceiver 908 may be configured to or otherwise support a component for: generating a notification that specifies, for a PSSCH allocation set, a first logical channel condition associated with a logical channel priority ranking for a first subset of PSSCH allocations in the PSSCH allocation set; and a second logical channel condition associated with a logical channel priority ranking for a second subset of PSSCH allocations in the PSSCH allocation set; and sending the notification to a UE.

[0131] In addition, in some implementations, the notification specifies that: the first subset of PSSCH allocations will start from the first PSSCH allocation in the PSSCH allocation set; wherein the first logical channel condition is different from the second logical channel condition; wherein the first logical channel condition specifies that: high priority data will not be mapped to the first subset of PSSCH allocations; wherein the second logical channel condition includes: an indication that data above a threshold priority will be mapped to a second subset of PSSCH allocations; wherein the second logical channel condition includes: when data above a threshold priority is mapped to the PSSCH resources of the second subset of PSSCH allocations, one or more of the following items: the PSSCH resources will not include PSFCH; the PSFCH timing will not be delayed; the PSSCH resources will not include a sidelink PRS; the PSSCH resources will be within the DRX time of the destination UE; or the MCS to be used for transmission on the PSSCH resources will not be a specified level higher than the MCS previously selected for the PSSCH resources.

[0132] The processor 904 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, a discrete gate or transistor logic component, a discrete hardware component, or any combination thereof). In some implementations, the processor 904 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 904. The processor 904 may be configured to execute computer-readable instructions stored in a memory (e.g., a memory 906) to cause the device 902 to perform various functions of the present disclosure.

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

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

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

[0136] Fig.10 1 is a flow chart of a method 1000 for supporting channel configuration based on logical channel conditions according to various aspects of the present disclosure. The operations of the method 1000 may be implemented by the apparatus described herein or components thereof. For example, the operations of the method 1000 may be implemented by reference to Figures 1 to 9 The UE 104 described herein may be used to perform the functions described herein. 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 various aspects of the described functions.

[0137] At 1002, the method may include, for a set of PSSCH allocations, generating a first set of MAC PDUs for a first subset of PSSCH allocations in the set of PSSCH allocations based at least in part on a first logical channel condition associated with a logical channel prioritization. The operations of 1002 may be performed according to examples as described herein. In some implementations, aspects of the operations of 1002 may be described with reference to Figure 1 The device is used to perform the above.

[0138] At 1004, the method may include, for the PSSCH allocation set, generating a second set of MAC PDUs for a second subset of PSSCH allocations in the PSSCH allocation set based at least in part on a second logical channel condition associated with the logical channel prioritization. The operations of 1004 may be performed according to examples as described herein. In some implementations, aspects of the operations of 1004 may be described with reference to Figure 1 The device is used to perform the above.

[0139] At 1006, the method may include: sending data via one or more of the first set of MAC PDUs or the second set of MAC PDUs. The operations of 1006 may be performed according to examples as described herein. In some implementations, aspects of the operations of 1006 may be described with reference to Figure 1 The device is used to perform the above.

[0140] Fig.11 1 is a flow chart of a method 1100 for supporting channel configuration based on logical channel conditions according to various aspects of the present disclosure. The operations of the method 1100 may be implemented by the apparatus described herein or components thereof. For example, the operations of the method 1100 may be implemented by reference to Figures 1 to 9 The UE 104 described herein may be used to perform the functions described herein. 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 various aspects of the described functions.

[0141] At 1102, the method may include: performing, by the UE, a listen-before-talk procedure on a first sidelink resource to be used for a sidelink transmission. The operations of 1102 may be performed according to examples as described herein. In some implementations, aspects of the operations of 1102 may be performed by reference to Figure 1 The device is used to perform the above.

[0142] At 1104, the method may include autonomously selecting, by the UE, a second sidelink resource to be used for sidelink transmission based at least in part on the failure of the listen-before-talk procedure. The operations of 1104 may be performed according to examples as described herein. In some implementations, aspects of the operations of 1104 may be described with reference to Figure 1 The device is used to perform the above.

[0143] At 1106, the method may include sending a sidelink transmission using the second sidelink resource. The operations of 1106 may be performed according to examples as described herein. In some implementations, aspects of the operations of 1106 may be described with reference to Figure 1 The device is used to perform the above.

[0144] Fig.12 1 is a flow chart of a method 1200 for supporting channel configuration based on logical channel conditions according to various aspects of the present disclosure. The operations of the method 1200 may be implemented by the apparatus described herein or components thereof. For example, the operations of the method 1200 may be implemented by reference to Figures 1 to 9 The network entity 102 described herein may be used to perform the functions described herein. 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 various aspects of the described functions.

[0145] At 1202, the method may include: generating a notification that specifies, for a PSSCH allocation set, a first logical channel condition associated with a logical channel priority ordering for a first subset of PSSCH allocations in the PSSCH allocation set; and a second logical channel condition associated with a logical channel priority ordering for a second subset of PSSCH allocations in the PSSCH allocation set. The operations of 1202 may be performed according to examples as described herein. In some implementations, aspects of the operations of 1202 may be performed by reference to Figure 1 The device is used to perform the above.

[0146] At 1204, the method may include sending the notification to the UE. The operations of 1204 may be performed according to examples as described herein. In some implementations, aspects of the operations of 1204 may be described by reference to Figure 1 The device is used to perform the above.

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

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

[0149] 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 on or sent via a computer-readable medium as one or more instructions or codes. 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, hard wiring, or any combination of these. Features that implement the functions may also be physically located in various locations, including being distributed so that portions of the functions are implemented in different physical locations.

[0150] Computer-readable media include both non-transient computer storage media and communication media, and communication media include any medium that facilitates the transfer of computer programs from one place to another. Non-transient storage media can be any available medium that can be accessed by a general or special-purpose computer. As an example and not limitation, non-transient computer-readable media can include RAM, ROM, electrically erasable programmable ROM (EEPROM), flash memory, compact disk (CD) ROM or other optical disk storage, disk storage or other magnetic storage devices, or can be used to carry or store desired program code devices in the form of instructions or data structures and can be accessed by a general or special-purpose computer, or any other non-transient medium of a general or special-purpose processor.

[0151] 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 disks as used herein include CDs, laser disks, optical disks, digital versatile disks (DVDs), floppy disks, and blue-ray disks, wherein disks typically reproduce data magnetically, and optical disks reproduce data optically with lasers. Combinations of the above are also included within the scope of computer-readable media.

[0152] 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). In addition, as used herein, the phrase "based on" should not be interpreted as a reference to a closed set of conditions. For example, an example step described as "based on condition A" may be based on both condition A and condition B without departing from the scope of the present 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." In addition, as used herein, including in the claims, a "set" may include one or more elements.

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

[0154] The descriptions described herein in conjunction with the accompanying drawings describe example configurations and do not represent all examples that may be implemented or within the scope of the claims. The term "example" as used herein means "used as an example, instance, or illustration," rather than "preferred" or "better than other examples." The detailed description includes specific details to facilitate understanding of the described techniques. However, these techniques may be practiced without these specific details. In some cases, known structures and devices are shown in block diagram form to avoid confusing the concepts of the described examples.

[0155] 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 clear 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 conform to the widest scope consistent with the principles and novel features disclosed herein.

Claims

1. A device comprising: Transceiver; as well as a processor coupled to the transceiver, the processor and the transceiver being configured to cause the apparatus to: for a set of physical sidelink shared channel (PSSCH) assignments, generating a first set of medium access control (MAC) protocol data units (PDUs) for a first subset of PSSCH assignments in the set of PSSCH assignments based at least in part on a first logical channel condition associated with a logical channel prioritization; as well as For the set of PSSCH allocations, a second set of MAC PDUs is generated for a second subset of PSSCH allocations in the set of PSSCH allocations based at least in part on a second logical channel condition associated with the logical channel prioritization. 2 . The apparatus according to claim 1 , wherein the processor and the transceiver are configured such that the apparatus: determines the PSSCH allocation set based on at least one predefined criterion.

3. The apparatus of claim 2, wherein the at least one predefined criterion comprises: The second subset of the PSSCH allocation does not include a physical sidelink feedback channel (PSFCH).

4. The apparatus of claim 2, wherein the at least one predefined criterion comprises: The second subset of the PSSCH allocation does not include a sidelink positioning reference signal (PRS).

5. The apparatus of claim 1, wherein the first subset of PSSCH allocations starts from a first PSSCH allocation in the set of PSSCH allocations.

6. The apparatus of claim 1, wherein the processor and the transceiver are configured to cause the apparatus to: perform a listen-before-talk procedure prior to the first subset of the PSSCH allocations.

7. The apparatus of claim 6, wherein the processor and the transceiver are configured such that the apparatus: as part of the logical channel prioritization, prevents mapping of high priority data to the first subset of the PSSCH allocation.

8. The apparatus of claim 1, wherein the first logical channel condition is different from the second logical channel condition.

9. The apparatus according to claim 1, wherein the PSSCH allocation set comprises: Continuous PSSCH allocation.

10. An apparatus comprising: Transceiver; as well as a processor coupled to the transceiver, the processor and the transceiver being configured to cause the apparatus to: Generate a notification, for a physical sidelink shared channel (PSSCH) assignment set, the notification specifying: a first logical channel condition associated with logical channel prioritization for a first subset of PSSCH allocations in the set of PSSCH allocations; as well as a second logical channel condition associated with logical channel prioritization for a second subset of PSSCH allocations in the set of PSSCH allocations; as well as The notification is sent to a user equipment (UE).

11. The apparatus of claim 10, wherein the notification specifies that the first subset of PSSCH allocations will start from a first PSSCH allocation in the set of PSSCH allocations.

12. The apparatus of claim 10, wherein the first logical channel condition is different from the second logical channel condition.

13. The apparatus of claim 10, wherein the first logical channel condition specifies that high priority data is not to be mapped to the first subset of the PSSCH allocation.

14. The apparatus according to claim 10, wherein the second logical channel condition comprises: An indication that data above a threshold priority will be mapped to a second subset of the PSSCH allocation.

15. The apparatus according to claim 10, wherein the second logical channel condition comprises: When data with a priority higher than a threshold is mapped to PSSCH resources of the second subset of the PSSCH allocation, one or more of the following: The PSSCH resources shall not include a physical sidelink feedback channel (PSFCH); PSFCH timing will not be delayed; The PSSCH resources shall not include a sidelink positioning reference signal (PRS); The PSSCH resource will be within the discontinuous reception (DRX) time of the destination user equipment (UE); or The modulation and coding scheme (MCS) to be used for transmission on the PSSCH resource shall not be a specified level higher than the MCS previously selected for the PSSCH resource.

16. A user equipment (UE), comprising: Transceiver; as well as a processor coupled to the transceiver, the processor and the transceiver being configured to cause the UE to: performing a listen-before-talk procedure on a first sidelink resource to be used for sidelink transmission; autonomously selecting, by the UE, a second sidelink resource to be used for the sidelink transmission based at least in part on a failure of the listen-before-talk procedure; and The sidelink transmission is sent using the second sidelink resource.

17. The UE of claim 16, wherein the processor and the transceiver are configured to cause the UE to: receive an indication of the failure of the listen-before-talk procedure from a physical layer (PHY).

18. The UE according to claim 16, wherein the second sidelink resource comprises: The next time slot after the first sidelink resource.

19. The UE of claim 16, wherein the processor and the transceiver are configured to cause the UE to: select the second sidelink resource as a sidelink resource such that one or more of the following items: The second sidelink resource does not include a physical sidelink feedback channel (PSFCH); PSFCH timing will not be delayed due to the selection of the second sidelink resource; The second sidelink resource does not include a sidelink positioning reference signal (PRS); The second sidelink resource is within a discontinuous reception (DRX) time of a sending destination UE; or The modulation and coding scheme (MCS) to be used for transmissions on the second sidelink resource is not a specified level higher than the MCS previously selected for the first sidelink resource.

20. The UE of claim 16, wherein the sidelink transmission on the first sidelink resource comprises: A transport block in a hybrid automatic repeat request (HARQ) buffer, and wherein sending the sidelink transmission using the second sidelink resource comprises: a HARQ retransmission of the transport block.

Images