WO2024157235A1

WO2024157235A1 - Sidelink assistance information for sidelink communication

Info

Publication number: WO2024157235A1
Application number: PCT/IB2024/053371
Authority: WO
Inventors: Alexander Golitschek Edler Von Elbwart; Joachim Löhr; Karthikeyan Ganesan; Prateek Basu Mallick
Original assignee: Lenovo (Singapore) Pte. Ltd.
Priority date: 2023-04-06
Filing date: 2024-04-05
Publication date: 2024-08-02
Also published as: WO2024157234A1

Abstract

Various aspects of the present disclosure relate to methods, apparatuses, and systems that support sidelink assistance information for sidelink communication. For instance, implementations provide ways for enabling sidelink assistance information to be transmitted between devices, e.g., from a first UE to a second UE to facilitate the second UE to determine suitable candidate UEs for COT sharing. Sidelink assistance information, for example, enables the second UE to determine whether a transmission to a first UE is to be scheduled by the second UE to allow the first UE to share a COT of the second UE. Further, this disclosure provides ways for triggering and requesting a sidelink assistance information transmission that facilitates a recipient of the sidelink assistance information to determine suitable candidate UEs for sidelink transmission, e.g., as part of COT sharing.

Description

SIDELINK ASSISTANCE INFORMATION FOR SIDELINK COMMUNICATION

RELATED APPLICATIONS

[0001] This application claims priority to U.S. Provisional Application Serial No. 63/457,601 filed 06 APR 2023 entitled “SIDELINK ASSISTANCE INFORMATION FOR SIDELINK COMMUNICATION TECHNICAL FIELD,” the disclosure of which is incorporated by reference herein in its entirety. This application also claims priority to U.S. Provisional Application Serial No. 63/457,615 filed 06 APR 2023 entitled “SIDELINK ASSISTANCE INFORMATION FOR SIDELINK COMMUNICATION TECHNICAL FIELD,” the disclosure of which is incorporated by reference herein in its entirety.

TECHNICAL FIELD

[0002] The present disclosure relates to wireless communications, and more specifically to sidelink communication.

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 nextgeneration NodeB (gNB), or other suitable terminology. Each network communication devices, 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] Some wireless communications systems provide ways for sidelink communication, such as between different UE and via wireless channels in unlicensed spectrum. Further, devices such as UE can share sidelink resources, such as via channel occupancy time (COT) sharing. Some proposals for enabling sharing of sidelink resources, however, may fail to provide sufficient ways for enabling parameters for sharing of sidelink resources to be propagated among involved devices.

SUMMARY

[0005] The present disclosure relates to methods, apparatuses, and systems that support sidelink assistance information for sidelink communication. For instance, implementations provide ways for enabling sidelink assistance information to be transmitted between devices, e.g., from a first UE to a second UE to facilitate the second UE to determine suitable candidate UEs for COT sharing. Sidelink assistance information, for example, enables the second UE to determine whether a transmission to a first UE is to be scheduled by the second UE to allow the first UE to share a COT of the second UE. Further, this disclosure provides ways for triggering and requesting a sidelink assistance information transmission that facilitates a recipient of the sidelink assistance information to determine suitable candidate UEs for sidelink transmission, e.g., as part of COT sharing.

[0006] Thus, by utilizing the described techniques, sidelink resources can be more efficiently utilized.

[0007] Some implementations of the methods and apparatuses described herein may further include generating, by a first apparatus, a sidelink assistance information indication pertaining to data available for transmission from the first apparatus to a second apparatus; and transmitting the sidelink assistance information indication to a third apparatus.

[0008] Some implementations of the methods and apparatuses described herein may further include: where the sidelink assistance information indication includes identification information for the first apparatus and the second apparatus; the sidelink assistance information indication includes an available data indicator indicating whether the first apparatus has data to transmit to the second apparatus; the sidelink assistance information indication includes an available data indicator indicating an amount of data the first apparatus has to transmit to the second apparatus; the sidelink assistance information indication includes an indication of priority information for data to be transmitted from the first apparatus to the second apparatus; the indication of priority information includes one or more of logical channel priority (LCP) information or channel access priority class (CAPC) information; transmitting the sidelink assistance information via one or more of resource pool configuration information, radio resource control (RRC), or physical layer signaling; receiving cast type information via one or more of resource pool configuration information, RRC, or physical layer signaling, the cast type information including an indication of one or more cast types for which the sidelink assistance information is to be generated.

[0009] Some implementations of the methods and apparatuses described herein may further include: receiving cast type information including one or more of information indicating that an available data indicator per cast type is to be transmitted; or information indicating that an aggregated available data indicator for multiple cast types is to be transmitted; transmitting the sidelink assistance information via a channel state information (CSI) medium access control (MAC) control element (CE); the first apparatus includes a data transmission source, the second apparatus includes a data transmission destination of multiple data transmission destinations, and the sidelink assistance information includes an available data indicator indicating an amount of data that the first apparatus has to transmit to each of the multiple data transmission destinations; transmitting the sidelink assistance information via a physical sidelink feedback channel (PSFCH); transmitting the sidelink assistance information via sidelink control information (SCI); determining a highest CAPC value for multiplexed service data units (SDU); and selecting the highest CAPC value for a transport block (TB) associated with transmission of the sidelink assistance information; determining a lowest CAPC value for multiplexed service data units (SDU); and selecting the lowest CAPC value for a TB associated with transmission of the sidelink assistance information.

[0010] Some implementations of the methods and apparatuses described herein may further include receiving, at a first apparatus, a sidelink assistance information indication pertaining to data available for transmission from a second apparatus to a third apparatus; and configuring channel occupancy time sharing logic of the first apparatus based at least in part on the sidelink assistance information indication.

[0011] Some implementations of the methods and apparatuses described herein may further include: where the sidelink assistance information indication includes an available data indicator indicating an amount of data the second apparatus has to transmit to the third apparatus, and the method further includes determining whether to initiate channel occupancy time sharing with the second apparatus based at least in part on the amount of data; the sidelink assistance information indication includes an available data indicator indicating a data priority of data the second apparatus has to transmit to the third apparatus, and the method further includes determining whether to initiate channel occupancy time sharing with the second apparatus based at least in part on the data priority; the sidelink assistance information indication includes an indication of a cast type for data transmission from the second apparatus to the third apparatus, and the method further includes determining whether to initiate channel occupancy time sharing with the second apparatus based at least in part on the cast type; maintaining a list of source apparatus, including the second apparatus, from which data transmission is receivable by the first apparatus; and initiating channel occupancy time sharing with the second apparatus based at least in part on a priority indication of the second apparatus in the list of source apparatus.

[0012] Some implementations of the methods and apparatuses described herein may further include generating, by a first apparatus and based at least in part on a trigger event, a sidelink assistance information indication pertaining to data available for transmission from the first apparatus to a second apparatus; and transmitting the sidelink assistance information indication to a third apparatus.

[0013] Some implementations of the methods and apparatuses described herein may further include: where the trigger event includes the first apparatus receiving physical sidelink shared channel (PSSCH) transmission; the trigger event includes an expiry of a timer; the trigger event includes that the first apparatus has data to transmit and a sidelink grant with a data transmission capacity that is larger than a size of the data to transmit; the trigger event includes a change in LCP; the trigger event includes a change in CAPC; the trigger event includes exceeding a threshold number of listen before talk (LBT) failures; the trigger event includes a reception of a COT sharing indicator; the trigger event includes a reception of a request for sidelink assistance information; determining, based at least in part on a second trigger event, that a second sidelink assistance information indication is to be generated; and delaying generation of the second sidelink assistance information indication until expiry of a timer; determining, based at least in part on a second trigger event, that a second sidelink assistance information indication is to be generated; and ignoring the second trigger event based at least in part on a timer not being expired; the second apparatus includes the third apparatus; the first apparatus includes a first user equipment (UE), the second apparatus includes a second UE, and the third apparatus includes one or more of the second UE or a base station.

[0014] Some implementations of the methods and apparatuses described herein may further include generating an indication for triggering sidelink assistance information for data transmission from a second apparatus; and transmitting the indication of sidelink assistance information to one or more of the second apparatus or a third apparatus.

