User equipment scheduling assistance for mode 1 sidelink communication

Abstract

Methods, systems, and devices for wireless communication are described. In some examples, a user equipment (UE) may send scheduling assistance information (SAI) indicating a first set of sidelink resources for sidelink communications by the UE to a network entity via an uplink communication link. The UE may determine the first set of sidelink resources based on monitoring sidelink control information (SCI) from one or more other UEs, based on coordination messages received from one or more other UEs, or based on both. The UE may receive, from the network entity, a scheduling message that allocates a second set of sidelink resources for the sidelink communication by the UE based on the first set of sidelink resources indicated via the SAI. The UE may send a sidelink message to another UE via the second set of sidelink resources allocated by the scheduling message.

Description

Technical Field

[0001] The following involves wireless communications, including user equipment (UE) scheduling assistance for mode 1 side link communications. Background Art

[0002] Wireless communication systems are widely deployed to provide various types of communication content, such as voice, video, packet data, messaging, broadcast, etc. These systems may be able to support communication with multiple users by sharing available system resources (e.g., time, frequency, and power). Examples of such multiple access systems include fourth generation (4G) systems (such as long term evolution (LTE) systems, advanced LTE (LTE-A) systems, or LTE-A Pro systems) and fifth generation (5G) systems (which may be referred to as new radio (NR) systems). These systems may employ techniques such as code division multiple access (CDMA), time division multiple access (TDMA), frequency division multiple access (FDMA), orthogonal FDMA (OFDMA), or discrete Fourier transform spread orthogonal frequency division multiplexing (DFT-S-OFDM). A wireless multiple access communication system may include one or more base stations, each of which supports wireless communication of communication devices, which may be referred to as user equipment (UE).

[0003] In some wireless communication systems, a UE communicating on a sidelink may perform a channel sensing procedure to identify resources that may be used for sidelink transmission of a sidelink message. In some other systems, a network entity may allocate resources to a UE for sending a sidelink message. In such cases, the network entity may schedule sidelink communications by one or more UEs in a cell supported by the network entity. Summary of the invention

[0004] The described techniques relate to improved methods, systems, devices, and apparatuses that support user equipment (UE) scheduling assistance for mode 1 sidelink communications. For example, the described techniques allow a UE to send sidelink scheduling assistance information (SAI) to a network entity to assist in scheduling sidelink communications performed by the UE. The SAI may indicate a set of sidelink resources that are preferred (e.g., available) or not preferred (e.g., reserved or associated with relatively high interference) for sidelink transmissions performed by the UE. The UE may determine a set of sidelink resources based on a sidelink channel sensing procedure performed by the UE, based on inter-UE coordination information received from another UE, or based on both. For example, the UE, one or more other UEs, or both may monitor a sidelink resource pool for sidelink control information (SCI) sent by other UEs. The SCI may indicate sidelink resources reserved for transmissions performed by other UEs. The UE may indicate resource preference information (e.g., non-preferred resources from reserved resources or preferred resources from resources not indicated as reserved by SAI), or the UE may receive an inter-UE coordination message indicating resource preference information (e.g., resources from reserved resources or from resources not indicated as reserved) and the UE may forward the indication via SAI, or both. Thus, SAI may be based on such sidelink channel sensing procedures. The network entity may send a scheduling message to the UE to grant sidelink resources for sidelink transmission by the UE based on the resource set indicated via SAI (e.g., preferred or non-preferred resources). BRIEF DESCRIPTION OF THE DRAWINGS

[0005] Figure 1 An example of a wireless communication system that supports user equipment (UE) scheduling assistance for mode 1 side link communication is illustrated in accordance with one or more aspects of the present disclosure.

[0006] Figure 2 An example of a wireless communication system that supports UE scheduling assistance for mode 1 side link communication is illustrated in accordance with one or more aspects of the present disclosure.

[0007] Figure 3 An example of a side link resource reservation scheme that supports UE scheduling assistance for Mode 1 side link communication is exemplified in accordance with one or more aspects of the present disclosure.

[0008] Figure 4 An example of a process flow supporting UE scheduling assistance for mode 1 side link communication is illustrated in accordance with one or more aspects of the present disclosure.

[0009] Figure 5 and Figure 6 A block diagram of a device supporting UE scheduling assistance for mode 1 side link communication is shown in accordance with one or more aspects of the present disclosure.

[0010] Figure 7 A block diagram of a communication manager supporting UE scheduling assistance for mode 1 side link communication is shown in accordance with one or more aspects of the present disclosure.

[0011] Figure 8 A diagram of a system including a device supporting UE scheduling assistance for mode 1 side link communication is shown in accordance with one or more aspects of the present disclosure.

[0012] Fig. 9 and Fig.10 A block diagram of a device supporting UE scheduling assistance for mode 1 side link communication is shown in accordance with one or more aspects of the present disclosure.

[0013] Fig.11 A block diagram of a communication manager supporting UE scheduling assistance for mode 1 side link communication is shown in accordance with one or more aspects of the present disclosure.

[0014] Fig.12 A diagram of a system including a device supporting UE scheduling assistance for mode 1 side link communication is shown in accordance with one or more aspects of the present disclosure.

[0015] Figures 13 to 16 A flowchart illustrating a method of supporting UE scheduling assistance for mode 1 side link communication according to one or more aspects of the present disclosure is shown. DETAILED DESCRIPTION

[0016] Some wireless communication systems may support autonomous sidelink resource allocation modes (e.g., mode 2 sidelink communications), in which a user equipment (UE) may perform a sidelink channel sensing procedure to determine available sidelink resources for sidelink transmissions performed by the UE. In some examples, the sidelink channel sensing procedure performed by the UE may be assisted by an inter-UE coordination message from a receiving UE. The inter-UE coordination message may indicate the resources preferred or not preferred by the receiving UE for sidelink communications. In some other examples, the wireless communication system may support different sidelink resource allocation modes (e.g., mode 1 sidelink communications), in which a network entity may allocate resources to a UE for sidelink transmissions within a cell supported by the network entity. The network entity may determine which sidelink resources are available based on scheduling information at the network entity (e.g., a previous resource grant or allocation performed by the network entity). However, the network entity may not monitor or receive scheduling information sent by other neighboring network entities supporting other cells, which may result in conflicts between sidelink transmissions granted by neighboring network entities.

[0017] The techniques, systems and devices described herein allow a UE to send scheduling assistance information (SAI) to a network entity to improve the reliability of sidelink resource allocation for mode 1 sidelink communications. The SAI may indicate a preferred or non-preferred sidelink resource for a sidelink transmission performed by the UE. The preferred resource may be a sidelink resource that is available or not used by other UEs. The non-preferred resource may be a sidelink resource reserved for sidelink transmissions performed by other UEs in the same or different cells. The UE may determine the preferred or non-preferred resource based on a sidelink channel sensing procedure performed by the UE, based on inter-UE coordination information received from one or more other UEs, or based on both. Although the sidelink resource may be granted by the network entity during mode 1 sidelink communications, the UE may send an indication of the granted (e.g., reserved) resource in a future time slot via a sidelink message, a sidelink control information (SCI) associated with the sidelink message, or both. Therefore, the UE, one or more other UEs, or both may monitor the sidelink resource pool for SCI from other UEs to determine the sidelink resource availability or preference.

[0018] The SAI may be based on such a sidelink channel sensing procedure. If the UE performs sidelink channel sensing, the UE may indicate to the network entity via the SAI the unpreferred resources (e.g., one or more of the reserved resources) or the preferred resources (e.g., one or more of the resources determined to be available or unreserved) based on the sidelink channel sensing procedure. If one or more other UEs perform sidelink channel sensing, the one or more other UEs may send an inter-UE coordination message to the UE based on the sidelink channel sensing procedure to indicate the preferred resources or the unpreferred resources, and the UE may forward the one or more indications to the network entity via the SAI (e.g., the UE may aggregate feedback). In some examples, the UE may aggregate the results of the sidelink channel sensing procedure performed by the UE with the resources indicated via one or more inter-UE coordination messages, and the UE may send the aggregated resource preference to the network entity via the SAI. The network entity may send a scheduling message based on the sidelink resources indicated via the SAI to grant resources for sidelink transmission by the UE. The UE may send a sidelink message to one or more other UEs in the same or different cell as the UE via the granted resources.

[0019] The SAI described herein may support increased reliability and reduced interference of sidelink communications, among other advantages and improvements. For example, by scheduling sidelink resources based on the SAI, a network entity may take into account sidelink resources granted by other network entities in other wireless cells. In this way, the network entity may schedule the sidelink transmissions of the UE via resources that may not interfere with sidelink transmissions scheduled by other network entities in other cells, which may reduce interference and sidelink conflicts. Such sidelink resource allocation techniques may therefore reduce latency, improve throughput, and improve sidelink communication reliability.

[0020] Various aspects of the disclosure are first described in the context of a wireless communication system. Additional aspects of the disclosure are described with reference to a sidelink resource reservation scheme and process flow. Various aspects of the disclosure are further illustrated by and described with reference to apparatus diagrams, system diagrams, and flow diagrams related to UE scheduling assistance for mode 1 sidelink communications.

[0021] Figure 1 An example of a wireless communication system 100 supporting UE scheduling assistance for mode 1 sidelink communications according to one or more aspects of the present disclosure is illustrated. The wireless communication system 100 may include one or more network entities 105, one or more UEs 115, and a core network 130. In some examples, the wireless communication system 100 may be a long term evolution (LTE) network, an advanced LTE (LTE-A) network, an LTE-A Pro network, a new radio (NR) network, or a network operating according to other systems and radio technologies (including future systems and radio technologies not explicitly mentioned herein).

[0022] The network entities 105 may be dispersed throughout a geographic area to form the wireless communication system 100, and may include devices in different forms or with different capabilities. In various examples, the network entities 105 may be referred to as network elements, mobility elements, radio access network (RAN) nodes, or network equipment, among other nomenclature. In some examples, the network entities 105 and the UE 115 may communicate wirelessly via one or more communication links 125 (e.g., radio frequency (RF) access links). For example, the network entity 105 may support a coverage area 110 (e.g., a geographic coverage area) within which the UE 115 and the network entity 105 may establish one or more communication links 125. The coverage area 110 may be an example of a geographic area within which the network entity 105 and the UE 115 may support signal communications according to one or more radio access technologies (RATs).

[0023] The UEs 115 may be dispersed throughout the coverage area 110 of the wireless communication system 100, and each UE 115 may be stationary, or mobile, or both stationary and mobile at different times. The UEs 115 may be devices in different forms or with different capabilities. Figure 1 Some examples of UE 115 are illustrated. The UE 115 described herein may be able to support communication with various types of devices such as other UE 115 or network entity 105, such as Figure 1 shown.

[0024] As described herein, a node of the wireless communication system 100 (which may be referred to as a network node or a wireless node) may be a network entity 105 (e.g., any network entity described herein), a UE 115 (e.g., any UE described herein), a network controller, an apparatus, a device, a computing system, one or more components, or another suitable processing entity configured to perform any of the techniques described herein. For example, the node may be a UE 115. As another example, the node may be a network entity 105. As another example, a first node may be configured to communicate with a second node or a third node. In one aspect of this example, the first node may be a UE 115, the second node may be a network entity 105, and the third node may be a UE 115. In another aspect of this example, the first node may be a UE 115, the second node may be a network entity 105, and the third node may be a network entity 105. In yet other aspects of this example, the first node, the second node, and the third node may be different relative to these examples. Similarly, references to UE 115, network entity 105, apparatus, device, computing system, etc. may include disclosure of UE 115, network entity 105, apparatus, device, computing system, etc. as nodes. For example, a disclosure that UE 115 is configured to receive information from network entity 105 also discloses that the first node is configured to receive information from a second node.

[0025] In some examples, the network entities 105 may communicate with the core network 130, or with each other, or both. For example, the network entities 105 may communicate with the core network 130 via one or more backhaul communication links 120 (e.g., according to S1, N2, N3, or other interface protocols). In some examples, the network entities 105 may communicate with each other via the backhaul communication links 120 (e.g., according to X2, Xn, or other interface protocols) directly (e.g., directly between the network entities 105) or indirectly (e.g., via the core network 130). In some examples, the network entities 105 may communicate with each other via the midhaul communication links 162 (e.g., according to the midhaul interface protocol) or the fronthaul communication links 168 (e.g., according to the fronthaul interface protocol) or any combination thereof. The backhaul communication links 120, the midhaul communication links 162, or the fronthaul communication links 168 may be or include one or more wired links (e.g., electrical links, optical fiber links), one or more wireless links (e.g., radio links, wireless optical links), and other examples or various combinations thereof. The UE 115 may communicate with the core network 130 via the communication link 155 .

[0026] One or more of the network entities 105 described herein may include or may be referred to as a base station 140 (e.g., a transceiver base station, a radio base station, an NR base station, an access point, a radio transceiver, a Node B, an evolved Node B (eNB), a next generation Node B, or a Gigabit Node B (any of which may be referred to as a gNB), a 5G NB, a next generation eNB (ng-eNB), a Home Node B, a Home Evolved Node B, or other suitable terms). In some examples, the network entity 105 (e.g., a base station 140) may be implemented in an aggregated (e.g., monolithic, standalone) base station architecture, which may be configured to utilize a protocol stack that is physically or logically integrated within a single network entity 105 (e.g., a single RAN node, such as a base station 140).

[0027] In some examples, the network entity 105 may be implemented in a disaggregated architecture (e.g., a disaggregated base station architecture, a disaggregated RAN architecture) that may be configured to utilize a protocol stack that is physically or logically distributed between two or more network entities 105, such as an integrated access backhaul (IAB) network, an open RAN (O-RAN) (e.g., a network configuration initiated by the O-RAN Alliance), or a virtualized RAN (vRAN) (e.g., a cloud RAN (C-RAN)). For example, the network entity 105 may include one or more of the following: a central unit (CU) 160, a distributed unit (DU) 165, a radio unit (RU) 170, a RAN intelligent controller (RIC) 175 (e.g., a near real-time RIC (near RT RIC), a non-real-time RIC (non-RT RIC)), a service management and orchestration (SMO) 180 system, or any combination thereof. The RU 170 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 transmit receive point (TRP). One or more components of the network entity 105 in the decomposed RAN architecture may be co-located, or one or more components of the network entity 105 may be located in distributed locations (e.g., separate physical locations). In some examples, one or more network entities 105 of the decomposed RAN architecture may be implemented as virtual units (e.g., virtual CU (VCU), virtual DU (VDU), virtual RU (VRU)).

[0028] The functional split between CU 160, DU 165, and RU 170 is flexible and may support different functionalities depending on which functions (e.g., network layer functions, protocol layer functions, baseband functions, RF functions, and any combination thereof) are performed at CU 160, DU 165, or RU 170. For example, a functional split of a protocol stack may be employed between CU 160 and DU 165 such that CU 160 may support one or more layers of a protocol stack and DU 165 may support one or more different layers of a protocol stack. In some examples, CU 160 may host higher protocol layer (e.g., layer 3 (L3), layer 2 (L2)) functionality and signaling (e.g., radio resource control (RRC), service data adaptation protocol (SDAP), packet data convergence protocol (PDCP)). The CU 160 may be connected to one or more DUs 165 or RUs 170, and the one or more DUs 165 or RUs 170 may host lower protocol layers, such as layer 1 (L1) (e.g., physical (PHY) layer) or L2 (e.g., radio link control (RLC) layer, medium access control (MAC) layer) functionality and signaling, and may each be at least partially controlled by the CU 160. Additionally or alternatively, a functional split of the protocol stack may be employed between the DUs 165 and RUs 170, such that the DUs 165 may support one or more layers of the protocol stack, and the RUs 170 may support one or more different layers of the protocol stack. The DUs 165 may support one or more different cells (e.g., via one or more RUs 170). In some cases, the functional split between CU 160 and DU 165 or between DU 165 and RU 170 may be within the protocol layer (e.g., some functions of the protocol layer may be performed by one of CU 160, DU 165, or RU 170, while other functions of the protocol layer are performed by different ones of CU 160, DU 165, or RU 170). CU 160 may be further functionally split into CU control plane (CU-CP) functions and CU user plane (CU-UP) functions. CU 160 may be connected to one or more DUs 165 via midhaul communication links 162 (e.g., F1, F1-c, F1-u), and DU 165 may be connected to one or more RUs 170 via fronthaul communication links 168 (e.g., open fronthaul (FH) interface). In some examples, midhaul communication link 162 or fronthaul communication link 168 may be implemented based on an interface (e.g., a channel) between layers of a protocol stack supported by respective network entities 105 that communicate via such communication links.

[0029] In a wireless communication system (e.g., wireless communication system 100), infrastructure and spectrum resources for radio access may support wireless backhaul link capabilities to supplement wired backhaul connections, thereby providing an IAB network architecture (e.g., to a core network 130). In some cases, in an IAB network, one or more network entities 105 (e.g., IAB nodes 104) may be partially controlled by each other. One or more IAB nodes 104 may be referred to as donor entities or IAB donors. One or more DUs 165 or one or more RUs 170 may be controlled in part by one or more CUs 160 associated with a donor network entity 105 (e.g., a donor base station 140). One or more donor network entities 105 (e.g., IAB donors) may communicate with one or more additional network entities 105 (e.g., IAB nodes 104) via supported access and backhaul links (e.g., backhaul communication links 120). The IAB node 104 may include an IAB mobile terminal (IAB-MT) controlled (e.g., scheduled) by a coupled IAB donor's DU 165. The IAB-MT may include an independent set of antennas for relaying communications with the UE 115, or may share the same antennas of the IAB node 104 (e.g., of the RU 170) for access via the DU 165 of the IAB node 104 (e.g., referred to as a virtual IAB-MT (vIAB-MT)). In some examples, the IAB node 104 may include a DU 165 that supports communication links with additional entities (e.g., IAB node 104, UE 115) within a relay chain or configuration (e.g., downstream) of the access network. In such cases, one or more components of the decomposed RAN architecture (e.g., one or more IAB nodes 104 or components of the IAB node 104) may be configured to operate according to the techniques described herein.

