EP4666506A1

EP4666506A1 - Transmitting content during user equipment (ue) sidelink unlicensed operations

Info

Publication number: EP4666506A1
Application number: EP24706520.4A
Authority: EP
Inventors: Karthikeyan Ganesan; Alexander Johann Maria Golitschek Edler Von Elbwart
Original assignee: Lenovo Singapore Pte Ltd
Current assignee: Lenovo Singapore Pte Ltd
Priority date: 2023-02-16
Filing date: 2024-02-15
Publication date: 2025-12-24
Also published as: GB202511681D0; CN120693824A; WO2024121833A1; GB2641650A

Abstract

Various aspects of the present disclosure relate to UE sidelink unlicensed operations. For example, the systems and methods can identify content for a UE to transmit over a common PRB/interlace, and the UE can utilize the PRB/interlace to transmit least or low priority information, resource conflict information, information to be broadcast, and so on, over the common PRB/interlace.

Description

TRANSMITTING CONTENT DURING USER EQUIPMENT (UE) SIDELINK UNLICENSED OPERATIONS

CROSS REFERENCE TO RELATED APPLICATIONS

[0001] This application claims priority to U.S. Provisional Patent Application No. 63/485,478, filed on February 16, 2023, entitled TRANSMITTING CONTENT DURING USER EQUIPMENT (UE) SIDELINK UNLICENSED OPERATIONS, which is hereby incorporated by reference in its entirety.

TECHNICAL FIELD

[0002] The present disclosure relates to wireless communications, and more specifically to user equipment (UE) performing sidelink unlicensed operations.

BACKGROUND

