Sidelink preparation procedure time reduction

Abstract

Aspects of the present disclosure generally relate to wireless communications. In some aspects, a user equipment (UE) may receive a resource allocation associated with a sidelink communication from a network entity. The UE may initiate a physical sidelink shared channel preparation procedure associated with the sidelink communication prior to receiving the resource allocation associated with the sidelink communication. Numerous other aspects are described.

Description

[0001] CROSS-REFERENCE TO RELATED APPLICATIONS

[0002] This patent application claims priority to U.S. non-provisional patent application No. 17 / 816,848, filed on August 2, 2022, entitled “SIDELINK PREPARATION PROCEDURE TIME REDUCTION” and assigned to the assignee of this application. The disclosure of the prior application is considered a part of this patent application and is incorporated by reference into this patent application. Technical Field

[0003] Aspects of the present disclosure relate generally to wireless communications, and to techniques and apparatus for sidelink preparation procedure time reduction. Background Art

[0004] Wireless communication systems are widely deployed to provide a variety of telecommunication services, such as telephony, video, data, messaging, and broadcasting. Typical wireless communication systems may employ multiple access technologies that can support communication with multiple users by sharing available system resources (e.g., bandwidth, transmit power, etc.). Examples of such multiple access technologies include code division multiple access (CDMA) systems, time division multiple access (TDMA) systems, frequency division multiple access (FDMA) systems, orthogonal frequency division multiple access (OFDMA) systems, single carrier frequency division multiple access (SC-FDMA) systems, time division synchronous code division multiple access (TD-SCDMA) systems, and long term evolution (LTE). LTE / LTE-Advanced is a set of enhancements to the Universal Mobile Telecommunications System (UMTS) mobile standard promulgated by the Third Generation Partnership Project (3GPP).

[0005] A wireless network may include one or more network entities that support communications for a user equipment (UE) or multiple UEs. A UE may communicate with a network entity via downlink communications and uplink communications. A "downlink" (or "DL") refers to a communication link from a network entity to a UE, and an "uplink" (or "UL") refers to a communication link from a UE to a network entity.

[0006] The above-mentioned multiple access technologies have been adopted in various telecommunication standards to provide a common protocol that enables different UEs to communicate at a city, country, region and / or global level. New Radio (NR), which may be referred to as 5G, is a set of enhancements to the LTE mobile standard promulgated by 3GPP. NR is designed to better support mobile broadband Internet access by improving spectrum efficiency, reducing costs, improving services, utilizing new spectrum, and using orthogonal frequency division multiplexing (OFDM) with cyclic prefix (CP) (CP-OFDM) on the downlink, using CP-OFDM and / or single carrier frequency division multiplexing (SC-FDM) (also known as discrete Fourier transform spread OFDM (DFT-s-OFDM)) on the uplink to better integrate with other open standards, as well as supporting beamforming, multiple input multiple output (MIMO) antenna technology and carrier aggregation. As the demand for mobile broadband access continues to increase, further improvements in LTE, NR and other radio access technologies remain useful. Summary of the invention

[0007] Some aspects described herein relate to a method of wireless communication performed by a user equipment (UE). The method may include receiving a resource allocation associated with a sidelink communication from a network entity. The method may include initiating a physical sidelink shared channel (PSSCH) preparation procedure associated with the sidelink communication before receiving the resource allocation associated with the sidelink communication.

[0008] Some aspects described herein relate to a method of wireless communication performed by a network entity. The method may include receiving a buffer status report (BSR) associated with a sidelink communication from a UE, wherein the BSR indicates a transport block size (TBS) associated with the sidelink communication. The method may include sending a resource allocation associated with the sidelink communication to the UE based at least in part on the TBS.

[0009] Some aspects described herein relate to an apparatus for wireless communication at a UE. The apparatus may include a memory and one or more processors coupled to the memory. The one or more processors may be configured to receive a resource allocation associated with a sidelink communication from a network entity. The one or more processors may be configured to initiate a PSSCH preparation procedure associated with the sidelink communication before receiving the resource allocation associated with the sidelink communication.

[0010] Some aspects described herein relate to an apparatus for wireless communication at a network entity. The apparatus may include a memory and one or more processors coupled to the memory. The one or more processors may be configured to receive a BSR associated with a sidelink communication from a UE, wherein the BSR indicates a TBS associated with the sidelink communication. The one or more processors may be configured to send a resource allocation associated with the sidelink communication to the UE based at least in part on the TBS.

[0011] Some aspects described herein relate to a non-transitory computer-readable medium storing an instruction set for wireless communication by a UE. The instruction set, when executed by one or more processors of the UE, may cause the UE to receive a resource allocation associated with a sidelink communication from a network entity. The instruction set, when executed by one or more processors of the UE, may cause the UE to initiate a PSSCH preparation procedure associated with the sidelink communication before receiving the resource allocation associated with the sidelink communication.

[0012] Some aspects described herein relate to a non-transitory computer-readable medium storing an instruction set for wireless communication by a network entity. The instruction set, when executed by one or more processors of the network entity, may cause the network entity to receive a BSR associated with a sidelink communication from a UE, wherein the BSR indicates a TBS associated with the sidelink communication. The instruction set, when executed by one or more processors of the network entity, may cause the network entity to send a resource allocation associated with the sidelink communication to the UE based at least in part on the TBS.

[0013] Some aspects described herein relate to an apparatus for wireless communication. The apparatus may include components for receiving a resource allocation associated with a sidelink communication from a network entity. The apparatus may include components for initiating a PSSCH preparation procedure associated with the sidelink communication prior to receiving the resource allocation associated with the sidelink communication.

[0014] Some aspects described herein relate to an apparatus for wireless communication. The apparatus may include components for receiving a BSR associated with a sidelink communication from a UE, wherein the BSR indicates a TBS associated with the sidelink communication. The apparatus may include components for sending a resource allocation associated with the sidelink communication to the UE based at least in part on the TBS.

[0015] The various aspects generally include methods, apparatuses, systems, computer program products, non-transitory computer-readable media, user equipment, network entities, wireless communication devices and / or processing systems as fully described herein with reference to the drawings and description and as illustrated in the drawings and description.

[0016] The features and technical advantages of examples according to the present disclosure have been outlined quite broadly above so that the following specific embodiments may be better understood. Additional features and advantages will be described below. The disclosed concepts and specific examples may be easily used as a basis for modifying or designing other structures for achieving the same purpose of the present disclosure. Such equivalent constructions do not depart from the scope of the appended claims. The characteristics of the concepts disclosed herein, both in terms of their organization and method of operation, and the associated advantages will be better understood by considering the following description in conjunction with the accompanying drawings. Each of the figures in the accompanying drawings is provided for the purpose of illustration and description, and not as a definition of the limitations of the claims.

[0017] Although various aspects are described in the present disclosure by illustrating some examples, it will be understood by those skilled in the art that such aspects can be implemented in many different arrangements and scenarios. The technology described herein can be implemented using different platform types, devices, systems, shapes, sizes and / or packaging arrangements. For example, some aspects can be implemented via integrated chip implementations or other devices based on non-module components (e.g., end-user devices, vehicles, communication equipment, computing equipment, industrial equipment, retail / shopping equipment, medical equipment and / or artificial intelligence devices). Various aspects can be implemented in chip-level components, modular components, non-modular components, non-chip-level components, device-level components and / or system-level components. The equipment incorporating the various aspects and features described may include additional components and features for implementing and practicing the various aspects claimed and described. For example, the transmission and reception of wireless signals may include one or more components for analog and digital purposes (e.g., hardware components, including antennas, radio frequency (RF) chains, power amplifiers, modulators, buffers, processors, interleavers, adders and / or summers). The various aspects described herein are intended to be practiced in various devices, components, systems, distributed arrangements and / or end-user devices of various sizes, shapes and configurations. BRIEF DESCRIPTION OF THE DRAWINGS

[0018] In order to fully understand the above-mentioned features of the present disclosure, a more specific description of the invention briefly summarized above can be obtained by referring to various aspects (some of which are illustrated in the accompanying drawings). However, it should be noted that the accompanying drawings only illustrate certain typical aspects of the present disclosure and are therefore not to be considered as limiting the scope thereof, as the specification may admit other equally effective aspects. The same reference numerals in different drawings may identify the same or similar elements.

[0019] Figure 1 is a diagram illustrating an example of a wireless network according to the present disclosure.

[0020] Figure 2 is a diagram illustrating an example of a network entity communicating with a user equipment (UE) in a wireless network according to the present disclosure.

[0021] Figure 3 is a diagram illustrating an example of an open radio access network architecture according to the present disclosure.

[0022] Figure 4 is a diagram illustrating an example of physical channels and reference signals in a wireless network according to the present disclosure.

[0023] Figure 5 is a diagram illustrating an example of side link communication according to the present disclosure.

[0024] Figure 6 is a diagram illustrating an example of side link communication and access link communication according to the present disclosure.

[0025] Figure 7 is a diagram illustrating an example of a physical sidelink shared channel (PSSCH) preparation procedure according to the present disclosure.

[0026] Figure 8 is a diagram illustrating another example of a PSSCH preparation procedure according to the present disclosure.

[0027] Fig. 9 is a diagram of an example associated with sidelink preparation procedure time reduction according to the present disclosure.

[0028] Fig.10 is a diagram illustrating an example process performed, for example, by a UE according to the present disclosure.

[0029] Fig.11 is a diagram illustrating an example process performed, for example, by a network entity according to the present disclosure.

[0030] Fig.12 is a diagram of an example apparatus for wireless communications according to the present disclosure.

[0031] Fig.13 is a diagram of an example apparatus for wireless communications according to the present disclosure. DETAILED DESCRIPTION

[0032] The various aspects of the present disclosure are described more fully below with reference to the accompanying drawings. However, the present disclosure can be embodied in many different forms, and should not be construed as being limited to any specific structure or function presented throughout the present disclosure. Instead, these aspects are provided so that the present disclosure will be thorough and complete, and the protection scope of the present disclosure will be fully conveyed to those skilled in the art. It should be appreciated by those skilled in the art that the scope of the present disclosure is intended to cover any aspect of the present disclosure disclosed herein, whether it is implemented independently or in combination with any other aspect of the present disclosure. For example, any number of aspects set forth herein may be used to implement a device or practice method. In addition, the scope of the present disclosure is intended to cover such devices or methods implemented using other structures, functionality, or structures and functionality in addition to or different from the various aspects of the disclosure set forth herein. It should be understood that any aspect of the disclosure disclosed herein may be embodied by one or more elements of the present invention.

[0033] Several aspects of telecommunication systems will now be presented with reference to various devices and techniques. These devices and techniques will be described in the following detailed description and illustrated in the accompanying drawings by various blocks, modules, components, circuits, steps, processes, algorithms, etc. (collectively referred to as "elements"). These elements can be implemented using hardware, software, or a combination thereof. Whether these elements are implemented as hardware or software depends on the specific application and the design constraints imposed on the overall system.

[0034] Although various aspects may be described herein using terms generally associated with 5G or new radio (NR) radio access technology (RAT), various aspects of the present disclosure may be applicable to other RATs, such as 3G RAT, 4G RAT and / or RATs beyond 5G (e.g., 6G).

[0035] Figure 11 is a diagram illustrating an example of a wireless network 100 according to the present disclosure. The wireless network 100 may be a 5G (e.g., NR) network and / or a 4G (e.g., Long Term Evolution (LTE)) network, or may include elements of a 5G (e.g., NR) network and / or elements of a 4G (e.g., Long Term Evolution (LTE)) network, etc. The wireless network 100 may include one or more network entities 110 (shown as NE 110a, NE 110b, NE 110c, and NE 110d), a user equipment (UE) 120 or multiple UEs 120 (shown as UE 120a, UE 120b, UE 120c, UE 120d, and UE 120e), and / or other network entities. The network entity 110 is an entity that communicates with the UE 120. The network entity 110 (sometimes referred to as NE) may include, for example, an NR network entity, an LTE network entity, a Node B, an eNB (e.g., in 4G), a gNB (e.g., in 5G), an access point, a transmit receive point (TRP), a base station, and / or a disaggregated component of a base station such as a centralized unit (CU), a distributed unit (DU), and / or a radio unit (RU), which may be combined with Figure 3 1. The term "cell" may refer to a coverage area of ​​a network entity 110 and / or a network entity subsystem serving the coverage area, depending on the context in which the term is used.

[0036] The network entity 110 may provide communication coverage for a macro cell, a pico cell, a femto cell, and / or another type of cell. A macro cell may cover a relatively large geographic area (e.g., a radius of several kilometers) and may allow unrestricted access by a UE 120 with a service subscription. A pico cell may cover a relatively small geographic area and may allow unrestricted access by a UE 120 with a service subscription. A femto cell may cover a relatively small geographic area (e.g., a home) and may allow restricted access by a UE 120 associated with the femto cell (e.g., a UE 120 in a closed subscriber group (CSG)). The network entity 110 for a macro cell may be referred to as a macro network entity. The network entity 110 for a pico cell may be referred to as a pico network entity. The network entity 110 for a femto cell may be referred to as a femto network entity or a home network entity. In Figure 1 In the example shown, NE 110a may be a macro network entity for macro cell 102a, NE 110b may be a pico network entity for pico cell 102b, and NE 110c may be a femto network entity for femto cell 102c. A network entity may support one or more (eg, three) cells.

[0037] In some examples, the cells may not necessarily be stationary, and the geographic area of ​​the cells may move depending on the location of the mobile network entity 110 (e.g., the mobile network entity). In some examples, the network entities 110 may be interconnected with each other and / or with one or more other network entities 110 or network nodes (not shown) in the wireless network 100 using any suitable transport network through various types of backhaul interfaces (such as direct physical connections or virtual networks).

[0038] The wireless network 100 may include one or more relay stations. A relay station is an entity capable of receiving transmissions of data from an upstream station (e.g., a network entity 110 or a UE 120) and transmitting transmissions of data to a downstream station (e.g., a UE 120 or a network entity 110). A relay station may be a UE 120 capable of relaying transmissions for other UEs 120. Figure 1 In the example shown, NE 110d (eg, a relay network entity) may communicate with NE 110a (eg, a macro network entity) and UE 120d to facilitate communications between NE 110a and UE 120d. A network entity 110 that relays communications may be referred to as a relay station, relay network entity, relay, or the like.

[0039] The wireless network 100 may be a heterogeneous network that includes different types of network entities 110, such as macro network entities, pico network entities, femto network entities, relay network entities, etc. These different types of network entities 110 may have different transmit power levels, different coverage areas, and / or different impacts on interference in the wireless network 100. For example, a macro network entity may have a high transmit power level (e.g., 5 watts to 40 watts), while a pico network entity, a femto network entity, and a relay network entity may have a lower transmit power level (e.g., 0.1 watt to 2 watts).