[0030] For example, an access network (AN) or RAN may include an access node (e.g., an IAB donor), communications between an IAB node 104, and one or more UEs 115. The IAB donor may facilitate connectivity between the core network 130 and the AN (e.g., via a wired or wireless connection to the core network 130). That is, the IAB donor may refer to a RAN node having a wired or wireless connection to the core network 130. The IAB donor may include a CU 160 and at least one DU 165 (e.g., and RU 170), in which case the CU 160 may communicate with the core network 130 via an interface (e.g., a backhaul link). The IAB donor and the IAB node 104 may communicate via an F1 interface according to a protocol defining signaling messages (e.g., an F1 AP protocol). Additionally or alternatively, CU 160 may communicate with the core network via an interface (which may be an example of a portion of a backhaul link) and may communicate with other CUs 160 (e.g., CUs 160 associated with an alternative IAB donor) via an Xn-C interface (which may be an example of a portion of a backhaul link).

[0031] An IAB node 104 may refer to a RAN node that provides IAB functionality (e.g., access for UE 115, wireless self-backhaul capabilities, etc.). DU 165 may act as a distributed scheduling node toward child nodes associated with IAB node 104, and IAB-MT may act as a scheduled node toward a parent node associated with IAB node 104. That is, an IAB donor may be referred to as a parent node that communicates with one or more child nodes (e.g., an IAB donor may relay transmissions to a UE through one or more other IAB nodes 104). Additionally or alternatively, depending on the relay chain or configuration of the AN, an IAB node 104 may also be referred to as a parent node or child node of other IAB nodes 104. Thus, the IAB-MT entity of the IAB node 104 may provide a Uu interface for the child IAB node 104 to receive signaling from the parent IAB node 104 , and a DU interface (eg, DU 165 ) may provide a Uu interface for the parent IAB node 104 to signal to the child IAB node 104 or the UE 115 .

[0032] For example, the IAB node 104 may be referred to as a parent node that supports communications to a child IAB node, or as a child node associated with an IAB donor, or both. The IAB donor may include a CU 160 having a wired or wireless connection to the core network 130 (e.g., a backhaul communication link 120), and may act as a parent node of the IAB node 104. For example, the DU 165 of the IAB donor may relay transmissions to the UE 115 through the IAB node 104, or may directly signal the transmissions to the UE 115, or both. The CU 160 of the IAB donor may signal the establishment of a communication link to the IAB node 104 via the F1 interface, and the IAB node 104 may schedule transmissions (e.g., transmissions relayed from the IAB donor to the UE 115) via the DU 165. That is, data may be relayed to and from the IAB node 104 via signaling via the NR Uu interface of the MT to the IAB node 104. Communication with IAB node 104 may be scheduled by the DU 165 of the IAB donor, and communication with IAB node 104 may be scheduled by the DU 165 of the IAB node 104.

[0033] Where the techniques described herein are applied to the context of a disaggregated RAN architecture, one or more components of the disaggregated RAN architecture may be configured to support UE scheduling assistance for mode 1 sidelink communications as described herein. For example, some operations described as being performed by a UE 115 or a network entity 105 (e.g., a base station 140) may additionally or alternatively be performed by one or more components of the disaggregated RAN architecture (e.g., an IAB node 104, a DU 165, a CU 160, a RU 170, a RIC 175, a SMO 180).

[0034] UE 115 may include or may be referred to as a mobile device, a wireless device, a remote device, a handheld device, or a subscriber device, or some other suitable terminology, where a "device" may also be referred to as a unit, a station, a terminal, or a client, among other examples. UE 115 may also include or may be referred to as a personal electronic device, such as a cellular phone, a personal digital assistant (PDA), a tablet computer, a laptop computer, or a personal computer. In some examples, UE 115 may include or may be referred to as a wireless local loop (WLL) station, an Internet of Things (IoT) device, an Internet of Everything (IoE) device, or a machine type communication (MTC) device, among other examples, which may be implemented in various objects such as appliances or vehicles, meters, and the like.

[0035] The UE 115 described herein may be capable of communicating with various types of devices, such as other UEs 115, which may sometimes act as relays, as well as network entities 105 and network equipment including macro eNBs or gNBs, small cell eNBs or gNBs, or relay base stations, among other examples, such as Figure 1 shown.

[0036] The UE 115 and the network entity 105 may use resources associated with one or more carriers to wirelessly communicate with each other via one or more communication links 125 (e.g., access links). The term "carrier" may refer to a set of RF spectrum resources having a defined physical layer structure for supporting a communication link 125. For example, a carrier for a communication link 125 may include a portion of an RF spectrum band (e.g., a bandwidth portion (BWP)) that operates according to one or more physical layer channels for a given radio access technology (e.g., LTE, LTE-A, LTE-A Pro, NR). Each physical layer channel may carry acquisition signaling (e.g., synchronization signals, system information), control signaling for coordinating carrier operations, user data, or other signaling. The wireless communication system 100 may support communications with the UE 115 using carrier aggregation or multi-carrier operation. Depending on the carrier aggregation configuration, the UE 115 may be configured with multiple downlink component carriers and one or more uplink component carriers. Carrier aggregation may be used for both frequency division duplex (FDD) component carriers and time division duplex (TDD) component carriers. Communication between the network entity 105 and other devices may refer to communication between these devices and any portion (e.g., entity, sub-entity) of the network entity 105. For example, the terms "send," "receive," or "communicate" when referring to the network entity 105 may refer to any portion of the network entity 105 (e.g., base station 140, CU 160, DU 165, RU 170) of the RAN communicating with another device (e.g., directly or via one or more other network entities 105).

[0037] In some examples, such as in a carrier aggregation configuration, a carrier may also have acquisition signaling or control signaling that coordinates the operation of other carriers. A carrier may be associated with a frequency channel (e.g., an Evolved Universal Mobile Telecommunications System Terrestrial Radio Access (E-UTRA) Absolute RF Channel Number (EARFCN)) and may be identified based on a channel raster for discovery by UE 115. A carrier may operate in a standalone mode, in which case initial acquisition and connection may be performed by UE 115 via the carrier, or a carrier may operate in a non-standalone mode, in which case a different carrier (e.g., a different carrier of the same or different radio access technology) is used to anchor the connection.

[0038] The communication link 125 shown in the wireless communication system 100 may include downlink transmissions (e.g., forward link transmissions) from the network entity 105 to the UE 115, uplink transmissions (e.g., return link transmissions) from the UE 115 to the network entity 105, or both, as well as other transmission configurations. A carrier may carry either downlink communications or uplink communications (e.g., in an FDD mode), or may be configured to carry both downlink communications and uplink communications (e.g., in a TDD mode).

[0039] A carrier may be associated with a particular bandwidth of the RF spectrum, and in some examples, the carrier bandwidth may be referred to as a "system bandwidth" of the carrier or wireless communication system 100. For example, the carrier bandwidth may be one of a set of bandwidths of carriers of a particular radio access technology (e.g., 1.4 megahertz (MHz), 3 MHz, 5 MHz, 10 MHz, 15 MHz, 20 MHz, 40 MHz, or 80 MHz). A device of the wireless communication system 100 (e.g., a network entity 105, a UE 115, or both) may have a hardware configuration that supports communications using a particular carrier bandwidth, or may be capable of being configured to support communications using one of the carrier bandwidths in the set of carrier bandwidths. In some examples, the wireless communication system 100 may include a network entity 105 or a UE 115 that supports concurrent communications using carriers associated with multiple carrier bandwidths. In some examples, each served UE 115 may be configured to operate using a portion (e.g., a subband, a BWP) or all of the carrier bandwidth.

[0040] The signal waveform transmitted via the carrier may be composed of multiple subcarriers (e.g., using multi-carrier modulation (MCM) techniques, such as orthogonal frequency division multiplexing (OFDM) or discrete Fourier transform spread OFDM (DFT-S-OFDM)). In a system using MCM techniques, a resource element may refer to a resource of one symbol period (e.g., the duration of one modulation symbol) and one subcarrier, in which case the symbol period and the subcarrier spacing may be inversely related. The number of bits carried by each resource element may depend on the modulation scheme (e.g., the order of the modulation scheme, the coding rate of the modulation scheme, or both), so that a relatively higher number of resource elements (e.g., in the transmission duration) and a relatively higher order modulation scheme may correspond to a relatively higher communication rate. Wireless communication resources may refer to a combination of RF spectrum resources, time resources, and spatial resources (e.g., spatial layers, beams), and the use of multiple spatial resources may increase the data rate or data integrity of communications with UE 115.

[0041] One or more parameter sets for a carrier may be supported, and the parameter sets may include subcarrier spacing (Δf) and cyclic prefixes. A carrier may be divided into one or more BWPs with the same or different parameter sets. In some examples, a UE 115 may be configured with multiple BWPs. In some examples, a single BWP for a carrier may be active at a given time, and communications of a UE 115 may be constrained to one or more active BWPs.

[0042] The time interval for the network entity 105 or the UE 115 may be expressed in multiples of a basic time unit, which may be, for example, T s =1 / (Δf max ·N f ) seconds sampling period, where Δf max It can represent the supported subcarrier spacing, and N f The supported discrete Fourier transform (DFT) size may be indicated. The time intervals of the communication resources may be organized according to radio frames, each having a specified duration (e.g., 10 milliseconds (ms)). Each radio frame may be identified by a system frame number (SFN) (e.g., in the range of 0 to 1023).

[0043] Each frame may include multiple consecutively numbered subframes or time slots, and each subframe or time slot may have the same duration. In some examples, the frame may be divided into subframes (e.g., in the time domain), and each subframe may be further divided into a certain number of time slots. Alternatively, each frame may include a variable number of time slots, and the number of time slots may depend on the subcarrier spacing. Each time slot may include a certain number of symbol periods (e.g., depending on the length of the cyclic prefix appended in front of each symbol period). In some wireless communication systems 100, the time slot may be further divided into a plurality of micro time slots associated with one or more symbols. Excluding the cyclic prefix, each symbol period may be associated with one or more (e.g., N f ) sampling periods are associated. The duration of the symbol period may depend on the subcarrier interval or the operating frequency band.

[0044] A subframe, slot, mini-slot, or symbol may be the smallest scheduling unit (e.g., in the time domain) of the wireless communication system 100 and may be referred to as a transmission time interval (TTI). In some examples, the TTI duration (e.g., the number of symbol periods in a TTI) may be variable. Additionally or alternatively, the smallest scheduling unit of the wireless communication system 100 may be dynamically selected (e.g., in a burst of a shortened TTI (sTTI)).

[0045] Physical channels may be multiplexed according to various techniques for communicating using a carrier. Physical control channels and physical data channels may be multiplexed for signaling via a downlink carrier, for example, using one or more of a time division multiplexing (TDM) technique, a frequency division multiplexing (FDM) technique, or a hybrid TDM-FDM technique. A control region (e.g., a control resource set (CORESET)) of a physical control channel may be defined by a set of symbol periods and may extend across a system bandwidth or a subset of a system bandwidth of a carrier. One or more control regions (e.g., CORESETs) may be configured for a set of UEs 115. For example, one or more UEs in UE115 may monitor or search a control region for control information according to one or more search space sets, and each search space set may include one or more control channel candidates in one or more aggregation levels arranged in a cascaded manner. The aggregation level of a control channel candidate may refer to the amount of control channel resources (e.g., control channel elements (CCEs)) associated with coded information for a control information format having a given payload size. The search space sets may include a common search space set configured for transmitting control information to a plurality of UEs 115 , and a UE-specific search space set for transmitting control information to a specific UE 115 .

[0046] The network entity 105 may provide communication coverage via one or more cells (e.g., macro cells, small cells, hot spots, or other types of cells, or any combination thereof). The term "cell" may refer to a logical communication entity used to communicate with the network entity 105 (e.g., using a carrier), and may be associated with an identifier used to distinguish adjacent cells (e.g., a physical cell identifier (PCID), a virtual cell identifier (VCID), or other cell identifier). In some examples, a cell may also refer to a coverage area 110 or a portion of a coverage area 110 (e.g., a sector) within which the logical communication entity operates. Depending on various factors such as the capabilities of the network entity 105, such cells may range from smaller areas (e.g., structures, subsets of structures) to larger areas. For example, a cell may be or may include a building, a subset of a building, or an external space between or overlapping coverage areas 110, as well as other examples.

[0047] A macro cell typically covers a relatively large geographic area (e.g., several kilometers in radius) and may allow unrestricted access to UEs 115 that have service subscriptions with a network provider that supports the macro cell. Small cells may be associated with lower power network entities 105 (e.g., lower power base stations 140) than macro cells, and small cells may operate using the same or different (e.g., licensed, unlicensed) frequency bands as macro cells. Small cells may provide unrestricted access to UEs 115 that have service subscriptions with a network provider, or may provide restricted access to UEs 115 associated with small cells (e.g., UEs 115 in a closed subscriber group (CSG), UEs 115 associated with users in a home or office). The network entity 105 may support one or more cells, and may also use one or more component carriers to support communications via one or more cells.

[0048] In some examples, a carrier may support multiple cells, and different cells may be configured according to different protocol types (e.g., MTC, narrowband IoT (NB-IoT), enhanced mobile broadband (eMBB)) that may provide access to different types of devices.

[0049] In some examples, the network entities 105 (e.g., base stations 140, RUs 170) may be mobile and thus provide communication coverage for mobile coverage areas 110. In some examples, different coverage areas 110 associated with different technologies may overlap, but the different coverage areas 110 may be supported by the same network entity 105. In some other examples, overlapping coverage areas 110 associated with different technologies may be supported by different network entities 105. The wireless communication system 100 may include, for example, a heterogeneous network in which different types of network entities 105 provide coverage for various coverage areas 110 using the same or different radio access technologies.

[0050] The wireless communication system 100 may support synchronous operation or asynchronous operation. For synchronous operation, the network entities 105 (e.g., base stations 140) may have similar frame timing, and transmissions from different network entities 105 may be approximately aligned in time. For asynchronous operation, the network entities 105 may have different frame timing, and in some examples, transmissions from different network entities 105 may not be aligned in time. The techniques described herein may be used for synchronous operation or asynchronous operation.

[0051] Some UEs 115, such as MTC or IoT devices, may be low-cost or low-complexity devices and may provide automated communication between machines (e.g., via machine-to-machine (M2M) communication). M2M communication or MTC may refer to data communication technology that allows devices to communicate with each other or with a network entity 105 (e.g., base station 140) without human intervention. In some examples, M2M communication or MTC may include communications from devices that integrate sensors or meters to measure or capture information and relay such information to a central server or application that uses the information or presents the information to a person interacting with the application. Some UEs 115 may be designed to collect information or implement automated behavior of machines or other devices. Examples of applications for MTC devices include: smart metering, inventory monitoring, water level monitoring, equipment monitoring, health care monitoring, wildlife monitoring, weather and geographic event monitoring, queue management and tracking, remote security sensing, physical access control, and transaction-based commercial charging.

[0052] Some UEs 115 may be configured to employ an operating mode that reduces power consumption, such as half-duplex communication (e.g., a mode that supports one-way communication via transmission or reception but does not transmit and receive concurrently). In some examples, half-duplex communication may be performed at a reduced peak rate. Other power saving techniques for UE 115 include entering a power saving deep sleep mode when not engaged in active communications, operating using limited bandwidth (e.g., according to narrowband communications), or a combination of these techniques. For example, some UEs 115 may be configured to operate using a narrowband protocol type that is associated with a defined portion or range (e.g., a subcarrier or resource block (RB) set) within a carrier, within a guard band of a carrier, or outside a carrier.

[0053] The wireless communication system 100 may be configured to support ultra-reliable communication or low-latency communication or various combinations thereof. For example, the wireless communication system 100 may be configured to support ultra-reliable low-latency communication (URLLC). The UE 115 may be designed to support ultra-reliable, low-latency or critical functions. Ultra-reliable communication may include private communication or group communication, and may be supported by one or more services (such as push-to-talk, video or data). Support for ultra-reliable, low-latency functions may include prioritization of services, and such services may be used for public safety or general commercial applications. The terms ultra-reliable, low-latency and ultra-reliable low-latency may be used interchangeably herein.

[0054] In some examples, a UE 115 may be configured to support direct communication with other UEs 115 via a device-to-device (D2D) communication link 135 (e.g., according to a peer-to-peer (P2P), D2D, or sidelink protocol). In some examples, one or more UEs 115 in a group that are performing D2D communication may be within a coverage area 110 of a network entity 105 (e.g., a base station 140, a RU 170), which may support aspects of such D2D communication configured (e.g., scheduled) by the network entity 105. In some examples, one or more UEs 115 in such a group may be outside of the coverage area 110 of the network entity 105, or may otherwise be unable or not configured to receive transmissions from the network entity 105. In some examples, a group of UEs 115 communicating via D2D communication may support a one-to-many (1:M) system, in which each UE 115 transmits to each of the other UEs 115 in the group. In some examples, network entity 105 may facilitate scheduling of resources for D2D communication. In some other examples, D2D communication may be performed between UEs 115 without involving network entities 105.