[0003] A wireless communications system may include one or multiple network communication devices, such as base stations, which may be otherwise known as an eNodeB (eNB), a next-generation NodeB (gNB), or other suitable terminology. Each network communication device, such as a base station, may support wireless communications for one or multiple user communication devices, which may be otherwise known as user equipment (UE), or other suitable terminology. The wireless communications system may support wireless communications with one or multiple user communication devices by utilizing resources of the wireless communication system (e.g., time resources (e.g., symbols, slots, subframes, frames, or the like) or frequency resources (e.g., subcarriers, carriers). Additionally, the wireless communications system may support wireless communications across various radio access technologies including third generation (3G) radio access technology, fourth generation (4G) radio access technology, fifth generation (5G) radio access technology, among other suitable radio access technologies beyond 5G (e.g., sixth generation (6G)).

[0004] In some cases, a UE can communicate with other UEs using sidelink channels, which can include the unlicensed spectrum. To meet certain regulations, such as power- spectral density (PSD) regulations and minimum channel occupancy (e.g., occupied channel bandwidth, or OCB, of 80 percent), LTE-unlicensed and NT-unlicensed developed interlacing methods.

[0005] An interlace can be ten equally spaced resource blocks (RBs) within a certain frequency bandwidth. For example, for a 20 MHz wide LTE channel, corresponding to 100 RBs, there are ten interlaces with a 10 RB/interlace (e.g., Interlace #0 contains resource blocks {0, 10, 20, 30, 40, 50, 60, 70, 80, 90}).

SUMMARY

[0006] The present disclosure relates to methods, apparatuses, and systems that support identifying content for a UE to transmit over a common (physical resource block) PRB/interlace. For example, the UE can utilize the common PRB/interlace to transmit least or low priority information, resource conflict information, information to be broadcast, and so on, over the common PRB/interlace.

[0007] Some implementations of the method and apparatuses described herein may further include a UE, including at least one memory and at least one processor coupled with the at least one memory and configured to cause the UE to receive a first configuration associated with a time or frequency placement common resource, receive a second configuration associated with content to be transmitted, and transmit channel content based on the first configuration and the second configuration.

[0008] In some implementations of the method and apparatuses described herein, the time or frequency placement common resource is part of a resource pool or resource block set (RBset) available to the UE during sidelink unlicensed operation.

[0009] In some implementations of the method and apparatuses described herein, the channel content includes Physical Sidelink Feedback Channel (PSFCH) content to be transmitted via the time or frequency placement common resource indicated by the first configuration. [0010] In some implementations of the method and apparatuses described herein, the PSFCH content includes multiple bits conveying a channel state information (CSI) report.

[0011] In some implementations of the method and apparatuses described herein, the PSFCH content includes multiple bits conveying beam related information.

[0012] In some implementations of the method and apparatuses described herein, the PSFCH content includes multiple bits conveying Resource Conflict information.

[0013] In some implementations of the method and apparatuses described herein, the PSFCH content includes multiple bits conveying Channel Occupancy Time (COT) information.

[0014] In some implementations of the method and apparatuses described herein, channel content includes low priority information and does not include Hybrid Automatic Repeat Request Acknowledgment (HARQ-ACK) information.

[0015] In some implementations of the method and apparatuses described herein, the received first configuration includes a dedicated frequency cyclic shift via which the UE transmits content via the time or frequency placement common resource.

[0016] In some implementations of the method and apparatuses described herein, the received first configuration includes information indicating placement of Physical Resource Blocks (PRBs) with each interlace of the time or frequency placement common resource.

[0017] In some implementations of the method and apparatuses described herein, the received first configuration includes information indicating placement of PRBs for a common interlace at both ends of a resource block set (RBset) available to the UE within the time or frequency placement common resource.

[0018] In some implementations of the method and apparatuses described herein, the UE transmits the channel content via a common interlace or one or multiple common PRBs available to the UE within the time or frequency placement common resource.

[0019] Some implementations of the method and apparatuses described herein may further include a method performed by a UE the method comprising receiving a first configuration associated with a time or frequency placement common resource, receiving a second configuration associated with content to be transmitted, and transmitting channel content based on the first configuration and the second configuration.

[0020] In some implementations of the method and apparatuses described herein, the time or frequency placement common resource is part of a resource pool or RBset available to the UE during sidelink unlicensed operation.

[0021] In some implementations of the method and apparatuses described herein, the channel content includes PSFCH content to be transmitted via the time or frequency placement common resource indicated by the first configuration.

[0022] In some implementations of the method and apparatuses described herein, the PSFCH content includes multiple bits conveying a CSI report.

[0023] In some implementations of the method and apparatuses described herein, the PSFCH content includes multiple bits conveying beam related information.

[0024] In some implementations of the method and apparatuses described herein, the PSFCH content includes multiple bits conveying Resource Conflict information.

[0025] In some implementations of the method and apparatuses described herein, the PSFCH content includes multiple bits conveying COT information.

[0026] In some implementations of the method and apparatuses described herein, the channel content includes low priority information and does not include HARQ-ACK information.

[0027] In some implementations of the method and apparatuses described herein, the received first configuration includes a dedicated frequency cyclic shift via which the UE transmits content via the time or frequency placement common resource.

[0028] In some implementations of the method and apparatuses described herein, the received first configuration includes information indicating placement of PRBs with each interlace of the time or frequency placement common resource. [0029] In some implementations of the method and apparatuses described herein, the received first configuration includes information indicating placement of PRBs for a common interlace at both ends of a RBset available to the UE within the time or frequency placement common resource.

[0030] In some implementations of the method and apparatuses described herein, the UE transmits the channel content via a common interlace or one or multiple common PRBs available to the UE within the time or frequency placement common resource.

[0031] Some implementations of the method and apparatuses described herein may further include a processor for wireless communication, comprising at least one controller coupled with at least one memory and configured to cause the processor to receive a first configuration associated with a time or frequency placement common resource, receive a second configuration associated with content to be transmitted, and transmit channel content based on the first configuration and the second configuration.

[0032] Some implementations of the method and apparatuses described herein may further include a UE comprising at least one memory and at least one processor coupled with the at least one memory and configured to cause the UE to receive a configuration of a time or frequency placement common resource and transmit channel content based on the configuration.

BRIEF DESCRIPTION OF THE DRAWINGS

[0033] FIG. 1 illustrates an example of a wireless communications system that supports UE sidelink unlicensed operations in accordance with aspects of the present disclosure.

[0034] FIG. 2 illustrates an example of a diagram that supports configuring a common interlace for each RBset in accordance with aspects of the present disclosure.

[0035] FIG. 3 illustrates an example of a block diagram of a device that supports UE sidelink unlicensed operations in accordance with aspects of the present disclosure.

[0036] FIG. 4 illustrates a flowchart of a method that supports transmitting content over a sidelink in accordance with aspects of the present disclosure. DETAILED DESCRIPTION

[0037] Interlacing methods have been defined, in LTE-unlicensed and NR-unlicensed, such as utilizing interlacing over uplink channels (e.g., Physical Uplink Shared Channel (PUSCH) and Physical Uplink Control Channel (PUCCH) at a resource block level (e.g., for physical resource blocks, or PRBs). However, interlacing over the data/feedback channels should also meet the PSD and OCB regulations. Thus, traditional sidelink operations and designs of sub-channels and/or resource pools may be modified to meet the regulations.

[0038] To meet the OCB regulation, a common PRBs/interlace is defined to transmit over a physical sidelink feedback channel (PSFCH). A UE, transmitting over the PSFCH, can be configured (or pre-configured) with a set of common resources and a set of dynamic resources (e.g., by a network entity such as a gNB). However, previous solutions have yet to identify or define what content is to be transmitted over the common PRB/interlace.

[0039] The technology described herein solves these problems by identifying content for a UE to transmit over the common PRB/interlace. For example, the UE can utilize the PRB/interlace to transmit least or low priority information, resource conflict information, information to be broadcast, and so on, over the common PRB/interlace.

[0040] Thus, the UE, by sending certain types of content over the common PRB/interlace, can meet various transmission requirements (e.g., OCB) for a network, among other benefits.

[0041] Aspects of the present disclosure are described in the context of a wireless communications system. Aspects of the present disclosure are further illustrated and described with reference to device diagrams and flowcharts.

[0042] FIG. 1 illustrates an example of a wireless communications system 100 that supports UE performing sidelink unlicensed operations in accordance with aspects of the present disclosure. The wireless communications 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 communications system 100 may support various radio access technologies. In some implementations, the wireless communications system 100 may be a 4G network, such as an LTE network or an LTE- Advanced (LTE-A) network. In some other implementations, the wireless communications system 100 may be a 5 G network, such as an NR network. In other implementations, the wireless communications system 100 may be a combination of a 4G network and a 5G network, or other suitable radio access technology including Institute of Electrical and Electronics Engineers (IEEE) 802.11 (WiFi), IEEE 802.16 (WiMAX), IEEE 802.20. The wireless communications system 100 may support radio access technologies beyond 5G. Additionally, the wireless communications system 100 may support technologies, such as time division multiple access (TDMA), frequency division multiple access (FDMA), or code division multiple access (CDMA), etc.

[0043] The one or more network entities 102 may be dispersed throughout a geographic region to form the wireless communications 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 terminology. A network entity 102 and a UE 104 may communicate via a communication link 110, which may be a wireless or wired connection. For example, a network entity 102 and a UE 104 may perform wireless communication (e.g., receive signaling, transmit signaling) over a Uu interface.

[0044] A network entity 102 may provide a geographic coverage area 112 for which the network entity 102 may support services (e.g., voice, video, packet data, messaging, broadcast, etc.) for one or more UEs 104 within the geographic coverage area 112. For example, a network entity 102 and a UE 104 may support wireless communication of signals related to services (e.g., voice, video, packet data, messaging, broadcast, etc.) according to one or multiple radio access technologies. In some implementations, a network entity 102 may be moveable, 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 the different geographic coverage areas 112 may be associated with different network entities 102. 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.

[0045] The one or more UEs 104 may be dispersed throughout a geographic region of the wireless communications system 100. A 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, or a subscriber device, or some other suitable terminology. In some implementations, the UE 104 may be referred to as a unit, a station, a terminal, or a client, among other examples. Additionally, or alternatively, the UE 104 may be referred to as an Internet-of-Things (loT) device, an Internet-of-Everything (loE) device, or machine-type communication (MTC) device, among other examples. In some implementations, a UE 104 may be stationary in the wireless communications system 100. In some other implementations, a UE 104 may be mobile in the wireless communications system 100.

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

[0047] A UE 104 may also be able to support wireless communication directly with other UEs 104 over a communication link 114. For example, a UE 104 may support wireless communication directly with another UE 104 over a device-to-device (D2D) communication link. In some implementations, such as vehicle-to-vehicle (V2V) deployments, vehicle-to-everything (V2X) deployments, or cellular-V2X deployments, the communication link 114 may be referred to as a sidelink. For example, a UE 104 may support wireless communication directly with another UE 104 over a PC5 interface. [0048] A network entity 102 may support communications with the core network 106, or with another network entity 102, or both. For example, a network entity 102 may interface with the core network 106 through one or more backhaul links 116 (e.g., via an SI, N2, N2, or another network interface). The network entities 102 may communicate with each other over the backhaul links 116 (e.g., via an X2, Xn, or another network interface). In some implementations, the network entities 102 may communicate with each other directly (e.g., between the network entities 102). In some other implementations, the network entities 102 may communicate with each other or indirectly (e.g., via the core network 106). In some implementations, one or more network entities 102 may include subcomponents, such as an access network entity, which may be an example of an access node controller (ANC). An ANC may communicate with the one or more UEs 104 through one or more other access network transmission entities, which may be referred to as a radio heads, smart radio heads, or transmission-reception points (TRPs).

[0049] In some implementations, a network entity 102 may be configured in a disaggregated architecture, which may be configured to utilize a protocol stack physically or logically distributed among 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, a network entity 102 may include one or more of a central unit (CU), a distributed unit (DU), a radio unit (RU), a RAN Intelligent Controller (RIC) (e.g., a NearReal Time RIC (Near-RT RIC), a Non-Real Time RIC (Non-RT RIC)), a Service Management and Orchestration (SMO) system, or any combination thereof.

[0050] An 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). One or more components of the network entities 102 in a disaggregated RAN architecture may be co-located, or one or more components of the network entities 102 may be located in distributed locations (e.g., separate physical locations). In some implementations, one or more network entities 102 of a disaggregated RAN architecture may be implemented as virtual units (e.g., a virtual CU (VCU), a virtual DU (VDU), a virtual RU (VRU)). [0051] Split of functionality between a CU, a DU, and an RU may be flexible and may support different functionalities depending upon which functions (e.g., network layer functions, protocol layer functions, baseband functions, radio frequency functions, and any combinations thereof) are performed at a CU, a DU, or an RU. For example, a functional split of a protocol stack may be employed between a CU and a DU such that the CU may support one or more layers of the protocol stack and the DU may support one or more different layers of the protocol stack. In some implementations, the CU may host upper protocol layer (e.g., a layer 3 (L3), a layer 2 (L2)) functionality and signaling (e.g., Radio Resource Control (RRC), service data adaption protocol (SDAP), Packet Data Convergence Protocol (PDCP)). The CU may be connected to one or more DUsor RUs, and the one or more DUs or RUs may host lower protocol layers, such as a layer 1 (LI) (e.g., physical (PHY) layer) or an L2 (e.g., radio link control (RLC) layer, medium access control (MAC) layer) functionality and signaling, and may each be at least partially controlled by the CU 160.

[0052] Additionally, or alternatively, a functional split of the protocol stack may be employed between a DU and an 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 multiple different cells (e.g., via one or more RUs). In some implementations, a functional split between a CU and a DU, or between a DU and an RU may be within a protocol layer (e.g., some functions for a protocol layer may be performed by one of a CU, a DU, or an RU, while other functions of the protocol layer are performed by a different one of the CU, the DU, or the RU).

[0053] A CU may be functionally split further into CU control plane (CU-CP) and CU user plane (CU-UP) functions. A CU may be connected to one or more DUs via a midhaul communication link (e.g., Fl, Fl-c, Fl-u), and a DU may be connected to one or more RUs via a fronthaul communication link (e.g., open fronthaul (FH) interface). In some implementations, a midhaul communication link or a fronthaul communication link may be implemented in accordance with an interface (e.g., a channel) between layers of a protocol stack supported by respective network entities 102 that are in communication via such communication links. [0054] The core network 106 may support user authentication, access authorization, tracking, connectivity, and other access, routing, or mobility functions. The core network 106 may be an evolved packet core (EPC), or a 5G core (5GC), which may include a control plane entity that manages access and mobility (e.g., a mobility management entity (MME), an access and mobility management functions (AMF)) and a user plane entity that routes packets or interconnects to external networks (e.g., a serving gateway (S-GW), a Packet Data Network (PDN) gateway (P-GW), or a user plane function (UPF)). In some implementations, the control plane entity may manage non-access stratum (NAS) functions, such as mobility, authentication, and bearer management (e.g., data bearers, signal bearers, etc.) for the one or more UEs 104 served by the one or more network entities 102 associated with the core network 106.

[0055] The core network 106 may communicate with the packet data network 108 over one or more backhaul links 116 (e.g., via an SI, 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. A UE 104 may establish a session (e.g., a protocol data unit (PDU) session, or the like) with the core network 106 via a network entity 102. The core network 106 may route traffic (e.g., control information, data, and the like) between the UE 104 and the application server 118 using the established session (e.g., the established PDU session). 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).

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

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

[0058] A time interval of a resource (e.g., a communication resource) may be organized according to frames (also referred to as radio frames). Each frame may have a duration, for example, a 10 millisecond (ms) duration. In some implementations, each frame may include multiple subframes. For example, each frame may include 10 subframes, and each subframe may have a duration, for example, a 1 ms duration. In some implementations, each frame may have the same duration. In some implementations, each subframe of a frame may have the same duration.

[0059] Additionally or alternatively, a time interval of a resource (e.g., a communication resource) may be organized according to slots. For example, a subframe may include a number (e.g., quantity) of slots. The number of slots in each subframe may also depend on the one or more numerologies supported in the wireless communications system 100. For instance, the first, second, third, fourth, and fifth numerologies (i.e., /r=0, jU=l, /r=2, jU=3, /r=4) associated with respective subcarrier spacings of 15 kHz, 30 kHz, 60 kHz, 120 kHz, and 240 kHz may utilize a single slot per subframe, two slots per subframe, four slots per subframe, eight slots per subframe, and 16 slots per subframe, respectively. Each slot may include a number (e.g., quantity) of symbols (e.g., OFDM symbols). In some implementations, the number (e.g., quantity) of slots for a subframe may depend on a numerology. For a normal cyclic prefix, a slot may include 14 symbols. For an extended cyclic prefix (e.g., applicable for 60 kHz subcarrier spacing), a slot may include 12 symbols. The relationship between the number of symbols per slot, the number of slots per subframe, and the number of slots per frame for a normal cyclic prefix and an extended cyclic prefix may depend on a numerology. It should be understood that reference to a first numerology (e.g., /r=0) associated with a first subcarrier spacing (e.g., 15 kHz) may be used interchangeably between subframes and slots.

[0060] In the wireless communications system 100, an electromagnetic (EM) spectrum may be split, based on frequency or wavelength, into various classes, frequency bands, frequency channels, etc. By way of example, the wireless communications system 100 may support one or multiple operating frequency bands, such as frequency range designations FR1 (410 MHz - 7.125 GHz), FR2 (24.25 GHz - 52.6 GHz), FR3 (7.125 GHz - 24.25 GHz), FR4 (52.6 GHz - 114.25 GHz), FR4a or FR4-1 (52.6 GHz - 71 GHz), and FR5 (114.25 GHz - 300 GHz). In some implementations, the network entities 102 and the UEs 104 may perform wireless communications over one or more of the operating frequency bands. In some implementations, FR1 may be used by the network entities 102 and the UEs 104, among other equipment or devices for cellular communications traffic (e.g., control information, data). In some implementations, FR2 may be used by the network entities 102 and the UEs 104, among other equipment or devices for short-range, high data rate capabilities.

[0061] FR1 may be associated with one or multiple numerologies (e.g., at least three numerologies). For example, FR1 may be associated with a first numerology (e.g., /r=0), which includes 15 kHz subcarrier spacing; a second numerology (e.g., /r=l), which includes 30 kHz subcarrier spacing; and a third numerology (e.g., /r=2), which includes 60 kHz subcarrier spacing. FR2 may be associated with one or multiple numerologies (e.g., at least 2 numerologies). For example, FR2 may be associated with a third numerology (e.g., /r=2), which includes 60 kHz subcarrier spacing; and a fourth numerology (e.g., /r=3), which includes 120 kHz subcarrier spacing. [0062] As described herein, a network entity (e.g., the gNB) can configure the UE to receive a configuration of a time or frequency placement common resource and transmit channel content based on the configuration.

[0063] In some embodiments, the technology identifies content for a UE to transmit over the common PRB/interlace, and transmits the content (e.g., least or low priority information) over the common PRB/interlace. For example, the UE, such as the UE 104, can transmit any of the following information over a common resource (e.g., a common PRB/interlace):

[0064] Least priority information, other than Hybrid Automatic Repeat Request Acknowledgment (HARQ-ACK) information;

[0065] PSFCH F2 (similar to PUCCH F2) which contains channel state information (CSI) reports (e.g., precoding matrix indicator (PMI), rank indicator (RI), beam related information (e.g., beam index), and so on;

[0066] Resource Conflict information, such as information that is part of inter-UE coordination;

[0067] Any broadcast/groupcast type of information, such as resource conflict information or channel occupancy time (COT) sharing information; and so on.

[0068] In some cases, to improve user multiplexing, frequency domain OCC-2/4 on PF2 PSFCH data resource elements (Res) and demodulation reference signal (DMRS) REs could be applied, just as in NR-U PUCCH F2. Also, within one or more common resource interlaces - one set of common resources may be allocated for transmitting PSFCH F0 and another set of common resources may be allocated for transmitting PSFCH F2.

[0069] In some embodiments, the UE 104 may be configured with a common resource (PRB/interlace) within the PSFCH symbol of an RBset (e.g., LBT bandwidth (20MHz BW)). FIG. 2 illustrates an example of a diagram 200 that supports configuring a common interlace for each RBset in accordance with aspects of the present disclosure. As shown, there can be a common interlace 210 that is present at edge PRBs 215 of an RBset, or a common interlace 220 equally spaced within the RBset, such as is present at center PRBs 225.

[0070] As described herein, the UE 104 may transmit least/low priority information, other than HARQ-ACK, in the common resource using PSFCH. The common resource may be configured to transmit PSFCH F2 (aka PUCCH F2), which can be used to convey multiple bits using Quadrature Phase Shift Keying (QPSK) transmission using multiple PRBs in a interlace, since the PSFCH F0 is limited to one RB as it is usually based on sequence-based transmission conveying one bit HARQ-ACK transmission using PRB, cyclic shift, or a combination of the two.

[0071] The PSFCH F2 may be configured to be transmitted using more than one PRB within one common interlace. In some cases, the UE 104 can transmit PSFCH F2 carrying CSI reports (e.g., PMI, RI, beam related information such as beam index, and so on) within one common interlace/PRBs.

[0072] In some cases, the UE 104 can transmit resource conflict information conveyed as part of inter-UE coordination scheme 2 in the common resource, where the resource conflict information may contain an indication to solve half duplex, partial or full overlapping resources among transmitter UEs.

[0073] In some cases, the UE 104 can transmit a COT sharing indicator as a groupcast/broadcast to multiple UEs using the common resource.

[0074] In some cases, the UE 104 can be configured with a user specific/dedicated cyclic shift to be used for the transmission of PSFCH F2 in the common resource.

[0075] In some cases, the UE 104 can transmit a truncated source id/destination id in the PSFCH F2 to help associate the UE 104 to the right receiver.

[0076] In some cases, the UE 104 may transmit in the common resource only when HARQ-ACK information is transmitted in a dedicated resource.

[0077] In some embodiments, within one or more common resource interlaces - one set of common resources may be allocated for transmitting PSFCH F0, and another set of common resource maybe allocated for transmitting PSFCH F2. [0078] In some embodiments, a total number of PSFCH transmissions within a PSFCH symbol should meet OCB requirements, and a maximum number of PSFCH transmissions may be based on UE capabilities. Thus, the total number of PSFCH transmissions in the dedicated and common resource should meet the OCB requirement, and the maximum number of PSFCH transmissions can be based on the UE capability.

[0079] In some cases, when the UE attempts to transmit the PSFCH in the dedicated resource, and OCB requirements are not fulfilled, the UE may transmit additional PSFCH, such as the least priority information described herein, to meet the OCB requirement. The UE capability may indicate a total number of PSFCH transmissions per PSFCH format type. Also, the total number of PSFCH transmissions in a symbol/slot may also be indicated per PSFCH format type.

[0080] For example, when a total number of PSFCH transmissions in a PSFCH symbol is limited according to the UE capability to 6 transmissions, and the number of PSFCH transmissions in a dedicated resource is 4 (fulfilling OCB requirement), then no PSFCH transmission in the common resource is required. However, when the OCB requirement is not met, the UE may need to transmit additional PSFCHs in the common resource, such that the total number of PSFCH transmissions in the common resource and the PSFCH transmissions in the dedicated resource meets the UE capability, as described herein. The UE may drop least priority PSFCH transmissions in the dedicated resource, so the PSFCH transmission can be made in the common resource to meet the OCB requirement and UE capability.

[0081] In some embodiments, a PSFCH transmission in the common interlace may contain a PSFCH repetition, or be part of the repetition, from the dedicated interlace or dedicated PRBs to meet the OCB requirement. Such a transmission may be a dummy transmission. In such cases:

[0082] The common interlace contains part of the repetition from the dedicated interlace or dedicated PRBs starting from the content repeated from the lowest dedicated PRB or lowest dedicated interlace; [0083] The common interlace contains part of the repetition from the dedicated interlace or dedicated PRBs starting from the content repeated from the lowest dedicated PRB or lowest dedicated interlace, in combination with HARQ cast type such as unicast HARQ, groupcast HARQ containing dedicated ACK/NACK and then the groupcast HARQ containing common NACK; or

[0084] The common interlace may contain repeated dedicated interlace/PRBs according to the cast type and HARQ feedback option. The common interlace may chose the dedicated interlace/PRBs according to a priority of a cast type, where such priority may be preconfigured in a resource pool. For example, the common interlace may chose the dedicated interlace/PRBs according to groupcast feedback option 2 due to number of HARQ.ACKs from member UEs; and so on. In such cases, the UE may choose to transmit dummy transmissions containing any information or HARQ-ACK from a lowest dedicated PRB/interlace of the corresponding UE’s PSFCH transmission or least priority information (e.g., CSI reports) in the common interlace/PRBs.

[0085] In some embodiments, a PSFCH transmission containing dedicated ACK/NACK may be transmitted in both the dedicated interlace and the common interlace. However, the PSFCH transmission containing common NACK, such as groupcast HARQ feedback option 1 when transmitted in the dedicated PRBs/interlace, then a dummy transmission containing any information or least priority information as described herein are transmitted in the common interlace.

[0086] In some embodiments, a receiver UE may be configured to decode or not decode the content of the common interlace according to the PSFCH format type and content.

[0087] FIG. 3 illustrates an example of a block diagram 300 of a device 302 that supports UE sidelink unlicensed operations in accordance with aspects of the present disclosure. The device 302 may be an example of a UE 104 as described herein. The device 302 may support wireless communication with one or more network entities 102, UEs 104, or any combination thereof. The device 302 may include components for bi-directional communications including components for transmitting and receiving communications, such as a processor 304, a memory 306, a transceiver 308, and an I/O controller 310. These components may be in electronic communication or otherwise coupled (e.g., operatively, communicatively, functionally, electronically, electrically) via one or more interfaces (e.g., buses).

[0088] The processor 304, the memory 306, the transceiver 308, or various combinations thereof or various components thereof may be examples of means for performing various aspects of the present disclosure as described herein. For example, the processor 304, the memory 306, the transceiver 308, or various combinations or components thereof may support a method for performing one or more of the operations described herein.

[0089] In some implementations, the processor 304, the memory 306, the transceiver 308, or various combinations or components thereof may be implemented in hardware (e.g., in communications management circuitry). 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, a discrete gate or transistor logic, discrete hardware components, or any combination thereof configured as or otherwise supporting a means for performing the functions described in the present disclosure. In some implementations, the processor 304 and the memory 306 coupled with the processor 304 may be configured to perform one or more of the functions described herein (e.g., executing, by the processor 304, instructions stored in the memory 306).

[0090] For example, the processor 304 may support wireless communication at the device 302 in accordance with examples as disclosed herein. The processor 304 may be configured as or otherwise support a means for receiving a first configuration associated with a time or frequency placement common resource, receiving a second configuration associated with content to be transmitted, and transmitting channel content based on the first configuration and the second configuration.

[0091] The processor 304 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 304 may be configured to operate a memory array using a memory controller. In some other implementations, a memory controller may be integrated into the processor 304. The processor 304 may be configured to execute computer-readable instructions stored in a memory (e.g., the memory 306) to cause the device 302 to perform various functions of the present disclosure.

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

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

[0094] In some implementations, the device 302 may include a single antenna 312. However, in some other implementations, the device 302 may have more than one antenna 312 (i.e., multiple antennas), including multiple antenna panels or antenna arrays, which may be capable of concurrently transmitting or receiving multiple wireless transmissions. The transceiver 308 may communicate bi-directionally, via the one or more antennas 312, wired, or wireless links as described herein. For example, the transceiver 308 may represent a wireless transceiver and may communicate bi-directionally with another wireless transceiver. The transceiver 308 may also include a modem to modulate the packets, to provide the modulated packets to one or more antennas 312 for transmission, and to demodulate packets received from the one or more antennas 312.

[0095] FIG. 4 illustrates a flowchart of a method 400 that supports transmitting content over a sidelink in accordance with aspects of the present disclosure. The operations of the method 400 may be implemented by a device or its components as described herein. For example, the operations of the method 400 may be performed by the UE 104 as described with reference to FIGs. 1 through 2. In some implementations, the device may execute a set of instructions to control the function elements of the device to perform the described functions. Additionally, or alternatively, the device may perform aspects of the described functions using special-purpose hardware.

[0096] At 405, the method may include receiving a first configuration associated with a time or frequency placement common resource. The operations of 405 may be performed in accordance with examples as described herein. In some implementations, aspects of the operations of 405 may be performed by a device as described with reference to FIG. 1.

[0097] At 410, the method may include receiving a second configuration associated with content to be transmitted. The operations of 410 may be performed in accordance with examples as described herein. In some implementations, aspects of the operations of 410 may be performed by a device as described with reference to FIG. 1.

[0098] At 415, the method may include transmitting channel content based on the first configuration and the second configuration. The operations of 415 may be performed in accordance with examples as described herein. In some implementations, aspects of the operations of 415 may be performed by a device as described with reference to FIG. 1.

[0099] It should be noted that the methods described herein describes possible implementations, and that the operations and the steps may be rearranged or otherwise modified and that other implementations are possible. Further, aspects from two or more of the methods may be combined. [0100] The various illustrative blocks and components described in connection with the disclosure herein may be implemented or performed with a general-purpose processor, a DSP, an ASIC, a CPU, an FPGA or other programmable logic device, discrete gate or transistor logic, discrete hardware components, or any combination thereof designed to perform the functions described herein. A general-purpose processor may be a microprocessor, but in the alternative, the processor may be any processor, controller, microcontroller, or state machine. A processor may also be implemented as a combination of computing devices (e.g., a combination of a DSP and a microprocessor, multiple microprocessors, one or more microprocessors in conjunction with a DSP core, or any other such configuration.

[0101] 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 transmitted over as one or more instructions or code on a computer-readable medium. Other examples and implementations are within the scope of the disclosure and appended claims. For example, due to the nature of software, functions described herein may be implemented using software executed by a processor, hardware, firmware, hardwiring, or combinations of any of these. Features implementing functions may also be physically located at various positions, including being distributed such that portions of functions are implemented at different physical locations.

[0102] Computer-readable media includes both non-transitory computer storage media and communication media including any medium that facilitates transfer of a computer program from one place to another. A non-transitory storage medium may be any available medium that may be accessed by a general-purpose or special-purpose computer. By way of example, and not limitation, non-transitory computer-readable media may include RAM, ROM, electrically erasable programmable ROM (EEPROM), flash memory, compact disk (CD) ROM or other optical disk storage, magnetic disk storage or other magnetic storage devices, or any other non-transitory medium that may be used to carry or store desired program code means in the form of instructions or data structures and that may be accessed by a general-purpose or special-purpose computer, or a general-purpose or special-purpose processor. [0103] Any connection may be properly termed a computer-readable medium. For example, if the software is transmitted from a website, server, or other remote source using a coaxial cable, fiber optic cable, twisted pair, digital subscriber line (DSL), or wireless technologies such as infrared, radio, and microwave, then the coaxial cable, fiber optic cable, twisted pair, DSL, or wireless technologies such as infrared, radio, and microwave are included in the definition of computer-readable medium. Disk and disc, as used herein, include CD, laser disc, optical disc, digital versatile disc (DVD), floppy disk and Blu-ray disc where disks usually reproduce data magnetically, while discs reproduce data optically with lasers. Combinations of the above are also included within the scope of computer- readable media.

[0104] As used herein, including in the claims, “or” as used in a list of items (e.g., a list of items prefaced by a phrase such as “at least one of’ or “one or more of’ or “one or both of’) indicates an inclusive list such that, for example, a list of at least one of A, B, or C means A or B or C or AB or AC or BC or ABC (i.e., A and B and C). Also, as used herein, the phrase “based on” shall not be construed as a reference to a closed set of conditions. For example, an example step that is described as “based on condition A” may be based on both a condition A and a condition B without departing from the scope of the present disclosure. In other words, as used herein, the phrase “based on” shall be construed in the same manner as the phrase “based at least in part on. Further, as used herein, including in the claims, a “set” may include one or more elements.

[0105] The terms “transmitting,” “receiving,” or “communicating,” when referring to a network entity, may refer to any portion of a network entity (e.g., a base station, a CU, a DU, a RU) of a RAN communicating with another device (e.g., directly or via one or more other network entities).

[0106] The description set forth herein, in connection with the appended drawings, describes example configurations and does not represent all the examples that may be implemented or that are within the scope of the claims. The term “example” used herein means “serving as an example, instance, or illustration,” and not “preferred” or “advantageous over other examples.” The detailed description includes specific details for the purpose of providing an understanding of the described techniques. These techniques, however, may be practiced without these specific details. In some instances, known structures and devices are shown in block diagram form to avoid obscuring the concepts of the described example.

[0107] The description herein is provided to enable a person having ordinary skill in the art to make or use the disclosure. Various modifications to the disclosure will be apparent to a person having ordinary skill in the art, and the generic principles defined herein may be applied to other variations without departing from the scope of the disclosure. Thus, the disclosure is not limited to the examples and designs described herein but is to be accorded the broadest scope consistent with the principles and novel features disclosed herein.

Claims

CLAIMS What is claimed is:

1. User equipment (UE), comprising: at least one memory; and at least one processor coupled with the at least one memory and configured to cause the UE to: receive a first configuration associated with a time or frequency placement common resource; receive a second configuration associated with content to be transmitted; and transmit channel content based on the first configuration and the second configuration.

2. The UE of claim 1, wherein the time or frequency placement common resource is part of a resource pool or resource block set (RBset) available to the UE during sidelink unlicensed operation.

3. The UE of claim 1, wherein the channel content includes Physical Sidelink Feedback Channel (PSFCH) content to be transmitted via the time or frequency placement common resource indicated by the first configuration.

4. The UE of claim 3, wherein the PSFCH content includes multiple bits conveying a channel state information (CSI) report.

5. The UE of claim 3, wherein the PSFCH content includes multiple bits conveying beam related information.

6. The UE of claim 3, wherein the PSFCH content includes multiple bits conveying Resource Conflict information.

7. The UE of claim 3, wherein the PSFCH content includes multiple bits conveying Channel Occupancy Time (COT) information.

8. The UE of claim 1, wherein the channel content includes low priority information and does not include Hybrid Automatic Repeat Request Acknowledgment (HARQ-ACK) information.

9. The UE of claim 1, wherein the received first configuration includes a dedicated frequency cyclic shift via which the UE transmits content via the time or frequency placement common resource.

10. The UE of claim 1 , wherein the received first configuration includes information indicating placement of Physical Resource Blocks (PRBs) with each interlace of the time or frequency placement common resource.

11. The UE of claim 1 , wherein the received first configuration includes information indicating placement of Physical Resource Blocks (PRBs) for a common interlace at both ends of a resource block set (RBset) available to the UE within the time or frequency placement common resource.

12. The UE of claim 1 , wherein the UE transmits the channel content via a common interlace or one or multiple common Physical Resource Blocks (PRBs) available to the UE within the time or frequency placement common resource.

13. A method performed by user equipment (UE), the method comprising: receiving a first configuration associated with a time or frequency placement common resource; receiving a second configuration associated with content to be transmitted; and transmitting channel content based on the first configuration and the second configuration.

14. The method of claim 13, wherein the time or frequency placement common resource is part of a resource pool or resource block set (RBset) available to the UE during sidelink unlicensed operation.

15. The method of claim 13, wherein the channel content includes Physical Sidelink Feedback Channel (PSFCH) content to be transmitted via the time or frequency placement common resource indicated by the first configuration.

16. The method of claim 15, wherein the PSFCH content includes multiple bits conveying a channel state information (CSI) report.

17. The method of claim 15, wherein the PSFCH content includes multiple bits conveying beam related information.

18. The method of claim 15, wherein the PSFCH content includes multiple bits conveying Resource Conflict information.

19. A processor for wireless communication, comprising: at least one controller coupled with at least one memory and configured to cause the processor to: receive a first configuration associated with a time or frequency placement common resource; receive a second configuration associated with content to be transmitted; and transmit channel content based on the first configuration and the second configuration.

20. User equipment (UE), comprising: at least one memory; and at least one processor coupled with the at least one memory and configured to cause the UE to: receive a configuration of a time or frequency placement common resource; and transmit channel content based on the configuration.