[0015] Some implementations of the methods and apparatuses described herein may further include: transmitting the indication of sidelink assistance information via SCI; the indication of sidelink assistance information includes a COT sharing indicator; the indication of sidelink assistance information includes a sidelink assistance information request; the first apparatus includes a first user equipment (UE), the second apparatus includes a second UE, and the method further includes: receiving, from the second UE, sidelink assistance information including an indication that the second UE has data to transmit to the first UE; and initiating, based at least in part on the sidelink assistance information, COT sharing between the first UE and the second UE for transmission of the data from the second UE to the first UE.

BRIEF DESCRIPTION OF THE DRAWINGS

[0016] FIG. 1 illustrates an example of a wireless communications system that supports sidelink assistance information for sidelink communication in accordance with aspects of the present disclosure.

[0017] FIG. 2 illustrates an example of a sidelink shared channel (SL-SCH) MAC subheader.

[0018] FIG. 3 illustrates a sidelink CSI reporting MAC CE.

[0019] FIGs. 4-8 illustrate examples of new MAC CEs that can be used to transmit sidelink assistance information.

[0020] FIGs. 9 and 10 illustrate examples of block diagrams of devices that support sidelink assistance information for sidelink communication in accordance with aspects of the present disclosure. [0021] FIGs. 11 through 15 illustrate flowcharts of methods that support sidelink assistance information for sidelink communication in accordance with aspects of the present disclosure.

DETAILED DESCRIPTION

[0022] In wireless communications systems, COT sharing is a mechanism to attempt to improve the resource utilization for communication between two UEs over the PC5 interface. In order to share the COT efficiently, it can be beneficial for a COT initiator to be aware of whether potential responding UEs have data to transmit to the initiating UE. Some wireless communications systems, however, lack provisions for sharing such information, which can cause inefficiencies in utilization of available wireless resources. Likewise any scheduling unit will benefit from being aware whether and which UEs have data to transmit to which other UE over the PC5 interface.

[0023] Accordingly, this disclosure provides for techniques that support sidelink assistance information for sidelink communication. For instance, implementations provide ways for enabling sidelink assistance information to be transmitted between devices, e.g., from a first UE to a second UE to facilitate the second UE to determine suitable candidate UEs for COT sharing or for scheduling radio resources. Sidelink assistance information, for example, enables the second UE to determine whether a transmission to a first UE is to be scheduled by the second UE to allow the first UE to share a COT of the second UE. Further, this disclosure provides ways for triggering and requesting a sidelink assistance information transmission that facilitates a recipient of the sidelink assistance information to determine suitable candidate UEs for sidelink transmission, e.g., as part of COT sharing or radio resource scheduling.

[0024] Thus, by utilizing the described techniques, sidelink resources can be more efficiently utilized.

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

[0026] FIG. 1 illustrates an example of a wireless communications system 100 that supports sidelink assistance information for sidelink communication 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 5G 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 (Wi-Fi), 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.

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

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

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

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

[0031] 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, 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.

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

[0033] 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 Near-Real Time RIC (Near-real time (RT) RIC), a Non-Real Time RIC (Non-RT RIC)), a Service Management and Orchestration (SMO) system, or any combination thereof.

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

[0035] 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., RRC, service data adaption protocol (SDAP), Packet Data Convergence Protocol (PDCP). The CU may be connected to one or more DUs or 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, MAC layer) functionality and signaling, and may each be at least partially controlled by the CU.

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

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

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

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

[0040] 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 (e.g., multiple frame structures). The network entities 102 and the UEs 104 may support various frame structures based on one or more numerologies.

[0041] 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. 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., /2=1) 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., jU=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. A sixth numerology (e.g., jU=5) may be associated with a sixth subcarrier spacing (e.g., 480 kHz) and a normal cyclic prefix. A seventh numerology (e.g., /r=6) may be associated with a sixth subcarrier spacing (e.g., 960 kHz) and a normal cyclic prefix.

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