[0055] In some systems, the D2D communication link 135 can be an example of a communication channel (such as a sidelink communication channel) between vehicles (e.g., UE 115). In some examples, the vehicles can communicate using vehicle-to-everything (V2X) communications, vehicle-to-vehicle (V2V) communications, or some combination of these communications. The vehicles can signal information related to traffic conditions, signal scheduling, weather, safety, emergency situations, or any other information related to the V2X system. In some examples, vehicles in the V2X system can communicate with roadside infrastructure (such as roadside units), or communicate with the network using vehicle-to-network (V2N) communications via one or more network nodes (e.g., network entity 105, base station 140, RU 170), or both.

[0056] The core network 130 may provide user authentication, access authorization, tracking, Internet Protocol (IP) connectivity, and other access, routing, or mobility functions. The core network 130 may be an evolved packet core (EPC) or a 5G core (5GC), which may include at least one control plane entity (e.g., a mobility management entity (MME), an access and mobility management function (AMF)) for managing access and mobility and at least one user plane entity (e.g., a serving gateway (S-GW), a packet data network (PDN) gateway (P-GW), or a user plane function (UPF)) for routing packets or interconnecting to an external network. The control plane entity may manage non-access layer (NAS) functions, such as mobility, authentication, and bearer management of UE 115 served by a network entity 105 (e.g., a base station 140) associated with the core network 130. User IP packets may be delivered through the user plane entity, which may provide IP address allocation and other functions. The user plane entity may be connected to the IP service 150 of one or more network operators. IP services 150 may include access to the Internet, an intranet, an IP Multimedia Subsystem (IMS), or packet-switched streaming services.

[0057] The wireless communication system 100 may operate using one or more frequency bands that may be in the range of 300 megahertz (MHz) to 300 gigahertz (GHz). Generally speaking, the region from 300 MHz to 3 GHz is referred to as the ultra-high frequency (UHF) region or decimeter band because the wavelength ranges from about one decimeter to one meter in length. UHF waves may be blocked or redirected by buildings and environmental features (which may be referred to as clusters), but these waves may be sufficient to penetrate structures so that macro cells provide services to UEs 115 located indoors. Communications using UHF waves may be associated with smaller antennas and shorter ranges (e.g., less than 100 kilometers) compared to communications using smaller frequencies and longer waves in the high frequency (HF) or very high frequency (VHF) portions of the spectrum below 300 MHz.

[0058] The wireless communication system 100 may also operate using a super high frequency (SHF) region (also known as a centimeter band) that may be in the range of 3 GHz to 30 GHz or an extremely high frequency (EHF) region (e.g., 30 GHz to 300 GHz) (also known as a millimeter band) using a spectrum. In some examples, the wireless communication system 100 may support millimeter wave (mmW) communications between UE 115 and network entity 105 (e.g., base station 140, RU 170), and the EHF antenna of the corresponding device may be smaller and closer than the UHF antenna. In some examples, such technology may facilitate the use of antenna arrays within the device. However, the propagation of EHF transmissions may have even greater attenuation and a shorter range than SHF or UHF transmissions. The technology disclosed herein may be adopted across transmissions using one or more different frequency regions, and the use of frequency bands specified across these frequency regions may vary by country or regulatory agency.

[0059] The wireless communication system 100 may utilize both licensed RF spectrum bands and unlicensed RF spectrum bands. For example, the wireless communication system 100 may employ license assisted access (LAA), LTE unlicensed (LTE-U) radio access technology, or NR technology using an unlicensed band (such as the 5 GHz Industrial, Scientific, and Medical (ISM) band). When operating using an unlicensed RF spectrum band, devices such as the network entity 105 and the UE 115 may employ carrier sensing for conflict detection and avoidance. In some examples, operations using an unlicensed band may be based on a carrier aggregation configuration in conjunction with a component carrier (e.g., LAA) operating using a licensed band. Operations using unlicensed spectrum may include downlink transmissions, uplink transmissions, P2P transmissions, or D2D transmissions, among other examples.

[0060] The network entity 105 (e.g., base station 140, RU 170) or UE 115 may be equipped with multiple antennas that can be used to employ technologies such as transmit diversity, receive diversity, multiple-input multiple-output (MIMO) communications, or beamforming. The antennas of the network entity 105 or UE 115 may be located in one or more antenna arrays or antenna panels, which may support MIMO operations or transmit or receive beamforming. For example, one or more base station antennas or antenna arrays may be co-located at an antenna assembly, such as an antenna tower. In some examples, antennas or antenna arrays associated with the network entity 105 may be located at different geographical locations. The network entity 105 may include an antenna array having a collection of multiple rows and columns of antenna ports that the network entity 105 can use to support beamforming for communications with the UE 115. Similarly, the UE 115 may include one or more antenna arrays that may support various MIMO or beamforming operations. Additionally or alternatively, the antenna panel may support RF beamforming for signals sent via the antenna ports.

[0061] The network entity 105 or UE 115 may use MIMO communication to utilize multipath signal propagation and improve spectral efficiency by sending or receiving multiple signals via different spatial layers. Such a technology may be referred to as spatial multiplexing. The multiple signals may be sent, for example, by a transmitting device via different antennas or different combinations of antennas. Similarly, the multiple signals may be received by a receiving device via different antennas or different combinations of antennas. Each of the multiple signals may be referred to as a separate spatial stream and may carry information associated with the same data stream (e.g., the same codeword) or different data streams (e.g., different codewords). Different spatial layers may be associated with different antenna ports for channel measurement and reporting. MIMO technologies include: single-user MIMO (SU-MIMO), in which multiple spatial layers are sent to the same receiving device; and multi-user MIMO (MU-MIMO), in which multiple spatial layers are sent to multiple devices.

[0062] Beamforming (which may also be referred to as spatial filtering, directional transmission, or directional reception) is a signal processing technique that may be used at a transmitting device or a receiving device (e.g., a network entity 105, a UE 115) to shape or direct an antenna beam (e.g., a transmit beam, a receive beam) along a spatial path between the transmitting device and the receiving device. Beamforming may be achieved by combining signals conveyed via antenna elements of an antenna array so that some signals propagating along a particular orientation relative to the antenna array experience constructive interference, while other signals experience destructive interference. Adjustments to signals conveyed via antenna elements may include the transmitting device or the receiving device applying an amplitude offset, a phase offset, or both to signals carried via antenna elements associated with the device. Adjustments associated with each of these antenna elements may be defined by a set of beamforming weights associated with a particular orientation (e.g., relative to the antenna array of the transmitting device or the receiving device or relative to some other orientation).

[0063] The network entity 105 or UE 115 may use beam scanning techniques as part of a beamforming operation. For example, the network entity 105 (e.g., base station 140, RU 170) may use multiple antennas or antenna arrays (e.g., antenna panels) to perform beamforming operations for directional communication with UE 115. Some signals (e.g., synchronization signals, reference signals, beam selection signals, or other control signals) may be sent multiple times by the network entity 105 along different directions. For example, the network entity 105 may send signals according to different sets of beamforming weights associated with different transmission directions. Transmissions along different beam directions may be used to identify (e.g., by a transmitting device (such as network entity 105), or by a receiving device (such as UE 115)) beam directions for later transmission or reception by the network entity 105.

[0064] Some signals, such as data signals associated with a particular receiving device, may be sent by a transmitting device (e.g., transmitting network entity 105, transmitting UE 115) along a single beam direction (e.g., a direction associated with a receiving device (such as receiving network entity 105 or receiving UE 115)). In some examples, a beam direction associated with transmission along a single beam direction may be determined based on signals sent along one or more beam directions. For example, UE 115 may receive one or more of the signals sent by network entity 105 along different directions, and may report to network entity 105 an indication of the signal received by UE 115 with the highest signal quality or other acceptable signal quality.

[0065] In some examples, transmission by a device (e.g., by network entity 105 or UE 115) may be performed using multiple beam directions, and the device may use a combination of digital precoding or beamforming to generate a combined beam for transmission (e.g., from network entity 105 to UE 115). UE 115 may report feedback indicating precoding weights for one or more beam directions, and the feedback may correspond to a configured beam set across a system bandwidth or one or more subbands. Network entity 105 may send a reference signal (e.g., a cell-specific reference signal (CRS), a channel state information reference signal (CSI-RS)), which may be precoded or unprecoded. UE 115 may provide feedback for beam selection, which may be a precoding matrix indicator (PMI) or codebook-based feedback (e.g., a multi-panel codebook, a linear combination codebook, a port selection codebook). Although these techniques are described with reference to signals sent along one or more directions by a network entity 105 (e.g., base station 140, RU 170), UE 115 may use similar techniques to send signals multiple times along different directions (e.g., to identify a beam direction for subsequent transmission or reception by UE 115), or to send signals along a single direction (e.g., to send data to a receiving device).

[0066] A receiving device (e.g., UE 115) may perform receiving operations according to multiple receiving configurations (e.g., directional listening) when receiving various signals (such as synchronization signals, reference signals, beam selection signals, or other control signals) from a receiving device (e.g., network entity 105). For example, the receiving device may perform reception according to multiple receiving directions by receiving via different antenna subarrays, processing received signals according to different antenna subarrays, receiving according to different receiving beamforming weight sets (e.g., different directional listening weight sets) applied to signals received at multiple antenna elements of an antenna array, or processing received signals according to different receiving beamforming weight sets applied to signals received at multiple antenna elements of an antenna array, any of which may be referred to as "listening" according to different receiving configurations or receiving directions. In some examples, the receiving device may use a single receiving configuration to receive along a single beam direction (e.g., when receiving a data signal). A single receive configuration may be aligned along a beam direction determined based on listening according to different receive configuration directions (e.g., a beam direction determined to have the highest signal strength, highest signal-to-noise ratio (SNR), or other acceptable signal quality based on listening according to multiple beam directions).

[0067] The wireless communication system 100 may be a packet-based network that operates according to a layered protocol stack. In the user plane, communications at the bearer or PDCP layer may be IP-based. The RLC layer may perform packet segmentation and reassembly to communicate via logical channels. The MAC layer may perform priority processing and multiplexing of logical channels into transport channels. The MAC layer may also implement error detection techniques, error correction techniques, or both to support retransmission to improve link efficiency. In the control plane, the RRC layer may provide the establishment, configuration, and maintenance of an RRC connection that supports a radio bearer for user plane data between the UE 115 and the network entity 105 or the core network 130. The PHY layer may map a transport channel to a physical channel.

[0068] UE 115 and network entity 105 may support retransmission of data to increase the likelihood that the data is successfully received. Hybrid automatic repeat request (HARQ) feedback is a technique for increasing the likelihood of correctly receiving data via a communication link (e.g., communication link 125, D2D communication link 135). HARQ may include a combination of error detection (e.g., using a cyclic redundancy check (CRC)), forward error correction (FEC), and retransmission (e.g., automatic repeat request (ARQ)). HARQ may improve the throughput at the MAC layer under poor radio conditions (e.g., low signal-to-noise ratio conditions). In some examples, the device may support same-slot HARQ feedback, in which case the device may provide HARQ feedback in a specific slot for data received via a previous symbol in the slot. In some other examples, the device may provide HARQ feedback in a subsequent slot or according to some other time interval.

[0069] The wireless communication system 100 may support sidelink communication between two or more wireless devices (e.g., UE 115). The wireless communication system 100 may support two sidelink communication modes: one of mode 1 and mode 2. In mode 1 sidelink communication, UE 115 may request resources from network entity 105 for transmission. UE 115 (e.g., vehicle-to-device (V2X) UE 115 or some other wireless device) may transmit a scheduling request for sidelink transmission, a sidelink buffer status report (BSR), or both to network entity 105. Network entity 105 may allocate sidelink resources by sending a control message (e.g., downlink control information (DCI)) granting one or more resources for sidelink transmission on an access link (e.g., Uu link). UE 115 may use one or more resources to perform transmission to another UE 115 on a sidelink (e.g., PC5 link). In some examples, the sidelink transmission may include SCI, data, or both. The SCI may notify other receiving UEs 115 of resource reservations so that nearby UEs 115 operating in mode 1 side link communication can avoid using side link resources reserved for transmission by UEs 115.

[0070] In some examples, the network entity 105 may grant multiple resources for transmission by the UE 115 over time (e.g., resources in a certain number of time slots, or resources allocated according to an indicated periodicity, or both), and the UE 115 may indicate the granted resources in future time slots to other receiving UEs 115 via the SCI. The UE 115 may communicate with another UE 115, and the other UE 115 may be in the same cell or in a different cell as the UE 115 (e.g., the sidelink communication may not be limited by the cell boundary). In order to facilitate sidelink communication between cells, the sidelink resource pool configuration may be aligned across cells. For example, if the resources in the first time slot of the resource pool are reserved for transmission by the UE 115 associated with the first cell, the same resources in the same time slot may also be indicated as reserved in the sidelink resource pool indicated in another cell (e.g., aligned resource pool configuration). The aligned resource pool configuration may allow the UE 115 to send and receive sidelink communications regardless of the cell association. Due to the cross-cell aligned side link resource pool, UE 115 may monitor (eg, blindly decode) potential resource reservations from other UE 115 in each resource that configures the side link resource pool.

[0071] During mode 1 sidelink communications, the network entity 105 scheduling the sidelink communications may not monitor or receive scheduling information sent by other neighboring network entities 105 associated with other cells, which may result in conflicts between sidelink transmissions granted by different network entities 105 in different cells. For example, a first network entity 105 in a first cell may reserve a first resource in a sidelink resource pool for a first UE 115. The UE 115 may use the first resource to transmit to a second UE 115 in a second cell, but a second network entity 105 associated with the second UE 115 (e.g., a target UE 115) may not be aware of the reservation of the first resource. In some cases, the second network entity 105 may schedule resources that may overlap with the second resource reserved for the first UE 115, and the corresponding transmissions may conflict, which may result in reduced reliability of the sidelink communication and interference at the receiving UE 115.

[0072] In mode 2 sidelink communication, UE 115 may autonomously select sidelink resources from a sidelink resource pool for transmission based on a sidelink channel sensing procedure. In order to perform the sidelink channel sensing procedure, UE 115 may monitor and decode SCIs sent by other UEs 115. SCI may indicate resources in a resource pool reserved by other UEs 115 for transmission in future time slots. In some examples, UE 115 may perform reference signal received power (RSRP) measurements on SCI to determine which resources to reserve during a resource selection window. UE 115 may select available resources based on a sidelink channel sensing procedure to avoid conflicts (e.g., conflicts from hidden nodes) that may occur when multiple UEs 115 reserve the same resources for sidelink transmission. UE 115 may reserve sidelink resources by sending SCIs to other UEs 115.

[0073] In some cases, the sidelink channel sensing procedure performed by the UE 115 may be assisted by an inter-UE coordination message from another UE 115. For example, the other UE 115 may send an inter-UE coordination message to the UE 115. The inter-UE coordination message may include a resource preference indication. The inter-UE coordination message may be request-based or condition-based, wherein the UE 115 may request the inter-UE coordination message from the other UE 115, or the other UE 115 may determine whether to send the inter-UE coordination message based on a condition.

[0074] The techniques, systems, and devices described herein allow a UE 115 to send a SAI to a network entity 105 to improve the reliability of sidelink resource allocation for mode 1 sidelink communications. The SAI may indicate preferred or non-preferred sidelink resources for sidelink transmissions by the UE 115. The UE 115 may determine preferred or non-preferred resources based on a sidelink channel sensing procedure performed by the UE 115, based on inter-UE coordination information received from one or more other UEs 115, or based on both. The sidelink resources indicated via the SAI may be based on such sidelink channel sensing procedures. The network entity 105 may send a scheduling message to grant resources for sidelink transmissions by the UE 115 based on the preferred or non-preferred resources indicated via the SAI, which may increase reliability and reduce interference associated with sidelink communications.

[0075] Figure 2An example of a wireless communication system 200 that supports UE scheduling assistance for mode 1 sidelink communications according to one or more aspects of the present disclosure is illustrated. In some examples, the wireless communication system 200 can implement aspects of the wireless communication system 100. For example, the wireless communication system 200 can support communications between the network entity 105-a, the network entity 105-b, the network entity 105-c, the UE 115-a, the UE 115-b, and the UE 115-c, which can be as described in reference Figure 1 Examples of the corresponding network entities 105 and UEs 115 described above. In some examples, the network entity 105 may communicate with one or more UEs 115 via a wireless link 210 within a cell 205 (e.g., cell 205-a, cell 205-b, cell 205-c). For example, the network entity 105-a may perform downlink transmissions to the UE 115-a via a wireless link 210-a within the cell 205-a. In another example, the UE 115 may perform sidelink communications with another UE 115 via a sidelink communication link 215 within or across the cell 205. For example, a UE 115-a in a cell 205-a may send a sidelink transmission to a UE 115-b in a cell 205-b via a sidelink communication link 215-a.

[0076] The UE 115 in the wireless communication system 200 may support sidelink communications according to a first sidelink resource allocation mode or a second sidelink resource allocation mode (e.g., sidelink resource allocation mode 1 or sidelink resource allocation mode 2). For mode 1 sidelink resource allocation, the network entity 105 may allocate resources to the transmitting UE 115 for transmission by the UE 115, as described in reference to Figure 1 The techniques, systems, and devices described herein allow a UE 115 to send a scheduling assistance message 220 to a network entity 105 to improve the reliability of sidelink resource allocation for mode 1 sidelink communications. The scheduling assistance message 220 may include a SAI, which may indicate one or more sidelink resources for sidelink communications conducted by the UE 115. The UE 115 may autonomously determine the SAI based on sidelink channel sensing performed at the UE 115, based on information received via an inter-UE coordination message 225 received from another UE 115, or based on both.