[0040] The network controller 130 may be coupled to or in communication with a set of network entities 110 and may provide coordination and control for the network entities 110. The network controller 130 may communicate with the network entities 110 via backhaul communication links. The network entities 110 may also communicate directly or indirectly with each other via wireless or wired backhaul communication links.

[0041] UE 120 may be dispersed throughout the wireless network 100, and each UE 120 may be stationary or mobile. UE 120 may include, for example, an access terminal, a terminal, a mobile station, and / or a subscriber unit. UE 120 may be a cellular phone (e.g., a smart phone), a personal digital assistant (PDA), a wireless modem, a wireless communication device, a handheld device, a laptop computer, a cordless phone, a wireless local loop (WLL) station, a tablet computer, a camera, a gaming device, a netbook, a smartbook, an ultrabook, a medical device, a biometric device, a wearable device (e.g., a smart watch, smart clothing, smart glasses, a smart wristband, smart jewelry (e.g., a smart ring or a smart bracelet)), an entertainment device (e.g., a music device, a video device, and / or a satellite radio), a vehicle component or sensor, a smart meter / sensor, an industrial manufacturing equipment, a global positioning system device, and / or any other suitable device configured to communicate via a wireless medium.

[0042] Some UEs 120 may be considered as machine type communication (MTC) or evolved or enhanced machine type communication (eMTC) UEs. MTC UEs and / or eMTC UEs may include, for example, robots, drones, remote devices, sensors, meters, monitors, and / or location tags, which may communicate with a network entity, another device (e.g., a remote device), or some other entity. Some UEs 120 may be considered as Internet of Things (IoT) devices and / or may be implemented as NB-IoT (narrowband IoT) devices. Some UEs 120 may be considered as customer premises equipment. UE 120 may be included in a housing that houses components of UE 120, such as a processor component and / or a memory component. In some examples, the processor component and the memory component may be coupled together. For example, a processor component (e.g., one or more processors) and a memory component (e.g., a memory) may be operably coupled, communicatively coupled, electronically coupled, and / or electrically coupled.

[0043] Generally speaking, any number of wireless networks 100 may be deployed in a given geographic area. Each wireless network 100 may support a specific RAT and may operate on one or more frequencies. RAT may be referred to as a radio technology, air interface, etc. Frequency may be referred to as a carrier, frequency channel, etc. Each frequency may support a single RAT in a given geographic area to avoid interference between wireless networks of different RATs. In some cases, NR or 5G RAT networks may be deployed.

[0044] In some examples, two or more UEs 120 (e.g., shown as UE 120a and UE 120e) may communicate directly (e.g., without using network entity 110 as an intermediary to communicate with each other) using one or more side link channels. For example, UE 120 may communicate using peer-to-peer (P2P) communication, device-to-device (D2D) communication, vehicle-to-everything (V2X) protocols (e.g., which may include vehicle-to-vehicle (V2V) protocols, vehicle-to-infrastructure (V2I) protocols, or vehicle-to-pedestrian (V2P) protocols), and / or mesh networks. In such examples, UE 120 may perform scheduling operations, resource selection operations, and / or other operations described elsewhere herein as being performed by network entity 110.

[0045] The devices of the wireless network 100 may communicate using an electromagnetic spectrum, which may be subdivided into various categories, bands, channels, etc., according to frequency or wavelength. For example, the devices of the wireless network 100 may communicate using one or more operating bands. In 5G NR, two initial operating bands have been identified as frequency ranges designated FR1 (410 MHz to 7.125 GHz) and FR2 (24.25 GHz to 52.6 GHz). It should be understood that although a portion of FR1 is greater than 6 GHz, FR1 is often (interchangeably) referred to as the "below 6 GHz" band in various documents and articles. A similar naming problem sometimes occurs with respect to FR2, which is often (interchangeably) referred to as the "millimeter wave" band in documents and articles, although it is different from the extremely high frequency (EHF) band (30 GHz to 300 GHz) identified as the "millimeter wave" band by the International Telecommunication Union (ITU).

[0046] Frequencies between FR1 and FR2 are generally referred to as mid-band frequencies. Recent 5G NR research has identified the operating bands for these mid-band frequencies as frequency range designation FR3 (7.125GHz to 24.25GHz). The bands falling within FR3 can inherit FR1 characteristics and / or FR2 characteristics, and therefore the features of FR1 and / or FR2 can be effectively extended to mid-band frequencies. In addition, higher frequency bands are currently being explored to extend 5G NR operations to more than 52.6GHz. For example, three higher operating bands have been identified as frequency range designations FR4a or FR4-1 (52.6GHz to 71GHz), FR4 (52.6GHz to 114.25GHz) and FR5 (114.25GHz to 300GHz). Each of these higher frequency bands falls within the EHF band.

[0047] Considering the above examples, unless otherwise explicitly stated, it should be understood that if the term "below 6 GHz" or the like is used herein, the term may broadly refer to frequencies that may be lower than 6 GHz, may be within FR1, or may include mid-band frequencies. In addition, unless otherwise explicitly stated, it should be understood that if the term "millimeter wave" or the like is used herein, the term may broadly refer to frequencies that may include mid-band frequencies, may be within FR2, FR4, FR4-a or FR4-1, and / or FR5, or may be within the EHF band. It is contemplated that the frequencies included in these operating bands (e.g., FR1, FR2, FR3, FR4, FR4-a, FR4-1, and / or FR5) may be modified, and the techniques described herein are applicable to those modified frequency ranges.

[0048] In some aspects, UE 120 may include a communication manager 140. As described in more detail elsewhere herein, the communication manager 140 may receive a resource allocation associated with a sidelink communication from the network entity 110; and prior to receiving the resource allocation associated with the sidelink communication, initiate a physical sidelink shared channel (PSSCH) preparation procedure associated with the sidelink communication. Additionally or alternatively, the communication manager 140 may perform one or more other operations described herein.

[0049] In some aspects, the network entity 110 may include a communication manager 150. As described in greater detail elsewhere herein, the communication manager 150 may receive a buffer status report (BSR) associated with the sidelink communication from the UE 120, wherein the BSR indicates a transport block size (TBS) associated with the sidelink communication; and send a resource allocation associated with the sidelink communication to the UE 120 based at least in part on the TBS. Additionally or alternatively, the communication manager 150 may perform one or more other operations described herein.

[0050] As indicated above, Figure 1 are provided as examples. Other examples can be found in the Figure 1 The examples described are different.

[0051] Figure 2 2 is a diagram illustrating an example 200 of a network entity 110 communicating with a UE 120 in a wireless network 100 according to the present disclosure. The network entity 110 may be equipped with a set of antennas 234a to 234t, such as T antennas (T≥1). The UE 120 may be equipped with a set of antennas 252a to 252r, such as R antennas (R≥1).

[0052] At the network entity 110, a transmit processor 220 may receive data intended for a UE 120 (or a set of UEs 120) from a data source 212. The transmit processor 220 may select one or more modulation and coding schemes (MCS) for the UE 120 based at least in part on one or more channel quality indicators (CQIs) received from the UE 120. The network entity 110 may process (e.g., encode and modulate) the data for the UE 120 based at least in part on the MCS selected for the UE 120, and provide data symbols for the UE 120. The transmit processor 220 may process system information (e.g., for semi-static resource partitioning information (SRPI)) and control information (e.g., CQI requests, grants, and / or upper layer signaling), and provide overhead symbols and control symbols. The transmit processor 220 may generate reference symbols for reference signals (e.g., cell-specific reference signals (CRS) or demodulation reference signals (DMRS)) and synchronization signals (e.g., primary synchronization signals (PSS) or secondary synchronization signals (SSS)). The transmit (TX) multiple-input multiple-output (MIMO) processor 230 may perform spatial processing (e.g., precoding) on ​​data symbols, control symbols, overhead symbols, and / or reference symbols, where applicable, and may provide a set of output symbol streams (e.g., T output symbol streams) to a corresponding set of modems 232 (e.g., T modems) (shown as modems 232a to 232t). For example, each output symbol stream may be provided to a modulator component (shown as MOD) of the modem 232. Each modem 232 may process a corresponding output symbol stream (e.g., for OFDM) using a corresponding modulator component to obtain an output sample stream. Each modem 232 may further process (e.g., convert to analog, amplify, filter, and / or upconvert) the output sample stream using a corresponding modulator component to obtain a downlink signal. The modems 232a through 232t may transmit a set of downlink signals (eg, T downlink signals) via a corresponding set of antennas 234 (eg, T antennas) (shown as antennas 234a through 234t).

[0053] At the UE 120, a set of antennas 252 (shown as antennas 252a through 252r) may receive downlink signals from the network entity 110 and / or other network entities 110 and may provide a set of received signals (e.g., R received signals) to a set of modems 254 (e.g., R modems) (shown as modems 254a through 254r). For example, each received signal may be provided to a demodulator component (shown as DEMOD) of the modem 254. Each modem 254 may use a corresponding demodulator component to condition (e.g., filter, amplify, downconvert, and / or digitize) the received signal to obtain input samples. Each modem 254 may use a demodulator component to further process the input samples (e.g., for OFDM) to obtain received symbols. A MIMO detector 256 may obtain received symbols from the modem 254, may perform MIMO detection on the received symbols where applicable, and may provide detected symbols. The receive processor 258 may process (e.g., demodulate and decode) the detected symbols, may provide decoded data for the UE 120 to the data sink 260, and may provide decoded control information and system information to the controller / processor 280. The term "controller / processor" may refer to one or more controllers, one or more processors, or a combination thereof. The channel processor may determine a reference signal received power (RSRP) parameter, a received signal strength indicator (RSSI) parameter, a reference signal received quality (RSRQ) parameter, and / or a CQI parameter, among other things. In some examples, one or more components of the UE 120 may be included in the housing 284.

[0054] The network controller 130 may include a communication unit 294, a controller / processor 290, and a memory 292. The network controller 130 may include, for example, one or more devices in a core network. The network controller 130 may communicate with the network entity 110 via the communication unit 294.