[0043] 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. Each slot may include a number (e.g., quantity) of symbols (e.g., orthogonal frequency-division multiplexing (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.

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

[0045] 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., ^=0), which includes 15 kHz subcarrier spacing; a second numerology (e.g., /z=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.

[0046] According to implementations for sidelink assistance information for sidelink communication, a UE 104(1) detects a trigger event 120 that indicates that sidelink assistance information is to be generated and transmitted. The trigger event 120 can occur in various ways, such as based on local events generated at the UE 104(1), transmissions from other devices (e.g., a different UE 104, a network entity 102, etc.), and so forth. Different examples of the trigger event 120 are detailed throughout this disclosure.

[0047] Based at least in part on the trigger event 120, the UE 104(1) generates sidelink assistance information 122 and transmits the sidelink assistance information 122, such as to a UE 104(2) and/or a network entity 102. Different examples of the sidelink assistance information 122 are detailed throughout this disclosure. The sidelink assistance information 122, for instance, indicates that the UE 104(1) has data to transmit via sidelink transmission to the UE 104(2). Accordingly, based on the sidelink assistance information 122, the UE 104(1) performs sidelink transmission 124 to the UE 104(2). In at least one implementation, the sidelink transmission 124 involves COT sharing from the UE 104(2) to the UE 104(1) to enable the UE 104(1) to participate in COT sharing for the sidelink transmission 124 to the UE 104(2).

[0048] FIG. 2 illustrates an example of a sidelink shared channel (SL-SCH) MAC subheader 200. For instance, in wireless communication systems a MAC PDU can be utilized to transmit sidelink information, such as via SL-SCH. In implementations, a SL-SCH subheader is of a fixed size and consists of the seven header fields V/R/R/R/R/SRC/DST. A MAC subheader except for fixed-sized MAC CE and padding can include four header fields R/F/LCID/L, e.g., with an 8-bit L field or with a 16-bit L field. A MAC subheader for fixed-sized MAC CE and padding can include two header fields R/LCID.

[0049] For a MAC subheader for SL-SCH, the MAC subheader can include the following fields:

[0050] V: The MAC PDU format version number field indicates which version of the SL-SCH subheader is used. In this version of the specification, the V field is set to 0. The size of the V field is 4 bits;

[0051] SRC (Source): The SRC field carries the 16 most significant bits of the Source Layer-2 identifier (ID) set to the identifier provided by upper layers as defined in Technical Specification (TS) 23.287 or TS 23.304. The length of the field is 16 bits;

[0052] DST (Destination): The DST field carries the 8 most significant bits of the Destination Layer-2 ID set to the identifier provided by upper layers as defined in TS 23.287 or TS 23.304. The length of the field is 8 bits;

[0053] LCID (Logical Channel ID): The Logical Channel ID field identifies the logical channel instance of the corresponding MAC SDU or the type of the corresponding MAC CE within the scope of one Source Layer-2 ID and Destination Layer-2 ID pair or padding as described in Tables 6.2.4-1 for SL-SCH. There is one LCID field per MAC subheader except for SL-SCH subheader. The size of the LCID field is 6 bits;

[0054] L: The Length field indicates the length of the corresponding MAC SDU or variablesized MAC CE in bytes. There is one L field per MAC subheader except for SL-SCH subheader and subheaders corresponding to the fixed-sized MAC CE or padding. The size of the L field is indicated by the F field;

[0055] F: The Format field indicates the size of the Length field. There is one F field per MAC subheader except for SL-SCH subheader and subheaders corresponding to the fixed-sized MAC CE or padding. The size of the F field is 1 bit. The value 0 indicates 8 bits of the Length field. The value 1 indicates 16 bits of the Length field;

[0056] R: Reserved bit, set to 0.

Table 6.2.4-1 Values of LCID for SL-SCH

[0057] Accordingly, solutions are provided in this disclosure to enable sidelink assistance information sharing. In the present disclosure, sidelink assistance information can include data that is exchanged between sidelink devices to facilitate efficient use of the unlicensed spectrum. For instance, efficient use can be characterised by a high spectral efficiency for transmissions, a usage of channel occupancy up to the allowed maximum channel occupancy time, a prioritized transmission of data with a small packet delay budget or a high data priority, and so forth.

[0058] Examples of sidelink assistance information include one or more of an indication of whether a device has data to transmit (e.g., buffer status such as via a buffer status report), an indication of a priority of data to be transmitted, an indication of CAPC, etc. For instance, sidelink assistance information can include an indication of whether a device has data to transmit and/or how much data a device has to transmit, such as indicated as available data (AD) and/or available data indicator (ADI). An AD/ ADI can be transmitted to a receiver, per group of receivers, per receiver, and so forth. Further, a receiver of data as well as a transmitter of the sidelink assistance information can be represented by an identifier, and thus the sidelink assistance information may be characterized and specific to one or more source/destination identifiers (SRC/DST IDs) or SRC- DST ID pairs.

[0059] In implementations, sidelink assistance information can include a priority indication of a priority of available data for transmission, e.g. a logical channel priority level. A priority indication, for instance, may be for defined priority levels, e.g., in an ordered fashion. Further, a priority indication may be for one or more priority levels for which a device has available data. A priority indication, for example, may indicate a highest priority for which data is available to be transmitted.

[0060] In implementations, sidelink assistance information can include an indication of a CAPC. For instance, a transmission may be associated with a CAPC and/or a CAPC indication for defined CAPC, e.g., in an ordered fashion. Further, a CAPC indication may be for one or more CAPCs for which a device has available data and a highest CAPC level for which data is available can be indicated.

[0061] In implementations, a COT initiating UE may be configured to determine whether another UE (e.g., a receiving UE) has data to transmit, e.g., to the COT initiating UE. Further, a sidelink scheduler (e.g., gNB) may be configured to determine if a UE has data in its buffer for a certain connection to another UE and/or one or more (pre)determined/configured/indicated SRC- DST pair(s).

[0062] In example implementations, a UE can indicate sidelink assistance information in various ways, such as in the context of at least one SRC-DST pair. The SRC-DST pair, for example, can be indicated according to a SL-SCH subheader, as part of “additional IDs” (e.g. configured for the purpose of COT sharing), via sidelink assistance information per CAPC level, etc. As another example, an ID such as a SRC ID or DST ID can be indicated by a bit field, or it can be used for a scrambling a CRC of a control information.

[0063] In implementations, a sidelink assistance information indicator includes one or more bits to represent available data. For instance, a sidelink assistance information indication can indicate whether available data for transmission is above or below a specific threshold data amount ADthres. According to various implementations, AD_thres=0; ADthres is a configurable number of bytes (e.g., per resource pool); ADthres is equivalent to one or more of existing 5-bit/8-bit base station (BS) values (e.g., as in Table 6.1.3.1-1, Table 6.1.3.1-2 in 38.321), is configurable, e.g., per resource pool, etc.

[0064] In implementations, a logical channel (LCH) priority level (e.g., highest level) for which a UE has data available for transmission can be indicated in sidelink assistance information, such as using 8 levels and/or 3 bits. Further, sidelink assistance information can include CAPC levels for data that is available to be transmitted, such as using 4 levels and/or 2 bits.

[0065] In implementations, a cast type (e.g., groupcast, broadcast, unicast, etc.) for sidelink assistance information can be configurable, e.g., using resource pool configuration, RRC, physical layer signaling (e.g., SCI), etc. For example, the configuration may indicate that the sidelink assistance information is to be broadcast to all devices within communication range. In another example, the configuration may indicate the ID(s) of one or more specific device(s), such as for a UE or a scheduling unit, so that the sidelink assistance information can be transmitted to those device(s).

[0066] In implementations, a cast type (e.g., groupcast, broadcast, unicast, etc.) for which sidelink assistance information is applicable can be configurable using resource pool configuration, RRC, or physical layer signaling. For example, the configuration may indicate that sidelink assistance information is to include an available data indicator for available unicast data, or for unicast and groupcast data, or for various combinations of unicast, groupcast, and broadcast data. Further, the configuration may indicate whether an available data indicator is to be transmitted per cast type (e.g., via cast type specific assistance information such as one MAC CE per cast type) or as an aggregate sidelink assistance information for combined cast types.

[0067] FIG. 3 illustrates a sidelink CSI reporting MAC CE 300. In implementations sidelink assistance information can be included in a sidelink CSI report MAC CE. For instance, similarly to TS 38.321, the sidelink CSI reporting MAC CE 300 can be identified by a MAC subheader with LCID as specified in Table 6.2.4-1, below. The priority of the sidelink CSI reporting MAC CE can be fixed to T. The sidelink CSI reporting MAC CE can be defined as indicated by MAC CE 300:

[0068] RI (Rank Indicator): This field indicates the derived value of the Rank Indicator for sidelink CSI reporting as specified in clause 8.5 of TS 38.214. The length of the field is 1 bit;

[0069] CQI (Channel Quality Indicator): This field indicates the derived value of the CQI for sidelink CSI reporting as specified in clause 8.5 of TS 38.214. The length of the field is 4 bits;

[0070] R: Reserved bit, set to 0.

[0071] According to implementations, one or more bits, such as those marked by R in MAC CE 300, can be used to transmit sidelink assistance information. Further, three bits, such as those marked by R in MAC CE 300 may represent sidelink assistance information per cast type, e.g., a first bit for unicast data assistance information, a second bit for groupcast data assistance information, a third bit for broadcast data assistance information.

[0072] FIG. 4 illustrates a new MAC CE 400 that can be used to transmit sidelink assistance information. The MAC CE 400, for instance, indicates sidelink assistance information for each of a plurality of the SRC-DST IDs. For example, if available data is indicated per SRC-DST ID i (ADL), the sidelink assistance information can indicate whether the ADL is above or below a specific threshold ADthres. The threshold ADthres can be applicable to all SRC-DST IDs and configurable accordingly, or it can be a threshold specifically applicable to SRC-DST ID i and configurable accordingly.

[0073] FIG. 5 illustrates a new MAC CE 500 that can be used to transmit sidelink assistance information. The MAC CE 500, for instance, indicates sidelink assistance information for each of a plurality of the CAPCs (e.g. CAPC 1, 2, 3, 4). For example if available data for a SRC-DST ID (e.g. according to SL-SCH subheader) for CAPC #i (ADL) is above or below a specific threshold ADthres. The threshold ADthres can be applicable to all CAPCs and configurable accordingly, or it can be a threshold specifically applicable to CAPC #i and configurable accordingly. In an implementation the MAC CE 500 can include a highest LCH priority level for which data is available or above a threshold.

[0074] FIG. 6 illustrates a new MAC CE 600 that can be used to transmit sidelink assistance information. The MAC CE 600, for instance, indicates sidelink assistance information for each of a plurality of the sidelink LCH priority levels (e.g. LCH priority levels 1, 2, ... , 8). For example, the MAC CE 600 can indicate if available data for a SRC-DST ID (e.g. according to SL-SCH subheader) for LCH priority level #i ( ADL) is above or below a specific threshold ADthres. The threshold ADthres can be applicable to all LCH priority levels and configurable accordingly, or it can be a threshold specifically applicable to LCH priority level #i and configurable accordingly.

[0075] FIG. 7 illustrates a new MAC CE 700 that can be used to transmit sidelink assistance information. The MAC CE 700, for instance, includes sidelink assistance information that is applicable to and determined considering logical channels after a MAC PDU has been generated for a SRC-DST pair or other additional IDs, e.g., after a logical channel prioritization procedure. For example, the sidelink assistance information can include the available data size considering logical channels after the MAC PDU has been generated for a SRC-DST pair or other additional IDs. The amount of available data, for example, can be indicated in number of bytes, or by an index to an element of a table representing the number of bytes. In implementations the MAC CE 700 can include a highest LCH priority indication for which data is available at or above a threshold.

[0076] FIG. 8 illustrates a new MAC CE 800 that can be used to transmit sidelink assistance information. In the MAC CE 800, for instance, one or more of: available data size is data with an indicated LCH priority; available data size is data for all LCH priority; available data size is data for all LCH priorities equal to or higher than an indicated LCH priority level; or available data size includes data for all LCH priority equal to or lower than the indicated LCH priority level. In an option, a resource pool can be selected for this MAC CE transmission (e.g., the assistance data transmission) corresponding to a highest LCH priority for which data is available. [0077] According to implementations, the sidelink assistance information can be conveyed per cast type, e.g., a first bit/field for available unicast data indicator, a second bit/field for available groupcast data, a third bit/field for available broadcast data indicator, etc.

[0078] In implementations a corresponding MAC CE may be associated with its own LCID. For instance, Table 2 below illustrates that a LCID 55 can be used to indicate sidelink assistance information. Table 2, for example, represents a modification of Table 6.2.4-1 above that utilizes a previously reserved LCID for sidelink assistance information.

Table 2 of LCID for SL-SCH

[0079] In implementations sidelink assistance information can be transmitted on PSFCH resources. For instance, implementations can determine a PSFCH resource such as by configuring a third resource set of W_{PPB seL} physical resource blocks (PRBs) in a resource pool for PSFCH transmission with sidelink assistance information in a PRB of the resource pool. For instance, the first set represents PSFCH resources for acknowledgement/negative acknowledgement (ACK/NACK) and the second set represents PSFCH resources for conflict information.

[0080] As an example, consider UE procedures for reporting and obtaining control information in PSFCH including control information provided by a PSFCH transmission including hybrid automatic repeat request (HARQ)-ACK information or conflict information.

[0081] For a UE procedure for transmitting PSFCH with control information, a UE is provided by sl-PSFCH-RB-Set a set of PRBs in a resource pool for PSFCH transmission with

HARQ-ACK information in a PRB of the resource pool. A UE can be provided by sl-RB-SetPSFCH a set of PRBs in a resource pool for PSFCH transmission with conflict information in a

PRB of the resource pool. A UE can be provided by s1-NewName a set of PRBs in a

resource pool for PSFCH transmission with assistance information in a PRB of the resource pool. A UE can be configured with logic that indicates that different PRBs are to be (pre)configured for conflict information and HARQ-ACK information. For a number of N_subch sub-channels for the resource pool, provided by sl-NumSubchcmnel, and a number of PSSCH slots associated with a

PSFCH slot that is less than or equal to , the UE allocates the

slot i among the

PSSCH slots associated with the PSFCH slot and sub-channel j, where

, and the allocation starts in an ascending order of i and continues in an ascending order of j. The UE can be configured with logic that indicates that that

is a multiple of

[0082] Further, the UE can determine a number of PSFCH resources available for multiplexing HARQ-ACK or conflict information in a PSFCH transmission as

is a number of cyclic shift pairs for the resource pool provided by sl-

NumMuxCS-Pair and, based on an indication by sl-PSFCH-CandidateResourceType, if sl-PSFCH-CandidateResourceType is configured as and the

PRBs are associated with the starting sub-channel of the corresponding PSSCH

if sl-PSFCH-CandidateResourceType is configured as allocSubCH,

and the PRBs are associated with the sub-channels of the

corresponding PSSCH for conflict information, the corresponding PSSCH is determined based on sl-PSFCH- Occasion

[0083] A UE can determine an index of a PSFCH resource for a PSFCH transmission with HARQ-ACK information in response to a PSSCH reception or with conflict information corresponding to a reserved resource as where P_ID is a physical layer

source ID provided by SCI format 2-A/2-B/2-C [TS 38.212] scheduling the PSSCH reception, or by SCI format 2-A/2-B/2-C with corresponding SCI format 1-A reserving the resource from another UE to be provided with the conflict information. For HARQ-ACK information, M_ID is the identity of the UE receiving the PSSCH as indicated by higher layers if the UE detects a SCI format 2-A with Cast type indicator field value of "01"; otherwise, M_ID is zero. For conflict information, M_ID is zero.

[0084] For a UE procedure for receiving PSFCH with control information, a UE that transmits a PSSCH scheduled by a SCI format 2-A/2-B/2-C that indicates HARQ feedback enabled can attempt to receive associated PSFCHs with HARQ-ACK information according to PSFCH resources. The UE can determine an ACK or a NACK value for HARQ-ACK information provided in each PSFCH resource as described in TS 38.101-4. The UE may not determine both an ACK value and a NACK value at a same time for a PSFCH resource.

[0085] For each PSFCH reception occasion, from a number of PSFCH reception occasions, the UE can generate HARQ-ACK information to report to higher layers. For generating the HARQ- ACK information, the UE can be indicated by a SCI format to perform one or more of the following: if the UE receives a PSFCH associated with a SCI format 2-A with Cast type indicator field value of " 10" or a SCI format 2-C; report to higher layers HARQ-ACK information with same value as a value of HARQ- ACK information that the UE determines from the PSFCH reception; if the UE receives a PSFCH associated with a SCI format 2-A with Cast type indicator field value of "01"; report an ACK value to higher layers if the UE determines an ACK value from at least one PSFCH reception occasion from the number of PSFCH reception occasions in PSFCH resources corresponding to every identity M_ID of UEs that the UE expects to receive corresponding PSSCHs as described in clause 16.3; otherwise, report a NACK value to higher layers; if the PSFCH reception occasion is associated with a SCI format 2-B or a SCI format 2- A with Cast type indicator field value of " 11 " ; report to higher layers an ACK value if the UE determines absence of PSFCH reception for the PSFCH reception occasion; otherwise, report a NACK value to higher layers;

A UE that transmitted SCI format 1-A, indicating one or more reserved resources in a resource pool enabled by sl-InterUE-CoordinationScheme2, attempts to receive associated PSFCH with conflict information in a resource pool with PSFCH resources that the UE determines as described in clause 16.3.0. If the UE determines presence of a resource conflict based on conflict information in a PSFCH reception, the UE reports the resource conflict to higher layers; if sl-SlotLevelResourceExclusion is not provided, the UE reports resources overlapping with a next in time reserved resource indicated by the SCI format 1-A; if sl-SlotLevelResourceExclusion is provided, the UE reports resources in a slot of a next in time reserved resource indicated by the SCI format 1-A.

[0086] In implementations sidelink assistance information can be included in SCI. For instance, considering that sidelink assistance information can include information pertaining to L2 buffer for each LCH priority, a UE may use first stage SCI format and/or second stage SCI format (as defined e.g., in 3GPP TS 38.212 vl7.4.0) for the transmission of sidelink assistance information, such as when a number of bits for the sidelink assistance information transmission is smaller than or equal to a configured threshold. If the number of bits for the sidelink assistance information transmission is larger than a configured threshold, the UE may use a MAC CE for the transmission of sidelink assistance information.

[0087] In implementations CAPC level determination can be considered for reporting CAPC- specific sidelink assistance information. For instance, a UE can determine a CAPC for a TB as a largest of the CAPC values of multiplexed MAC SDUs as the CAPC for a TB when sidelink assistance information is to be reported. According to an alternative implementation, a UE can determine the CAPC for a TB as the lowest of the CAPC values of multiplexed MAC SDUs as the CAPC for a TB when the sidelink assistance information is to be reported. Such implementations can allow for greater flexibility for multiplexing data associated with a larger CAPC value in scenarios where the available data changes between a time of sidelink assistance information transmission and a time of a subsequent data transmission.

[0088] Implementations also provide for triggering sidelink assistance information. For instance, sidelink assistance information can be triggered by an event (e.g., condition), such as:

[0089] Being a recipient of PSSCH transmission, e.g., being a unicast data recipient (DST ID in SCI matches the UE ID);

[0090] Expiry of a timer: a device can be configured with a timer which controls reporting of sidelink assistance information, e.g. for periodic sidelink assistance information reporting. Whenever the timer expires, sidelink assistance information is triggered. The timer can be immediately restarted, or can be restarted by an indication;

[0091] When a device has available sidelink resources and a sidelink grant size is larger than a size required for the transmission of data available for a selected destination and a sidelink assistance information. For instance, sidelink assistance information can be transmitted fully or partly instead of padding, e.g., no padding is required or less padding is required to fill the available sidelink resources;

[0092] When a highest LCH priority for which data is available has changed compared to a most recently reported LCH priority. For instance, in such an event a prohibit timer may be considered expired; [0093] When the highest CAPC (e.g., lowest CAPC value) for available data for transmission has changed compared with a most recently reported CAPC. According to implementations, sidelink assistance information may be transmitted if the CAPC of available data is above or below a CAPC threshold and/or above or below an LCH priority threshold;

[0094] Based on N LBT failures. For example, N LBT failures on transmission resources within a past M slot duration. N and M can be configured by RRC (e.g., by network, gNB) and/or specific to a resource pool configuration According to implementations, the counter N is reset (e.g., set to zero) if sidelink assistance information is triggered by this mechanism.

[0095] In implementations triggering of sidelink assistance information can occur by implicit and/or explicit requests. For instance, a sidelink assistance information request can be triggered by one or more of the following:

[0096] Reception of a COT sharing indicator. When a sidelink assistance information request is enabled by RRC, UE that are potential recipients of COT sharing may transmit sidelink assistance information in response to reception of a COT sharing indicator;

[0097] If sidelink assistance information request is enabled by RRC, a COT sharing indicator may explicitly trigger a sidelink assistance information request from a UE;

[0098] Reception of a sidelink PSSCH transmission, such as being a unicast recipient (e.g., DST ID in SCI matches a UE ID);

[0099] Positive request bit (explicit), e.g. in SCI format 1-A such as a conflict information receiver flag. For instance, consider the following:

[0100] SCI format 1-A: SCI format 1-A can be used for the scheduling of PSSCH and 2^nd-stage- SCI on PSSCH. The following information can be transmitted by means of the SCI format 1-A:

[0101] Conflict information receiver flag - 0 or 1 bit;

[0102] 1 bit if higher layer parameter sl-IndicationUE-B is configured to 'enabled', where the bit value of 0 indicates that the UE cannot be a UE to receive conflict information and the bit value of 1 indicates that the UE can be a UE to receive conflict information as defined in Clause 16.3.0 of [TS 38.213]; [0103] 0 bit otherwise.

[0104] Sidelink assistance information request flag - a value of 0 indicates that no assistance data is being requested, and a value of 1 indicates that assistance data is being requested.

[0105] SCI format 2: SCI format 2-A can be used for the decoding of PSSCH, with HARQ operation when HARQ-ACK information includes ACK or NACK, when HARQ-ACK information includes NACK, or when there is no feedback of HARQ-ACK information.

[0106] The following information can be transmitted by means of the SCI format 2-A:

[0107] HARQ process number - 4 bits.

[0108] New data indicator - 1 bit.

[0109] Redundancy version.

[0110] Source ID - 8 bits.

[0111] Destination ID - 16 bits.

[0112] HARQ feedback enabled/disabled indicator - 1 bit.

[0113] Cast type indicator - 2 bits.

[0114] CSI request - 1 bit.

[0115] Assistance information request flag: a value of 0 can indicate that no sidelink assistance data is being requested and a value of 1 can indicate that sidelink assistance data is being requested.

[0116] SCI format 2-C can be used for the decoding of PSSCH, providing inter-UE coordination information, and requesting inter-UE coordination information. SCI format 2-C can be used for unicast. The following information can be transmitted by means of the SCI format 2-C:

[0117] CSI request - 1 bit

[0118] Assistance information request flag - a value of 0 can indicate that no assistance data is being requested and a value of 1 can indicate that assistance data is being requested.

[0119] Providing/Requesting indicator - 1 bit, where value 0 indicates SCI format 2-C is used for providing inter-UE coordination information and value 1 indicates SCI format 2-C is used for requesting inter-UE coordination information. If the 'Providing/Requesting indicator' field is set to 0, remaining fields can be set as follows:

Resource combinations bits

where: and is the number of entries in the higher layer

parameter sl-ResourceReservePeriodList, if higher layer parameter sl-MultiReserveResource is configured; 7 = 0 otherwise;

"

is the number of subchannels in a resource pool provided by the higher layer parameter sl-NumSubchannel,'

First resource location - 8 bits;

Reference slot location

Resource set type - 1 bit, where value 0 indicates preferred resource set and value 1 indicates non-preferred resource set;

Lowest subChannel indices

[0120] If the 'Providing/Requesting indicator' field is set to 1, the remaining fields can be set as follows:

Priority - 3 bits. Value '000' of Priority field corresponds to priority value '1', value '001' of Priority field corresponds to priority value '2', and so on;

Number of subchannels

Resource reservation period bits, where is the number of

entries in the higher layer parameter sl-ResourceReservePeriodList, if higher layer parameter sl-MultiReserveResource is configured; 0 bit otherwise;

Resource selection window location bits;

Resource set type - 1 bit, where value 0 indicates a request for inter-UE coordination information providing preferred resource set and value 1 indicates a request for inter-UE coordination information providing non-preferred resource set, if higher layer parameter sl- DetermineResourceType is configured to 'ueb'; otherwise, 0 bit;

Padding bits.

[0121] In implementations and according to a variant for explicit signaling in a first stage or second stage SCI format, the presence (or alternatively the size: 0 or 1 bit) can be configurable by a higher layer parameter. Further, a MAC-CE can include a bit/field (such as similar to first or second stage SCI format), e.g. in a COT sharing indication MAC CE.

[0122] In implementations, when sidelink assistance information is triggered (e.g. by being a recipient of a PSSCH transmission), a prohibit timer is started. While the prohibit timer is running (e.g. not expired), a new sidelink assistance information trigger for the same SRC-DST pair can be ignored. Alternatively or additionally, while the prohibit timer is running, a triggered sidelink assistance information is not transmitted.

[0123] In implementations, when sidelink assistance information is triggered (e.g. by being a recipient of a PSSCH transmission), a scheduling request (SR) is triggered. Triggering of a scheduling request is particularly beneficial if the device where the sidelink assistance information is triggered does not have sufficient SL-SCH resources available to accommodate the transmission of the sidelink assistance information. Triggering of a SR is particularly applicable if the device where the sidelink assistance information is triggered is configured with Sidelink resource allocation mode 1. The corresponding SR is transmitted to a network entity, e.g. a gNB, so that the gNB can subsequently allocate resources to the device for transmission of the sidelink assistance information. These allocated resources may be resources used for PC5 transmission by the device so that the sidelink information can be transmitted directly to other devices without having to go through a network entity. In implementations the sidelink assistance information transmission is mapped to a specific SR configuration for all PC5-RRC connections. The SR configuration of the triggered sidelink assistance information transmission is considered as corresponding SR configuration for the triggered SR. [0124] FIG. 9 illustrates an example of a block diagram 900 of a device 902 (e.g., an apparatus) that supports sidelink assistance information for sidelink communication in accordance with aspects of the present disclosure. The device 902 may be an example of UE 104 as described herein. The device 902 may support wireless communication with one or more network entities 102, UEs 104, or any combination thereof. The device 902 may include components for bi-directional communications including components for transmitting 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., buses).

[0125] 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 as described herein. For example, the processor 904, the memory 906, the transceiver 908, or various combinations or components thereof may support a method for performing one or more of the operations described herein.

[0126] In some implementations, the processor 904, the memory 906, the transceiver 908, 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 904 and the memory 906 coupled with the processor 904 may be configured to perform one or more of the functions described herein (e.g., executing, by the processor 904, instructions stored in the memory 906). In the context of UE 104, for example, the transceiver 908 and the processor coupled 904 coupled to the transceiver 908 are configured to cause the UE 104 to perform the various described operations and/or combinations thereof.

[0127] For example, the processor 904 and/or the transceiver 908 may support wireless communication at the device 902 in accordance with examples as disclosed herein. For instance, the processor 904 and/or the transceiver 908 may be configured as and/or otherwise support a means to generate a sidelink assistance information indication pertaining to data available for transmission from the first apparatus to a second apparatus; and transmit the sidelink assistance information indication to a third apparatus.

[0128] Further, in some implementations, the sidelink assistance information indication includes identification information for the first apparatus and the second apparatus; the sidelink assistance information indication includes an available data indicator indicating whether the first apparatus has data to transmit to the second apparatus; the sidelink assistance information indication includes an available data indicator indicating an amount of data the first apparatus has to transmit to the second apparatus; the sidelink assistance information indication includes an indication of priority information for data to be transmitted from the first apparatus to the second apparatus; the indication of priority information includes one or more of LCP information or CAPC information; the processor is configured to cause the first apparatus to transmit the sidelink assistance information via one or more of resource pool configuration information, RRC, or physical layer signaling.

[0129] Further, in some implementations, the processor is configured to cause the first apparatus to receive cast type information via one or more of resource pool configuration information, RRC, or physical layer signaling, the cast type information including an indication of one or more cast types for which the sidelink assistance information is to be generated; the processor is configured to cause the first apparatus to receive cast type information including one or more of: information indicating that an available data indicator per cast type is to be transmitted; or information indicating that an aggregated available data indicator for multiple cast types is to be transmitted; the processor is configured to cause the first apparatus to transmit the sidelink assistance information via a CSI MAC CE.

[0130] Further, in some implementations, the first apparatus includes a data transmission source, the second apparatus includes a data transmission destination of multiple data transmission destinations, and the sidelink assistance information includes an available data indicator indicating an amount of data that the first apparatus has to transmit to each of the multiple data transmission destinations; the processor is configured to cause the apparatus to transmit the sidelink assistance information via a PSFCH; the processor is configured to cause the apparatus to transmit the sidelink assistance information via SCI; the processor is configured to cause the apparatus to: determine a highest CAPC value for multiplexed service data units (SDU); and select the highest CAPC value for a TB associated with transmission of the sidelink assistance information; the processor is configured to cause the apparatus to: determine a lowest CAPC value for multiplexed service data units (SDU); and select the lowest CAPC value for a TB associated with transmission of the sidelink assistance information.

[0131] In a further example, the processor 904 and/or the transceiver 908 may support wireless communication at the device 902 in accordance with examples as disclosed herein. The processor 904 and/or the transceiver 908, for instance, may be configured as or otherwise support a means for generating, by a first apparatus, a sidelink assistance information indication pertaining to data available for transmission from the first apparatus to a second apparatus; and transmitting the sidelink assistance information indication to a third apparatus.

[0132] Further, in some implementations, the sidelink assistance information indication includes identification information for the first apparatus and the second apparatus; the sidelink assistance information indication includes an available data indicator indicating whether the first apparatus has data to transmit to the second apparatus; the sidelink assistance information indication includes an available data indicator indicating an amount of data the first apparatus has to transmit to the second apparatus; the sidelink assistance information indication includes an indication of priority information for data to be transmitted from the first apparatus to the second apparatus; the indication of priority information includes one or more of LCP information or CAPC information; transmitting the sidelink assistance information via one or more of resource pool configuration information, RRC, or physical layer signaling.

[0133] Further, in some implementations, processor 904 and/or the transceiver 908 may be configured as or otherwise support a means for receiving cast type information via one or more of resource pool configuration information, RRC, or physical layer signaling, the cast type information including an indication of one or more cast types for which the sidelink assistance information is to be generated; receiving cast type information including one or more of information indicating that an available data indicator per cast type is to be transmitted; or information indicating that an aggregated available data indicator for multiple cast types is to be transmitted; transmitting the sidelink assistance information via a CSI MAC CE; the first apparatus includes a data transmission source, the second apparatus includes a data transmission destination of multiple data transmission destinations, and the sidelink assistance information includes an available data indicator indicating an amount of data that the first apparatus has to transmit to each of the multiple data transmission destinations; transmitting the sidelink assistance information via a PSFCH; transmitting the sidelink assistance information via SCI; determining a highest CAPC value for multiplexed service data units (SDU); and selecting the highest CAPC value for a TB associated with transmission of the sidelink assistance information; determining a lowest CAPC value for multiplexed service data units (SDU); and selecting the lowest CAPC value for a TB associated with transmission of the sidelink assistance information.

[0134] For example, the processor 904 and/or the transceiver 908 may support wireless communication at the device 902 in accordance with examples as disclosed herein. For instance, the processor 904 and/or the transceiver 908 may be configured as and/or otherwise support a means to generate, based at least in part on a trigger event, a sidelink assistance information indication pertaining to data available for transmission from the first apparatus to a second apparatus; and transmit the sidelink assistance information indication to a third apparatus.

[0135] Further, in some implementations, the trigger event includes the first apparatus receiving PSSCH transmission; the trigger event includes an expiry of a timer; the trigger event includes that the first apparatus has data to transmit and a sidelink grant with a data transmission capacity that is larger than a size of the data to transmit; the trigger event includes a change in LCP; the trigger event includes a change in CAPC; the trigger event includes exceeding a threshold number of LBT failures; the trigger event includes a reception of a COT sharing indicator; the trigger event includes a reception of a request for sidelink assistance information.

[0136] Further, in some implementations, the processor is configured to cause the apparatus to: determine, based at least in part on a second trigger event, that a second sidelink assistance information indication is to be generated; and delay generation of the second sidelink assistance information indication until expiry of a timer; the processor is configured to cause the apparatus to: determine, based at least in part on a second trigger event, that a second sidelink assistance information indication is to be generated; and ignore the second trigger event based at least in part on a timer not being expired; the second apparatus includes the third apparatus; the first apparatus includes a first user equipment (UE), the second apparatus includes a second UE, and the third apparatus includes one or more of the second UE or a base station; receive, from the second UE, sidelink assistance information including an indication that the second UE has data to transmit to the first UE; and initiate, based at least in part on the sidelink assistance information, COT sharing between the first UE and the second UE for transmission of the data from the second UE to the first

UE.

[0137] In a further example, the processor 904 and/or the transceiver 908 may support wireless communication at the device 902 in accordance with examples as disclosed herein. The processor 904 and/or the transceiver 908, for instance, may be configured as or otherwise support a means for generating, by a first apparatus and based at least in part on a trigger event, a sidelink assistance information indication pertaining to data available for transmission from the first apparatus to a second apparatus; and transmitting the sidelink assistance information indication to a third apparatus.

[0138] Further, in some implementations, the trigger event includes the first apparatus receiving PSSCH transmission; the trigger event includes an expiry of a timer; the trigger event includes that the first apparatus has data to transmit and a sidelink grant with a data transmission capacity that is larger than a size of the data to transmit; the trigger event includes a change in LCP; the trigger event includes a change in CAPC; the trigger event includes exceeding a threshold number of LBT failures; the trigger event includes a reception of a COT sharing indicator; the trigger event includes a reception of a request for sidelink assistance information; determining, based at least in part on a second trigger event, that a second sidelink assistance information indication is to be generated; and delaying generation of the second sidelink assistance information indication until expiry of a timer; determining, based at least in part on a second trigger event, that a second sidelink assistance information indication is to be generated; and ignoring the second trigger event based at least in part on a timer not being expired; the second apparatus includes the third apparatus; the first apparatus includes a first user equipment (UE), the second apparatus includes a second UE, and the third apparatus includes one or more of the second UE or a base station.

[0139] For example, the processor 904 and/or the transceiver 908 may support wireless communication at the device 902 in accordance with examples as disclosed herein. For instance, the processor 904 and/or the transceiver 908 may be configured as and/or otherwise support a means to receive, from the second UE, sidelink assistance information including an indication that the second UE has data to transmit to the first UE; and initiate, based at least in part on the sidelink assistance information, COT sharing between the first UE and the second UE for transmission of the data from the second UE to the first UE.

[0140] In a further example, the processor 904 and/or the transceiver 908 may support wireless communication at the device 902 in accordance with examples as disclosed herein. The processor 904 and/or the transceiver 908, for instance, may be configured as or otherwise support a means for receiving, from the second UE, sidelink assistance information including an indication that the second UE has data to transmit to the first UE; and initiating, based at least in part on the sidelink assistance information, COT sharing between the first UE and the second UE for transmission of the data from the second UE to the first UE.

[0141] The processor 904 of the device 902, such as a UE 104, may support wireless communication in accordance with examples as disclosed herein. The processor 904 includes at least one controller coupled with at least one memory, and the at least one controller is configured to and/or operable to cause the processor to generate, based at least in part on a trigger event, a sidelink assistance information indication pertaining to data available for transmission from a first UE to a second apparatus; and transmit the sidelink assistance information indication to a third apparatus. Further, the at least one controller is configured to and/or operable to cause the processor to generate an indication for triggering sidelink assistance information for data transmission from a second apparatus; and transmit the indication of sidelink assistance information to one or more of the second apparatus or a third apparatus. Further, the at least one controller is configured to and/or operable to cause the processor to perform any of the various operations described herein, such as with reference to a UE 104 and/or the device 902.

[0142] 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, a 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., the memory 906) to cause the device 902 to perform various functions of the present disclosure. [0143] The memory 906 may include random access memory (RAM) and read-only memory (ROM). The memory 906 may store computer-readable, computer-executable code including 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 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 functions described herein. In some implementations, the memory 906 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.