[0077] exist Figure 2In an example of , UE 115-c may send a scheduling assistance message 220 to network entity 105-b to indicate preferred or non-preferred resources for transmissions by UE 115-c. Network entity 105-b may schedule or allocate sidelink resources for transmissions by UE 115-c based on the SAI included in the scheduling assistance message 220. In some examples, to determine the SAI, UE 115-c may perform a sidelink channel sensing procedure to monitor resource reservation information, such as SCI, from one or more other UEs 115 (such as UE 115-a, UE 115-b, or both) in the same or different cell 205. Techniques for monitoring resource reservation information and performing sensing procedures may be described elsewhere herein (including reference 1 to 3). Figure 3 ) is described in further detail.

[0078] The SCI may indicate a set of sidelink resources reserved for sidelink transmissions by one or more other UEs 115. In some examples, UE 115-c may not know whether the resources indicated in the SCI may be reserved by a UE 115 (such as UE 115-b) in the same cell 205-b as UE 115-c or by a UE 115 (such as UE 115-a in cell 205-a) in a different cell 205 from UE 115-c. In this example, UE 115-c may indicate each of the resources reserved via scheduling assistance message 220 (e.g., non-preferred resources), or UE 115-c may indicate each of the resources not reserved via scheduling assistance message 220 (e.g., preferred or available resources). The network entity 105 - b may determine whether the reserved resources indicated via the scheduling assistance message 220 are reserved by the network entity 105 - b in the cell 205 - b or reserved (e.g., allocated, scheduled) by another network entity 105 in a different cell 205 (such as the network entity 105 - a or the network entity 105 - c).

[0079] In some examples, the SCI received by the UE 115-b may include a cell identifier (ID) corresponding to a cell associated with a resource reservation made by another UE 115. The cell ID may indicate whether the resources indicated in the SCI are reserved by a UE 115 in the same cell 205-b as the UE 115-c or by a UE in a different cell 205 than the UE 115-c. If the cell ID is included in the SCI, the UE 115-c may determine which sidelink resources to indicate via the scheduling assistance message 220 based on the cell ID associated with the resource reservation indicated in the SCI. For example, the UE 115-c may indicate reserved resources in a neighboring cell 205 that is different from the cell 205-b supported by the network entity 105-b, and the UE 115-c may avoid indicating the reserved resources in the same cell 205-b via the scheduling assistance message 220 (e.g., because the network entity 105-b may be aware of the scheduled resources and reserved resources within the cell 205-b), which may reduce overhead. The scheduling assistance message 220 may indicate a set of sidelink resources that may be preferred (e.g., preferred resources) or a set of sidelink resources that may not be preferred (e.g., non-preferred resources) for sidelink communications by the UE 115-c. For example, if the cell ID indicates that the resources are reserved by the UE 115 in a different cell 205, the UE 115-c may report the resources to the network entity 105-b as not preferred.

[0080] In some examples, UE 115-b may send a coordination message 225 to UE 115-c via sidelink communication link 215-b. Coordination message 225 may indicate a resource set based on an SCI received by UE 115-b during a sidelink channel sensing procedure performed by UE 115-b. Coordination message 225 may include a resource preference indication, a cell ID, or both associated with the resource set. The resource preference indication may indicate whether the resource set is a preferred resource or a non-preferred resource. In some examples, the preferred resources may be one or more available resources (e.g., resources not reserved by other UEs 115 via SCI), and the non-preferred resources may be one or more unavailable resources (e.g., resources reserved by other UEs 115). In some examples, the resource preference indication may include one or more non-preferred resources from a resource set reserved for transmission by other UEs 115, or one or more preferred resources from a resource set not indicated as reserved by other UEs 115.

[0081] For example, UE 115-b may send a coordination message 225 to UE 115-c, and the coordination message 225 may include an indication of a reservation made by another UE 115 in another cell, such as by UE 115-a in cell 205-a. The coordination message 225 may indicate that the resources reserved by UE 115-a are non-preferred resources. UE 115-c may receive the coordination message 225 from UE 115-b and forward some or all of the resource reservation information indicated via the coordination message 225 to the network entity 105-b via the SAI in the scheduling assistance message 220. For example, if the coordination message 225 indicates preferred or non-preferred resources, the UE 115-c may indicate such resource preference to the network entity 105-b via the SAI.

[0082] In some examples, the UE 115-c may receive multiple coordination messages 225 from multiple UEs 115. The UE 115-c may combine (e.g., aggregate) the resources and other information indicated via the multiple coordination messages 225 and report the resource reservation to the network entity 105-b as part of the scheduling assistance message 220. For example, if the UE 115-c receives multiple coordination messages 225 indicating multiple preferred resources, the UE 115-c may send, to the network entity 105-b, a scheduling assistance message 220 indicating resources common to each of the coordination messages 225 (e.g., an intersection of the resources). If the UE 115-c receives multiple coordination messages 225 indicating multiple non-preferred resources, the UE 115-c may send, to the network entity 105-b, a scheduling assistance message 220 having the combination of resources (e.g., the union of the resources).

[0083] In some examples, the SAI may be based on a sidelink channel sensing procedure performed by UE 115-c and one or more coordination messages 225 received from other UEs 115. For example, UE 115-a may determine available or unavailable resources based on sensing and reception performed by UE 115-a (e.g., reservation information indicated by SCI, decoded transmitted RSRP measurements, or both). UE 115-a may send a coordination message 225 to UE 115-c to indicate resource preference information (e.g., available or unavailable resources). In some examples, UE 115-b may perform a similar procedure to indicate resource preference information to UE 115-c. UE 115-c may determine available or unavailable resources based on sensing and reception performed by UE 115-a (e.g., reservation information indicated by SCI, decoded transmitted RSRP measurements, or both). The UE 115-c may determine resource preference information based on the availability identified by the UE 115-c in addition to the preference information received via the coordination message 225. The UE 115-c may aggregate the resource preference information and send the aggregated resource preference information via the SAI.

[0084] UE 115-c may determine whether to use a sidelink channel sensing procedure at UE 115-c, use one or more coordination messages 225, or a combination of both to determine resource preference information to be sent via the SAI based on the capabilities of UE 115-c, an indication via signaling from network entity 105-b, a defined rule or criteria, or any combination thereof. For example, in some examples, UE 115-c may not be capable of sidelink sensing (e.g., a power-sensitive UE 115). In such cases, UE 115-c may use coordination messages 225 from other UEs 115 to determine what resource preference information to report (e.g., and UE 115-c may avoid performing a sidelink channel sensing procedure). Additionally or alternatively, network entity 105-b may determine to use one of these methods, and network entity 105-b may indicate the selection to UE 115-c via control signaling or may configure the selection per resource pool configuration.

[0085] The UE 115-c sends a scheduling assistance message 220 to the network entity 105-b via a wireless link 210-b (e.g., a Uu link, an uplink communication link) within the cell 205-b. The scheduling assistance message 220 may indicate a set of sidelink resources that may or may not be preferred for sidelink communications by the UE 115-c. The scheduling assistance message 220 may be sent from the UE 115-c to the network entity 105-b via one or more of a medium access control-control element (MAC-CE), a sidelink BSR, or a physical uplink control channel (PUCCH) transmission.

[0086] The network entity 105-b may instruct the UE 115-c to report the resource reservation included in the scheduling assistance message 220. In some examples, the network entity 105-b may send a DCI to the UE 115-c, and the DCI may dynamically trigger the UE 115-c to send the scheduling assistance message 220. For example, a field in the DCI may include a trigger indication. In another example, the network entity 105-b may send some other signaling such as a MAC-CE or RRC message to enable the UE 115-c to report the scheduling assistance message 220. In some other examples, the network entity 105-b may send other signaling, such as a system information block (SIB), to enable reporting for one or more UEs 115 (such as UE 115-c and UE 115-b) in the cell 205-b. The control signaling sent by the network entity 105-b may indicate whether the resource preference report performed by the UE 115-c includes preferred resource information, non-preferred resource information, or both.

[0087] Additionally or alternatively, the UE 115-c may send the scheduling assistance message 220 based on a set of conditions. For example, the UE 115-c may determine whether to send based on whether the UE 115-c has received a coordination message 225 from another UE 115, whether the UE 115-c has experienced reduced sidelink performance, whether the UE 115-c has determined that the channel is associated with a relatively high channel busy rate (CBR), or any combination thereof. The UE 115-c may determine the reduced sidelink performance based on whether the UE 115-c receives a certain number (e.g., greater than a threshold number) of consecutive negative acknowledgments (NACKs), based on a ratio of received NACKs to received ACKs exceeding a threshold NACK ratio, or based on both. The UE 115-c may measure the CBR of the sidelink resource pool and compare the measured CBR to a CBR threshold. If the measured CBR exceeds the CBR threshold, the UE 115-c may send the scheduling assistance message 220.

[0088] In response to the scheduling assistance message 220, the network entity 105-b may send a scheduling message (e.g., a scheduling grant) to the UE 115-c via the wireless link 210-b. The scheduling message may allocate or schedule a set of sidelink resources for sidelink transmissions by the UE 115-c. The scheduling message may be based on the SAI indicated via the scheduling assistance message 220. For example, the scheduling message may indicate a resource reservation based on the resources indicated via the scheduling assistance message 220. If the scheduling assistance message 220 indicates resources preferred by the UE 115-c, the network entity 105-b is more likely to select at least some of these resources. If the scheduling assistance message 220 indicates resources not preferred by the UE 115-c, the network entity 105-b may attempt to avoid allocating or scheduling these resources. When scheduling sidelink communications, the network entity 105-b may additionally or alternatively consider other communications in the cell 205-b. UE 115-c may use the side link resource set indicated in the scheduling message to UE 115-b, UE 115-a, or both.

[0089] The UE 115 as described herein may thereby generate and send a scheduling assistance message 220 to the network entity 105 to report sidelink resources for sidelink communications conducted by the UE 115. The sidelink resources may be determined based on a sidelink channel sensing procedure performed by one or more UEs 115 in the same or different cells 205, and may assist the network entity 105 in identifying available sidelink communications. The described techniques may thereby provide increased communication reliability and improved coordination between devices.

[0090] Figure 3 An example of a sidelink resource reservation scheme 300 that supports UE scheduling assistance for mode 1 sidelink communications in accordance with one or more aspects of the present disclosure is illustrated. In some examples, the sidelink resource reservation scheme 300 may represent a sidelink resource reservation scheme used by a first UE 115 (e.g., a transmitting UE 115) to select sidelink resources for sending a sidelink message. The first UE 115 may communicate with one or more second UEs 115 on a sidelink channel using resources 330 (e.g., time and frequency resources) in a resource pool 305. The first UE 115 and the one or more second UEs 115 may be reference UEs. Figure 1 and Figure 2 An example of the UE 115 described. In some examples, as part of the scheduling assistance procedure, the first UE 115 may determine the resource to be indicated via the scheduling assistance message.

[0091] Some sidelink communications (e.g., V2X communications or other device-to-device communications) may support autonomous resource allocation (e.g., Mode 2 resource allocation) by UE 115. For example, a first UE 115 may identify available resources (e.g., time and frequency resources, such as resources 330 in time slots and subchannels) of a resource pool 305 for sidelink transmissions. The first UE 115 may select one or more resources for the sidelink transmission from the resources in the resource pool 305 (e.g., a time and frequency resource pool). In some examples, the UE 115 may receive an indication of preferred resources, non-preferred (e.g., unavailable) resources, or both via a sidelink transmission (e.g., an inter-UE coordination message) from another UE.

[0092] exist Figure 3 In an example, the first UE 115 and one or more second UE 115 may operate according to mode 1 side link communication, as reference Figure 1 and Figure 2 However, the first UE 115, one or more second UEs 115, or both may perform a sidelink channel sensing procedure to identify resources to indicate to the network entity 105 via the SAI. The indicated resources may be preferred (e.g., available) or non-preferred (e.g., reserved) for sidelink transmissions by the first UE 115, and may improve the reliability and efficiency of sidelink resource allocations by the network entity 105 during mode 1 sidelink communications.

[0093] In some aspects, the sidelink channel sensing procedure may be triggered by a resource selection trigger 320. The resource selection trigger 320 may be a signal received by the UE 115, or may correspond to one or more conditions being satisfied, or both. The UE 115 may monitor one or more sidelink resources in the resource pool 305. The resource pool 305 may be aligned across one or more cells, as shown in FIG. Figure 2 When the sidelink channel sensing procedure is triggered, resources previously monitored by UE 115 may correspond to sensing window 310 , and future resources from which UE 115 may select may correspond to resource selection window 315 .

[0094] In the example of the sidelink resource reservation scheme 300, the UE 115 may monitor each resource 330 within the resource pool 305 during the sensing window 310 to identify the available resources of the resource pool 305 within the corresponding resource selection window 315. The UE 115 may indicate one or more available resources (e.g., preferred resources) in the resource selection window 315, one or more reserved resources (e.g., non-preferred resources) in the reserved resources (e.g., non-preferred resources) in the resource selection window 315, or both via the SAI, via the inter-UE coordination message, or both. All resources within time slots 0 to 5 and subchannels 0 to 3 of the resource selection window 315 may be included in the resource set for the UE 115 to select from and indicate via the SAI. The UE 115 may monitor the SCI from one or more other UEs 115 and perform sidelink channel sensing to determine the measured signal metric level (e.g., RSRP) associated with each resource 330 in the sensing window 310. The SCI may indicate one or more resources in the resource selection window 315 that may be reserved for future transmissions by another UE 115. The UE 115 may group the one or more reserved resources, and the UE 115 may determine that the remaining resources in the resource selection window 315 are available resources.

[0095] In some examples, UE 115 may measure the RSRP level of the SCI or other signaling received during the sensing window 310 and compare the measured RSRP to an RSRP threshold. If the measured RSRP is below the RSRP threshold, UE 115 may include the corresponding resources in the set of available resources (e.g., UE 115 may determine that transmissions via these resources may not interfere with transmissions by UE 115). If the measured RSRP is below the RSRP threshold, UE 115 may determine that transmissions in one or more resources scheduled by the SCI are unlikely to cause significant interference to transmissions by UE 115 in the resources. The RSRP threshold may be configured by the network entity 105 and indicated to UE 115 via control signaling (such as RRC signaling) or some other control signaling.

[0096] When the first UE 115 receives or detects the resource selection trigger 320, the UE 115 may identify the sensing window 310 (e.g., a past window) and the resource selection window 315 (e.g., a future window), and the UE 115 may perform resource selection. For example, the first UE 115 may determine the set of available resources in the resource selection window 315 based on SCI decoding in the sensing window 310, RSRP measurement, or both.

[0097] If the first UE 115 performs a sidelink channel sensing procedure, the first UE 115 may indicate to the network entity 105 one or more available resources (e.g., preferred resources) or one or more reserved resources (e.g., non-preferred resources) in the resource selection window 315 via an SAI (e.g., via a scheduling assistance message). If one or more second UEs in the second UE 115 perform a sidelink channel sensing procedure, the one or more second UEs 115 may send an indication of one or more available resources (e.g., preferred resources) or one or more reserved resources (e.g., non-preferred resources) in the resource selection window 315 to the first UE 115 via an inter-UE coordination message. The first UE 115 may aggregate the resource preference information received from the one or more second UEs 115 and indicate the aggregated information to the network entity 105 via an SAI. In some other examples, the first UE 115 may combine the resource preference information determined by the UE 115 with the resource preference information determined by the one or more second UEs 115, and the UE 115 may indicate the combined resource preference information via an SAI, as described with reference to Figure 2 above. The SAI may indicate the time and frequency positions (e.g., corresponding time slots and sub-channels) of each of the preferred or non-preferred resources in the preferred or non-preferred resources.

[0098] After identifying the available resources of the resource pool 305 within the resource selection window 315, the first UE 115 may select a resource for sending a scheduling assistance message to the network entity 105. In some aspects, the network entity 105 may allocate a resource for the UE 115 to send a scheduling assistance message. The sidelink resources indicated via the scheduling assistance message may be within a threshold time period of the resource via which the scheduling assistance message is sent. For example, if the first UE 115 sends a scheduling assistance message in the first time slot n, the scheduling assistance message may include an indication of resources between the first time periods n + m1 and n + m2, where m1 < m2. In Figure 3 an example, if the first UE 115 sends a scheduling assistance message via time slot 0, m1 is one time slot, and m2 is four time slots, the resources indicated via the scheduling assistance message may be within time slots 1 to 4.

[0099] In some examples, the threshold time period (e.g., m1 value and m2 value) may be configured by the network entity 105. For example, the threshold time period may be configured as part of the resource pool configuration, indicated via an RRC message, or indicated via a signal (such as a resource selection trigger 320) that triggers a resource preference report performed by the first UE 115. In another example, the threshold time period may be defined according to one or more rules (e.g., predetermined or standardized). Additionally or alternatively, the first UE 115 may determine the threshold time period based on one or more conditions associated with the communication at the first UE 115, such as a packet delay budget (PDB). For example, the UE 115 may measure one or more metrics including the PDB, and the corresponding measurement range may be mapped to the corresponding threshold time period. In this way, the first UE 115 can ensure that the reported resources are within the PDB so that the sidelink transmission can be performed with reduced latency (e.g., on time).