[0055] One or more antennas (e.g., antennas 234a to 234t and / or antennas 252a to 252r) may include or be included within one or more antenna panels, one or more antenna groups, one or more sets of antenna elements, and / or one or more antenna arrays, etc. Antenna panels, antenna groups, sets of antenna elements, and / or antenna arrays may include one or more antenna elements (in a single housing or multiple housings), sets of coplanar antenna elements, sets of non-coplanar antenna elements, and / or coupled to one or more transmit and / or receive components (such as, Figure 2 One or more antenna elements of one or more components in.

[0056] On the uplink, at the UE 120, the transmit processor 264 may receive and process data from the data source 262 and control information from the controller / processor 280 (e.g., for reports including RSRP, RSSI, RSRQ, and / or CQI). The transmit processor 264 may generate reference symbols for one or more reference signals. The symbols from the transmit processor 264 may be pre-decoded by the TX MIMO processor 266, where applicable, further processed by the modem 254 (e.g., for DFT-s-OFDM or CP-OFDM), and sent to the network entity 110. In some examples, the modem 254 of the UE 120 may include a modulator and a demodulator. In some examples, the UE 120 includes a transceiver. The transceiver may include any combination of an antenna 252, a modem 254, a MIMO detector 256, a receive processor 258, a transmit processor 264, and / or a TX MIMO processor 266. The transceiver may be used by a processor (eg, controller / processor 280) and memory 282 to perform the functions described herein (eg, with reference to Figures 8 to 13 )Aspects of any of the methods described herein.

[0057] At the network entity 110, uplink signals from the UE 120 and / or other UEs may be received by the antenna 234, processed by the modem 232 (e.g., a demodulator component of the modem 232, shown as DEMOD), detected by the MIMO detector 236 (if applicable), and further processed by the receive processor 238 to obtain decoded data and control information sent by the UE 120. The receive processor 238 may provide the decoded data to the data sink 239 and the decoded control information to the controller / processor 240. The network entity 110 may include a communication unit 244 and may communicate with the network controller 130 via the communication unit 244. The network entity 110 may include a scheduler 246 to schedule one or more UEs 120 for downlink and / or uplink communications. In some examples, the modem 232 of the network entity 110 may include a modulator and a demodulator. In some examples, the network entity 110 includes a transceiver. The transceiver may include any combination of antenna 234, modem 232, MIMO detector 236, receive processor 238, transmit processor 220, and / or TX MIMO processor 230. The transceiver may be used by a processor (e.g., controller / processor 240) and memory 242 to perform operations described herein (e.g., with reference to Figures 8 to 13 )Aspects of any of the methods described herein.

[0058] The controller / processor 240 of the network entity 110, the controller / processor 280 of the UE 120, and / or Figure 2Any other component in the network entity 110 may perform one or more techniques associated with sidelink preparation procedure time reduction, as described in more detail elsewhere herein. For example, the controller / processor 240 of the network entity 110, the controller / processor 280 of the UE 120, and / or Figure 2 Any other component in may perform or direct e.g. Fig.10 The process of 1000 Fig.11 1100 and / or operations of other processes as described herein. Memory 242 and memory 282 may store data and program codes for network entity 110 and UE 120, respectively. In some examples, memory 242 and / or memory 282 may include a non-transitory computer-readable medium that stores one or more instructions (e.g., code and / or program code) for wireless communication. For example, the one or more instructions, when executed by one or more processors of network entity 110 and / or UE 120 (e.g., directly executed, or executed after compilation, conversion, and / or interpretation), may cause the one or more processors, UE 120, and / or network entity 110 to perform or direct, for example, Fig.10 The process of 1000 Fig.11 The process 1100 and / or operations of other processes as described herein. In some examples, executing instructions may include running instructions, converting instructions, compiling instructions, and / or interpreting instructions, etc.

[0059] In some aspects, the UE 120 includes means for receiving a resource allocation associated with the sidelink communication from the network entity receiving 110; and / or means for initiating a PSSCH preparation procedure associated with the sidelink communication prior to receiving the resource allocation associated with the sidelink communication. Means for the UE 120 to perform operations described herein may include, for example, one or more of the communication manager 140, the antenna 252, the modem 254, the MIMO detector 256, the receive processor 258, the transmit processor 264, the TX MIMO processor 266, the controller / processor 280, or the memory 282.

[0060] In some aspects, the network entity 110 includes means for receiving a BSR associated with the sidelink communication from the UE 120, wherein the BSR indicates a TBS associated with the sidelink communication; and / or means for sending a resource allocation associated with the sidelink communication to the UE based at least in part on the TBS. In some aspects, means for the network entity 110 to perform operations described herein may include, for example, one or more of the communication manager 150, the transmit processor 220, the TX MIMO processor 230, the modem 232, the antenna 234, the MIMO detector 236, the receive processor 238, the controller / processor 240, the memory 242, or the scheduler 246.

[0061] Although Figure 2 The blocks in the 200 and 210 are illustrated as distinct components, but the functionality described above for these blocks may be implemented in a single hardware, software, or combined component or in various combinations of components. For example, the functionality described for the transmit processor 264, the receive processor 258, and / or the TX MIMO processor 266 may be performed by or under the control of the controller / processor 280.

[0062] As indicated above, Figure 2 are provided as examples. Other examples can be found in the Figure 2 The examples described are different.

[0063] Figure 3 3 is a diagram illustrating an example 300 of an O-RAN architecture according to the present disclosure. Figure 3 As shown, the O-RAN architecture may include a CU 310 that communicates with a core network 320 via a backhaul link. In addition, the CU 310 may communicate with one or more DUs 330 via corresponding midhaul links. The DUs 330 may each communicate with one or more RUs 340 via corresponding fronthaul links, and the RUs 340 may each communicate with a corresponding UE 120 via a radio frequency (RF) access link. The DU 330 and the RU 340 may also be referred to as O-RAN DU (O-DU) 330 and O-RAN RU (O-RU) 340, respectively.

[0064] In some aspects, the DU 330 and the RU 340 may be implemented according to a functional split architecture, wherein functionality of a network entity 110 (e.g., an eNB, gNB, and / or base station) is provided by a DU 330 and one or more RUs 340 that communicate via a fronthaul link. Thus, as described herein, the network entity 110 may include a DU 330 and one or more RUs 340, which may be co-located or geographically distributed. In some aspects, the DU 330 and associated RUs 340 may communicate via a fronthaul link to exchange real-time control plane information via a lower layer split (LLS) control plane (LLS-C) interface, non-real-time management information via an LLS management plane (LLS-M) interface, and / or user plane information via an LLS user plane (LLS-U) interface.

[0065] Thus, the DU 330 may correspond to a logical unit that includes one or more network entity functions to control the operation of one or more RUs 340. For example, in some aspects, the DU 330 may host a radio link control (RLC) layer, a medium access control (MAC) layer, and one or more high physical (PHY) layers (e.g., forward error correction (FEC) encoding and decoding, scrambling, and / or modulation and demodulation) based at least in part on the lower layer functional split. Higher layer control functions (such as packet data convergence protocol (PDCP), radio resource control (RRC), and / or service data adaptation protocol (SDAP)) may be hosted by the CU 310. Based at least in part on the lower layer functional split, the RU 340 controlled by the DU 330 may correspond to a logical node that hosts RF processing functions and low PHY layer functions (e.g., fast Fourier transform (FFT), inverse FFT (iFFT), digital beamforming, and / or physical random access channel (PRACH) extraction and filtering). Thus, in the O-RAN architecture, the RU 340 handles all over-the-air (OTA) communications with the UE 120, and the real-time and non-real-time aspects of the control plane and user plane communications with the RU 340 are controlled by the corresponding DU 330, which enables the DU 330 and the CU 310 to be implemented in a cloud-based RAN architecture.

[0066] As indicated above, Figure 3 are provided as examples. Other examples can be found in the Figure 3 The examples described are different.

[0067] Figure 4 4 is a diagram illustrating an example 400 of physical channels and reference signals in a wireless network according to the present disclosure. Figure 4As shown, the downlink channel and the downlink reference signal may carry information from the network entity 110 to the UE 120 , and the uplink channel and the uplink reference signal may carry information from the UE 120 to the network entity 110 .

[0068] As shown, the downlink channel may include a physical downlink control channel (PDCCH) carrying downlink control information (DCI), a physical downlink shared channel (PDSCH) carrying downlink data, or a physical broadcast channel (PBCH) carrying system information, etc. In some aspects, PDSCH communication may be scheduled by PDCCH communication. As further shown, the uplink channel may include a physical uplink control channel (PUCCH) carrying uplink control information (UCI), a physical uplink shared channel (PUSCH) carrying uplink data, or a physical random access channel (PRACH) for initial network access, etc. In some aspects, UE 120 may send confirmation (ACK) or negative confirmation (NACK) feedback (e.g., ACK / NACK feedback or ACK / NACK information) in the UCI on PUCCH and / or PUSCH.

[0069] As further shown in the figure, the downlink reference signal may include a synchronization signal block (SSB), a channel state information (CSI) reference signal (CSI-RS), a demodulation reference signal (DMRS), a positioning reference signal (PRS) or a phase tracking reference signal (PTRS), etc. As also shown in the figure, the uplink reference signal may include a sounding reference signal (SRS), a DMRS or a PTRS, etc.

[0070] The SSB may carry information used for initial network acquisition and synchronization, such as a primary synchronization signal (PSS), a secondary synchronization signal (SSS), a PBCH, and a PBCH DMRS. The SSB is sometimes referred to as a synchronization signal / PBCH (SS / PBCH) block. In some aspects, the network entity 110 may send multiple SSBs on multiple corresponding beams, and the SSBs may be used for beam selection.

[0071] The CSI-RS may carry information for downlink channel estimation (e.g., downlink CSI acquisition), which may be used for scheduling, link adaptation, or beam management, etc. The network entity 110 may configure a set of CSI-RS for the UE 120, and the UE 120 may measure the configured set of CSI-RS. Based at least in part on these measurements, the UE 120 may perform channel estimation and may report channel estimation parameters to the network entity 110 (e.g., in a CSI report), such as a channel quality indicator (CQI), a precoding matrix indicator (PMI), a CSI-RS resource indicator (CRI), a layer indicator (LI), a rank indicator (RI), or RSRP, etc. The network entity 110 can use the CSI report to select transmission parameters for downlink communication to the UE 120, such as the number of transmission layers (e.g., rank), the precoding matrix (e.g., precoder), the modulation and coding scheme (MCS), or the refined downlink beam (e.g., using a beam refinement procedure or a beam management procedure), etc.

[0072] DMRS may carry information for estimating a radio channel to demodulate an associated physical channel (e.g., PDCCH, PDSCH, PBCH, PUCCH, or PUSCH). The design and mapping of DMRS may be specific to the physical channel that the DMRS is used to estimate. DMRS is UE-specific, may be beamformed, may be restricted to scheduled resources (e.g., rather than being sent over a wideband), and may be sent only when necessary. As shown, DMRS is used for both downlink and uplink communications.

[0073] PTRS may carry information for compensating for oscillator phase noise. Typically, phase noise increases with increasing oscillator carrier frequency. Therefore, PTRS may be utilized at high carrier frequencies (such as millimeter wave frequencies) to mitigate phase noise. PTRS may be used to track the phase of a local oscillator and to achieve suppression of phase noise and common phase error (CPE). As shown, PTRS is used for both downlink communications (e.g., on PDSCH) and uplink communications (e.g., on PUSCH).

[0074] The PRS may carry information for enabling timing or ranging measurements of the UE 120 based on signals sent by the network entity 110 to improve observed time difference of arrival (OTDOA) positioning performance. For example, the PRS may be a pseudo-random quadrature phase shift keying (QPSK) sequence mapped in a diagonal pattern with a frequency offset and a time offset to avoid collisions with cell-specific reference signals and control channels (e.g., PDCCH). In general, the PRS may be designed to improve detectability of the UE 120, which may need to detect downlink signals from multiple neighboring network entities in order to perform OTDOA-based positioning. Thus, the UE 120 may receive PRS from multiple cells (e.g., a reference cell and one or more neighboring cells), and may report a reference signal time difference (RSTD) based on OTDOA measurements associated with the PRS received from the multiple cells. In some aspects, the network entity 110 may then calculate the position of the UE 120 based on the RSTD measurements reported by the UE 120.

[0075] The SRS may carry information for uplink channel estimation, which may be used for scheduling, link adaptation, pre-decoder selection, or beam management, etc. The network entity 110 may configure one or more SRS resource sets for the UE 120, and the UE 120 may send the SRS on the configured SRS resource sets. The SRS resource sets may have configured purposes such as uplink CSI acquisition, downlink CSI acquisition for reciprocity-based operation, uplink beam management, etc. The network entity 110 may measure the SRS, may perform channel estimation based at least in part on these measurements, and may use the SRS measurements to configure communications with the UE 120.

[0076] As indicated above, Figure 4 are provided as examples. Other examples can be found in the Figure 4 The examples described are different.

[0077] Figure 5 is a diagram illustrating an example 500 of sidelink communications according to the present disclosure.

[0078] like Figure 5As shown, the first UE 505-1 can communicate with the second UE 505-2 (and one or more other UEs 505) via one or more side link channels 510. UEs 505-1 and 505-2 can communicate using one or more side link channels 510 for P2P communication, D2D communication, V2X communication (e.g., which may include cellular V2X (C-V2X) communication, V2V communication, V2I communication and / or V2P communication) and / or mesh networks. In some aspects, UE 505 (e.g., UE 505-1 and / or UE 505-2) may correspond to one or more other UEs described elsewhere herein, such as UE 120. In some aspects, one or more side link channels 510 may use a PC5 interface and / or may operate in a high frequency band (e.g., a 5.9 GHz band). Additionally or alternatively, the UE 505 may use Global Navigation Satellite System (GNSS) timing to synchronize the timing of a transmit time interval (TTI) (eg, a frame, subframe, time slot, or symbol).

[0079] like Figure 5 As further shown, the one or more sidelink channels 510 may include a physical sidelink control channel (PSCCH) 515, a physical sidelink shared channel (PSSCH) 520, and / or a physical sidelink feedback channel (PSFCH) 525. The PSCCH 515 may be used to communicate control information, similar to a physical downlink control channel (PDCCH) and / or a physical uplink control channel (PUCCH) used for cellular communication with the network entity 110 via an access link or access channel. The PSSCH 520 may be used to communicate data, similar to a physical downlink shared channel (PDSCH) and / or a physical uplink shared channel (PUSCH) used for cellular communication with the network entity 110 via an access link or access channel. For example, the PSCCH 515 may carry sidelink control information (SCI) 530, which may indicate various control information for sidelink communication, such as one or more resources (e.g., time resources, frequency resources, and / or space resources), wherein a transport block (TB) 535 may be carried on the PSSCH 520. The TB 535 may include data. The PSFCH 525 may be used to communicate sidelink feedback 540, such as hybrid automatic repeat request (HARQ) feedback (eg, acknowledgement or negative acknowledgement (ACK / NACK) information), transmit power control (TPC), and / or scheduling request (SR).

[0080] Although shown on the PSCCH 515, in some aspects, the SCI 530 may include multiple communications in different levels, such as a first level SCI (SCI-1) and a second level SCI (SCI-2). The SCI-1 may be sent on the PSCCH 515. The SCI-2 may be sent on the PSSCH 520. The SCI-1 may include, for example, an indication of one or more resources (e.g., time resources, frequency resources, and / or space resources) on the PSSCH 520, information for decoding sidelink communications on the PSSCH, a quality of service (QoS) priority value, a resource reservation period, a PSSCH demodulation reference signal (DMRS) pattern, an SCI format for SCI-2, a beta offset for SCI-2, a number of PSSCH DMRS ports, and / or an MCS. The SCI-2 may include information associated with data transmission on the PSSCH 520, such as a HARQ process ID, a new data indicator (NDI), a source identifier, a destination identifier, and / or a channel state information (CSI) report trigger.

[0081] In some aspects, one or more sidelink channels 510 may use a resource pool. For example, a scheduling assignment (e.g., included in SCI 530) may be sent in a subchannel across time using specific resource blocks (RBs). In some aspects, data transmissions associated with a scheduling assignment (e.g., on PSSCH 520) may occupy adjacent RBs in the same subframe as the scheduling assignment (e.g., using frequency division multiplexing). In some aspects, the scheduling assignment and the associated data transmission are not sent on adjacent RBs.

[0082] In some aspects, UE 505 may operate using a sidelink transmission mode (e.g., Mode 1) in which resource selection and / or scheduling is performed by network entity 110. For example, UE 505 may receive a grant (e.g., in a DCI or in an RRC message, such as for a configured grant) from network entity 110 for sidelink channel access and / or scheduling. Figure 7 and Figure 8Various aspects of Mode 1 are described in more detail. In some aspects, the UE 505 may operate using a transmission mode (e.g., Mode 2) in which resource selection and / or scheduling is performed by the UE 505 (e.g., rather than the network entity 110). In some aspects, the UE 505 may perform resource selection and / or scheduling by sensing channel availability for transmission. For example, the UE 505 may measure RSSI parameters associated with various side link channels (e.g., Sidelink-RSSI (S-RSSI) parameters), may measure RSRP parameters associated with various side link channels (e.g., PSSCH-RSRP parameters), and / or may measure RSRQ parameters associated with various side link channels (e.g., PSSCH-RSRQ parameters), and may select a channel for transmitting side link communications based at least in part on the measurement results.

[0083] Additionally or alternatively, the UE 505 may perform resource selection and / or scheduling using the SCI 530 received in the PSCCH 515, which may indicate occupied resources and / or channel parameters. Additionally or alternatively, the UE 505 may perform resource selection and / or scheduling by determining a channel busy rate (CBR) associated with each sidelink channel, which may be used for rate control (e.g., by indicating a maximum number of resource blocks that the UE 505 may use for a particular set of subframes).

[0084] In a transmission mode in which resource selection and / or scheduling is performed by the UE 505, the UE 505 may generate a sidelink grant and may transmit the grant in the SCI 530. The sidelink grant may indicate, for example, one or more parameters (e.g., transmission parameters) to be used for an upcoming sidelink transmission, such as one or more resource blocks (e.g., for TB 535) to be used for an upcoming sidelink transmission on the PSSCH 520, one or more subframes to be used for an upcoming sidelink transmission, and / or an MCS to be used for an upcoming sidelink transmission. In some aspects, the UE 505 may generate a sidelink grant that indicates one or more parameters (such as the periodicity of the sidelink transmission) for semi-persistent scheduling (SPS). Additionally or alternatively, the UE 505 may generate a sidelink grant for event-driven scheduling (such as for an on-demand sidelink message).

[0085] In some V2X applications (e.g., C-V2X applications), the receiver UE 120 (e.g., the second UE 505-2) may perform blind decoding in all sidelink subchannels to receive sidelink communications. In this regard, the number of sidelink subchannels may be small, such as 1 to 27 subchannels (where each subchannel occupies one of 10, 15, 20, 25, 50, 75, or 100 physical resource blocks (PRBs)), such that blind decoding of all subchannels is feasible. In addition, the PSCCH 515 and the PSSCH 520 may be transmitted in the same time slot, where the PSSCH 520 occupies multiple consecutive subchannels (sometimes referred to as ) and / or wherein the PSCCH 515 occupies at most one subchannel associated with the lowest subchannel index. In addition, the PSCCH 515 (which may include SCI-1) may be configured to occupy 10, 12, 15, 20, or 25 PRBs (limited to one subchannel), wherein the duration of the PSCCH 515 is configured to be two or three symbols. For a given resource pool, the size of the PSCCH 515 may be fixed, with the PSCCH 515 occupying 10% to 100% of the first two or three symbols of the subchannel, depending on the configuration.

[0086] In some aspects, SCI-1 may be sent in PSCCH 515 and may include information regarding PSSCH 520 bandwidth and resource reservations in future time slots. For example, SCI 1_0 associated with SCI-1 communication included in PSCCH 515 may specify a frequency domain resource allocation (FDRA), which, when associated with two reservations, may include bits, and when associated with three reservations, it may include bits. Additionally or alternatively, SCI 1_0 may specify a time domain resource allocation (TDRA), which may include five bits when associated with two reservations and nine bits when associated with three reservations. SCI-2 communications that may be sent in PSSCH 520 may be found and decoded after decoding PSCCH 515, where a source identifier and a destination identifier are used to determine whether the packet is intended for a receiver UE 120 and to determine which transmitter UE 120 the packet originated from. In some aspects, subchannels in certain V2X applications may be larger, such as associated with a minimum of 10 RBs.

[0087] As indicated above, Figure 5 are provided as examples. Other examples can be found in relation to Figure 5 The examples described are different.

[0088] Figure 6 is a diagram illustrating an example 600 of side link communications and access link communications according to the present disclosure.

[0089] like Figure 6 As shown, the transmitter (Tx) / receiver (Rx) UE 605 and the Rx / Tx UE 610 can communicate with each other via a side link, as described above in conjunction with Figure 5 As further shown in the figure, in some sidelink modes, the network entity 110 can communicate with the Tx / Rx UE 605 via the first access link. Additionally or alternatively, in some sidelink modes, the network entity 110 can communicate with the Rx / Tx UE 610 via the second access link. The Tx / Rx UE 605 and / or the Rx / Tx UE 610 can correspond to one or more UEs described elsewhere in this document, such as Figure 1 120. Thus, a direct link between UEs 120 (e.g., via a PC5 interface) may be referred to as a side link, and a direct link between network entity 110 and UE 120 (e.g., via a Uu interface) may be referred to as an access link. Side link communications may be sent via a side link, and access link communications may be sent via an access link. Access link communications may be downlink communications (from network entity 110 to UE 120) or uplink communications (from UE 120 to network entity 110).

[0090] As indicated above, Figure 6 are provided as examples. Other examples can be found in relation to Figure 6 The examples described are different.

[0091] Figure 7 is a diagram illustrating an example 700 of a PSSCH preparation procedure according to the present disclosure.

[0092] As above combined Figure 5 As described, when operating in sidelink transmission mode 1, resource selection and / or scheduling is performed by the network entity 110. In such a case, and as shown by reference numeral 705, when a sidelink packet arrives in a buffer at a UE 120 (e.g., UE 505-1, UE 505-2, Tx / Rx UE 605, and / or Rx / TX UE 610), the UE 120 may select and schedule the sidelink packet at a predefined timing (e.g., in conjunction with Figure 41 (at an opportunity in one of the uplink channels described above) sends an SR to the network entity 110 indicating that the UE 120 has data to send. In response, the network entity 110 may schedule uplink resources (e.g., PUSCH resources) for the UE 120 to report its buffer size and / or related information, such as via a DCI message (as shown by reference numeral 710) or an RRC message. As shown by reference numeral 715, the UE 120 may then use the uplink resources scheduled by the network entity 110 (e.g., using MAC control element (MAC-CE) communication sent via PUSCH resources scheduled by the network entity 110) to send a buffer status report (BSR) associated with the sidelink communication, which may indicate to the network entity 110 that the data in the buffer is sidelink data to be sent to another UE 120 (e.g., another one of the UE 505-1, UE 505-2, Tx / Rx UE 605 and / or Rx / TX UE 610), the buffer size and / or related information associated with the sidelink transmission. More specifically, the BSR may indicate the amount of logical channel data of the packet to be sent in the sidelink.

[0093] As shown by reference numeral 720, the network entity 110 may send a DCI communication (sometimes referred to as a scheduling grant) to the UE 120, which schedules sidelink resources (e.g., PSSCH resources) for the UE 120 to send one or more sidelink packets. The scheduling grant may indicate a range of MCSs to be used for sidelink transmissions and / or resources to be used for sidelink transmissions, as well as other relevant information. For example, the DCI message may be a DCI format 3_0 message. The DCI format 3_0 message may include an indication of a resource pool index to be used for sidelink transmission (sometimes referred to as sl-TxPoolScheduling), a time interval between the DCI format 3_0 message and the sidelink transmission (sometimes referred to as sl-DCI-ToSL-Trans), a HARQ process number (HPN), an NDI, a lowest subcarrier index associated with the sidelink resource allocation, SCI-1 fields such as indications of TDRA and FDRA associated with the sidelink transmission (e.g., SCI 1_0 fields), an indication of PSFCH to HARQ feedback timing (sometimes referred to as sl-PSFCH-ToPUCCH), a PUCCH resource indicator, a configuration index, a counter sidelink assignment indicator (SAI), padding bits, and other information. In some aspects, the DCI format 3_0 message or a similar scheduling grant may specify a resource allocation for a TB (e.g., TB 535), and the DCI format 3_0 message may indicate that up to three resources are to be used for retransmissions associated with the TB (e.g., to be used as part of a HARQ process associated with the TB). In some aspects, UE 120 may maintain a one-to-one mapping of HPNs in DCI and SCI for a given TB. In addition, an NDI included in a DCI format 3_0 message or a similar scheduling grant may be used to switch the NDI in the SCI. Additionally or alternatively, a DCI format 3_0 message or a similar scheduling grant may include a PUCCH resource for UE 120 to use for providing sidelink HARQ feedback, which may be specified using an offset (e.g., using a feedback timing parameter) from a PDCCH carrying the DCI format 3_0 message or a similar scheduling grant to the PUCCH resource for providing sidelink HARQ feedback.

[0094] As shown by reference numeral 725, after receiving the scheduling grant from the network entity 110, the UE 120 may begin preparing one or more sidelink packets for transmission. As used herein, a PSSCH preparation process may refer to a process in which the UE 120 prepares a TB (e.g., TB 535) for transmission on the physical layer (such as transmission within the PSSCH 520 or another physical channel). The UE 120 must receive the scheduling grant before starting the PSSCH preparation process because the UE 120 needs the resource allocation of the network entity 110 in the scheduling grant to determine certain aspects of the sidelink transmission, such as the TB size (TBS) to be transmitted, the MCS to be used for transmission, and related aspects of the sidelink transmission. More specifically, before the UE 120 receives the scheduling grant from the network entity 110, the UE 120 does not know the resource allocation for the transmission of the TB, the resource allocation for the retransmission of the TB, the NDI (which may force the UE 120 to discard the retransmission of the TB because the maximum number of retransmissions under mode 1 depends on the network entity) and / or the range of the MCS to be used for the sidelink transmission. However, after receiving the scheduling grant, the UE 120 may select an appropriate MCS to be used for the sidelink transmission within a range specified by the network entity 110, which may be based at least in part on the CSI associated with the sidelink channel known only to the UE 120 and not to the network entity 110. The UE 120 may also decide which TB to transmit using resources provided by the network entity 110, may determine whether a sidelink HARQ process should be enabled for the sidelink transmission, and / or may decide a corresponding HPN to be used for the sidelink transmission. In addition, the UE 120 may determine a DMRS pattern and / or port to be used for the sidelink transmission, and / or may determine the number of transmission layers to be used for the sidelink transmission. In addition, the UE 120 may determine a type of precoding to be used for the sidelink transmission, may determine a CSI-RS to be used for the sidelink transmission, may determine a redundancy version (RV) identifier (RV-ID) to be used for the sidelink transmission, may determine a broadcast type to be used for the sidelink transmission, and / or may determine other transmission-related parameters.

[0095] With knowledge of the resource allocation for the sidelink transmission, the UE 120 may prepare one or more sidelink packets for transmission (e.g., may perform a PSSCH preparation procedure). For example, the PSSCH preparation procedure may include one or more procedures, such as the procedure within the dashed box attached to the reference numeral 725. This may include performing one or more of the following: assembling TBs, appending a cyclic redundancy check (CRC) to the TBs, selecting a low-density parity-check (LDPC) base graph (BG) for the TBs, performing code block (CB) segmentation for the TBs, appending a CRC to one or more CBs, performing channel coding for the TBs according to an MCS selected by the UE 120 within a range of MCSs indicated by the network entity 110, and performing a rate matching procedure associated with the TBs.

[0096] To ensure that the UE 120 has sufficient time to perform TB preparation, such as the PSSCH preparation procedure shown at reference numeral 725, the network entity 110 may schedule (e.g., via the sl-DCI-ToSL-Trans parameter) resources for sidelink transmissions that occur no earlier than N2+1 OFDM symbols after the scheduling grant. In some cases, the value of N2 may depend on the subcarrier spacing (SCS) used for the sidelink transmission. For example, for SCSs of 15 kHz, 30 kHz, 60 kHz, and 120 kHz (e.g., μ equals 0, 1, 2, and 3, respectively), the value of N2 may be equal to 10 OFDM symbols, 12 OFDM symbols, 23 OFDM symbols, and 36 OFDM symbols, respectively. Therefore, in some cases, a mode 1 sidelink resource allocation (such as Figure 7 Mode 1 sidelink resource allocation (shown in FIG. 7 ) results in high latency because there may be a long period of time between the transmission of the SR by UE 120 and the sidelink transmission of the TB by UE 120 (shown in FIG. 730 ). The latency caused by Mode 1 resource allocation may be particularly problematic for time-sensitive sidelink communications such as C-V2X communications.

[0097] Some techniques and apparatus described herein enable PSSCH preparation by UE 120 prior to receiving a resource allocation from network entity 110. In some aspects, UE 120 may indicate certain transmission parameters in a BSR sent to network entity 110, and may initiate a PSSCH preparation procedure prior to receiving a scheduling grant based at least in part on the indicated transmission parameters. For example, sidelink transmissions may be associated with Industrial Internet of Things (IIoT) applications, which typically include a deterministic payload size. More specifically, in IIoT applications, sidelink communications may enable direct programmable logic controller (PLC) and sensor / actuator (SA) communications, where a wireless PLC typically controls 20 to 50 SAs. In some aspects, these IIoT applications may be associated with strict latency (e.g., 1 ms to 2 ms) and ultra-high reliability requirements (e.g., 10 -6 Furthermore, traffic between such IIoT components may be deterministic, with smaller known packet sizes typically in the range of 32 bytes to 256 bytes being sent between PLCs and / or SAs (thus requiring relatively small bandwidth, such as 2 RBs in some cases).

[0098] Thus, in some aspects, such as for IIoT applications with deterministic payload size and / or stringent latency and ultra-high reliability requirements, UE 120 may indicate that the TBS is determined prior to sending the BSR, and thus may indicate the TBS in the BSR sent to network entity 110, and thus begin PSSCH preparation prior to receiving a scheduling grant. Additionally or alternatively, based at least in part on UE 120's knowledge of the sidelink channel (e.g., PSSCH 520), UE 120 may determine the MCS to be used for sidelink transmissions prior to receiving the scheduling grant, and thus UE 120 may indicate the selected MCS in the BSR and begin PSSCH preparation prior to receiving the scheduling grant based at least in part on knowing the MCS. By UE 120 initiating the PSSCH preparation procedure prior to receiving a resource allocation from network entity 110 (and in some aspects, prior to sending a BSR to network entity 110), the time between the transmission of the SR and the corresponding sidelink transmission may be reduced, resulting in reduced latency, increased throughput, and overall more efficient use of network resources. For example, in combination with Figure 7 Compared to the PSSCH preparation process described, some techniques and apparatus described herein can result in a latency reduction of 40% or more, which can be equivalent to a time saving of multiple OFDM symbols (e.g., four or more OFDM symbols), and this time saving can be more significant for situations such as larger TBSs associated with a large number of CBs.

[0099] As indicated above, Figure 7 are provided as examples. Other examples can be found in relation to Figure 7 The examples described are different.

[0100] Figure 8 is a diagram illustrating another example 800 of a PSSCH preparation procedure according to the present disclosure.

[0101] Figure 8 The illustrated example includes similar messages sent between UE 120 (e.g., UE 505-1, UE 505-2, Tx / Rx UE 605, and / or Rx / TX UE 610) and network entity 110, but the PSSCH preparation procedure starts earlier (e.g., closer in time to the transmission of the SR) in order to reduce the amount of time between the SR and the associated sidelink transmission. More specifically, when the sidelink packet arrives in the buffer at UE 120, UE 120 may, at a predefined timing (e.g., in conjunction with Figure 4 1 ) sends an SR to the network entity 110 indicating that the UE 120 has sidelink data to send to another UE 120 (e.g., another one of the UE 505-1, UE 505-2, Tx / Rx UE 605, and / or Rx / TX UE 610), as shown at reference numeral 805. The SR may be similar to the SR described above in conjunction with reference numeral 705. In response, the network entity 110 may schedule uplink resources (e.g., PUSCH resources) for the UE 120 to report its buffer size and / or related information. The UE 120 may receive an indication of the scheduled uplink resources via a DCI message or an RRC message, etc., as shown by reference numeral 810. The message indicated by reference numeral 810 may be similar to the message described above in conjunction with reference numeral 710.

[0102] As shown in the dashed box accompanying the PSSCH preparation procedure indicated at reference numeral 815, in some aspects, the UE 120 may begin performing some (e.g., most) of the TB preparation steps described in conjunction with reference numeral 725 prior to receiving a scheduling grant from the network entity 110, and in some aspects, even prior to sending a BSR to the network entity 110. In other words, in some aspects, the UE 120 may begin the PSSCH preparation procedure without knowing the resource allocation from the network entity 110. The UE 120 may be able to begin PSSCH preparation at an early stage (e.g., prior to receiving a scheduling grant) because, in some aspects, the sidelink transmission may be associated with a known TBS (e.g., the sidelink transmission may be associated with a deterministic payload, etc.), may be associated with an MCS selected by the UE 120 prior to receiving a scheduling grant, and / or may be associated with other transmission parameters selected by the UE 120 prior to receiving a scheduling grant.

[0103] More specifically, the UE 120 may prepare a TB (e.g., TB 535) and / or determine a TBS before receiving a scheduling grant and / or before knowing the sidelink resource allocation. Additionally or alternatively, the UE 120 may attach a CRC to the TB before receiving a scheduling grant and / or before knowing the sidelink resource allocation (using a plurality of CRC bits depending on the TBS). Additionally or alternatively, the UE 120 may select an LDPC BG before receiving a scheduling grant and / or before knowing the sidelink resource allocation. For example, the UE 120 may select an LDPC BG based at least in part on a target code rate, which may or may not be reported to the network entity 110. Additionally or alternatively, the UE 120 may perform CB segmentation and attach a CRC to each CB before receiving a scheduling grant and / or before knowing the sidelink resource allocation. In some aspects, performing a CB segmentation may be based at least in part on the TBS plus the attached CRC and / or the selected LDPC BG. Additionally or alternatively, UE 120 may perform channel coding, such as calculating check bits into a buffer, before receiving a scheduling grant and / or before knowing the sidelink resource allocation.

[0104] In some aspects, the UE 120 may select and / or determine certain transmission parameters (e.g., TBS, MCS, BG, etc.) before sending the BSR, and signal the selected transmission parameters to the network entity 110 via the BSR. For example, as shown in reference numeral 820, the UE 120 may send a BSR to the network entity 110, which may be similar to the BSR described above in conjunction with reference numeral 715. However, in this aspect, the BSR may include additional information, such as an indication of a TBS associated with the sidelink transmission and / or an indication of a selected MCS associated with the sidelink transmission. Additionally or alternatively, the UE 120 may indicate certain additional channel information in the BSR, such as CSI associated with a sidelink channel (e.g., PSSCH), CQI associated with the sidelink channel, or similar information. Additionally or alternatively, the UE 120 may indicate a selected BG in the BSR, and / or the UE 120 may indicate a selected code rate in the BSR.

[0105] In some aspects, UE 120 may not report the selected modulation order, but rather network entity 110 may assume that a certain MCS will be implemented by UE 120. For example, network entity 110 may be configured to assume that UE 120 will use QPSK for sidelink transmissions, and thus may determine the number of resource elements (REs) for resource allocation based at least in part on the assumption that QPSK will be used even in the absence of signaling of the selected MCS from UE 120. In such aspects, UE 120 may provide an indication of a scaling factor (sometimes referred to as a TB scaling factor) to be used by network entity 110 if UE 120 will implement modulation higher or lower than QPSK. For example, if UE 120 will implement 16 quadrature amplitude modulation (QAM) instead of QPSK for sidelink transmissions, the BSR may indicate a scaling factor less than 1, such that network entity 110 allocates fewer REs than would be allocated if UE 120 were to implement QPSK. Alternatively, if UE 120 is to implement binary phase shift keying (BPSK) instead of QPSK for sidelink transmissions, the BSR may indicate a scaling factor greater than 1, such that network entity 110 allocates more REs than would be allocated if UE 120 were to implement QPSK. In some other aspects, UE 120 may include an MCS indication and / or a CQI indication in the BSR (e.g., within a MAC-CE carrying the BSR), and network entity 110 may scale the indicated buffer size and / or the indicated TBS by the modulation order and / or the code rate. For example, in some aspects, the TBS may be scaled according to the expression TBS / (modulation order×code rate×number of transmit layers×(1-overhead)).

[0106] In some aspects, the UE 120 may use the BSR described in conjunction with reference numeral 820 (e.g., a BSR indicating certain transmission parameters such as MCS, TBS, BG, code rate, etc.) for certain urgent services and / or for certain types of TBs, but not for less urgent services and / or other types of TBs. For example, the UE 120 may use the BSR for high priority services (e.g., services associated with a priority value that satisfies a priority threshold), and / or for services associated with a TBS that satisfies a TBS threshold. In addition, in some aspects, the BSR may include one or more fields indicating whether certain transmission parameters are indicated by the BSR. For example, the BSR may be associated with a MAC-CE having an enhanced logical channel identification (eLCID) field and / or other dedicated fields that indicate the type of BSR being transmitted. For example, the eLCID field and / or other dedicated fields may indicate that the BSR indicates one of the original TBS (e.g., the TBS before modulation) or the TBS with MCS considerations (e.g., the TBS after modulation).

[0107] Additionally or alternatively, the BSR may indicate whether the TBS is a fixed TBS or a flexible TBS. The indication of a fixed TBS may signal that the UE 120 may not be able to insert padding bits or otherwise split the TB to change the TBS to accommodate resource allocations from the network entity 110. However, the indication of a flexible TBS may signal that the UE 120 may perform padding or splitting (if necessary), which will be described in more detail below in conjunction with reference numeral 835.

[0108] As shown by reference numeral 825, UE 120 may receive a DCI message or similar message (e.g., a scheduling grant) indicating resource allocation for UE 120 to perform sidelink transmission, which may include similar information as described above in conjunction with reference numeral 720. More specifically, in some aspects, the scheduling grant may be a DCI format 3_0 message, which may include an indication of a resource pool index to be used for sidelink transmission (e.g., sl-TxPoolScheduling), a time interval between the DCI format 3_0 message and the sidelink transmission (e.g., sl-DCI-ToSL-Trans), HPN, NDI, a minimum subcarrier index associated with the sidelink resource allocation, an SCI-1 such as an indication of a TDRA and FDRA associated with the sidelink transmission, an indication of PSFCH to HARQ feedback timing (e.g., sl-PSFCH-ToPUCCH), a PUCCH resource indicator, a configuration index, a counter SAI, padding bits, and other information. Moreover, in aspects where the selected MCS is indicated by the BSR, the scheduling grant may schedule sidelink resources based at least in part on the selected MCS (e.g., the network entity 110 may consider the modulation order when determining a number of REs to schedule for sidelink transmissions).

[0109] As indicated by reference numeral 830, after receiving the scheduling grant, the UE 120 may perform additional PSSCH preparations, if necessary. That is, the UE 120 may perform one or more PSSCH preparation steps that the UE 120 could not perform before receiving the resource allocation from the network entity 110 and / or that the UE 120 did not complete or otherwise did not have time to perform before receiving the scheduling grant. For example, as indicated by the dashed box accompanying the additional preparation steps indicated by reference numeral 830, in this regard, the UE 120 may perform a rate matching procedure or similar preparation steps after receiving the scheduling grant.

[0110] In this regard, the amount of processing time after receiving a scheduling grant can be reduced because less PSSCH preparation may be required after receiving the scheduling grant since UE 120 has completed at least some PSSCH preparation before receiving the scheduling grant. Thus, in some aspects, compared to the PSSCH preparation procedure described in conjunction with Figure 7 , resources allocated for sidelink transmission can be scheduled closer to the scheduling grant (e.g., a smaller time interval defined by sl-DCI-ToSL-Trans can be used to schedule resources). More specifically, different from scheduling sidelink transmission in a time period not earlier than N2 + 1 OFDM symbols after the scheduling grant as described in conjunction with Figure 7 , in this aspect, the network entity 110 can schedule sidelink transmission in a time period not earlier than a time interval sometimes referred to as K'2, and this time interval can be less than N2 + 1 (e.g., K'2 < N2 + 1). Thus, after K'2 has passed (again, this time interval can be less than N2 + 1), UE 120 can use the resources allocated by the scheduling grant to transmit sidelink communication, as shown by reference numeral 835 in the accompanying figure. Note that in this aspect, because K'2 < N2 + 1, sidelink transmission can be scheduled closer to the scheduling grant compared to the sidelink transmission described above in conjunction with reference numeral 730, thereby reducing the latency associated with sidelink reduction. For example, aspects of the present disclosure can result in a latency reduction (indicated by reference numeral 840 in Figure 8 ) equal to the time period between the time to transmit the sidelink transmission shown by reference numeral 835 and the time to transmit the sidelink transmission using the process described in Figure 7 .

[0111] In some aspects, because UE 120 may start PSSCH preparation before receiving the resource allocation in the scheduling grant, the resource allocation may not match the TBS. That is, in some aspects, the network entity 110 may allocate more or fewer REs than necessary for a given TBS for sidelink transmission. In some aspects, if the number of REs indicated by the scheduling grant is less than a threshold (e.g., if the number of allocated REs is less than the TBS), the UE 120 may discard and / or ignore the scheduling grant sent for that particular TB. In other words, in aspects where the TBS is a fixed TBS that cannot be split, etc., if the resource allocation is less than the fixed TBS, the UE 120 may refuse to use the resource allocation to send the fixed TBS. In some aspects, the UE 120 may still use the allocated resources for different sidelink transmissions, such as for sidelink transmissions associated with a flexible TBS (e.g., a TBS that can be split, etc.). In some aspects, if UE 120 discards the allocated resources because the TBS is a fixed TBS, etc., UE 120 may indicate to network entity 110 that the scheduling grant is discarded because it does not correspond to a fixed TBS (eg, because the resource allocation is too small for the TBS).

[0112] Alternatively, if the number of REs indicated by the scheduling grant is less than a threshold (e.g., if the resource allocation is less than the TBS), the UE 120 may truncate the transmission in order to use the allocated resources to transmit a portion of the sidelink transmission. For example, the UE 120 may transmit less than all CBs associated with the sidelink transmission, and in some aspects, any remaining CBs may be transmitted using retransmission resources (e.g., using resources associated with a HARQ process, etc.). Alternatively, the UE 120 may trigger another SR (similar to the SR described above in conjunction with reference numeral 805) and / or another BSR (similar to the BSR described above in conjunction with reference numeral 820) in order to receive another resource allocation for transmitting the remaining CBs. In such aspects, the receiver UE 120 may need to wait for another transmission (e.g., a transmission of the remaining CBs transmitted in the retransmission resources and / or in the additionally allocated resources) before the TBs can be assembled and delivered to the MAC layer at the receiver UE 120. In such aspects, the transmitter UE 120 may indicate to the receiver UE 120, such as via SCI-2 signaling, that the sidelink transmission has been truncated.

[0113] In aspects where the number of REs indicated by the scheduling grant is greater than a threshold (e.g., in aspects where the resource allocation is greater than the TBS), the UE 120 may use the allocated resources to send the TB and some additional data and / or information. For example, in some aspects, the UE 120 may append padding bits to the TB. Additionally or alternatively, the UE 120 may use excess REs to send reference signals, such as sidelink CSI-RS, additional DMRS, etc. Additionally or alternatively, the UE 120 may use excess REs to repeat certain information, such as by repeating bits in a circular buffer of the UE 120. Additionally or alternatively, the UE 120 may use a different modulation order (e.g., a lower modulation order) while maintaining the same forward error correction (FEC) rate in order to utilize the excess REs. In such aspects, the transmitter UE 120 may signal to the network entity 110 and / or the receiver UE 120 that a different modulation order is being used, such as by signaling a scaling factor (sometimes referred to as an SCI scaling factor) applied to a previously communicated MCS, etc. Additionally or alternatively, UE 120 may use only as many resources in the resource allocation as are needed to send a TB. For example, if the resource allocation includes three subchannels, but only two subchannels are needed to send a complete TB, UE 120 may use two of the three subchannels to perform sidelink transmission.

[0114] As indicated above, Figure 8 are provided as examples. Other examples can be found in relation to Figure 8 The examples described are different.

[0115] Fig. 9 is a diagram of an example 900 associated with a sidelink preparation procedure time reduction according to the present disclosure. Fig. 9 As shown, UE 120 (e.g., UE 505-1, UE 505-2, Tx / Rx UE 605, Rx / TX UE 610, or similar UE) and network entity 110 may communicate with each other. In some aspects, UE 120 and network entity 110 may be part of a wireless network (e.g., wireless network 100). UE 120 and network entity 110 may be in communication with each other. Fig. 9 The illustrated operations are preceded by establishing a wireless connection.In some aspects, UE 120 may communicate with another UE 120 (eg, another one of UE 505-1, UE 505-2, Tx / Rx UE 605, Rx / TXUE 610, or similar UEs) via a sidelink.

[0116] As shown in reference numeral 905, UE 120 may initiate a PSSCH preparation procedure associated with the sidelink communication prior to receiving a resource allocation associated with the sidelink communication. For example, in some aspects, UE 120 may perform one or more of the PSSCH preparation steps described in conjunction with reference numeral 815 prior to receiving a resource allocation associated with the sidelink communication. More specifically, prior to receiving a resource allocation associated with the sidelink communication, UE 120 may append a CRC to a TB, select an LDPC BG, perform CB segmentation, append a CRC to one or more CBs, perform channel coding, and / or perform similar PSSCH preparation steps.

[0117] As shown in reference numeral 910, the UE 120 may send a BSR to the network entity 110. For example, the UE 120 may send the BSR described in conjunction with reference numeral 820. In this regard, the BSR may indicate certain transmission parameters associated with the sidelink communication, such as a TBS associated with the sidelink communication, an MCS associated with the sidelink communication (or, in some aspects, a plurality of candidate MCSs associated with the sidelink communication), a CQI associated with the sidelink communication, a selected BG for LDPC coding, or similar transmission parameters, as described above in conjunction with reference numeral 820. In aspects where the BSR includes the TBS, the TBS may be based at least in part on the selected MCS associated with the sidelink communication (e.g., the TBS may take into account bits required for the selected MCS). In such aspects, the BSR may include an indication that the TBS is associated with the MCS, such as within an eLCID or dedicated field of the BSR, as described in conjunction with reference numeral 820. Furthermore, as described, the BSR may indicate whether the TBS is a fixed size or a flexible size. In some aspects, the BSR may indicate a priority value associated with the TBS. For example, the BSR may indicate that the TBS is associated with a priority value that exceeds a threshold priority value. In addition, in some aspects, UE 120 may initiate a PSSCH preparation procedure associated with sidelink communications, as described in conjunction with reference numerals 815 and 820, before sending a BSR associated with sidelink communications.

[0118] As shown in reference numeral 915, UE 120 may receive resource allocations associated with sidelink communications from network entity 110. For example, UE 120 may receive a DCI message or an RRC message indicating resource allocations associated with sidelink communications, such as a scheduling grant described in conjunction with reference numeral 825. In aspects where the BSR indicates a TBS, MCS, and / or CQI associated with the sidelink communications, the resource allocations may be based at least in part on the TBS, MCS, and / or CQI. Further, and as described in conjunction with reference numeral 825, in some aspects, network entity 110 may assume that UE 120 uses a certain MCS for sidelink communications, such as QPSK modulation. In this regard, the resource allocations may be based at least in part on a determined number of REs associated with the QPSK modulation. In such aspects, if the sidelink communications are associated with a selected modulation other than QPSK modulation (e.g., if UE 120 selects a different MCS), the BSR may further indicate a TB scaling factor associated with the selected modulation, as described above in conjunction with reference numeral 820.

[0119] As shown in reference numeral 920, UE 120 may perform sidelink communications with another UE 120 based at least in part on the resource allocation. For example, UE 120 may perform any additional PSSCH preparation steps, such as the rate matching steps described in conjunction with reference numeral 830, and then send sidelink communications (e.g., TBs) to another UE 120 using the resources allocated by the network entity 110 as indicated by the communication described in conjunction with reference numeral 915.

[0120] In some aspects, the resource allocation associated with the sidelink communication may include a number of REs less than the RE threshold (e.g., the number of REs allocated may be less than the number of REs necessary to send the entire sidelink communication). In such aspects, the UE 120 may not use the resource allocation for the sidelink communication, but may use the resource allocation to send another sidelink communication to another UE 120, and / or may send an indication to the network entity 110 that the resource allocation is not used for the sidelink communication, as described in conjunction with reference numeral 835. Alternatively, if the resource allocation associated with the sidelink communication includes a number of REs less than the RE threshold, the UE 120 may send an indication to the other UE 120 that only a portion of the sidelink communication will be sent using the resource allocation for the sidelink communication. In such aspects, the UE 120 may send a first portion of the sidelink communication to the other UE 120 using the resource allocation for the sidelink communication, and send a second portion of the sidelink communication to the other UE 120 using the resource allocation associated with the retransmission communication. Additionally or alternatively, UE 120 may send another BSR associated with a portion of the sidelink communication to network entity 110 in order to receive additional resource allocations for sending the remaining portion of the sidelink communication, as described in conjunction with reference numeral 835 .

[0121] In some other aspects, the resource allocation associated with the sidelink communication may include a number of REs greater than the RE threshold (e.g., the allocated REs may be more than the REs necessary to send the entire sidelink communication). In such aspects, the UE 120 may append at least one of filler bits, a sidelink CSI-RS, or a DMRS to the sidelink communication, as described in conjunction with reference numeral 835. Additionally or alternatively, if the number of REs is greater than the RE threshold, the UE 120 may repeat bits in a circular buffer associated with the sidelink communication, the UE 120 may select a different modulation order associated with the sidelink communication, and / or the UE 120 may use a portion of the resources (e.g., using a subset of the subchannels of the resource allocation) to send the sidelink communication to another UE 120, as described in conjunction with reference numeral 835.

[0122] In some aspects, UE 120 may be permitted to perform operations faster than UE 120 in certain legacy procedures (such as in conjunction with Figure 7 More specifically, in some aspects, the sidelink communication may be permitted to be sent after a time interval (e.g., K'2) after receiving a resource allocation associated with the sidelink communication, where the time interval is less than N2+1 symbols (e.g., in combination with Figure 7In such aspects, N2 may be equal to one of 10, 12, 23, or 36, corresponding to subcarrier spacings of 15 kHz, 30 kHz, 60 kHz, and 120 kHz, respectively (e.g., μ is equal to 0, 1, 2, and 3). In this regard, based at least in part on the UE 120 initiating a PSSCH preparation procedure prior to receiving a resource allocation associated with sidelink communications, the UE 120 and / or the network entity 110 may communicate using reduced latency (as well as other beneficial effects) (e.g., may communicate using the latency reduction described in conjunction with reference numeral 840).

[0123] As indicated above, Fig. 9 are provided as examples. Other examples can be found in relation to Fig. 9 The examples described are different.

[0124] Fig.10 is a diagram illustrating an example process 1000, performed, for example, by a UE, according to the present disclosure. Example process 1000 is an example in which a UE (eg, UE 120) performs operations associated with sidelink preparation procedure time reduction.

[0125] like Fig.10 As shown, in some aspects, process 1000 may include receiving a resource allocation associated with sidelink communication from a network entity (e.g., network entity 110) (block 1010). For example, a UE (e.g., using Fig.12 The communication manager 1208 and / or receiving component 1202 depicted in FIG. 1204 may receive resource allocations associated with sidelink communications from a network entity, as described above.

[0126] like Fig.10 As further shown, in some aspects, process 1000 may include initiating a PSSCH preparation procedure associated with sidelink communication prior to receiving a resource allocation associated with sidelink communication (block 1020). Fig.12 The communication manager 1208 and / or sidelink component 1210 depicted in FIG. 1 may initiate a PSSCH preparation procedure associated with sidelink communications prior to receiving a resource allocation associated with sidelink communications, as described above.

[0127] Process 1000 may include additional aspects, such as any single aspect or any combination of aspects described below and / or in conjunction with one or more other processes described elsewhere herein.

[0128] In a first aspect, the sidelink communication is permitted to be sent after a time interval after receiving the resource allocation associated with the sidelink communication, and the time interval is less than N2+1 symbols, where N2 is equal to one of 10, 12, 23 or 36, corresponding to subcarrier spacings of 15kHz, 30kHz, 60kHz and 120kHz, respectively.

[0129] In a second aspect, either alone or in combination with the first aspect, before receiving the resource allocation associated with the side link communication, initiating the PSSCH preparation procedure associated with the side link communication includes at least one of: appending to a transport block, selecting a low-density parity check base map, performing CB segmentation, appending a CRC to one or more CBs, or performing channel coding.

[0130] In a third aspect, either alone or in combination with one or more of the first and second aspects, process 1000 includes sending a BSR associated with the sidelink communication to the network entity, wherein the BSR indicates a TBS associated with the sidelink communication, and wherein the resource allocation associated with the sidelink communication is based at least in part on the TBS.

[0131] In a fourth aspect, alone or in combination with one or more of the first to third aspects, process 1000 includes initiating the PSSCH preparation procedure associated with the sidelink communication before sending the BSR associated with the sidelink communication.

[0132] In a fifth aspect, alone or in combination with one or more of the first to fourth aspects, the BSR further indicates a selected base graph for low density parity check coding.

[0133] In a sixth aspect, either alone or in combination with one or more of the first to fifth aspects, the TBS associated with the sidelink communication is based at least in part on a selected modulation and coding scheme associated with the sidelink communication.

[0134] In a seventh aspect, alone or in combination with one or more of the first to sixth aspects, the resource allocation is based at least in part on a determined number of resource elements associated with a quadrature phase shift keying modulation.

[0135] In an eighth aspect, either alone or in combination with one or more of the first to seventh aspects, the side link communication is associated with a selected modulation other than quadrature phase shift keying modulation, and the BSR further indicates a transport block scaling factor associated with the selected modulation.

[0136] In a ninth aspect, alone or in combination with one or more of the first to eighth aspects, the BSR further indicates at least one of an MCS associated with the sidelink communication or a CQI associated with the sidelink communication.

[0137] In a tenth aspect, either alone or in combination with one or more of the first to ninth aspects, the resource allocation is based at least in part on at least one of the MCS associated with the sidelink communication or the CQI associated with the sidelink communication.

[0138] In an eleventh aspect, alone or in combination with one or more of the first to tenth aspects, the BSR further indicates a plurality of candidate modulation and coding schemes associated with the sidelink communication.

[0139] In a twelfth aspect, either alone or in combination with one or more of aspects 1 to eleven, the BSR indicates the TBS associated with the side link communication based at least in part on the side link communication being associated with a priority value exceeding a threshold priority value.

[0140] In a thirteenth aspect, either alone or in combination with one or more of the first to twelfth aspects, the BSR indicates the TBS associated with the side link communication based at least in part on a size of the TBS associated with the side link communication.

[0141] In a fourteenth aspect, alone or in combination with one or more of the first to thirteenth aspects, the BSR further indicates whether the TBS is associated with a modulation and coding scheme.

[0142] In a fifteenth aspect, alone or in combination with one or more of the first to fourteenth aspects, the BSR further indicates whether the TBS is a fixed size.

[0143] In a sixteenth aspect, either alone or in combination with one or more of the first to fifteenth aspects, the resource allocation associated with the sidelink communication comprises a plurality of resource elements, and the number of resource elements is less than a resource element threshold.

[0144] In a seventeenth aspect, either alone or in combination with one or more of the first to sixteenth aspects, the resource allocation is not used for the sidelink communication based at least in part on the number of resource elements being less than the resource element threshold.

[0145] In an eighteenth aspect, alone or in combination with one or more of the first to seventeenth aspects, process 1000 includes sending another sidelink communication to another UE using the resource allocation for the sidelink communication.

[0146] In a nineteenth aspect, either alone or in combination with one or more of aspects one to eighteen, process 1000 includes sending an indication to the network entity that the resource allocation is not used for the side link communication based at least in part on the number of resource elements being less than the resource element threshold.

[0147] In the twentieth aspect, either alone or in combination with one or more of the first to nineteenth aspects, process 1000 includes sending an indication to another UE that only a portion of the side link communication will be sent using the resource allocation for the side link communication based at least in part on the number of resource elements being less than the resource element threshold.

[0148] In aspect twenty-one, alone or in combination with one or more of aspects one to twentieth, process 1000 includes sending a first portion of the side link communication to the other UE using the resource allocation for the side link communication, and sending a second portion of the side link communication to the other UE using the resource allocation associated with the retransmission communication.

[0149] In aspect twenty-second, either alone or in combination with one or more of aspects one to twenty-first, process 1000 comprises sending a buffer status report associated with another portion of the side link communication to the network entity based at least in part on the number of resource elements being less than the resource element threshold.

[0150] In a twenty-third aspect, either alone or in combination with one or more of the first to twenty-second aspects, the resource allocation associated with the sidelink communication comprises a plurality of resource elements, and the number of resource elements is greater than a resource element threshold.

[0151] In aspect twenty-four, either alone or in combination with one or more of aspects one to twenty-three, process 1000 comprises appending at least one of fill bits, a side link channel state information reference signal, or a demodulation reference signal to the side link communication based at least in part on the number of resource elements being greater than the resource element threshold.

[0152] In aspect twenty-fifth, either alone or in combination with one or more of aspects one to twenty-fourth, process 1000 comprises repeating bits in a circular buffer associated with the side link communication based at least in part on the number of resource elements being greater than the resource element threshold.

[0153] In a twenty-sixth aspect, either alone or in combination with one or more of aspects one to twenty-fifth, process 1000 comprises selecting a modulation order associated with the side link communication based at least in part on the number of resource elements being greater than the resource element threshold.

[0154] In aspect twenty-seven, either alone or in combination with one or more of aspects one to twenty-six, process 1000 includes sending the side link communication to another UE using a portion of the resource allocation associated with the side link communication based at least in part on the number of resource elements being greater than the resource element threshold.

[0155] although Fig.10 An example block diagram of process 1000 is shown, but in some aspects, process 1000 may include Fig.10 Additional blocks, fewer blocks, different blocks, or blocks arranged in a different manner than those depicted in the process 1000. Additionally or alternatively, two or more of the blocks in the process 1000 may be performed in parallel.

[0156] Fig.11 is a diagram illustrating an example process 1100, performed, for example, by a network entity, in accordance with the present disclosure. The example process 1100 is an example in which a network entity (eg, network entity 110) performs operations associated with sidelink preparation procedure time reduction.

[0157] like Fig.11 As shown, in some aspects, process 1100 may include receiving a BSR associated with a sidelink communication from a UE (e.g., UE 120), wherein the BSR indicates a TBS associated with the sidelink communication (block 1110). For example, a network entity (e.g., using Fig.13 The communication manager 1308 and / or receiving component 1302 depicted in FIG. 1 may receive a BSR associated with a sidelink communication from a UE, wherein the BSR indicates a TBS associated with the sidelink communication, as described above.

[0158] like Fig.11 As further shown, in some aspects, process 1100 may include sending a resource allocation associated with sidelink communication to the UE based at least in part on the TBS (block 1120). Fig.13 The communication manager 1308 and / or the sending component 1304 depicted in the figure may send a resource allocation associated with sidelink communications to the UE based at least in part on the TBS, as described above.

[0159] Process 1100 may include additional aspects, such as any single aspect or any combination of aspects described below and / or in conjunction with one or more other processes described elsewhere herein.

[0160] In a first aspect, the sidelink communication is permitted to be sent after a time interval after receiving the resource allocation associated with the sidelink communication, and the time interval is less than N2+1 symbols, where N2 is equal to one of 10, 12, 23 or 36, corresponding to subcarrier spacings of 15kHz, 30kHz, 60kHz and 120kHz, respectively.

[0161] In a second aspect, either alone or in combination with the first aspect, the BSR further indicates a selected base graph for low density parity check coding.

[0162] In a third aspect, alone or in combination with one or more of the first and second aspects, the TBS associated with the sidelink communication is based at least in part on a selected modulation and coding scheme associated with the sidelink communication.

[0163] In a fourth aspect, alone or in combination with one or more of the first to third aspects, the resource allocation is based at least in part on a determined number of resource elements associated with a quadrature phase shift keying modulation.

[0164] In a fifth aspect, either alone or in combination with one or more of the first to fourth aspects, the sidelink communication is associated with a selected modulation other than quadrature phase shift keying modulation, and the BSR further indicates a transport block scaling factor associated with the selected modulation.

[0165] In a sixth aspect, alone or in combination with one or more of the first to fifth aspects, the BSR further indicates at least one of an MCS associated with the sidelink communication or a CQI associated with the sidelink communication.

[0166] In a seventh aspect, either alone or in combination with one or more of the first to sixth aspects, the resource allocation is based at least in part on at least one of the MCS associated with the sidelink communication or the CQI associated with the sidelink communication.

[0167] In an eighth aspect, alone or in combination with one or more of the first to seventh aspects, the BSR further indicates a plurality of candidate modulation and coding schemes associated with the sidelink communication.

[0168] In a ninth aspect, either alone or in combination with one or more of aspects 1 to 8, the BSR indicates the TBS associated with the side link communication based at least in part on the side link communication being associated with a priority value exceeding a threshold priority value.

[0169] In a tenth aspect, either alone or in combination with one or more of the first to ninth aspects, the BSR indicates the TBS associated with the sidelink communication based at least in part on a size of the TBS associated with the sidelink communication.

[0170] In an eleventh aspect, alone or in combination with one or more of the first to tenth aspects, the BSR further indicates whether the TBS is associated with a modulation and coding scheme.

[0171] In a twelfth aspect, alone or in combination with one or more of the first to eleventh aspects, the BSR further indicates whether the TBS is a fixed size.

[0172] In a thirteenth aspect, either alone or in combination with one or more of the first to twelfth aspects, the resource allocation associated with the side link communication comprises a plurality of resource elements, and the number of resource elements is less than a resource element threshold.

[0173] In a fourteenth aspect, either alone or in combination with one or more of the first to thirteenth aspects, the resource allocation is not used for the sidelink communication based at least in part on the number of resource elements being less than the resource element threshold.

[0174] In a fifteenth aspect, either alone or in combination with one or more of aspects one to fourteen, process 1100 includes receiving, from the UE, an indication that the resource allocation is not to be used for the sidelink communication based at least in part on the number of resource elements being less than the resource element threshold.

[0175] In a sixteenth aspect, either alone or in combination with one or more of aspects one to fifteen, process 1100 includes receiving, from the UE, another BSR associated with a portion of the sidelink communication based at least in part on the number of resource elements being less than the resource element threshold.

[0176] In a seventeenth aspect, either alone or in combination with one or more of the first to sixteenth aspects, the resource allocation associated with the side link communication comprises a plurality of resource elements, and the number of resource elements is greater than a resource element threshold.

[0177] although Fig.11 An example block diagram of process 1100 is shown, but in some aspects, process 1100 may include Fig.11 Additional blocks, fewer blocks, different blocks, or blocks arranged in a different manner than those depicted in the process 1100. Additionally or alternatively, two or more blocks of the blocks of process 1100 may be performed in parallel.

[0178] Fig.121 is a diagram of an example apparatus 1200 for wireless communication according to the present disclosure. Apparatus 1200 may be a UE (e.g., UE 120), or a UE may include apparatus 1200. In some aspects, apparatus 1200 includes a receiving component 1202 and a transmitting component 1204 that may communicate with each other (e.g., via one or more buses and / or one or more other components). As shown, apparatus 1200 may communicate with another apparatus 1206 (such as a UE, a base station, or another wireless communication device) using receiving component 1202 and transmitting component 1204. As further shown, apparatus 1200 may include a communication manager 1208 (e.g., communication manager 140). Communication manager 1208 may include sidelink component 1210, among other things.

[0179] In some aspects, the apparatus 1200 may be configured to perform Figures 8 to 9 Additionally or alternatively, the apparatus 1200 may be configured to perform one or more of the processes described herein, such as Fig.10 The process 1000. In some aspects, Fig.12 The device 1200 and / or one or more components shown may include a combination of Figure 2 One or more components of the described UE 120. Additionally or alternatively, Fig.12 One or more of the components shown may be combined with Figure 2 Additionally or alternatively, one or more components in the set of components may be implemented at least in part as software stored in a memory. For example, a component (or a portion of a component) may be implemented as instructions or codes that are stored in a non-transitory computer-readable medium and can be executed by a controller or processor to perform the function or operation of the component.

[0180] The receiving component 1202 may receive communications, such as reference signals, control information, data communications, or combinations thereof, from the device 1206. The receiving component 1202 may provide the received communications to one or more other components of the device 1200. In some aspects, the receiving component 1202 may perform signal processing (such as filtering, amplification, demodulation, analog-to-digital conversion, demultiplexing, deinterleaving, demapping, equalization, interference cancellation, or decoding, etc.) on the received communications and may provide the processed signals to one or more other components of the device 1200. In some aspects, the receiving component 1202 may include combining Figure 2 The UE 120 is described as having one or more antennas, modems, demodulators, MIMO detectors, receive processors, controllers / processors, memories, or combinations thereof.

[0181] The transmitting component 1204 may transmit communications, such as reference signals, control information, data communications, or combinations thereof, to the device 1206. In some aspects, one or more other components of the device 1200 may generate communications and may provide the generated communications to the transmitting component 1204 for transmission to the device 1206. In some aspects, the transmitting component 1204 may perform signal processing (such as filtering, amplification, modulation, digital-to-analog conversion, multiplexing, interleaving, mapping, or encoding, etc.) on the generated communications and may transmit the processed signals to the device 1206. In some aspects, the transmitting component 1204 may include combining Figure 2 One or more antennas, modems, modulators, transmit MIMO processors, transmit processors, controllers / processors, memories, or combinations thereof, of the depicted UE 120. In some aspects, the transmit component 1204 can be co-located with the receive component 1202 in a transceiver.

[0182] Receiving component 1202 can receive a resource allocation associated with a sidelink communication from a network entity. Sidelink component 1210 can initiate a PSSCH preparation procedure associated with the sidelink communication prior to receiving the resource allocation associated with the sidelink communication.

[0183] Transmitting component 1204 may transmit a BSR associated with the sidelink communication to the network entity, wherein the BSR indicates a TBS associated with the sidelink communication, and wherein the resource allocation associated with the sidelink communication is based at least in part on the TBS.

[0184] The sidelink component 1210 can initiate the PSSCH preparation procedure associated with the sidelink communication before sending the BSR associated with the sidelink communication.

[0185] Transmitting component 1204 and / or sidelink component 1210 can transmit another sidelink communication to another UE using the resource allocation for the sidelink communication.

[0186] Transmitting component 1204 can transmit, based at least in part on the number of resource elements being less than a resource element threshold, an indication to the network entity that the resource allocation is not to be used for the sidelink communication.

[0187] Transmitting component 1204 and / or sidelink component 1210 may transmit, based at least in part on the number of resource elements being less than the resource element threshold, an indication to another UE that only a portion of the sidelink communication will be transmitted using the resource allocation for the sidelink communication.

[0188] Transmitting component 1204 and / or sidelink component 1210 may transmit a first portion of the sidelink communication to the other UE using the resource allocation for the sidelink communication and transmit a second portion of the sidelink communication to the other UE using the resource allocation associated with the retransmission communication.

[0189] Transmitting component 1204 can transmit, to the network entity, a buffer status report associated with another portion of the sidelink communication based at least in part on the number of resource elements being less than the resource element threshold.

[0190] The sidelink component 1210 may append at least one of filler bits, a sidelink channel state information reference signal, or a demodulation reference signal to the sidelink communication based at least in part on the number of resource elements being greater than the resource element threshold.

[0191] The side link component 1210 can repeat bits in a circular buffer associated with the side link communication based at least in part on the number of resource elements being greater than the resource element threshold.

[0192] Side link component 1210 can select a modulation order associated with the side link communication based at least in part on the number of resource elements being greater than the resource element threshold.

[0193] Transmitting component 1204 and / or sidelink component 1210 may transmit the sidelink communication to another UE using a portion of the resource allocation associated with the sidelink communication based at least in part on the number of resource elements being greater than the resource element threshold.

[0194] Fig.12 The number and arrangement of components shown are provided as examples. In practice, there may be Fig.12 The components shown may include additional components, fewer components, different components, or components arranged in a different manner. Fig.12 Two or more components shown may be implemented in a single component, or Fig.12 The single component shown may be implemented as multiple distributed components. Additionally or alternatively, Fig.12 The illustrated set of component(s) may be described as being executable by Fig.12 Another collection of components shown performs one or more functions.

[0195] Fig.131 is a diagram of an example apparatus 1300 for wireless communication according to the present disclosure. Apparatus 1300 may be a network entity (e.g., network entity 110), or a network entity may include apparatus 1300. In some aspects, apparatus 1300 includes a receiving component 1302 and a transmitting component 1304 that may communicate with each other (e.g., via one or more buses and / or one or more other components). As shown, apparatus 1300 may communicate with another apparatus 1306 (such as a UE, a base station, or another wireless communication device) using receiving component 1302 and transmitting component 1304. As further shown, apparatus 1300 may include a communication manager 1308 (e.g., communication manager 150). Communication manager 1308 may include a scheduling component 1310, among other things.

[0196] In some aspects, the apparatus 1300 may be configured to perform Figures 8 to 9 Additionally or alternatively, the apparatus 1300 may be configured to perform one or more processes described herein, such as Fig.11 The process 1100. In some aspects, Fig.13 The device 1300 and / or one or more components shown may include a combination of Figure 2 One or more components of the described network entity 110. Additionally or alternatively, Fig.13 One or more of the components shown may be combined with Figure 2 Additionally or alternatively, one or more components in the set of components may be implemented at least in part as software stored in a memory. For example, a component (or a portion of a component) may be implemented as instructions or codes that are stored in a non-transitory computer-readable medium and can be executed by a controller or processor to perform the function or operation of the component.

[0197] The receiving component 1302 may receive communications, such as reference signals, control information, data communications, or combinations thereof, from the device 1306. The receiving component 1302 may provide the received communications to one or more other components of the device 1300. In some aspects, the receiving component 1302 may perform signal processing (such as filtering, amplification, demodulation, analog-to-digital conversion, demultiplexing, deinterleaving, demapping, equalization, interference cancellation, or decoding, etc.) on the received communications and may provide the processed signals to one or more other components of the device 1300. In some aspects, the receiving component 1302 may include combining Figure 2 The depicted network entity 110 may include one or more antennas, modems, demodulators, MIMO detectors, receive processors, controllers / processors, memories, or combinations thereof.

[0198] Transmit component 1304 may transmit communications, such as reference signals, control information, data communications, or combinations thereof, to device 1306. In some aspects, one or more other components of device 1300 may generate communications and may provide the generated communications to transmit component 1304 for transmission to device 1306. In some aspects, transmit component 1304 may perform signal processing (such as filtering, amplification, modulation, digital-to-analog conversion, multiplexing, interleaving, mapping, or encoding, etc.) on the generated communications and may transmit the processed signals to device 1306. In some aspects, transmit component 1304 may include combining Figure 2 One or more antennas, modems, modulators, transmit MIMO processors, transmit processors, controllers / processors, memories, or combinations thereof, of the depicted network entity 110. In some aspects, the transmit component 1304 can be co-located with the receive component 1302 in a transceiver.

[0199] The receiving component 1302 can receive a BSR associated with the sidelink communication from a UE (e.g., UE 120), wherein the BSR indicates a TBS associated with the sidelink communication. The sending component 1304 and / or the scheduling component 1310 can send a resource allocation associated with the sidelink communication to the UE based at least in part on the TBS.

[0200] Receiving component 1302 can receive, from the UE, an indication that the resource allocation is not to be used for the sidelink communication based at least in part on the number of resource elements being less than a resource element threshold.

[0201] Receiving component 1302 can receive, from the UE, another BSR associated with a portion of the sidelink communications based at least in part on the number of resource elements being less than the resource element threshold.

[0202] Fig.13 The number and arrangement of components shown are provided as examples. In practice, there may be Fig.13 The components shown may include additional components, fewer components, different components, or components arranged in a different manner. Fig.13 Two or more components shown may be implemented in a single component, or Fig.13 The single component shown may be implemented as multiple distributed components. Additionally or alternatively, Fig.13 The illustrated set of component(s) may be described as being executable by Fig.13 Another collection of components shown performs one or more functions.

[0203] The following provides an overview of some aspects of the disclosure:

[0204] Aspect 1: A method of wireless communication performed by a UE, the method comprising: receiving a resource allocation associated with a sidelink communication from a network entity; and before receiving the resource allocation associated with the sidelink communication, initiating a PSSCH preparation procedure associated with the sidelink communication.

[0205] Aspect 2: A method according to Aspect 1, wherein the sidelink communication is permitted to be sent after a time interval after receiving the resource allocation associated with the sidelink communication, and wherein the time interval is less than N2+1 symbols, wherein N2 is equal to one of 10, 12, 23 or 36, corresponding to subcarrier spacings of 15kHz, 30kHz, 60kHz and 120kHz, respectively.

[0206] Aspect 3: A method according to any one of Aspects 1 to 2, wherein before receiving the resource allocation associated with the sidelink communication, initiating the PSSCH preparation procedure associated with the sidelink communication includes at least one of the following: appending to a transmission block, selecting a low-density parity check base map, performing CB segmentation, appending a CRC to one or more CBs, or performing channel coding.

[0207] Aspect 4: According to the method described in any one of Aspects 1 to 3, the method further includes: sending a BSR associated with the sidelink communication to the network entity, wherein the BSR indicates a TBS associated with the sidelink communication, and wherein the resource allocation associated with the sidelink communication is at least partially based on the TBS.

[0208] Aspect 5: The method according to aspect 4 further comprises: before sending the BSR associated with the sidelink communication, initiating the PSSCH preparation procedure associated with the sidelink communication.

[0209] Aspect 6: The method according to any one of aspects 4 to 5, wherein the BSR further indicates a selected base map for low density parity check coding.

[0210] Aspect 7: The method according to any one of aspects 4 to 6, wherein the TBS associated with the sidelink communication is based at least in part on a selected modulation and coding scheme associated with the sidelink communication.

[0211] Aspect 8: The method according to any one of aspects 4 to 7, wherein the resource allocation is based at least in part on a determined number of resource elements associated with a quadrature phase shift keying modulation.

[0212] Aspect 9: A method according to any one of Aspects 4 to 8, wherein the sidelink communication is associated with a selected modulation other than orthogonal phase shift keying modulation, and wherein the BSR also indicates a transport block scaling factor associated with the selected modulation.

[0213] Aspect 10: The method according to any one of aspects 4 to 9, wherein the BSR further indicates at least one of an MCS associated with the sidelink communication or a CQI associated with the sidelink communication.

[0214] Aspect 11: The method of aspect 10, wherein the resource allocation is based at least in part on at least one of the MCS associated with the sidelink communication or the CQI associated with the sidelink communication.

[0215] Aspect 12: The method according to any one of aspects 4 to 11, wherein the BSR further indicates a plurality of candidate modulation and coding schemes associated with the sidelink communication.

[0216] Aspect 13: A method according to any one of aspects 4 to 12, wherein the BSR indicates the TBS associated with the sidelink communication based at least in part on the sidelink communication being associated with a priority value exceeding a threshold priority value.

[0217] Aspect 14: A method according to any one of aspects 4 to 13, wherein the BSR indicates the TBS associated with the sidelink communication based at least in part on the size of the TBS associated with the sidelink communication.

[0218] Aspect 15: The method according to any one of aspects 4 to 14, wherein the BSR further indicates whether the TBS is associated with a modulation and coding scheme.

[0219] Aspect 16: The method according to any one of aspects 4 to 15, wherein the BSR further indicates whether the TBS is of a fixed size.

[0220] Aspect 17: A method according to any one of Aspects 1 to 16, wherein the resource allocation associated with the sidelink communication includes a plurality of resource elements, and wherein the number of resource elements is less than a resource element threshold.

[0221] Aspect 18: The method of aspect 17, wherein the resource allocation is not used for the sidelink communication based at least in part on the number of resource elements being less than the resource element threshold.

[0222] Aspect 19: The method according to aspect 18, the method further comprising: sending another sidelink communication to another UE using the resource allocation for the sidelink communication.

[0223] Aspect 20: According to the method described in any one of Aspects 18 to 19, the method further includes: sending an indication to the network entity that the resource allocation is not used for the sidelink communication, at least in part based on the number of resource elements being less than the resource element threshold.

[0224] Aspect 21: According to the method according to Aspect 17, the method also includes: at least in part based on the number of resource elements being less than the resource element threshold, sending an indication to another UE that only a portion of the sidelink communication will be sent using the resource allocation for the sidelink communication.

[0225] Aspect 22: According to the method according to Aspect 21, the method also includes: using the resource allocation for the sidelink communication to send a first part of the sidelink communication to the other UE, and using the resource allocation associated with the retransmission communication to send a second part of the sidelink communication to the other UE.

[0226] Aspect 23: According to the method described in any one of Aspects 21 to 22, the method also includes: sending a buffer status report associated with another part of the side link communication to the network entity, at least in part based on the number of resource elements being less than the resource element threshold.

[0227] Aspect 24: A method according to any one of aspects 1 to 16, wherein the resource allocation associated with the sidelink communication includes a plurality of resource elements, and wherein the number of resource elements is greater than a resource element threshold.

[0228] Aspect 25: According to the method described in Aspect 24, the method also includes: adding at least one of fill bits, sidelink channel state information reference signals or demodulation reference signals to the sidelink communication at least in part based on the number of resource elements being greater than the resource element threshold.

[0229] Aspect 26: The method according to any one of Aspects 24 to 25, further comprising: repeating bits in a circular buffer associated with the sidelink communication based at least in part on the number of resource elements being greater than the resource element threshold.

[0230] Aspect 27: The method according to any one of Aspects 24 to 26, further comprising: selecting a modulation order associated with the sidelink communication based at least in part on the number of resource elements being greater than the resource element threshold.

[0231] Aspect 28: According to any one of Aspects 24 to 27, the method also includes: at least in part based on the number of resource elements being greater than the resource element threshold, using a portion of the resource allocation associated with the sidelink communication to send the sidelink communication to another UE.

[0232] Aspect 29: A method of wireless communication performed by a network entity, the method comprising: receiving a BSR associated with a sidelink communication from a UE, wherein the BSR indicates a TBS associated with the sidelink communication; and sending a resource allocation associated with the sidelink communication to the UE based at least in part on the TBS.

[0233] Aspect 30: A method according to Aspect 29, wherein the sidelink communication is permitted to be sent after a time interval after receiving the resource allocation associated with the sidelink communication, and wherein the time interval is less than N2+1 symbols, wherein N2 is equal to one of 10, 12, 23 or 36, corresponding to subcarrier spacings of 15kHz, 30kHz, 60kHz and 120kHz, respectively.

[0234] Aspect 31: The method according to any one of aspects 29 to 30, wherein the BSR further indicates a selected base map for low density parity check coding.

[0235] Aspect 32: A method according to any one of aspects 29 to 31, wherein the TBS associated with the sidelink communication is based at least in part on a selected modulation and coding scheme associated with the sidelink communication.

[0236] Aspect 33: The method according to any one of aspects 29 to 32, wherein the resource allocation is based at least in part on a determined number of resource elements associated with a quadrature phase shift keying modulation.

[0237] Aspect 34: A method according to any one of Aspects 29 to 33, wherein the sidelink communication is associated with a selected modulation other than orthogonal phase shift keying modulation, and wherein the BSR also indicates a transport block scaling factor associated with the selected modulation.

[0238] Aspect 35: The method according to any one of aspects 29 to 34, wherein the BSR further indicates at least one of an MCS associated with the sidelink communication or a CQI associated with the sidelink communication.

[0239] Aspect 36: The method according to aspect 35, wherein the resource allocation is based at least in part on at least one of the MCS associated with the sidelink communication or the CQI associated with the sidelink communication.

[0240] Aspect 37: A method according to any one of Aspects 29 to 36, wherein the BSR further indicates a plurality of candidate modulation and coding schemes associated with the sidelink communication.

[0241] Aspect 38: A method according to any one of Aspects 29 to 37, wherein the BSR indicates the TBS associated with the sidelink communication based at least in part on the sidelink communication being associated with a priority value exceeding a threshold priority value.

[0242] Aspect 39: A method according to any one of Aspects 29 to 38, wherein the BSR indicates the TBS associated with the sidelink communication based at least in part on the size of the TBS associated with the sidelink communication.

[0243] Aspect 40: The method according to any one of aspects 29 to 39, wherein the BSR further indicates whether the TBS is associated with a modulation and coding scheme.

[0244] Aspect 41: The method according to any one of Aspects 29 to 40, wherein the BSR further indicates whether the TBS is of a fixed size.

[0245] Aspect 42: A method according to any one of Aspects 29 to 41, wherein the resource allocation associated with the sidelink communication comprises a plurality of resource elements, and wherein the number of resource elements is less than a resource element threshold.

[0246] Aspect 43: The method according to aspect 42, wherein the resource allocation is not used for the sidelink communication based at least in part on the number of resource elements being less than the resource element threshold.

[0247] Aspect 44: The method according to aspect 43 further includes: receiving an indication from the UE that the resource allocation is not used for the sidelink communication based at least in part on the number of resource elements being less than the resource element threshold.

[0248] Aspect 45: According to any one of Aspects 43 to 44, the method also includes: receiving another BSR associated with a portion of the sidelink communication from the UE at least in part based on the number of resource elements being less than the resource element threshold.

[0249] Aspect 46: A method according to any one of Aspects 29 to 41, wherein the resource allocation associated with the sidelink communication comprises a plurality of resource elements, and wherein the number of resource elements is greater than a resource element threshold.

[0250] Aspect 47: An apparatus for performing wireless communications at a device, 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 one or more of the methods described in Aspects 1 to 28.

[0251] Aspect 48: A device for wireless communication, the device comprising: a memory; and one or more processors, the one or more processors coupled to the memory, the one or more processors configured to execute the method according to one or more of aspects 1 to 28.

[0252] Aspect 49: An apparatus for wireless communication, the apparatus comprising at least one component for performing the method according to one or more of aspects 1 to 28.

[0253] Aspect 50: A non-transitory computer-readable medium storing code for wireless communication, the code comprising instructions executable by a processor to perform the method according to one or more of aspects 1 to 28.

[0254] Aspect 51: A non-transitory computer-readable medium storing an instruction set for wireless communication, the instruction set comprising one or more instructions which, when executed by one or more processors of a device, cause the device to perform one or more of the methods described in aspects 1 to 28.

[0255] Aspect 52: An apparatus for performing wireless communications at a device, 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 one or more of the methods described in Aspects 29 to 46.

[0256] Aspect 53: A device for wireless communication, the device comprising: a memory; and one or more processors, the one or more processors coupled to the memory, the one or more processors configured to execute the method according to one or more of aspects 29 to 46.

[0257] Aspect 54: An apparatus for wireless communication, the apparatus comprising at least one component for performing the method according to one or more of aspects 29 to 46.

[0258] Aspect 55: A non-transitory computer-readable medium storing code for wireless communication, the code comprising instructions executable by a processor to perform the method according to one or more of aspects 29 to 46.

[0259] Aspect 56: A non-transitory computer-readable medium storing an instruction set for wireless communication, the instruction set comprising one or more instructions which, when executed by one or more processors of a device, cause the device to perform one or more of the methods described in aspects 29 to 46.

[0260] While the foregoing disclosure provides illustration and description, it is not intended to be exhaustive or to limit the aspects to the precise forms disclosed. Modifications and variations are possible in light of the above disclosure or may be acquired from practice of these aspects.

[0261] As used herein, the term "component" is intended to be broadly interpreted as a combination of hardware and / or hardware and software. Whether referred to as software, firmware, middleware, microcode, hardware description language or other names, "software" should be broadly interpreted as meaning instructions, instruction sets, codes, code segments, program codes, programs, subroutines, software modules, applications, software applications, software packages, routines, subroutines, objects, executable files, threads implemented, procedures and / or functions, etc. As used herein, a "processor" is implemented in a combination of hardware and / or hardware and software. It will be clear that the systems and / or methods described herein can be implemented by different forms of hardware and / or a combination of hardware and software. The actual dedicated control hardware or software code used to implement these systems and / or methods does not limit various aspects. Therefore, the operation and behavior of the system and / or method are not described herein with reference to specific software codes, because those skilled in the art will understand that software and hardware can be designed to implement the system and / or method based at least in part on the description herein.

[0262] As used herein, "satisfying a threshold" may refer to a value being greater than a threshold, greater than or equal to a threshold, less than a threshold, less than or equal to a threshold, equal to a threshold, not equal to a threshold, etc., depending on the context.

[0263] Although specific combinations of features are set forth in the claims and / or disclosed in the specification, these combinations are not intended to limit the disclosure of various aspects. Many of these features can be combined in a manner that is not specifically described in the claims and / or is not disclosed in the specification. The disclosure of various aspects includes each dependent claim combined with each other claim in the claim set. As used herein, the phrase "at least one of" the list of items refers to any combination of these items (which includes a single member). As an example, "at least one of a, b or c" is intended to cover a, b, c, a+b, a+c, b+c and a+b+c, and any combination with multiple identical elements (e.g., a+a, a+a+a, a+a+b, a+a+c, a+b+b, a+c+c, b+b, b+b+b, b+b+c, c+c and c+c+c, or any other ordering of a, b and c).

[0264] Any element, action or instruction used herein should not be interpreted as key or necessary, unless clearly stated so. In addition, as used herein, the articles "one" and "a kind of" are intended to include one or more items, and can be used interchangeably with "one or more". In addition, as used herein, the article "said" is intended to include one or more items connected with the article "said", and can be used interchangeably with "one or more". In addition, as used herein, the terms "set" and "group" are intended to include one or more items, and can be used interchangeably with "one or more". If only one item is intended to be referred to, the phrase "only one" or similar terms are used. Moreover, as used herein, the terms "have", "have" etc. are intended to be open terms, which do not limit the elements they modify (for example, "elements with" A can also have B). In addition, the phrase "based on" is intended to represent "based at least in part on", unless otherwise explicitly stated. Furthermore, as used herein, the term "or" when used in a series is intended to be open-ended and used interchangeably with "and / or" unless expressly stated otherwise (eg, if used in conjunction with "either" or "only one of").

Claims

1. An apparatus for wireless communication at a user equipment (UE), the apparatus comprising: Memory; and one or more processors coupled to the memory and configured to: receiving a resource allocation associated with a sidelink communication from a network entity; as well as Prior to receiving the resource allocation associated with the sidelink communication, a physical sidelink shared channel (PSSCH) preparation procedure associated with the sidelink communication is initiated.

2. An apparatus according to claim 1, wherein the sidelink communication is permitted to be sent after a time interval after receiving the resource allocation associated with the sidelink communication, and wherein the time interval is less than N2+1 symbols, where N2 is equal to one of 10, 12, 23 or 36, corresponding to subcarrier spacings of 15kHz, 30kHz, 60kHz and 120kHz, respectively.

3. An apparatus according to claim 1, wherein in order to initiate the PSSCH preparation procedure associated with the sidelink communication before receiving the resource allocation associated with the sidelink communication, the one or more processors are configured to attach a cyclic redundancy check (CRC) to a transport block, select a low-density parity-check base map, perform code block (CB) segmentation, attach a CRC to one or more CBs, or perform channel coding.

4. The apparatus of claim 1 , wherein the one or more processors are further configured to: send a buffer status report (BSR) associated with the sidelink communication to the network entity, wherein the BSR indicates a transport block size (TBS) associated with the sidelink communication, and wherein the resource allocation associated with the sidelink communication is based at least in part on the TBS.

5. The apparatus of claim 4, wherein the one or more processors are further configured to initiate the PSSCH preparation procedure associated with the sidelink communication before sending the BSR associated with the sidelink communication.

6. The apparatus of claim 4, wherein the TBS associated with the sidelink communication is based at least in part on a selected modulation and coding scheme associated with the sidelink communication.

7. The apparatus of claim 4, wherein the resource allocation is based at least in part on a determined number of resource elements associated with a quadrature phase shift keying modulation.

8. The apparatus of claim 4, wherein the sidelink communication is associated with a selected modulation other than quadrature phase shift keying modulation, and wherein the BSR further indicates a transport block scaling factor associated with the selected modulation.

9. The apparatus of claim 4, wherein the BSR further indicates whether the TBS is associated with a modulation and coding scheme.

10. The apparatus of claim 4, wherein the BSR further indicates whether the TBS is of a fixed size.

11. The apparatus of claim 1 , wherein the resource allocation associated with the sidelink communication comprises a plurality of resource elements, and wherein the number of resource elements is less than a resource element threshold.

12. The apparatus of claim 11, wherein the resource allocation is not used for the sidelink communication based at least in part on the number of resource elements being less than the resource element threshold.

13. The apparatus of claim 12, wherein the one or more processors are further configured to send another sidelink communication to another UE using the resource allocation for the sidelink communication.

14. The apparatus of claim 11, wherein the one or more processors are further configured to, based at least in part on the number of resource elements being less than the resource element threshold, send an indication to another UE that only a portion of the sidelink communication will be sent using the resource allocation for the sidelink communication.

15. The apparatus of claim 14, wherein the one or more processors are further configured to: send a first portion of the sidelink communication to the other UE using the resource allocation for the sidelink communication, and send a second portion of the sidelink communication to the other UE using a resource allocation associated with a retransmission communication.

16. An apparatus according to claim 14, wherein the one or more processors are further configured to: send a buffer status report associated with another portion of the sidelink communication to the network entity based at least in part on the number of resource elements being less than the resource element threshold.

17. The apparatus of claim 1, wherein the resource allocation associated with the sidelink communication comprises a plurality of resource elements, and wherein the number of resource elements is greater than a resource element threshold.

18. An apparatus according to claim 17, wherein the one or more processors are further configured to: append at least one of fill bits, sidelink channel state information reference signal, or demodulation reference signal to the sidelink communication based at least in part on the number of resource elements being greater than the resource element threshold.

19. The apparatus of claim 17, wherein the one or more processors are further configured to repeat bits in a circular buffer associated with the sidelink communication based at least in part on the number of resource elements being greater than the resource element threshold.

20. The apparatus of claim 17, wherein the one or more processors are further configured to select a modulation order associated with the sidelink communication based at least in part on the number of resource elements being greater than the resource element threshold.

21. The apparatus of claim 17, wherein the one or more processors are further configured to send the sidelink communication to another UE using a portion of the resource allocation associated with the sidelink communication based at least in part on the number of resource elements being greater than the resource element threshold.

22. An apparatus for wireless communication at a network entity, the apparatus comprising: Memory; and one or more processors coupled to the memory and configured to: receiving a buffer status report (BSR) associated with a sidelink communication from a user equipment (UE), wherein the BSR indicates a transport block size (TBS) associated with the sidelink communication; and A resource allocation associated with sidelink communications is sent to the UE based at least in part on the TBS.

23. An apparatus according to claim 22, wherein the sidelink communication is permitted to be sent after a time interval after receiving the resource allocation associated with the sidelink communication, and wherein the time interval is less than N2+1 symbols, where N2 is equal to one of 10, 12, 23 or 36, corresponding to subcarrier spacings of 15kHz, 30kHz, 60kHz and 120kHz, respectively.

24. The apparatus of claim 22, wherein the TBS associated with the sidelink communication is based at least in part on a selected modulation and coding scheme associated with the sidelink communication.

25. The apparatus of claim 22, wherein the BSR further indicates whether the TBS is a fixed size.

26. A method of wireless communication performed by a user equipment (UE), the method comprising: receiving a resource allocation associated with a sidelink communication from a network entity; as well as Prior to receiving the resource allocation associated with the sidelink communication, a physical sidelink shared channel (PSSCH) preparation procedure associated with the sidelink communication is initiated.

27. A method according to claim 26, wherein the sidelink communication is permitted to be sent after a time interval after receiving the resource allocation associated with the sidelink communication, and wherein the time interval is less than N2+1 symbols, where N2 is equal to one of 10, 12, 23 or 36, corresponding to subcarrier spacings of 15kHz, 30kHz, 60kHz and 120kHz, respectively.

28. The method according to claim 26, further comprising: A buffer status report (BSR) associated with the sidelink communication is sent to the network entity, wherein the BSR indicates a transport block size (TBS) associated with the sidelink communication, and wherein the resource allocation associated with the sidelink communication is based at least in part on the TBS.

29. A method of wireless communication performed by a network entity, the method comprising: receiving a buffer status report (BSR) associated with a sidelink communication from a user equipment (UE), wherein the BSR indicates a transport block size (TBS) associated with the sidelink communication; and A resource allocation associated with sidelink communications is sent to the UE based at least in part on the TBS.

30. A method according to claim 29, wherein the sidelink communication is permitted to be sent after a time interval after receiving the resource allocation associated with the sidelink communication, and wherein the time interval is less than N2+1 symbols, where N2 is equal to one of 10, 12, 23 or 36, corresponding to subcarrier spacings of 15kHz, 30kHz, 60kHz and 120kHz, respectively.

Images