[0144] The I/O controller 910 may manage input and output signals for the device 902. The I/O controller 910 may also manage peripherals not integrated into the device M02. In some implementations, the I/O controller 910 may represent a physical connection or port to an external peripheral. In some implementations, the I/O controller 910 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 910 may be implemented as part of a processor, such as the processor M08. In some implementations, a user may interact with the device 902 via the I/O controller 910 or via hardware components controlled by the I/O controller 910.

[0145] 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 (e.g., multiple antennas), including multiple antenna panels or antenna arrays, which may be capable of concurrently transmitting or receiving multiple wireless transmissions. The transceiver 908 may communicate bi-directionally, via the one or more antennas 912, wired, or wireless links as described herein. For example, the transceiver 908 may represent a wireless transceiver and may communicate bi-directionally with another wireless transceiver. The transceiver 908 may also include a modem to modulate the packets, to provide the modulated packets to one or more antennas 912 for transmission, and to demodulate packets received from the one or more antennas 912.

[0146] FIG. 10 illustrates an example of a block diagram 1000 of a device 1002 (e.g., an apparatus) that supports sidelink assistance information for sidelink communication in accordance with aspects of the present disclosure. The device 1002 may be an example of a network entity 102 and/or a UE 104 as described herein. The device 1002 may support wireless communication with one or more network entities 102, UEs 104, or any combination thereof. The device 1002 may include components for bi-directional communications including components for transmitting and receiving communications, such as a processor 1004, a memory 1006, a transceiver 1008, and an I/O controller 1010. 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).