[0100] Thus, the first UE 115 and one or more other UEs 115 may monitor resources within the sensing window 310, decode SCI and other signaling received via the resources, measure RSRP of the received signaling, and determine a set of available or reserved resources in a subsequent time period (e.g., resource selection window 315). One or more second UEs 115 may indicate the determined resources to the first UE 115 via an inter-UE coordination message. The first UE 115 may combine the resources determined by the first UE 115 with the resources indicated by the one or more second UEs 115, and send a scheduling assistance message indicating the determined resource preference information to the network entity 105. The network entity 105 may utilize the resource preference information to schedule sidelink communications, which may reduce power consumption at the first UE 115, improve throughput, and improve the quality of sidelink communications.

[0101] Figure 4 An example of a process flow 400 for supporting UE scheduling assistance for mode 1 sidelink communications in accordance with one or more aspects of the present disclosure is illustrated. The process flow 400 may implement or be implemented by aspects of the wireless communication system 100 or 200. For example, the process flow 400 may be implemented by UEs 115-d and 115-e and network entity 105-d, each of which may represent reference Figures 1 to 3 The process flow 400 may be implemented by the UEs 115-d and 115-e and the network entity 105-d, for example, to identify available resources for sidelink transmissions by the UE 115-d, as described with reference to FIG. Figures 2 to 3 described.

[0102] In the following description of process flow 400, operations may be performed in a different order than shown, or operations performed by UE 115-d and 115-e may be performed in a different order or at a different time. For example, specific operations may also be excluded from process flow 400, or other operations may be added to process flow 400. Although UE 115-d and 115-e are shown as performing the operations of process flow 400, some aspects of some operations may also be performed by one or more other wireless devices.

[0103] At 405, in some examples, UE 115-e may send one or more inter-UE coordination messages to UE 115-d via the sidelink communication link. The one or more inter-UE coordination messages may each indicate one or more sidelink resources based on a respective sidelink channel sensing procedure performed by UE 115-e, as described with reference to FIG. Figure 2 and Figure 3 As stated. In some examples, the multiple inter-UE coordination messages may include preferred resource information or unpreferred resource information.

[0104] In some examples, UE 115-d may monitor SCI from other UEs 115, such as UE 115-d. The SCI may indicate a plurality of sidelink resources reserved for sidelink transmissions by the other UEs 115. In some examples, the SCI may include an ID of a respective cell associated with each of the plurality of sidelink resources.

[0105] At 410, the UE 115-d may send the SAI to the network entity 105-d via the uplink communication link. The SAI may indicate a first set of sidelink resources for sidelink communication by the UE 115-d. The UE 115-d may determine the first set of sidelink resources based on a plurality of sidelink resources indicated via a plurality of inter-UE coordination messages, a plurality of sidelink resources indicated by the SCI, or both, as described with reference to FIG. Figure 2 and 3 As stated. In some examples, the UE 115-d may transmit the SAI based on the first set of resources associated with one or more second cells different from the first cell associated with the UE 115-d.

[0106] In some examples, UE 115-d may measure RSRP corresponding to a first side link resource set. UE 115-d may compare the measured RSRP with an RSRP threshold. UE 115-d may send SAI based on the measured RSRP exceeding the RSRP threshold. In some examples, UE 115-d may determine that a condition associated with side link communication at UE 115-d is met. The condition may correspond to an inter-UE coordination message received by UE 115-d, the number of NA CKs received by UE 115-d, or a measured CBR associated with a side link resource pool exceeding a threshold CBR. UE 115-d may send SAI based on determining that the condition is met.

[0107] The SAI may indicate a time and frequency location of a first set of sidelink resources. In some examples, network entity 105-d may send a control message to UE 115-d indicating an RSRP threshold for sidelink resource preference reporting, a trigger for resource preference reporting by UE 115-d, or both. The first set of sidelink resources may correspond to resources preferred by UE 115-d for sidelink communications or resources not preferred by UE 115-d for sidelink communications based on the control message.

[0108] In some examples, the UE 115-d may transmit a SAI in the first time slot. The first side link resource set indicated by the SAI may be located in a second time slot less than a threshold time period from the first time slot, as reference Figure 3 As stated. The SAI may be transmitted via MAC-CE, side link BSR, or uplink control channel (eg, PUCCH).

[0109] At 415, network entity 105-d may determine a second set of sidelink resources for sidelink communications by UE 115-d based on the first set of sidelink resources indicated by the SAI. In some examples, network entity 105-d may determine whether the first set of sidelink resources indicated by the SAI includes resources allocated by network entity 105-d or resources allocated by one or more other network entities 105. In some examples, the first set of sidelink resources may be associated with one or more second cells different from the first cell supported by network entity 105-d, and network entity 105-d may determine the second set of sidelink resources based on the first set of sidelink resources being associated with the one or more second cells.

[0110] At 420, the network entity 105-d may send a scheduling message to the UE 115-d. The scheduling message may allocate a second set of side link resources for side link communications by the UE 115-d. The second set of side link resources may be based on the first set of side link resources indicated by the SAI. In some examples, the network entity 105-d may send the scheduling message based on determining whether the first set of side link resources indicated by the SAI includes resources allocated by the network entity 105-d or resources allocated by one or more other network entities 105.

[0111] At 425, the UE 115-d may send a side link message to the UE 115-e using the second set of side link resources allocated by the scheduling message.

[0112] Figure 5 A block diagram 500 of a device 505 supporting UE scheduling assistance for mode 1 sidelink communications according to one or more aspects of the present disclosure is shown. The device 505 may be an example of aspects of the UE 115 as described herein. The device 505 may include a receiver 510, a transmitter 515, and a communication manager 520. The device 505 may also include a processor. Each of these components may communicate with each other (e.g., via one or more buses).

[0113] The receiver 510 may provide means for receiving information (such as packets, user data, control information, or any combination thereof) associated with various information channels (e.g., control channels related to UE scheduling assistance for mode 1 sidelink communications, data channels, information channels). The information may be communicated to other components of the device 505. The receiver 510 may utilize a single antenna or a collection of multiple antennas.

[0114] The transmitter 515 may provide means for transmitting signals generated by other components of the device 505. For example, the transmitter 515 may transmit information associated with various information channels (e.g., control channels related to UE scheduling assistance for mode 1 sidelink communications, data channels, information channels), such as packets, user data, control information, or any combination thereof. In some examples, the transmitter 515 may be co-located with the receiver 510 in a transceiver module. The transmitter 515 may utilize a single antenna or a collection of multiple antennas.

[0115] The communication manager 520, the receiver 510, the transmitter 515, or various combinations thereof, or various components thereof may be examples of means for performing various aspects of UE scheduling assistance for mode 1 sidelink communications as described herein. For example, the communication manager 520, the receiver 510, the transmitter 515, or various combinations thereof, or components thereof may support methods for performing one or more of the functions described herein.

[0116] In some examples, the communication manager 520, the receiver 510, the transmitter 515, or various combinations or components thereof may be implemented in hardware (e.g., in a communication management circuit). The hardware may include a processor, a digital signal processor (DSP), a central processing unit (CPU), an application specific integrated circuit (ASIC), a field programmable gate array (FPGA) or other programmable logic device, a microcontroller, discrete gate or transistor logic, discrete hardware components, or any combination thereof that is configured to or otherwise supports components for performing the functions described herein. In some examples, the processor and a memory coupled to the processor may be configured to perform one or more of the functions described herein (e.g., by executing instructions stored in the memory by the processor).

[0117] Additionally or alternatively, in some examples, the communication manager 520, the receiver 510, the transmitter 515, or various combinations or components thereof may be implemented in code executed by a processor (e.g., as communication management software or firmware). If implemented in code executed by a processor, the functionality of the communication manager 520, the receiver 510, the transmitter 515, or various combinations or components thereof may be performed by a general purpose processor (e.g., configured as or otherwise supporting components for performing the functionality described in the present disclosure), a DSP, a CPU, an ASIC, an FPGA, a microcontroller, or any combination of these or other programmable logic devices.

[0118] In some examples, communication manager 520 may be configured to perform various operations (e.g., receive, obtain, monitor, output, send) using or otherwise cooperating with receiver 510, transmitter 515, or both. For example, communication manager 520 may receive information from receiver 510, transmit information to transmitter 515, or be integrated in conjunction with receiver 510, transmitter 515, or both to obtain information, output information, or perform various other operations as described herein.

[0119] According to examples as disclosed herein, the communication manager 520 may support wireless communications at the UE. For example, the communication manager 520 may be configured to or otherwise support a component for sending an SAI indicating a first set of side link resources for side link communications performed by the UE via an uplink communication link. The communication manager 520 may be configured to or otherwise support a component for receiving a scheduling message allocating a second set of side link resources for side link communications performed by the UE, the second set of side link resources being based on the first set of side link resources indicated via the SAI. The communication manager 520 may be configured to or otherwise support a component for sending a side link message via the second set of side link resources allocated by the scheduling message.

[0120] By including or configuring the communication manager 520 according to examples as described herein, the device 505 (e.g., a processor controlling or otherwise coupled to the receiver 510, the transmitter 515, the communication manager 520, or a combination thereof) can support techniques for reducing processing and reducing power consumption. For example, by sending an identification of available resources corresponding to resources that the device 505 is not monitoring, the processor of the device 505 can avoid processing (e.g., monitoring and performing channel measurements) for each resource in the resource pool.

[0121] Figure 6 A block diagram 600 of a device 605 supporting UE scheduling assistance for mode 1 sidelink communications according to one or more aspects of the present disclosure is shown. The device 605 may be an example of aspects of the device 505 or UE 115 as described herein. The device 605 may include a receiver 610, a transmitter 615, and a communication manager 620. The device 605 may also include a processor. Each of these components may communicate with each other (e.g., via one or more buses).

[0122] The receiver 610 may provide means for receiving information (such as packets, user data, control information, or any combination thereof) associated with various information channels (e.g., control channels related to UE scheduling assistance for mode 1 sidelink communications, data channels, information channels). The information may be communicated to other components of the device 605. The receiver 610 may utilize a single antenna or a collection of multiple antennas.

[0123] The transmitter 615 may provide means for transmitting signals generated by other components of the device 605. For example, the transmitter 615 may transmit information associated with various information channels (e.g., control channels related to UE scheduling assistance for mode 1 sidelink communications, data channels, information channels), such as packets, user data, control information, or any combination thereof. In some examples, the transmitter 615 may be co-located with the receiver 610 in a transceiver module. The transmitter 615 may utilize a single antenna or a collection of multiple antennas.

[0124] The device 605 or its various components may be examples of components for performing various aspects of UE scheduling assistance for mode 1 sidelink communications as described herein. For example, the communication manager 620 may include an SAI component 625, a scheduling message component 630, a sending component 635, or any combination thereof. The communication manager 620 may be an example of various aspects of the communication manager 520 as described herein. In some examples, the communication manager 620 or its various components may be configured to use or otherwise cooperate with the receiver 610, the transmitter 615, or both to perform various operations (e.g., receive, obtain, monitor, output, send). For example, the communication manager 620 may receive information from the receiver 610, transmit information to the transmitter 615, or integrate with the receiver 610, the transmitter 615, or both to obtain information, output information, or perform various other operations as described herein.

[0125] According to examples as disclosed herein, the communication manager 620 may support wireless communications at the UE. The SAI component 625 may be configured to or otherwise support components for sending, via an uplink communication link, an SAI indicating a first set of sidelink resources for sidelink communications performed by the UE. The scheduling message component 630 may be configured to or otherwise support components for receiving a scheduling message allocating a second set of sidelink resources for sidelink communications performed by the UE, the second set of sidelink resources being based on the first set of sidelink resources indicated via the SAI. The sending component 635 may be configured to or otherwise support components for sending a sidelink message via the second set of sidelink resources allocated by the scheduling message.

[0126] Figure 7 A block diagram 700 of a communication manager 720 supporting UE scheduling assistance for mode 1 sidelink communications according to one or more aspects of the present disclosure is shown. The communication manager 720 can be an example of aspects of the communication manager 520, the communication manager 620, or both as described herein. The communication manager 720 or its various components can be examples of components for performing various aspects of UE scheduling assistance for mode 1 sidelink communications as described herein. For example, the communication manager 720 may include a SAI component 725, a scheduling message component 730, a sending component 735, a sidelink resource monitoring component 740, a sidelink resource component 745, an SCI component 750, a triggering component 755, a sidelink resource component 760, a control message component 765, a cell ID component 770, a measurement component 775, or any combination thereof. Each of these components can communicate with each other directly or indirectly (e.g., via one or more buses).

[0127] According to examples as disclosed herein, the communication manager 720 may support wireless communications at the UE. The SAI component 725 may be configured to or otherwise support components for sending, via an uplink communication link, an SAI indicating a first set of sidelink resources for sidelink communications performed by the UE. The scheduling message component 730 may be configured to or otherwise support components for receiving a scheduling message allocating a second set of sidelink resources for sidelink communications performed by the UE, the second set of sidelink resources being based on the first set of sidelink resources indicated via the SAI. The sending component 735 may be configured to or otherwise support components for sending a sidelink message via the second set of sidelink resources allocated by the scheduling message.

[0128] In some examples, the sidelink resource monitoring component 740 may be configured as or otherwise support components for monitoring an SCI from one or more other UEs, the SCI indicating a set of multiple sidelink resources reserved for sidelink transmissions by the one or more other UEs, wherein a first set of sidelink resources indicated via the SAI is based on the SCI.

[0129] In some examples, to support sending SAI, the sending component 735 may be configured as or otherwise support means for sending via SAI an indication that a first side link resource set is reserved based on a set of multiple side link resources indicated via SCI including at least the first side link resource set.

[0130] In some examples, the cell ID component 770 may be configured as or otherwise support components for receiving, via an SCI, an ID of a corresponding cell associated with each side link resource in a set of multiple side link resources, wherein sending an indication that a first set of side link resources is reserved is based on the first set of side link resources being associated with one or more second cells that are different from a first cell associated with the UE.

[0131] In some examples, sidelink component 775 may be configured or otherwise support means for measuring RSRP associated with the first subset of resources. In some examples, measurement component 775 may be configured or otherwise support means for comparing the measured RSRP to an RSRP threshold, wherein sending an indication of the first set of sidelink resources via the SAI is based on the measured RSRP exceeding the RSRP threshold.

[0132] In some examples, the side link resource component 745 may be configured as or otherwise support components for receiving one or more inter-UE coordination messages via a side link communication link, each of the one or more inter-UE coordination messages indicating one or more side link resources based on a corresponding side link channel sensing procedure, wherein sending the SAI is based on the one or more inter-UE coordination messages.

[0133] In some examples, the one or more inter-UE coordination messages include preferred resource information, and the side link resource component 760 may be configured as or otherwise support a component for determining that a first side link resource set is common to one or more side link resources indicated by each of the one or more inter-UE coordination messages, wherein sending the SAI indicating the first side link resource set is based on the determination.

[0134] In some examples, the one or more inter-UE coordination messages include non-preferred resource information, and the side link resource component 760 may be configured as or otherwise support a component for determining that a first side link resource set includes a union of one or more side link resources indicated via each of the one or more inter-UE coordination messages, wherein sending the SAI indicating the first side link resource set is based on the determination.

[0135] In some examples, the SCI component 750 may be configured to or otherwise support a component for monitoring the SCI in the side link resources of the side link resource pool, wherein the SCI indicates a set of multiple side link resources reserved for side link transmission by one or more second UEs. In some examples, the side link resource component 760 may be configured to or otherwise support a component for determining a first side link resource set based on one or more side link resources indicated via each of the one or more inter-UE coordination messages and a set of multiple side link resources indicated via the SCI, wherein sending the SAI is based on determining the first side link resource set.

[0136] In some examples, the SCI component 750 may be configured as or otherwise support components for determining that a condition associated with sidelink communications at a UE is satisfied, wherein sending the SAI is based on determining that the condition is satisfied, and wherein the condition corresponds to an inter-UE coordination message received by the UE, a number of negative acknowledgments received by the UE exceeding a threshold number, or a measured channel busy rate associated with a sidelink resource pool exceeding a threshold channel busy rate.

[0137] In some examples, trigger component 755 may be configured or otherwise support means for receiving a control message including a trigger for a resource preference report by the UE, wherein sending the SAI is based on the trigger.

[0138] In some examples, the control message indicates whether a resource preference report by the UE corresponds to reporting sidelink resources preferred by the UE for sidelink communication or sidelink resources not preferred by the UE for sidelink communication. In some examples, the SAI indicates a time and frequency location of a first set of sidelink resources, the first set of sidelink resources corresponding to resources preferred by the UE for sidelink communication or resources not preferred by the UE for sidelink communication based on the control message.

[0139] In some examples, the side link resource component 760 may be configured or otherwise support components for determining a first set of side link resources based on a side link channel sensing procedure, one or more inter-UE coordination messages, or both, depending on the capabilities of the UE.

[0140] In some examples, communication component 765 can be configured or otherwise support means for receiving a control message indicating a sidelink resource preference reporting configuration. In some examples, sidelink resource component 760 can be configured or otherwise support means for determining a first set of sidelink resources based on a sidelink channel sensing procedure, one or more inter-UE coordination messages, or both, in accordance with the sidelink resource preference reporting configuration.

[0141] In some examples, to support sending SAI, the sending component 735 may be configured to or otherwise support components for sending SAI via a first time slot, wherein a first side link resource set indicated via the SAI is located in a second time slot that is less than a threshold time period from the first time slot.

[0142] In some examples, to support sending SAI, the transmission component 735 may be configured or otherwise support components for sending a medium access control-control element, a sidelink buffer status report, or an uplink control channel including the SAI.