[0147] The processor 1004, the memory 1006, the transceiver 1008, 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 1004, the memory 1006, the transceiver 1008, or various combinations or components thereof may support a method for performing one or more of the operations described herein.

[0148] In some implementations, the processor 1004, the memory 1006, the transceiver 1008, 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 1004 and the memory 1006 coupled with the processor 1004 may be configured to perform one or more of the functions described herein (e.g., executing, by the processor 1004, instructions stored in the memory 1006). In the context of network entity 102, for example, the transceiver 1008 and the processor 1004 coupled to the transceiver 1008 are configured to cause the network entity 102 to perform the various described operations and/or combinations thereof.

[0149] For example, the processor 1004 and/or the transceiver 1008 may support wireless communication at the device 1002 in accordance with examples as disclosed herein. For instance, the processor 1004 and/or the transceiver 1008 may be configured as or otherwise support a means to receive a sidelink assistance information indication pertaining to data available for transmission from a second apparatus to a third apparatus; and configure channel occupancy time sharing logic of the first apparatus based at least in part on the sidelink assistance information indication.

[0150] Further, in some implementations, the sidelink assistance information indication includes an available data indicator indicating an amount of data the second apparatus has to transmit to the third apparatus, and the processor is configured to cause the first apparatus to determine whether to initiate channel occupancy time sharing with the second apparatus based at least in part on the amount of data; the sidelink assistance information indication includes an available data indicator indicating a data priority of data the second apparatus has to transmit to the third apparatus, and the processor is configured to cause the first apparatus to determine whether to initiate channel occupancy time sharing with the second apparatus based at least in part on the data priority; the sidelink assistance information indication includes an indication of a cast type for data transmission from the second apparatus to the third apparatus, and the processor is configured to cause the first apparatus to determine whether to initiate channel occupancy time sharing with the second apparatus based at least in part on the cast type; the processor is configured to cause the first apparatus to: maintain a list of source apparatus, including the second apparatus, from which data transmission is receivable by the first apparatus; and initiate channel occupancy time sharing with the second apparatus based at least in part on a priority indication of the second apparatus in the list of source apparatus.

[0151] In a further example, the processor 1004 and/or the transceiver 1008 may support wireless communication at the device 1002 in accordance with examples as disclosed herein. The processor 1004 and/or the transceiver 1008, for instance, may be configured as or otherwise support a means for receiving, at a first apparatus, a sidelink assistance information indication pertaining to data available for transmission from a second apparatus to a third apparatus; and configuring channel occupancy time sharing logic of the first apparatus based at least in part on the sidelink assistance information indication.

[0152] Further, in some implementations, the sidelink assistance information indication includes an available data indicator indicating an amount of data the second apparatus has to transmit to the third apparatus, and the method further includes determining whether to initiate channel occupancy time sharing with the second apparatus based at least in part on the amount of data; the sidelink assistance information indication includes an available data indicator indicating a data priority of data the second apparatus has to transmit to the third apparatus, and the method further includes determining whether to initiate channel occupancy time sharing with the second apparatus based at least in part on the data priority; the sidelink assistance information indication includes an indication of a cast type for data transmission from the second apparatus to the third apparatus, and the method further includes determining whether to initiate channel occupancy time sharing with the second apparatus based at least in part on the cast type; maintaining a list of source apparatus, including the second apparatus, from which data transmission is receivable by the first apparatus; and initiating channel occupancy time sharing with the second apparatus based at least in part on a priority indication of the second apparatus in the list of source apparatus.