[0143] Figure 8A diagram of a system 800 including a device 805 supporting UE scheduling assistance for mode 1 sidelink communications according to one or more aspects of the present disclosure is shown. The device 805 may be an example of a device 505, a device 605, or a UE 115 as described herein, or include components thereof. The device 805 may communicate (e.g., wirelessly) with one or more network entities 105, one or more UEs 115, or any combination thereof. The device 805 may include components for two-way voice and data communications, including components for sending and receiving communications, such as a communication manager 820, an input / output (I / O) controller 810, a transceiver 815, an antenna 825, a memory 830, a code 835, and a processor 840. These components may be electronically communicated or otherwise coupled (e.g., operatively, communicatively, functionally, electronically, electrically) via one or more buses (e.g., a bus 845).

[0144] I / O controller 810 can manage input signals and output signals of device 805. I / O controller 810 can also manage peripheral devices that are not integrated into device 805. In some cases, I / O controller 810 can represent a physical connection or port to an external peripheral device. In some cases, I / O controller 810 can utilize an operating system, such as or another known operating system. Additionally or alternatively, I / O controller 810 may represent or interact with a modem, keyboard, mouse, touch screen, or similar device. In some cases, I / O controller 810 may be implemented as part of a processor such as processor 840. In some cases, a user may interact with device 805 via I / O controller 810 or via hardware components controlled by I / O controller 810.

[0145] In some cases, the device 805 may include a single antenna 825. However, in some other cases, the device 805 may have more than one antenna 825, which may be capable of concurrently transmitting or receiving multiple wireless transmissions. The transceiver 815 may communicate bidirectionally via one or more antennas 825, wired or wireless links as described herein. For example, the transceiver 815 may represent a wireless transceiver and may communicate bidirectionally with another wireless transceiver. The transceiver 815 may also include a modem for modulating packets, providing the modulated packets to one or more antennas 825 for transmission, and demodulating packets received from one or more antennas 825. The transceiver 815 or the transceiver 815 and one or more antennas 825 may be examples of transmitters 515, transmitters 615, receivers 510, receivers 610, or any combination thereof or components thereof as described herein.

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

[0147] The processor 840 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 cases, the processor 840 may be configured to operate a memory array using a memory controller. In some other cases, the memory controller may be integrated into the processor 840. The processor 840 may be configured to execute computer-readable instructions stored in a memory (e.g., a memory 830) to cause the device 805 to perform various functions (e.g., functions or tasks that support UE scheduling assistance for mode 1 sidelink communications). For example, the device 805 or a component of the device 805 may include a processor 840 and a memory 830 coupled to or coupled to the processor 840, and the processor 840 and the memory 830 are configured to perform the various functions described herein.

[0148] According to examples as disclosed herein, the communication manager 820 may support wireless communications at the UE. For example, the communication manager 820 may be configured to or otherwise support a component for sending an SAI indicating a first set of side link resources for side link communications performed by the UE via an uplink communication link. The communication manager 820 may be configured to or otherwise support a component for receiving a scheduling message allocating a second set of side link resources for side link communications performed by the UE, the second set of side link resources being based on the first set of side link resources indicated via the SAI. The communication manager 820 may be configured to or otherwise support a component for sending a side link message via the second set of side link resources allocated by the scheduling message.

[0149] By including or configuring a communication manager 820 according to the examples described herein, the device 805 can support techniques for reducing latency, reducing power consumption, extending battery life, and improving utilization of processing capabilities. The device 805 can avoid the increased latency that may be caused by sending the SAI by determining that resources in the resource selection window corresponding to resources that the device 805 does not monitor in the corresponding sensing window are available for sidelink transmission. The device 805 can thus be configured with a resource reservation configuration that can allow for some potential interference to better enable the sidelink device 805 to perform sidelink transmissions without conflicts.

[0150] In some examples, the communication manager 820 may be configured to perform various operations (e.g., receive, monitor, transmit) using or otherwise cooperating with the transceiver 815, one or more antennas 825, or any combination thereof. Although the communication manager 820 is illustrated as a separate component, in some examples, one or more functions described with reference to the communication manager 820 may be supported or performed by the processor 840, the memory 830, the code 835, or any combination thereof. For example, the code 835 may include instructions that are executable by the processor 840 to cause the device 805 to perform various aspects of UE scheduling assistance for mode 1 sidelink communications as described herein, or the processor 840 and the memory 830 may be otherwise configured to perform or support such operations.

[0151] Fig. 9 A block diagram 900 of a device 905 supporting UE scheduling assistance for mode 1 sidelink communications according to one or more aspects of the present disclosure is shown. The device 905 may be an example of aspects of the network entity 105 as described herein. The device 905 may include a receiver 910, a transmitter 915, and a communication manager 920. The device 905 may also include a processor. Each of these components may communicate with each other (e.g., via one or more buses).

[0152] Receiver 910 may provide means for obtaining (e.g., receiving, determining, identifying) information associated with various channels (e.g., control channels, data channels, information channels, channels associated with a protocol stack), such as user data, control information, or any combination thereof (e.g., I / Q samples, symbols, packets, protocol data units, service data units). The information may be communicated to other components of device 905. In some examples, receiver 910 may support obtaining information by receiving signals via one or more antennas. Additionally or alternatively, receiver 910 may support obtaining information by receiving signals via one or more wired (e.g., electrical, optical) interfaces, wireless interfaces, or any combination thereof.

[0153] The transmitter 915 may provide a means for outputting (e.g., sending, providing, conveying, transmitting) information generated by other components of the device 905. For example, the transmitter 915 may output information associated with various channels (e.g., control channels, data channels, information channels, channels associated with a protocol stack), such as user data, control information, or any combination thereof (e.g., I / Q samples, symbols, packets, protocol data units, service data units). In some examples, the transmitter 915 may support outputting information by sending signals via one or more antennas. Additionally or alternatively, the transmitter 915 may support outputting information by sending signals via one or more wired (e.g., electrical, optical) interfaces, wireless interfaces, or any combination thereof. In some examples, the transmitter 915 and the receiver 910 may be co-located in a transceiver, which may include a modem or be coupled to a modem.

[0154] The communication manager 920, the receiver 910, the transmitter 915, or various combinations thereof, or various components thereof may be examples of means for performing various aspects of UE scheduling assistance for mode 1 sidelink communications as described herein. For example, the communication manager 920, the receiver 910, the transmitter 915, or various combinations thereof, or components thereof may support methods for performing one or more of the functions described herein.

[0155] In some examples, the communication manager 920, the receiver 910, the transmitter 915, or various combinations or components thereof may be implemented in hardware (e.g., in a communication management circuit). The hardware may include a processor, a DSP, a CPU, an ASIC, an FPGA or other programmable logic device, a microcontroller, discrete gate or transistor logic, discrete hardware components, or any combination thereof that is configured as or otherwise supports components for performing the functions described herein. In some examples, a processor and a memory coupled to the processor may be configured to perform one or more of the functions described herein (e.g., by executing instructions stored in the memory by the processor).

[0156] Additionally or alternatively, in some examples, the communication manager 920, the receiver 910, the transmitter 915, or various combinations or components thereof may be implemented in code executed by a processor (e.g., as communication management software or firmware). If implemented in code executed by a processor, the functionality of the communication manager 920, the receiver 910, the transmitter 915, or various combinations or components thereof may be performed by a general purpose processor (e.g., configured as or otherwise supporting components for performing the functions described in the present disclosure), a DSP, a CPU, an ASIC, an FPGA, a microcontroller, or any combination of these or other programmable logic devices.

[0157] In some examples, the communication manager 920 may be configured to perform various operations (e.g., receive, obtain, monitor, output, transmit) using or otherwise cooperating with the receiver 910, the transmitter 915, or both. For example, the communication manager 920 may receive information from the receiver 910, transmit information to the transmitter 915, or be integrated in conjunction with the receiver 910, the transmitter 915, or both to obtain information, output information, or perform various other operations as described herein.

[0158] According to examples as disclosed herein, the communication manager 920 may support wireless communications at a network entity. For example, the communication manager 920 may be configured to or otherwise support a component for receiving, via an uplink communication link, an SAI indicating a first set of sidelink resources for sidelink communications performed by the UE. The communication manager 920 may be configured to or otherwise support a component for determining a second set of sidelink resources for sidelink communications performed by the UE based on the first set of sidelink resources indicated via the SAI. The communication manager 920 may be configured to or otherwise support a component for sending a scheduling message allocating a second set of sidelink resources for sidelink communications performed by the UE.

[0159] By including or configuring the communication manager 920 according to examples as described herein, the device 905 (e.g., a processor controlling or otherwise coupled to the receiver 910, the transmitter 915, the communication manager 920, or a combination thereof) can support techniques for reducing processing and reducing power consumption. For example, by sending an identification of available resources corresponding to resources that the device 505 is not monitoring, the processor of the device 505 can avoid processing (e.g., monitoring and performing channel measurements) for each resource in the resource pool.

[0160] Fig.10 A block diagram 1000 of a device 1005 supporting UE scheduling assistance for mode 1 sidelink communications according to one or more aspects of the present disclosure is shown. The device 1005 may be an example of aspects of the device 905 or network entity 105 as described herein. The device 1005 may include a receiver 1010, a transmitter 1015, and a communication manager 1020. The device 1005 may also include a processor. Each of these components may communicate with each other (e.g., via one or more buses).

[0161] Receiver 1010 may provide means for obtaining (e.g., receiving, determining, identifying) information associated with various channels (e.g., control channels, data channels, information channels, channels associated with a protocol stack), such as user data, control information, or any combination thereof (e.g., I / Q samples, symbols, packets, protocol data units, service data units). The information may be communicated to other components of device 1005. In some examples, receiver 1010 may support obtaining information by receiving signals via one or more antennas. Additionally or alternatively, receiver 1010 may support obtaining information by receiving signals via one or more wired (e.g., electrical, optical) interfaces, wireless interfaces, or any combination thereof.

[0162] The transmitter 1015 may provide a means for outputting (e.g., sending, providing, conveying, transmitting) information generated by other components of the device 1005. For example, the transmitter 1015 may output information associated with various channels (e.g., control channels, data channels, information channels, channels associated with a protocol stack), such as user data, control information, or any combination thereof (e.g., I / Q samples, symbols, packets, protocol data units, service data units). In some examples, the transmitter 1015 may support outputting information by sending signals via one or more antennas. Additionally or alternatively, the transmitter 1015 may support outputting information by sending signals via one or more wired (e.g., electrical, optical) interfaces, wireless interfaces, or any combination thereof. In some examples, the transmitter 1015 and the receiver 1010 may be co-located in a transceiver, which may include a modem or be coupled to a modem.

[0163] Device 1005 or its various components may be examples of components for performing various aspects of UE scheduling assistance for mode 1 sidelink communications as described herein. For example, communication manager 1020 may include SAI component 1025, sidelink resource determination component 1030, transmission component 1035, or any combination thereof. Communication manager 1020 may be an example of various aspects of communication manager 920 as described herein. In some examples, communication manager 1020 or its various components may be configured to use or otherwise cooperate with receiver 1010, transmitter 1015, or both to perform various operations (e.g., receive, obtain, monitor, output, send). For example, communication manager 1020 may receive information from receiver 1010, transmit information to transmitter 1015, or integrate with receiver 1010, transmitter 1015, or both to obtain information, output information, or perform various other operations as described herein.

[0164] According to examples as disclosed herein, the communication manager 1020 may support wireless communications at a network entity. The SAI component 1025 may be configured to or otherwise support components for receiving, via an uplink communication link, an SAI indicating a first set of sidelink resources for sidelink communications performed by the UE. The sidelink resource determination component 1030 may be configured to or otherwise support components for determining a second set of sidelink resources for sidelink communications performed by the UE based on the first set of sidelink resources indicated via the SAI. The sending component 1035 may be configured to or otherwise support components for sending a scheduling message allocating a second set of sidelink resources for sidelink communications performed by the UE.

[0165] Fig.11 A block diagram 1100 of a communication manager 1120 supporting UE scheduling assistance for mode 1 sidelink communications according to one or more aspects of the present disclosure is shown. The communication manager 1120 may be an example of aspects of the communication manager 920, the communication manager 1020, or both as described herein. The communication manager 1120 or its various components may be examples of components for performing various aspects of UE scheduling assistance for mode 1 sidelink communications as described herein. For example, the communication manager 1120 may include a SAI component 1125, a sidelink resource determination component 1130, a transmission component 1135, a cell ID component 1140, a reception component 1145, or any combination thereof. Each of these components may communicate with each other directly or indirectly (e.g., via one or more buses), which communication may include communication within a protocol layer of a protocol stack, communication associated with a logical channel of a protocol stack (e.g., between protocol layers of a protocol stack, within a device, component, or virtualized component associated with the network entity 105, between devices, components, or virtualized components associated with the network entity 105), or any combination thereof.

[0166] According to examples as disclosed herein, the communication manager 1120 may support wireless communications at a network entity. The SAI component 1125 may be configured to or otherwise support components for receiving, via an uplink communication link, an SAI indicating a first set of sidelink resources for sidelink communications performed by the UE. The sidelink resource determination component 1130 may be configured to or otherwise support components for determining a second set of sidelink resources for sidelink communications performed by the UE based on the first set of sidelink resources indicated via the SAI. The sending component 1135 may be configured to or otherwise support components for sending a scheduling message allocating a second set of sidelink resources for sidelink communications performed by the UE.

[0167] In some examples, the side link resource determination component 1130 may be configured to or otherwise support a component for determining whether a first side link resource set indicated via the SAI includes resources allocated by a network entity or resources allocated by one or more second network entities, wherein sending a scheduling message allocating a second side link resource set is based on the determination.

[0168] In some examples, the first side link resource set indicated via the SAI is associated with one or more second cells different from the first cell supported by the network entity. In some examples, determining the second side link resource set is based on the first side link resource set being associated with the one or more second cells.

[0169] In some examples, transmitting component 1135 may be configured or otherwise support means for sending a control message indicating an RSRP threshold for sidelink resource preference reporting, wherein receiving an SAI indicating a first set of sidelink resources is based on the RSRP threshold.

[0170] In some examples, sending component 1135 may be configured or otherwise support means for sending a control message including a trigger for a resource preference report by the UE, wherein receiving the SAI is based on the trigger.

[0171] In some examples, the control message indicates whether a resource preference report by the UE corresponds to reporting sidelink resources preferred by the UE for sidelink communication or sidelink resources not preferred by the UE for sidelink communication. In some examples, the SAI indicates a time and frequency location of a first set of sidelink resources, the first set of sidelink resources corresponding to resources preferred by the UE for sidelink communication or resources not preferred by the UE for sidelink communication based on the control message.

[0172] In some examples, transmitting component 1135 may be configured as or otherwise support components for sending a control message indicating a side link resource preference reporting configuration, wherein a first set of side link resources is based on a first side link channel sensing procedure at a UE, a second side link channel sensing procedure at one or more second UEs, or both, in accordance with the side link resource preference reporting configuration.

[0173] In some examples, to support receiving SAI, SAI component 1125 may be configured or otherwise support means for receiving SAI via a first time slot, wherein a first side link resource set indicated via the SAI is located in a second time slot that is less than a threshold time period from the first time slot.

[0174] In some examples, to support receiving SAI, receiving component 1145 may be configured or otherwise support means for receiving a medium access control-control element, a sidelink buffer status report, an uplink control channel, or any combination thereof including SAI.

[0175] Fig.12 A diagram of a system 1200 including a device 1205 supporting UE scheduling assistance for mode 1 sidelink communications according to one or more aspects of the present disclosure is shown. The device 1205 may be an example of a device 905, a device 1005, or a network entity 105 as described herein, or include components thereof. The device 1205 may communicate with one or more network entities 105, one or more UEs 115, or any combination thereof, which communication may include communication through one or more wired interfaces, through one or more wireless interfaces, or any combination thereof. The device 1205 may include components that support output and acquisition of communications, such as a communication manager 1220, a transceiver 1210, an antenna 1215, a memory 1225, a code 1230, and a processor 1235. These components may be in electronic communication or otherwise coupled (e.g., operatively, communicatively, functionally, electronically, electrically) via one or more buses (e.g., bus 1240).

[0176] The transceiver 1210 may support bidirectional communication via a wired link, a wireless link, or both as described herein. In some examples, the transceiver 1210 may include a wired transceiver and may communicate bidirectionally with another wired transceiver. Additionally or alternatively, in some examples, the transceiver 1210 may include a wireless transceiver and may communicate bidirectionally with another wireless transceiver. In some examples, the device 1205 may include one or more antennas 1215, which may be capable of (e.g., concurrently) sending or receiving wireless transmissions. The transceiver 1210 may also include a modem for: modulating a signal, providing the modulated signal for transmission (e.g., via one or more antennas 1215, via a wired transmitter), receiving the modulated signal (e.g., from one or more antennas 1215, from a wired receiver), and demodulating the signal. In some implementations, the transceiver 1210 may include one or more interfaces, such as one or more interfaces coupled to one or more antennas 1215 configured to support various receiving or obtaining operations, or one or more interfaces coupled to one or more antennas 1215 configured to support various transmitting operations or output operations, or a combination thereof. In some implementations, the transceiver 1210 may include or be configured to be coupled to one or more processors or memory components that are operable to: perform or support operations based on received or obtained information or signals, or generate information or other signals for transmission or other output, or any combination thereof. In some implementations, the transceiver 1210, or the transceiver 1210 and one or more antennas 1215, or the transceiver 1210 and one or more antennas 1215 and one or more processors or memory components (e.g., processor 1235, or memory 1225, or both) may be included in a chip or chip assembly installed in the device 1205. In some examples, the transceiver may be operable to support communications via one or more communication links (eg, communication link 125, backhaul communication link 120, midhaul communication link 162, fronthaul communication link 168).