[0153] For example, the processor 1004 and/or the transceiver 1008 may support wireless communication at the device 1002 in accordance with examples as disclosed herein. For instance, the processor 1004 and/or the transceiver 1008 may be configured as or otherwise support a means to generate an indication for triggering sidelink assistance information for data transmission from a second apparatus; and transmit the indication of sidelink assistance information to one or more of the second apparatus or a third apparatus.

[0154] Further, in some implementations, the processor is configured to cause the apparatus to transmit the indication of sidelink assistance information via SCI; the indication of sidelink assistance information includes a COT sharing indicator; the indication of sidelink assistance information includes a sidelink assistance information request; the first apparatus includes a first user equipment (UE), the second apparatus includes a second UE.

[0155] In a further example, the processor 1004 and/or the transceiver 1008 may support wireless communication at the device 1002 in accordance with examples as disclosed herein. The processor 1004 and/or the transceiver 1008, for instance, may be configured as or otherwise support a means for generating an indication for triggering sidelink assistance information for data transmission from a second apparatus; and transmitting the indication of sidelink assistance information to one or more of the second apparatus or a third apparatus.

[0156] Further, in some implementations, the processor 1004 and/or the transceiver 1008 may be configured as or otherwise support a means for transmitting the indication of sidelink assistance information via SCI; the indication of sidelink assistance information includes a COT sharing indicator; the indication of sidelink assistance information includes a sidelink assistance information request.

[0157] The processor 1004 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 1004 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 1004. The processor 1004 may be configured to execute computer- readable instructions stored in a memory (e.g., the memory 1006) to cause the device 1002 to perform various functions of the present disclosure.

[0158] The memory 1006 may include random access memory (RAM) and read-only memory (ROM). The memory 1006 may store computer-readable, computer-executable code including instructions that, when executed by the processor 1004 cause the device 1002 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 1004 but may cause a computer (e.g., when compiled and executed) to perform functions described herein. In some implementations, the memory 1006 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.

[0159] The I/O controller 1010 may manage input and output signals for the device 1002. The I/O controller 1010 may also manage peripherals not integrated into the device M02. In some implementations, the I/O controller 1010 may represent a physical connection or port to an external peripheral. In some implementations, the I/O controller 1010 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 RO controller 1010 may be implemented as part of a processor, such as the processor M06. In some implementations, a user may interact with the device 1002 via the I/O controller 1010 or via hardware components controlled by the I/O controller 1010. [0160] In some implementations, the device 1002 may include a single antenna 1012. However, in some other implementations, the device 1002 may have more than one antenna 1012 (e.g., multiple antennas), including multiple antenna panels or antenna arrays, which may be capable of concurrently transmitting or receiving multiple wireless transmissions. The transceiver 1008 may communicate bi-directionally, via the one or more antennas 1012, wired, or wireless links as described herein. For example, the transceiver 1008 may represent a wireless transceiver and may communicate bi-directionally with another wireless transceiver. The transceiver 1008 may also include a modem to modulate the packets, to provide the modulated packets to one or more antennas 1012 for transmission, and to demodulate packets received from the one or more antennas 1012.

[0161] FIG. 11 illustrates a flowchart of a method 1100 that supports sidelink assistance information for sidelink communication in accordance with aspects of the present disclosure. The operations of the method 1100 may be implemented by a device or its components as described herein. For example, the operations of the method 1100 may be performed by a UE 104 as described with reference to FIGs. 1 through 10. 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.

[0162] At 1102, the method may include generating, by a first apparatus, a sidelink assistance information indication pertaining to data available for transmission from the first apparatus to a second apparatus. The operations of 1102 may be performed in accordance with examples as described herein. In some implementations, aspects of the operations of 1102 may be performed by a device as described with reference to FIG. 1.

[0163] At 1104, the method may include transmitting the sidelink assistance information indication to a third apparatus. The operations of 1104 may be performed in accordance with examples as described herein. In some implementations, aspects of the operations of 1104 may be performed by a device as described with reference to FIG. 1.

[0164] FIG. 12 illustrates a flowchart of a method 1200 that supports sidelink assistance information for sidelink communication in accordance with aspects of the present disclosure. The operations of the method 1200 may be implemented by a device or its components as described herein. For example, the operations of the method 1200 may be performed by a UE 104 as described with reference to FIGs. 1 through 10. 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.

[0165] At 1202, the method may include generating, by a first apparatus and based at least in part on a trigger event, a sidelink assistance information indication pertaining to data available for transmission from the first apparatus to a second apparatus. The operations of 1202 may be performed in accordance with examples as described herein. In some implementations, aspects of the operations of 1202 may be performed by a device as described with reference to FIG. 1.

[0166] At 1204, the method may include transmitting the sidelink assistance information indication to a third apparatus. The operations of 1204 may be performed in accordance with examples as described herein. In some implementations, aspects of the operations of 1204 may be performed by a device as described with reference to FIG. 1.

[0167] FIG. 13 illustrates a flowchart of a method 1300 that supports sidelink assistance information for sidelink communication in accordance with aspects of the present disclosure. The operations of the method 1300 may be implemented by a device or its components as described herein. For example, the operations of the method 1300 may be performed by a UE 104 as described with reference to FIGs. 1 through 10. 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.

[0168] At 1302, the method may include receiving, from the second UE, sidelink assistance information comprising an indication that the second UE has data to transmit to the first UE. The operations of 1302 may be performed in accordance with examples as described herein. In some implementations, aspects of the operations of 1302 may be performed by a device as described with reference to FIG. 1. [0169] At 1304, the method may include initiating, based at least in part on the sidelink assistance information, COT sharing between the first UE and the second UE for transmission of the data from the second UE to the first UE. The operations of 1304 may be performed in accordance with examples as described herein. In some implementations, aspects of the operations of 1304 may be performed by a device as described with reference to FIG. 1.

[0170] FIG. 14 illustrates a flowchart of a method 1400 that supports sidelink assistance information for sidelink communication in accordance with aspects of the present disclosure. The operations of the method 1400 may be implemented by a device or its components as described herein. For example, the operations of the method 1400 may be performed by a network entity 102 and/or a UE 104 as described with reference to FIGs. 1 through 10. 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.

[0171] At 1402, the method may include receiving, at a first apparatus, a sidelink assistance information indication pertaining to data available for transmission from a second apparatus to a third apparatus. The operations of 1402 may be performed in accordance with examples as described herein. In some implementations, aspects of the operations of 1402 may be performed by a device as described with reference to FIG. 1.

[0172] At 1404, the method may include configuring channel occupancy time sharing logic of the first apparatus based at least in part on the sidelink assistance information indication. The operations of 1404 may be performed in accordance with examples as described herein. In some implementations, aspects of the operations of 1404 may be performed by a device as described with reference to FIG. 1.

[0173] FIG. 15 illustrates a flowchart of a method 1500 that supports sidelink assistance information for sidelink communication in accordance with aspects of the present disclosure. The operations of the method 1500 may be implemented by a device or its components as described herein. For example, the operations of the method 1500 may be performed by a network entity 102 and/or a UE 104 as described with reference to FIGs. 1 through 10. 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.

[0174] At 1502, the method may include generating an indication for triggering sidelink assistance information for data transmission from a second apparatus. The operations of 1502 may be performed in accordance with examples as described herein. In some implementations, aspects of the operations of 1502 may be performed by a device as described with reference to FIG. 1.

[0175] At 1504, the method may include transmitting the indication of sidelink assistance information to one or more of the second apparatus or a third apparatus. The operations of 1504 may be performed in accordance with examples as described herein. In some implementations, aspects of the operations of 1504 may be performed by a device as described with reference to FIG. 1.

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

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

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

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

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

[0181] 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 (e.g., 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.

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

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

[0184] 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

1. A first 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 first UE to: generate, based at least in part on a trigger event, a sidelink assistance information indication pertaining to data available for transmission from the first UE to a second apparatus; and transmit the sidelink assistance information indication to a third apparatus.

2. The first UE of claim 1, wherein the trigger event comprises the first UE receiving physical sidelink shared channel (PSSCH) transmission.

3. The first UE of claim 1 , wherein the trigger event comprises an expiry of a timer.

4. The first UE of claim 1, wherein the trigger event comprises that the first UE has data to transmit and a sidelink grant with a data transmission capacity that is larger than a size of the data to transmit.

5. The first UE of claim 1, wherein the trigger event comprises a change in logical channel priority (LCP).

6. The first UE of claim 1 , wherein the trigger event comprises a change in channel access priority class (CAPC).

7. The first UE of claim 1, wherein the trigger event comprises exceeding a threshold number of listen before talk (LBT) failures.

8. The first UE of claim 1, wherein the trigger event comprises a reception of a channel occupancy time (COT) sharing indicator.

9. The first UE of claim 1, wherein the trigger event comprises a reception of a request for sidelink assistance information.

10. The first UE of claim 1, wherein the at least one processor is configured to cause the first UE to: determine, based at least in part on a second trigger event, that a second sidelink assistance information indication is to be generated; and delay generation of the second sidelink assistance information indication until expiry of a timer.

11. The first UE of claim 1, wherein the at least one processor is configured to cause the first UE to: determine, based at least in part on a second trigger event, that a second sidelink assistance information indication is to be generated; and ignore the second trigger event based at least in part on a timer not being expired.

12. The first UE of claim 1, wherein the second apparatus comprises the third apparatus.

13. The first UE of claim 1, wherein the second apparatus comprises a second UE, and the third apparatus comprises one or more of the second UE or a base station.

14. A first 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 first UE to: generate an indication for triggering sidelink assistance information for data transmission from a second apparatus; and transmit the indication of sidelink assistance information to one or more of the second apparatus or a third apparatus.

15. The first UE of claim 14, wherein the at least one processor is configured to cause the first UE to transmit the indication of sidelink assistance information via sidelink control information (SCI).

16. The first UE of claim 14, wherein the indication of sidelink assistance information comprises a channel occupancy time (COT) sharing indicator.

17. The first UE of claim 14, wherein the indication of sidelink assistance information comprises a sidelink assistance information request.

18. The first UE of claim 14, wherein the second apparatus comprises a second UE, and the at least one processor is configured to cause the first UE to: receive, from the second UE, sidelink assistance information comprising an indication that the second UE has data to transmit to the first UE; and initiate, based at least in part on the sidelink assistance information, channel occupancy time (COT) sharing between the first UE and the second UE for transmission of the data from the second UE to the first UE.

19. A processor for wireless communication, comprising: at least one controller coupled with at least one memory and configured to cause the processor to: generate, based at least in part on a trigger event, a sidelink assistance information indication pertaining to data available for transmission from a first UE to a second apparatus; and transmit the sidelink assistance information indication to a third apparatus.

20. A processor for wireless communication, comprising: at least one controller coupled with at least one memory and configured to cause the processor to: generate an indication for triggering sidelink assistance information for data transmission from a second apparatus; and transmit the indication of sidelink assistance information to one or more of the second apparatus or a third apparatus.