[0177] Memory 1225 may include RAM and ROM. Memory 1225 may store computer-readable, computer-executable code 1230 including instructions that, when executed by processor 1235, cause device 1205 to perform various functions described herein. Code 1230 may be stored in a non-transitory computer-readable medium such as system memory or another type of memory. In some cases, code 1230 may not be directly executable by processor 1235, but may (e.g., when compiled and executed) cause a computer to perform the functions described herein. In some cases, memory 1225 may also contain, among other things, a BIOS that may control basic hardware or software operations, such as interaction with peripheral components or devices.

[0178] The processor 1235 may include an intelligent hardware device (e.g., a general-purpose processor, a DSP, an ASIC, a CPU, an FPGA, a microcontroller, a programmable logic device, a discrete gate or transistor logic, a discrete hardware component, or any combination thereof). In some cases, the processor 1235 may be configured to operate a memory array using a memory controller. In some other cases, the memory controller may be integrated into the processor 1235. The processor 1235 may be configured to execute computer-readable instructions stored in a memory (e.g., memory 1225) to enable the device 1205 to perform various functions (e.g., functions or tasks that support UE scheduling assistance for mode 1 side link communication). For example, the device 1205 or a component of the device 1205 may include a processor 1235 and a memory 1225 coupled to the processor 1235, and the processor 1235 and the memory 1225 are configured to perform the various functions described herein. The processor 1235 may be an example of a cloud computing platform (e.g., one or more physical nodes and supporting software, such as an operating system, a virtual machine, or a container example) that can host functions (e.g., by executing code 1230) to perform functions of the device 1205. The processor 1235 may be any one or more suitable processors capable of executing scripts or instructions of one or more software programs stored in the device 1205 (such as in the memory 1225). In some specific implementations, the processor 1235 may be a component of a processing system. A processing system may generally refer to a system or a series of machines or components that receive inputs and process these inputs to produce a set of outputs (which may be passed to other systems or components (e.g., the device 1205)). For example, the processing system of the device 1205 may refer to a system including various other components or subcomponents of the device 1205, such as the processor 1235, or the transceiver 1210, or the communication manager 1220, or other components or combinations of components of the device 1205. The processing system of device 1205 may interface with other components of device 1205, and may process information (such as input or signals) received from other components or output information to other components. For example, a chip or modem of device 1205 may include a processing system and one or more interfaces for outputting information or for obtaining information or both. One or more interfaces may be implemented as or otherwise include a first interface configured to output information and a second interface configured to obtain information, or the same interface configured to output information and obtain information, as well as other specific implementations. In some specific implementations, one or more interfaces may refer to an interface between a processing system of a chip or modem and a transmitter, so that device 1205 can send information output from the chip or modem.Additionally or alternatively, in some implementations, one or more interfaces may refer to an interface between a processing system and a receiver of a chip or modem, such that the device 1205 may obtain information or signal input, and the information may be passed to the processing system. One of ordinary skill in the art will readily recognize that a first interface may also obtain information or signal input, and a second interface may also output information or signal output.

[0179] In some examples, bus 1240 may support communications of a protocol layer (e.g., within a protocol layer) of a protocol stack. In some examples, bus 1240 may support communications associated with a logical channel of a protocol stack (e.g., between protocol layers of a protocol stack), which may include communications performed within a component of device 1205, or communications performed between different components of device 1205 that may be co-located or may be located in different locations (e.g., where device 1205 may refer to a system in which one or more of communication manager 1220, transceiver 1210, memory 1225, code 1230, and processor 1235 may be located in one of the different components or divided between the different components).

[0180] In some examples, the communication manager 1220 may manage aspects of communications with the core network 130 (e.g., via one or more wired or wireless backhaul links). For example, the communication manager 1220 may manage the delivery of data communications for client devices, such as one or more UEs 115. In some examples, the communication manager 1220 may manage communications with other network entities 105 and may include a controller or scheduler for controlling communications with the UEs 115 in coordination with the other network entities 105. In some examples, the communication manager 1220 may support an X2 interface within an LTE / LTE-A wireless communication network technology to provide communications between network entities 105.

[0181] According to examples as disclosed herein, the communication manager 1220 may support wireless communications at a network entity. For example, the communication manager 1220 may be configured to or otherwise support a component for receiving, via an uplink communication link, an SAI indicating a first set of sidelink resources for sidelink communications performed by the UE. The communication manager 1220 may be configured to or otherwise support a component for determining a second set of sidelink resources for sidelink communications performed by the UE based on the first set of sidelink resources indicated via the SAI. The communication manager 1220 may be configured to or otherwise support a component for sending a scheduling message allocating a second set of sidelink resources for sidelink communications performed by the UE.

[0182] By including or configuring the communication manager 1220 according to the examples described herein, the device 1205 can support techniques for reducing latency, reducing power consumption, extending battery life, and improving utilization of processing power. The device 805 can avoid the increased latency that may be caused by sending the SAI by determining that resources in the resource selection window corresponding to resources that the device 805 did not monitor in the corresponding sensing window are available for sidelink transmission. The device 805 can thus be configured with a resource reservation configuration that can allow for some potential interference to better enable the sidelink device 805 to perform sidelink transmissions without conflicts.

[0183] In some examples, the communication manager 1220 may be configured to perform various operations (e.g., receive, obtain, monitor, output, transmit) using or otherwise cooperating with the transceiver 1210, one or more antennas 1215 (e.g., where applicable), or any combination thereof. Although the communication manager 1220 is illustrated as a separate component, in some examples, one or more functions described with reference to the communication manager 1220 may be supported or performed by the transceiver 1210, the processor 1235, the memory 1225, the code 1230, or any combination thereof. For example, the code 1230 may include instructions that are executable by the processor 1235 to cause the device 1205 to perform various aspects of UE scheduling assistance for mode 1 sidelink communications as described herein, or the processor 1235 and the memory 1225 may be otherwise configured to perform or support such operations.

[0184] Fig.13 A flow chart illustrating a method 1300 for supporting UE scheduling assistance for mode 1 sidelink communications according to one or more aspects of the present disclosure is shown. The operations of the method 1300 may be implemented by a UE or a component thereof as described herein. For example, the operations of the method 1300 may be implemented by a UE or a component thereof as described in reference to Figures 1 to 8 The UE 115 described herein performs. In some examples, the UE may execute an instruction set to control the functional elements of the UE to perform the described functions. Additionally or alternatively, the UE may use dedicated hardware to perform various aspects of the described functions.

[0185] At 1305, the method may include: sending, via an uplink communication link, a SAI indicating a first set of sidelink resources for sidelink communication by the UE. The operations of 1305 may be performed according to examples as disclosed herein. In some examples, aspects of the operations of 1305 may be performed as described in reference to Figure 7 The SAI component 725 executes.

[0186] At 1310, the method may include receiving a scheduling message allocating a second set of side link resources for side link communication by the UE, the second set of side link resources being based on the first set of side link resources indicated via the SAI. The operations of 1310 may be performed according to examples as disclosed herein. In some examples, aspects of the operations of 1310 may be performed as described in reference to Figure 7 The scheduling message component 730 executes.

[0187] At 1315, the method may include sending the side link message via the second side link resource set allocated by the scheduling message. The operations of 1315 may be performed according to examples as disclosed herein. In some examples, aspects of the operations of 1315 may be performed as described in reference to Figure 7 The sending component 735 executes.

[0188] Fig.14 A flow chart illustrating a method 1400 for supporting UE scheduling assistance for mode 1 sidelink communications according to one or more aspects of the present disclosure is shown. The operations of the method 1400 may be implemented by a UE or a component thereof as described herein. For example, the operations of the method 1400 may be implemented by a UE or a component thereof as described in reference to Figures 1 to 8 The UE 115 described herein performs. In some examples, the UE may execute an instruction set to control the functional elements of the UE to perform the described functions. Additionally or alternatively, the UE may use dedicated hardware to perform various aspects of the described functions.

[0189] At 1405, the method may include: monitoring an SCI from one or more other UEs, the SCI indicating a set of a plurality of sidelink resources reserved for sidelink transmissions by the one or more other UEs. The operations of 1405 may be performed according to examples as disclosed herein. In some examples, aspects of the operations of 1405 may be performed as described in reference to Figure 7 The side link resource monitoring component 740 executes.

[0190] At 1410, the method may include: sending, via an uplink communication link, an SAI indicating a first set of sidelink resources for sidelink communication by the UE, wherein the first set of sidelink resources indicated via the SAI is based on the SCI. The operations of 1410 may be performed according to examples as disclosed herein. In some examples, aspects of the operations of 1410 may be performed as described in reference to Figure 7 The SAI component 725 executes.

[0191] At 1415, the method may include receiving a scheduling message allocating a second set of side link resources for side link communication by the UE, the second set of side link resources being based on the first set of side link resources indicated via the SAI. The operations of 1415 may be performed according to examples as disclosed herein. In some examples, aspects of the operations of 1415 may be performed as described in reference to Figure 7 The scheduling message component 730 executes.

[0192] At 1420, the method may include sending a side link message via a second set of side link resources allocated by the scheduling message. The operations of 1420 may be performed according to examples as disclosed herein. In some examples, aspects of the operations of 1420 may be performed as described in reference to Figure 7 The sending component 735 executes.

[0193] Fig.15 A flow chart illustrating a method 1500 for supporting UE scheduling assistance for mode 1 sidelink communications according to one or more aspects of the present disclosure is shown. The operations of the method 1500 may be implemented by a network entity or a component thereof as described herein. For example, the operations of the method 1500 may be implemented by a network entity or a component thereof as described herein. Figures 1 to 4 as well as Figures 9 to 12 The network entity described performs. In some examples, the network entity may execute an instruction set to control the functional elements of the network entity to perform the described functions. Additionally or alternatively, the network entity may use dedicated hardware to perform various aspects of the described functions.

[0194] At 1505, the method may include receiving, via an uplink communication link, a SAI indicating a first set of sidelink resources for sidelink communication by the UE. The operations of 1505 may be performed according to examples as disclosed herein. In some examples, aspects of the operations of 1505 may be performed as described in reference to Fig.11 The SAI component 1125 executes.

[0195] At 1510, the method may include determining a second set of sidelink resources for sidelink communication by the UE based on the first set of sidelink resources indicated via the SAI. The operations of 1510 may be performed according to examples as disclosed herein. In some examples, aspects of the operations of 1510 may be performed as described in reference to Fig.11 The side link resource determination component 1130 executes.

[0196] At 1515, the method may include sending a scheduling message allocating a second set of side link resources for side link communications by the UE. The operations of 1515 may be performed according to examples as disclosed herein. In some examples, aspects of the operations of 1515 may be performed as described in reference to Fig.11 The sending component 1135 executes.

[0197] Fig.16 A flow chart illustrating a method 1600 for supporting UE scheduling assistance for mode 1 sidelink communications according to one or more aspects of the present disclosure is shown. The operations of the method 1600 may be implemented by a network entity or a component thereof as described herein. For example, the operations of the method 1600 may be implemented by a network entity or a component thereof as described herein. Figures 1 to 4 as well as Figures 9 to 12 The network entity described performs. In some examples, the network entity may execute an instruction set to control the functional elements of the network entity to perform the described functions. Additionally or alternatively, the network entity may use dedicated hardware to perform various aspects of the described functions.

[0198] At 1605, the method may include: receiving, via an uplink communication link, a SAI indicating a first set of sidelink resources for sidelink communication by the UE. The operations of 1605 may be performed according to examples as disclosed herein. In some examples, aspects of the operations of 1605 may be performed as described in reference to Fig.11 The SAI component 1125 executes.

[0199] At 1610, the method may include determining a second set of sidelink resources for sidelink communication by the UE based on the first set of sidelink resources indicated via the SAI. The operations of 1610 may be performed according to examples as disclosed herein. In some examples, aspects of the operations of 1610 may be performed as described in reference to Fig.11 The side link resource determination component 1130 executes.

[0200] At 1615, the method may include determining whether the first side link resource set indicated via the SAI includes resources allocated by the network entity or resources allocated by one or more second network entities. The operations of 1615 may be performed according to examples as disclosed herein. In some examples, aspects of the operations of 1615 may be performed as described in reference to Fig.11 The side link resource determination component 1130 executes.

[0201] At 1620, the method may include sending a scheduling message allocating a second set of side link resources for side link communications by the UE, wherein sending the scheduling message allocating the second set of side link resources is based on the determination. The operations of 1620 may be performed according to examples as disclosed herein. In some examples, aspects of the operations of 1620 may be performed as described in reference to Fig.11 The sending component 1135 executes.

[0202] The following provides an overview of various aspects of the disclosure:

[0203] Aspect 1: A method for performing wireless communications at a UE, the method comprising: sending an SAI indicating a first side link resource set for side link communications performed by the UE via an uplink communication link; receiving a scheduling message allocating a second side link resource set for the side link communications performed by the UE, the second side link resource set being at least partially based on the first side link resource set indicated via the SAI; and sending a side link message via the second side link resource set allocated by the scheduling message.

[0204] Aspect 2: According to the method of Aspect 1, the method also includes: monitoring SCI from one or more other UEs, the SCI indicating a plurality of side link resources reserved for side link transmissions performed by the one or more other UEs, wherein the first side link resource set indicated by the SAI is at least partially based on the SCI.

[0205] Aspect 3: A method according to Aspect 2, wherein sending the SAI includes: sending, via the SAI, an indication that the first side link resource set is reserved based at least in part on the multiple side link resources indicated via the SCI including at least the first side link resource set.

[0206] Aspect 4: According to the method described in Aspect 3, the method also includes: receiving, via the SCI, an ID of a corresponding cell associated with each of the multiple side link resources, wherein the indication that the first side link resource set is reserved is sent at least in part based on the first side link resource set being associated with one or more second cells different from the first cell associated with the UE.

[0207] Aspect 5: According to the method described in any one of Aspects 3 to 4, the method further includes: measuring the RSRP associated with the first side link resource set; comparing the measured RSRP with an RSRP threshold, wherein the indication of the first side link resource set sent via the SAI is at least partially based on the measured RSRP exceeding the RSRP threshold.

[0208] Aspect 6: According to the method described in any one of Aspects 1 to 5, the method further includes: receiving one or more inter-UE coordination messages via a side link communication link, each of the one or more inter-UE coordination messages indicating one or more side link resources based at least in part on a corresponding side link channel sensing procedure, wherein sending the SAI is based at least in part on the one or more inter-UE coordination messages.

[0209] Aspect 7: A method according to Aspect 6, wherein the one or more inter-UE coordination messages include preferred resource information, and the method further includes: determining that the first side link resource set is common to the one or more side link resources indicated by each inter-UE coordination message in the one or more inter-UE coordination messages, wherein sending the SAI indicating the first side link resource set is at least partially based on the determination.

[0210] Aspect 8: A method according to Aspect 6, wherein the one or more inter-UE coordination messages include non-preferred resource information, and the method further includes: determining that the first side link resource set includes the union of the one or more side link resources indicated by each of the one or more inter-UE coordination messages, wherein sending the SAI indicating the first side link resource set is at least partially based on the determination.

[0211] Aspect 9: According to the method described in any one of Aspects 6 to 8, the method further includes: monitoring SCI in the side link resources of the side link resource pool, wherein the SCI indicates a plurality of side link resources reserved for side link transmissions performed by one or more second UEs; and determining the first side link resource set based at least in part on the one or more side link resources indicated by each of the one or more inter-UE coordination messages and the plurality of side link resources indicated by the SCI, wherein sending the SAI is based at least in part on determining the first side link resource set.

[0212] Aspect 10: According to any one of Aspects 1 to 9, the method also includes: determining that a condition associated with the sidelink communication at the UE is satisfied, wherein sending the SAI is at least partially based on determining that the condition is satisfied, and wherein the condition corresponds to an inter-UE coordination message received by the UE, the number of negative acknowledgments received by the UE exceeds a threshold number, or a measured CBR associated with a sidelink resource pool exceeds a threshold CBR.

[0213] Aspect 11: According to any one of aspects 1 to 10, the method further includes: receiving a control message including a trigger for resource preference reporting by the UE, wherein sending the SAI is at least partially based on the trigger.

[0214] Aspect 12: A method according to Aspect 11, wherein the control message indicates whether the resource preference report performed by the UE corresponds to reporting the sidelink resources preferred by the UE for the sidelink communication or the sidelink resources not preferred by the UE for the sidelink communication; and the SAI indicates the time and frequency position of the first sidelink resource set, and the first sidelink resource set corresponds to the resources preferred by the UE for the sidelink communication or the resources not preferred by the UE for the sidelink communication based at least in part on the control message.

[0215] Aspect 13: According to any one of Aspects 1 to 12, the method also includes: determining the first side link resource set based at least in part on a side link channel sensing procedure, one or more inter-UE coordination messages, or both according to the capabilities of the UE.

[0216] Aspect 14: According to the method described in any one of Aspects 1 to 13, the method further includes: receiving a control message indicating a side link resource preference reporting configuration; and determining the first side link resource set based at least in part on a side link channel sensing procedure, one or more UE-to-UE coordination messages, or both according to the side link resource preference reporting configuration.

[0217] Aspect 15: A method according to any one of Aspects 1 to 14, wherein sending the SAI comprises: sending the SAI via a first time slot, wherein the first side link resource set indicated by the SAI is located in a second time slot that is less than a threshold time period away from the first time slot.

[0218] Aspect 16: The method according to any one of aspects 1 to 15, wherein sending the SAI comprises: sending a medium access control-control element, a sidelink buffer status report, or an uplink control channel including the SAI.

[0219] Aspect 17: A method for performing wireless communications at a network entity, the method comprising: obtaining, via an uplink communication link, an SAI indicating a first side link resource set for side link communications performed by a UE; and determining, at least in part based on the first side link resource set indicated via the SAI, a second side link resource set for the side link communications performed by the UE; and outputting a scheduling message allocating the second side link resource set for the side link communications performed by the UE.

[0220] Aspect 18: According to the method described in Aspect 17, the method also includes: determining whether the first side link resource set indicated via the SAI includes resources allocated by the network entity or resources allocated by one or more second network entities, wherein the scheduling message outputting the allocation of the second side link resource set is at least partially based on the determination.

[0221] Aspect 19: A method according to any one of Aspects 17 to 18, wherein the first side link resource set indicated via the SAI is associated with one or more second cells different from the first cell supported by the network entity; and determining that the second side link resource set is associated with the one or more second cells is at least partially based on the first side link resource set.

[0222] Aspect 20: According to the method described in any one of Aspects 17 to 19, the method further includes: outputting a control message indicating an RSRP threshold for side link resource preference reporting, wherein obtaining the SAI indicating the first side link resource set is at least partially based on the RSRP threshold.

[0223] Aspect 21: The method according to any one of aspects 17 to 20, the method further comprising: outputting a control message including a trigger for resource preference reporting by the UE, wherein obtaining the SAI is at least partially based on the trigger.

[0224] Aspect 22: A method according to Aspect 21, wherein the control message indicates whether the resource preference report performed by the UE corresponds to reporting the sidelink resources preferred by the UE for the sidelink communication or the sidelink resources not preferred by the UE for the sidelink communication; and the SAI indicates the time and frequency position of the first sidelink resource set, and the first sidelink resource set corresponds to the resources preferred by the UE for the sidelink communication or the resources not preferred by the UE for the sidelink communication based at least in part on the control message.

[0225] Aspect 23: According to the method described in any one of Aspects 17 to 22, the method further includes: outputting a control message indicating a side link resource preference reporting configuration, wherein the first side link resource set is based at least in part on a first channel sensing procedure at the UE, a second channel sensing procedure at one or more second UEs, or both according to the side link resource preference reporting configuration.

[0226] Aspect 24: A method according to any one of Aspects 17 to 23, wherein obtaining the SAI comprises: obtaining the SAI via a first time slot, wherein the first side link resource set indicated by the SAI is located in a second time slot that is less than a threshold time period away from the first time slot.

[0227] Aspect 25: A method according to any one of Aspects 17 to 24, wherein obtaining the SAI comprises: obtaining a medium access control-control element, a sidelink buffer status report, an uplink control channel, or any combination thereof including the SAI.

[0228] Aspect 26: An apparatus for performing wireless communications at a UE, the apparatus comprising: a processor; a memory coupled to the processor; and instructions stored in the memory and executable by the processor to cause the apparatus to perform a method according to any one of Aspects 1 to 16.

[0229] Aspect 27: An apparatus for wireless communication at a UE, the apparatus comprising at least one component for performing a method according to any one of aspects 1 to 16.

[0230] Aspect 28: A non-transitory computer-readable medium storing a code for wireless communication at a UE, the code comprising instructions executable by a processor to perform a method according to any one of aspects 1 to 16.

[0231] Aspect 29: An apparatus for wireless communication at a network entity, the apparatus comprising: a processor; a memory coupled to the processor; and instructions stored in the memory and executable by the processor to cause the apparatus to perform a method according to any one of Aspects 17 to 25.

[0232] Aspect 30: An apparatus for wireless communication at a network entity, the apparatus comprising at least one component for performing a method according to any one of aspects 17 to 25.

[0233] Aspect 31: A non-transitory computer-readable medium storing a code for wireless communication at a network entity, the code comprising instructions executable by a processor to perform a method according to any one of aspects 17 to 25.

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

[0235] Although aspects of LTE, LTE-A, LTE-A Pro, or NR systems may be described for example purposes, and LTE, LTE-A, LTE-A Pro, or NR terminology may be used in much of the description, the techniques described herein may also be applicable to networks other than LTE, LTE-A, LTE-A Pro, or NR networks. For example, the described techniques may be applicable to various wireless communication systems, such as Ultra Mobile Broadband (UMB), Institute of Electrical and Electronics Engineers (IEEE) 802.11 (Wi-Fi), IEEE 802.16 (WiMAX), IEEE 802.20, Flash-OFDM, and other systems and radio technologies not explicitly mentioned herein.

[0236] The information and signals described herein may be represented using any of a variety of different techniques and methods. For example, data, instructions, commands, information, signals, bits, symbols, and chips that may be mentioned throughout the specification may be represented by voltage, current, electromagnetic waves, magnetic fields or magnetic particles, optical fields or optical particles, or any combination thereof.

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

[0238] The functions described herein may be implemented using hardware, software executed by a processor, firmware, or any combination thereof. If implemented using software executed by a processor, the functions may be stored as one or more instructions or codes of a computer-readable medium, or sent using a computer-readable medium. Other examples and specific implementations are within the scope of the present disclosure and the appended claims. For example, due to the nature of software, the functions described herein may be implemented using software executed by a processor, hardware, firmware, hard wiring, or a combination of any of these items. Features that implement the functions may also be physically located at different locations, including being distributed so that the functions are implemented at different physical locations.

[0239] Computer-readable medium includes both non-transient computer storage medium and communication medium, and it includes any medium that promotes computer program to be transmitted from one position to another position.Non-transient storage medium can be any available medium that can be accessed by general or special-purpose computer.By way of example and not limitation, non-transient computer-readable medium can include RAM, ROM, electrically erasable programmable ROM (EEPROM), flash memory, compact disc (CD) ROM or other optical disc storage device, disk storage device or other magnetic storage device, or can be used for carrying or storing desired program code parts and any other non-transient medium that can be accessed by general or special-purpose computer or general or special-purpose processor in the form of instruction or data structure.In addition, any connection is appropriately referred to as computer-readable medium.For example, if software is sent from website, server or other remote source using coaxial cable, fiber optic cable, twisted pair, digital subscriber line (DSL) or wireless technology such as infrared, radio and microwave, then coaxial cable, fiber optic cable, twisted pair, DSL or wireless technology such as infrared, radio and microwave are included in the definition of computer-readable medium. As used herein, disks and discs include CDs, laser discs, optical discs, digital versatile discs (DVDs), floppy disks, and Blu-ray discs. Disks can reproduce data magnetically, and discs can reproduce data optically using lasers. Combinations of the above are also included within the scope of computer-readable media.

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

[0241] The term "determining" encompasses a variety of actions, and thus, "determining" may include calculating, computing, processing, deriving, investigating, looking up (such as via looking up in a table, database or other data structure), ascertaining, etc. Furthermore, "determining" may include receiving (e.g., receiving information), accessing (e.g., accessing data stored in a memory), etc. Additionally, "determining" may include resolving, obtaining, selecting, choosing, establishing, and other such similar actions.

[0242] In the drawings, similar components or features may have the same reference label. In addition, various components of the same type may be distinguished by following the reference label with a dash and a second label to distinguish between the similar components. If only the first reference label is used in the specification, the description may apply to any of the similar components having the same first reference label, regardless of the second reference label or other subsequent reference labels.

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

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

Claims

1. An apparatus for wireless communication at a user equipment (UE), the apparatus comprising: processor; a memory coupled to the processor; and instructions stored in the memory and executable by the processor to cause the apparatus to: sending, via an uplink communication link, scheduling assistance information indicating a first set of sidelink resources for sidelink communication by the UE; receiving a scheduling message allocating a second set of sidelink resources for the sidelink communication by the UE, the second set of sidelink resources being based at least in part on the first set of sidelink resources indicated via the scheduling assistance information; as well as A sidelink message is sent via the second sidelink resource set allocated by the scheduling message.

2. The apparatus of claim 1 , wherein the instructions are further executable by the processor to cause the apparatus to: Monitoring sidelink control information from one or more other UEs, the sidelink control information indicating a plurality of sidelink resources reserved for sidelink transmissions by the one or more other UEs, wherein the first set of sidelink resources indicated via the scheduling assistance information is based at least in part on the sidelink control information.

3. The apparatus of claim 2, wherein the instructions to send the dispatch assistance information are executable by the processor to cause the apparatus to: An indication is sent via the scheduling assistance information that the first set of sidelink resources is reserved based at least in part on the plurality of sidelink resources indicated via the sidelink control information including at least the first set of sidelink resources.

4. The apparatus of claim 3, wherein the instructions are further executable by the processor to cause the apparatus to: An identifier of a corresponding cell associated with each of the plurality of side link resources is received via the side link control information, wherein sending the indication that the first set of side link resources is reserved is based at least in part on the first set of side link resources being associated with one or more second cells different from a first cell associated with the UE.

5. The apparatus of claim 3, wherein the instructions are further executable by the processor to cause the apparatus to: measuring a reference signal received power associated with the first set of sidelink resources; and The measured reference signal received power is compared to a reference signal received power threshold, wherein sending the indication of the first set of side link resources via the scheduling assistance information is based at least in part on the measured reference signal received power exceeding the reference signal received power threshold.

6. The apparatus of claim 1, wherein the instructions are further executable by the processor to cause the apparatus to: One or more inter-UE coordination messages are received via a sidelink communication link, each of the one or more inter-UE coordination messages indicating one or more sidelink resources based at least in part on a corresponding sidelink channel sensing procedure, wherein sending the scheduling assistance information is based at least in part on the one or more inter-UE coordination messages.

7. The apparatus of claim 6, wherein the one or more inter-UE coordination messages include the preferred resource information, and the instructions are further executable by the processor to cause the apparatus to: Determining that the first set of sidelink resources is common to the one or more sidelink resources indicated via each of the one or more inter-UE coordination messages, wherein sending the scheduling assistance information indicating the first set of sidelink resources is based at least in part on the determination.

8. The apparatus of claim 6, wherein the one or more inter-UE coordination messages include the non-preferred resource information, and the instructions are further executable by the processor to cause the apparatus to: Determining the first set of sidelink resources comprises a union of the one or more sidelink resources indicated via each of the one or more inter-UE coordination messages, wherein sending the scheduling assistance information indicating the first set of sidelink resources is based at least in part on the determination.

9. The apparatus of claim 6, wherein the instructions are further executable by the processor to cause the apparatus to: monitoring sidelink resources in a sidelink resource pool for sidelink control information, wherein the sidelink control information indicates a plurality of sidelink resources reserved for sidelink transmissions by one or more second UEs; and The first sidelink resource set is determined at least in part based on the one or more sidelink resources indicated via each of the one or more inter-UE coordination messages and the multiple sidelink resources indicated via the sidelink control information, wherein sending the scheduling assistance information is at least in part based on determining the first sidelink resource set.

10. The apparatus of claim 1, wherein the instructions are further executable by the processor to cause the apparatus to: Determining that a condition associated with the sidelink communication at the UE is satisfied, wherein sending the scheduling assistance information is based at least in part on determining that the condition is satisfied, and wherein the condition corresponds to an inter-UE coordination message received by the UE, a number of negative acknowledgments received by the UE exceeding a threshold number, or a measured channel busy rate associated with a sidelink resource pool exceeding a threshold channel busy rate.

11. The apparatus of claim 1 , wherein the instructions are further executable by the processor to cause the apparatus to: A control message including a trigger for a resource preference report by the UE is received, wherein sending the scheduling assistance information is based at least in part on the trigger.

12. The device according to claim 11, wherein: The control message indicates whether the resource preference report by the UE corresponds to reporting a sidelink resource preferred by the UE for the sidelink communication or a sidelink resource not preferred by the UE for the sidelink communication; and The scheduling assistance information indicates a time and frequency location of the first set of sidelink resources, and the first set of sidelink resources corresponds to resources preferred by the UE for the sidelink communication or resources not preferred by the UE for the sidelink communication based at least in part on the control message.

13. The apparatus of claim 1, wherein the instructions are further executable by the processor to cause the apparatus to: The first set of sidelink resources is determined based at least in part on a sidelink channel sensing procedure, one or more inter-UE coordination messages, or both according to capabilities of the UE.

14. The apparatus of claim 1, wherein the instructions are further executable by the processor to cause the apparatus to: receiving a control message indicating a sidelink resource preference reporting configuration; and The first set of sidelink resources is determined based at least in part on a sidelink channel sensing procedure, one or more inter-UE coordination messages, or both in accordance with the sidelink resource preference reporting configuration.

15. The apparatus of claim 1, wherein the instructions to send the dispatch assistance information are executable by the processor to cause the apparatus to: The scheduling assistance information is transmitted via a first time slot, wherein the first side link resource set indicated via the scheduling assistance information is located in a second time slot that is less than a threshold time period away from the first time slot.

16. The apparatus of claim 1, wherein the instructions to send the dispatch assistance information are executable by the processor to cause the apparatus to: A medium access control-control element, a sidelink buffer status report or an uplink control channel including the scheduling assistance information is sent.

17. An apparatus for wireless communication at a network entity, the apparatus comprising: processor; a memory coupled to the processor; and instructions stored in the memory and executable by the processor to cause the apparatus to: obtaining, via an uplink communication link, scheduling assistance information indicating a first set of sidelink resources for sidelink communication by a user equipment (UE); determining a second set of sidelink resources for the sidelink communication by the UE based at least in part on the first set of sidelink resources indicated via the scheduling assistance information; as well as A scheduling message is output allocating the second set of sidelink resources for the sidelink communication by the UE.

18. The apparatus of claim 17, wherein the instructions are further executable by the processor to cause the apparatus to: and determining whether the first set of sidelink resources indicated via the scheduling assistance information comprises resources allocated by the network entity or resources allocated by one or more second network entities, wherein outputting the scheduling message allocating the second set of sidelink resources is based at least in part on the determination.

19. The apparatus of claim 17, wherein: The first sidelink resource set indicated via the scheduling assistance information is associated with one or more second cells different from a first cell supported by the network entity; and Determining the second set of sidelink resources is based at least in part on the first set of sidelink resources being associated with the one or more second cells.

20. The apparatus of claim 17, wherein the instructions are further executable by the processor to cause the apparatus to: Outputting a control message indicating a reference signal received power threshold for sidelink resource preference reporting, wherein obtaining the scheduling assistance information indicating the first set of sidelink resources is based at least in part on the reference signal received power threshold.

21. The apparatus of claim 17, wherein the instructions are further executable by the processor to cause the apparatus to: A control message is outputted including a trigger for a resource preference report by the UE, wherein obtaining the scheduling assistance information is based at least in part on the trigger.

22. The apparatus of claim 21, wherein: The control message indicates whether the resource preference report by the UE corresponds to reporting a sidelink resource preferred by the UE for the sidelink communication or a sidelink resource not preferred by the UE for the sidelink communication; and The scheduling assistance information indicates a time and frequency location of the first set of sidelink resources, and the first set of sidelink resources corresponds to resources preferred by the UE for the sidelink communication or resources not preferred by the UE for the sidelink communication based at least in part on the control message.

23. The apparatus of claim 17, wherein the instructions are further executable by the processor to cause the apparatus to: Output a control message indicating a sidelink resource preference reporting configuration, wherein the first set of sidelink resources is based at least in part on a first channel sensing procedure at the UE, a second channel sensing procedure at one or more second UEs, or both according to the sidelink resource preference reporting configuration.

24. The apparatus of claim 17, wherein the instructions to obtain the dispatch assistance information are executable by the processor to cause the apparatus to: The scheduling assistance information is obtained via a first time slot, wherein the first side link resource set indicated via the scheduling assistance information is located in a second time slot that is less than a threshold time period away from the first time slot.

25. The apparatus of claim 17, wherein the instructions to obtain the dispatch assistance information are executable by the processor to cause the apparatus to: A medium access control-control element, a sidelink buffer status report, an uplink control channel, or any combination thereof including the scheduling assistance information is obtained.

26. A method for wireless communication at a user equipment (UE), the method comprising: sending, via an uplink communication link, scheduling assistance information indicating a first set of sidelink resources for sidelink communication by the UE; receiving a scheduling message allocating a second set of sidelink resources for the sidelink communication by the UE, the second set of sidelink resources being based at least in part on the first set of sidelink resources indicated via the scheduling assistance information; as well as A sidelink message is sent via the second sidelink resource set allocated by the scheduling message.

27. The method according to claim 26, further comprising: Monitoring sidelink control information from one or more other UEs, the sidelink control information indicating a plurality of sidelink resources reserved for sidelink transmissions by the one or more other UEs, wherein the first set of sidelink resources indicated via the scheduling assistance information is based at least in part on the sidelink control information.

28. The method of claim 27, wherein sending the dispatch assistance information comprises: An indication is sent via the scheduling assistance information that the first set of sidelink resources is reserved based at least in part on the plurality of sidelink resources indicated via the sidelink control information including at least the first set of sidelink resources.

29. A method for wireless communication at a network entity, the method comprising: obtaining, via an uplink communication link, scheduling assistance information indicating a first set of sidelink resources for sidelink communication by a user equipment (UE); determining a second set of sidelink resources for the sidelink communication by the UE based at least in part on the first set of sidelink resources indicated via the scheduling assistance information; as well as A scheduling message is output allocating the second set of sidelink resources for the sidelink communication by the UE.

30. The method according to claim 29, further comprising: and determining whether the first set of sidelink resources indicated via the scheduling assistance information comprises resources allocated by the network entity or resources allocated by one or more second network entities, wherein outputting the scheduling message allocating the second set of sidelink resources is based at least in part on the determination.

Images