Supporting low latency transmissions in sidelinks

Abstract

Methods, systems, and devices for wireless communication are described. Sidelink communications between user equipments (UEs) may include services requiring low latency and high reliability, such as augmented reality (XR) and ultra-reliable low latency communications (URLLC). Given the latency requirements for the XR and URLLC, the XR and URLLC may have a higher priority than other communication types. The UE may determine that data for transmission on the sidelink has a high priority level based on a remaining packet delay budget associated with the data. The UE may monitor sidelink transmissions according to a discontinuous reception (DRX) cycle of a network configuration. However, DRX cycles configured by a network for sidelink communications may not match the periodicity of XR traffic. For XR communications, a transmitting UE may indicate an offset to apply to a DRX cycle such that a receiving UE may adjust the DRX cycle to match the periodicity of XR communications.

Description

[0001] CROSS-REFERENCE TO RELATED APPLICATIONS

[0002] This application claims the benefit of U.S. patent application No. 17 / 952,035, entitled “SUPPORT OF LOWLATENCY TRANSMISSIONS IN SIDELINK,” filed by Elshafie et al. on September 23, 2022, which is assigned to the assignee of this application and is expressly incorporated herein by reference. Technical Field

[0003] The following relates to wireless communications, including supporting low latency transmission in a sidelink. Background Art

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

[0005] The described technology relates to improved methods, systems, devices and apparatuses for supporting low-latency transmission in a side link. For example, the described technology provides management of a resource pool for low-latency communication via a side link. Side link communication between user equipment (UE) may include services requiring low latency and high reliability, such as extended reality (XR) and ultra-reliable low-latency communication (URLLC). In side link communication, the user equipment (UE) may be configured with a resource pool for side link communication by a higher layer. Given the latency requirements for XR and URLLC, XR and URLLC may have a higher priority than other communication types. The UE may determine that the data for transmission on the side link has a high priority level based on the remaining packet delay budget associated with the data. The UE may indicate that the data has a high priority level in a side link control information (SCI) message of a resource pool reserved for transmitting data. The high priority level indicated in the SCI may preempt other reservations of the resource pool. In some examples, it may be indicated to the UE that some resource pools or sub-resource pools are reserved for low-latency services, such as XR or URLLC, and the UE may select a resource pool based on an indication from a network entity.

[0006] Additionally, the UE may monitor the sidelink transmission according to a discontinuous reception (DRX) cycle configured by the network. However, the DRX cycle configured by the network for sidelink communication may not match the periodicity of the XR service. The mismatch between the DRX cycle and the periodicity of the XR service may result in jitter or missed reception of the XR transmission at the receiving UE. Therefore, for XR communication, the transmitting UE may indicate an offset to be applied to the DRX cycle so that the receiving UE can adjust the DRX cycle to match the periodicity of the XR communication. BRIEF DESCRIPTION OF THE DRAWINGS

[0007] Figure 1 An example of a wireless communication system supporting low-latency transmission in a side link according to one or more aspects of the present disclosure is illustrated.

[0008] Figure 2 An example of a timing diagram supporting low-latency transmission in a sidelink according to one or more aspects of the present disclosure is illustrated.

[0009] Figure 3 An example of a resource pool supporting low-latency transmission in a side link according to one or more aspects of the present disclosure is illustrated.

[0010] Figure 4 An example of a slot format supporting low-latency transmission in a sidelink according to one or more aspects of the present disclosure is illustrated.

[0011] Figure 5 An example of a slot format supporting low-latency transmission in a sidelink according to one or more aspects of the present disclosure is illustrated.

[0012] Figure 6 An example of a slot format supporting low-latency transmission in a sidelink according to one or more aspects of the present disclosure is illustrated.

[0013] Figure 7 An example of a wireless communication system supporting low-latency transmission in a side link according to one or more aspects of the present disclosure is illustrated.

[0014] Figure 8 An example of a process flow to support low-latency transmission in a sidelink according to one or more aspects of the present disclosure is illustrated.

[0015] Fig. 9 and Fig.10 A block diagram of a device supporting low-latency transmission in a side link according to one or more aspects of the present disclosure is shown.

[0016] Fig.11 A block diagram of a communication manager supporting low latency transmission in a sidelink is shown in accordance with one or more aspects of the present disclosure.

[0017] Fig.12 A diagram of a system including a device supporting low-latency transmission in a sidelink according to one or more aspects of the present disclosure is shown.

[0018] Figures 13 to 16 A flow chart illustrating a method of supporting low-latency transmission in a sidelink according to one or more aspects of the present disclosure is shown. DETAILED DESCRIPTION

[0019] Some wireless communication systems support sidelink communication between user equipment (UE). Sidelink communication may include services requiring low latency and high reliability, such as extended reality (XR) and ultra-reliable low latency communication (URLLC). In sidelink communication, the UE may be configured with a resource pool for sidelink communication by a higher layer. In sidelink mode 1, the network entity schedules resources (e.g., resource pools) for sidelink transmission. In sidelink mode 2, the UE autonomously selects sidelink resources from the configured resource pool based on reference signal received power (RSRP) measurements for different resource pools. Given the latency requirements for XR and URLLC, XR and URLLC may have higher priority than other communication types. Additionally, the UE may monitor sidelink transmissions according to the discontinuous reception (DRX) cycle configured by the network. However, the DRX cycle configured by the network may not match the periodicity of the XR service. For example, an XR service may have a period of 60 frames per second, which is equal to a non-integer 16.67ms period. A mismatch between the DRX cycle and the periodicity of the XR traffic may result in jitter or missed reception of XR transmissions at the receiving UE.

[0020] The UE may determine that the data for transmission on the side link has a high priority level based on the remaining packet delay budget associated with the data. The UE may indicate that the data has a high priority level in a side link control information (SCI) message of a resource pool reserved for transmitting data. The high priority level indicated in the SCI may preempt other reservations of the resource pool. In some examples, it may be indicated to the UE that some resource pools or sub-resource pools are reserved for low-latency services, such as XR or URLLC, and the UE may select a resource pool based on an indication from a network entity. For XR communications, the UE may indicate an offset to be applied to the DRX cycle so that the receiving UE may adjust the DRX cycle to match the periodicity of the XR communications. For mode 2 communications, different RSRP thresholds may be configured for selecting resource pools for XR and URLLC to take into account the higher reliability and latency requirements associated with XR and URLLC.

[0021] Aspects of the present disclosure are first described in the context of a wireless communication system. Aspects of the present disclosure are further illustrated by and described with reference to timing diagrams, resource pools, time slot formats, and process flows. Aspects of the present disclosure are further illustrated by and described with reference to apparatus diagrams, system diagrams, and flow diagrams related to supporting low-latency transmission in a sidelink.

[0022] Figure 1 An example of a wireless communication system 100 supporting low latency transmission in a side link according to one or more aspects of the present disclosure is illustrated. The wireless communication system 100 may include one or more network entities 105, one or more UEs 115, and a core network 130. In some examples, the wireless communication system 100 may be a Long Term Evolution (LTE) network, an Advanced LTE (LTE-A) network, an LTE-A Pro network, a New Radio (NR) network, or a network operating according to other systems and radio technologies, including future systems and radio technologies not explicitly mentioned herein.

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

[0024] The UEs 115 may be dispersed throughout the coverage area 110 of the wireless communication system 100, and each UE 115 may be stationary or mobile, or stationary and mobile at different times. The UEs 115 may be devices in different forms or with different capabilities. Figure 1 Some example UEs 115 are illustrated in FIG. 1. The UEs 115 described herein may be capable of supporting communication with various types of devices, such as Figure 1 Communicate with other UEs 115 or network entities 105) as shown.

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

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

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

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

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

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

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

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

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

[0034] In the case where the techniques described herein are applied to the context of a decomposed RAN architecture, one or more components of the decomposed RAN architecture may be configured to support low latency transmission in the side link as described herein. For example, some operations described as being performed by UE 115 or network entity 105 (e.g., base station 140) may additionally or alternatively be performed by one or more components of the decomposed RAN architecture (e.g., IAB node 104, DU 165, CU 160, RU 170, RIC 175, SMO 180).

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

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

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

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

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

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

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

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

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

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

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

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

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

[0048] A macro cell generally covers a relatively large geographic area (e.g., several kilometers in radius) and may allow unrestricted access to UEs 115 that have a service subscription with a network provider that supports the macro cell. A small cell may be associated with a lower power network entity 105 (e.g., a lower power base station 140) (compared to a macro cell), and the small cell may operate using the same or different (e.g., licensed, unlicensed) frequency band as the macro cell. A small cell may provide unrestricted access to a UE 115 that has a service subscription with a network provider, or may provide restricted access to a UE 115 associated with a small cell (e.g., a UE 115 in a closed subscriber group (CSG), a UE 115 associated with a user in a home or office). A network entity 105 may support one or more cells, and may also use one or more component carriers to support communications via one or more cells.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[0069] The wireless communication system 100 may support a variety of services, such as URLLC, XR, and Industrial Internet of Things (IIOT), which may have different sets of latency and reliability requirements. For example, some applications may require stricter latency and looser reliability. Some applications may have strict reliability requirements (e.g., 1e-6 block error rate (BLER)) and looser latency. Some applications may have strict latency requirements (e.g., 1ms) and strict reliability requirements (e.g., 1e-6BLER). The wireless communication system 100 may include various features for supporting such applications, such as micro-slot scheduling, fast UE processing time, span-based physical downlink control channel (PDCCH), physical uplink shared channel (PUSCH) repetition with type B, and multiple HARQ per slot.

[0070] Sidelink communications have been extended to areas beyond V2X, such as for industrial (IIOT) and consumer use cases (e.g., smart wearable devices). Sidelink communications between UE 115 may include services that require low latency and high reliability, such as XR and URLLC. In sidelink communications, the UE may be configured with a resource pool for sidelink communications by a higher layer. In sidelink mode 1, the network entity 105 schedules resources (e.g., resource pools) for sidelink transmission. In sidelink mode 2, the UE 115 autonomously selects sidelink resources from the configured resource pool based on RSRP measurements for different resource pools. Given the latency requirements for XR and URLLC, XR and URLLC may have higher priority than other sidelink communication types. UE 115 may determine that data for transmission on the sidelink has a high priority level based on the remaining packet delay budget associated with the data. UE 115 may indicate that the data has a high priority level in an SCI message of a resource pool reserved for data transmission. The high priority level indicated in the SCI may preempt other reservations of the resource pool. In some examples, UE 115 may be indicated that some resource pools or sub-resource pools are reserved for low-latency services, such as XR or URLLC, and UE 115 may select a resource pool based on the indication from the network entity.

[0071] Additionally, UE 115 may monitor sidelink transmissions according to a DRX cycle configured by the network. However, the DRX cycle configured by the network may not match the periodicity of the XR service. For example, the XR service may have a period of 60 frames per second, which is equal to a non-integer period of 16.67ms. The mismatch between the DRX cycle and the periodicity of the XR service may cause jitter or missed reception of XR transmissions at the receiving UE 115. For XR communications, UE 115 may indicate an offset to be applied to the DRX cycle so that the receiving UE may adjust the DRX cycle to match the periodicity of the XR communication. For Mode 2 communications, different RSRP thresholds may be configured for selecting resource pools for XR and URLLC to take into account the higher reliability and latency requirements associated with XR and URLLC.

[0072] Figure 2 An example of a timing diagram 200 that supports low latency transmission in a sidelink in accordance with one or more aspects of the present disclosure is illustrated. The timing diagram 200 may be implemented by aspects of the wireless communication system 100. For example, the timing diagram 200 may be implemented by one or more UEs 115.

[0073] Figure 2A first XR service flow 205-a and a second XR service flow 205-b are shown. The XR service may include variability in the number and size of packets per XR service burst. For example, for the first XR service flow 205-a, the first XR service burst 210-a includes 3 packets, and the second XR service burst 210-b includes 2 packets. The XR service may also include non-integer receive and transmit cycles. For example, if the XR service is sent at 60 frames per second, the period for the XR service (1 / 60) is 16.67ms. For another example, if the XR service is sent at 120 frames per second, the period for the XR service (1 / 120) is 8.33ms.

[0074] The arrival time of XR traffic may vary, which may cause jitter, for example, due to XR traffic variations and differences between the DRX cycle for the sidelink (which may be integer-based) and the non-integer cycle of the XR traffic. The jitter may be approximately + / -4ms. For example, in the first XR traffic flow 205-a, jitter may occur before the start of the first XR traffic burst 210-a and after the start of the second XR traffic burst 210-b. For another example, in the second XR traffic flow 205-b, jitter may occur after the start of the XR traffic burst 210-c and before the start of the second XR traffic burst 210-d.

[0075] Multiple streams of an XR service may be configured with different transmission configurations (eg, modulation and coding scheme (MCS), FPS). An XR service may include a packet delay budget (T wait ). For example, in the uplink and sidelink, the delay T at the air interface can be decomposed into T air and T wait . T=T air +T wait . T wait is the waiting time before sending. When a service data unit (SDU) arrives in the packet data convergence protocol (PDCP) queue, UE 115 stores the arrival time (T arrival ). When the first MAC packet data unit (PDU) from the SDU is sent (at time T first ), the UE waiting time of the SDU is determined by T wait =T first -T arrival Given. air It is the time difference from the first reception (even unsuccessful) of a MAC PDU containing a MAC Control Element (MAC-CE) or a Buffer Status Report (BSR) to the successful reception of the last MAC PDU carrying data from that SDU. Therefore, T wait=Equal to the uplink or sidelink PDCP queuing delay (e.g., the delay from the arrival of a packet at the PDCP upper layer Service Access Point (SAP) until an uplink or sidelink grant is available to send the packet, which includes the delay for the UE to obtain the granted resources (e.g., from scheduling request / RACH / SCI to obtaining the first resource). Therefore, the residual packet delay budget refers to the packet delay budget minus the experienced uplink or sidelink delay.

[0076] Several power saving techniques such as connected mode DRX (C-DRX) enhancements and PDCCH monitoring enhancements can be used to adapt to XR service characteristics (e.g., periodicity, multiple flows, jitter, latency requirements, reliability requirements). Additionally or alternatively, several techniques can be used to increase the capacity of XR via more efficient resource allocation and scheduling for XR service characteristics (e.g., periodicity, multiple flows, jitter, latency requirements, reliability requirements). For example, semi-persistent scheduling and configuration grant (CG) enhancements and dynamic scheduling / grant enhancements can allow for more efficient resource allocation and scheduling for XR service characteristics.

[0077] Figure 3 An example of a resource pool 300 supporting low-latency transmission in a sidelink according to one or more aspects of the present disclosure is illustrated. The resource pool 300 may be implemented by aspects of the wireless communication system 100.

[0078] Sidelink communications may be based on slot-based operations. Each semi-static uplink slot (or, optionally, a semi-static uplink portion of a flexible slot) may be indicated for sidelink communications (e.g., rather than for uplink). Resource pool 300 illustrates a slot structure including a first slot 305-a, a second slot 305-b, and a third slot 305-c, and a first subchannel 310-a, a second subchannel 310-b, and a third subchannel 310-c. In the frequency domain, a group of consecutive resource blocks forms a subchannel, which may be the smallest transmit / receive unit.

[0079] UE 115 may be configured with one or more sidelink resource pools by a higher layer. A sidelink resource pool may be used to send a physical sidelink shared channel (PSSCH) or to receive a PSSCH and may be associated with either sidelink resource allocation mode 1 or sidelink resource allocation mode 2. In the frequency domain, a sidelink resource pool includes a certain amount of consecutive subchannels (indicated by the information element sl-NumSubchannel in a higher layer). For example, resource pool 300 includes 3 subchannels (a first subchannel 310-a, a second subchannel 310-b, and a third subchannel 310-c). A subchannel includes a plurality of consecutive physical resource blocks (PRBs) (indicated by the information element sl-SubchannelSize in a higher layer).

[0080] Figure 4 An example of a slot format 400 that supports low latency transmission in a sidelink according to one or more aspects of the present disclosure is illustrated. The slot format 400 may be implemented by aspects of the wireless communication system 100. For example, the slot format 400 may be implemented by one or more UEs 115.

[0081] The sidelink scheduling may be based on time slots. For example, a sidelink time slot 405-a or a sidelink time slot 405-b includes a physical sidelink control channel (PSCCH) symbol 415, which is accompanied by a PSSCH symbol 420 at the beginning of the time slot, followed by a PSSCH symbol 420. In the sidelink, each PSCCH schedules a PSSCH in the same time slot, and may also reserve some time slots for retransmitting the same transport block (TB) in the future. The time slot (sidelink time slot 405-a or sidelink time slot 405-b) may include an automatic gain control (AGC) symbol 410 at the beginning of the time slot and a gap symbol 425 at the end of the time slot. The automatic gain control symbol may be used to adjust the gain control at the receiving UE 115.

[0082] The sidelink time slot 405-b includes a physical sidelink feedback channel (PSFCH) symbol 430 for HARQ feedback. The sidelink HARQ feedback can be based on time slots. PSFCH resources may be available at the end of some time slots (e.g., sidelink time slot 405-b), and the PSFCH resources may be indicated by an offset and a periodicity. The PSFCH periodicity for the resource pool may be set by a higher layer (e.g., RRC) to {0 (no PSFCH), 1, 2, or 4} (a count in time slots).

[0083] In some examples, for the initial transmission of a TB in slot n, the transmitting UE 115 (the UE that transmits the TB) may expect a PSFCH from the sidelink receiver UE 115 in slot n+3 at the earliest. Therefore, in such an example, the retransmission of the TB may occur at slot n+4 at the earliest. Given a subcarrier spacing (SCS) of 30kHz, the round-trip time will be at least 2ms. Unless the initial transmission is conservative (e.g., using a low coding rate) or blind repetition is implemented, URLLC applications with strict requirements (e.g., a latency of 1ms and an IIOT of 1e-6 BLER) may not be supported. Therefore, a new sidelink structure may be designed to support applications with high reliability and low latency requirements, such as XR and URLLC.

[0084] Figure 5An example of a slot format 500 that supports low latency transmission in a sidelink according to one or more aspects of the present disclosure is illustrated. The slot format 500 may be implemented by aspects of the wireless communication system 100. For example, the slot format 500 may be implemented by one or more UEs 115.

[0085] Some wireless communication systems may implement micro-slot scheduling to reduce scheduling and turnaround time for side link communications. For example, a micro-slot may include 14 OFDM symbols less than those included in a normal length slot. Slot 405-c may be divided into multiple micro-slots or sub-slots (e.g., a first micro-slot 510-a, a second micro-slot 510-b, and a third micro-slot 510-c). Each micro-slot includes a PSCCH symbol 415-a and a PSSCH symbol 420-a, and may be self-schedulable and decodable. Gap symbol 425-a may separate micro-slots (a first micro-slot 510-a, a second micro-slot 510-b, and a third micro-slot 510-c). In some examples, each micro-slot includes an AGC symbol 410-a. In some examples, the AGC symbol 410 - a in the first mini-slot 510 - a may be applied to each mini-slot (eg, the second mini-slot 510 - b and the third mini-slot 510 - c may omit the AGC symbol).

[0086] With mini-slot scheduling, each UE 115 may select and reserve one or more mini-slots (eg, first mini-slot 510-a, second mini-slot 510-b, and third mini-slot 510-c) per slot 405-c.

[0087] As the number of mini-slots or sub-slots per time slot increases (which increases scheduling latency and is suitable for small packets (e.g., 32 bits for IIoT)), more symbols may be allocated to the slot (e.g., slot symbol 425-a). For some cases (e.g., if a large number of UEs are supported), this slot overhead may reduce the latency reduction gain associated with mini-slot scheduling.

[0088] Figure 6 An example of a slot format 600 that supports low latency transmission in a sidelink according to one or more aspects of the present disclosure is illustrated. The slot format 600 may be implemented by aspects of the wireless communication system 100. For example, the slot format 600 may be implemented by one or more UEs 115.

[0089] Gap symbols (for example, Figure 5 The gap symbol 425-a) in the time slot is used for transmit / receive switching. In the case where the transmit / receive switching occurs only at the time slot boundary, the gap symbol 425-b can be used only at the end of the time slot.

[0090] For example, slot 405-d illustrates a slot divided into multiple sub-slots (first sub-slot 610-a, second sub-slot 610-b, third sub-slot 610-c, and fourth sub-slot 610-d). Each sub-slot (first sub-slot 610-a, second sub-slot 610-b, third sub-slot 610-c, and fourth sub-slot 610-d) includes PSSCH symbol 420-b. PSCCH symbol 415-b may only be at the beginning of slot 405-d. The SCI in PSCCH symbol 415-b may indicate the transmission or reservation of multiple sub-slots in the same slot (e.g., slot 405-d) or in a future slot. An AGC symbol may not be required in each subslot (e.g., the first subslot 610-a, the second subslot 610-b, the third subslot 610-c, and the fourth subslot 610-d) because the receiving UE may set the AGC based on the AGC symbol 410-b at the beginning of the slot 405-d and may use the same AGC setting for any of the PSSCH symbols 420-b in the slot 405-d.

[0091] Figure 7 An example of a wireless communication system 700 supporting low latency transmission in a sidelink according to one or more aspects of the present disclosure is illustrated. The wireless communication system 700 may include a first UE 115-a and a second UE 115-b, which may be examples of UEs 115 as described herein. The wireless communication system 700 may include a network entity 105-a, which may be an example of a network entity 105 as described herein.

[0092] The first UE 115-a may communicate with the network entity 105-a using a communication link 125-a, which may be an example of an NR or LTE link between the first UE 115-a and the network entity 105-a. The second UE 115-b may communicate with the network entity 105-a using a communication link 125-b, which may be an example of an NR or LTE link between the second UE 115-b and the network entity 105-a. The communication link 125-a and the communication link 125-b may include a bidirectional link that implements both uplink and downlink communications. For example, the first UE 115-a may send an uplink transmission (such as an uplink control signal or an uplink data signal) to the network entity 105-a using the communication link 125-a, and the network entity 105-a may send a downlink transmission (such as a downlink control signal or a downlink data signal) to the first UE 115-a using the communication link 125-a. The second UE 115-b may use the communication link 125-b to send uplink transmissions (such as uplink control signals or uplink data signals) to the network entity 105-a, and the network entity 105-a may use the communication link 125-b to send downlink transmissions (such as downlink control signals or downlink data signals) to the second UE 115-b.

[0093] The first UE 115-a may communicate with the second UE 115-b using the sidelink communication link 135-a. The sidelink communication link 135-a may include a bidirectional link that enables the first UE 115-a and the second UE 115-b to send and receive sidelink signals. In some examples (e.g., in Mode 1), the network (e.g., the serving network entity 105-a) may configure resources for the sidelink communication link 135-a. In some examples, the first UE 115-a and the second UE 115-b may communicate via the sidelink communication link 135-a using directional communication techniques (e.g., beamforming techniques). In some examples (e.g., in Mode 2), the first UE 115-a and the second UE 115-b may autonomously determine and configure resources for the sidelink communication link 135-a (e.g., without participation from the serving network entity 105-a).

[0094] The network entity 105-a may send control signaling 710 (e.g., RRC signaling) indicating a set of resource pools that can be used for sidelink communication. The first UE 115-a may send an SCI 715 indicating a reservation of a resource pool in the set of resource pools. The SCI 715 indicates a priority level associated with low-latency data. The priority level may be based on a delay budget associated with the low-latency data (e.g., a remaining packet delay budget). The priority indicated in the SCI may be indicated via three or more bits and may be a function of the packet delay budget (and any other application requirements). In some examples, the priority may be indicated in an SCI-1 message or an SCI-2 message. A first-level SCI message refers to an SCI message transmitted via a PSCCH and may be referred to as an SCI-1. A second-level SCI refers to an SCI message transmitted via a PSSCH and may be referred to as an SCI-2. Then, the first UE 115-a may send a sidelink message 720 including low-latency data to the second UE 115-b.

[0095] In some examples, the low latency data may be XR traffic. In some examples, if other traffic is allowed on the same resource pool as XR, XR may preempt other traffic. XR preemption may apply to old transmissions (e.g., similar to downlink preemption, where content already received by UE 115 may be removed for other services) or future transmissions (e.g., canceling future allocations to send / receive XR).

[0096] If the priority in SCI-1 or SCI-2 (e.g., in SCI 715) indicates a high priority based on the remaining packet delay budget, other UEs (e.g., the second UE 115-b) may be prohibited from using the indicated time slots / sub-time slots. The XR service indication in SCI 715 may also reserve future time slots without allowing other service types (e.g., eMBB). In some cases, XR service may allow URLLC service (e.g., due to the delay of URLLC packets relative to XR). For example, in the case where URLLC takes precedence over XR, there may be a threshold delay. The priority indication may be indicated based on the delay budget via K additional bits (e.g., in addition to 3 bits) for different service types or service priorities. The priority indication may help with priority sorting within the multiplexer. The priority indication may help the first UE 115-a preempt another reservation (e.g., another reservation sent via the second SCI 725).

[0097] The sidelink DRX configuration (including periodicity and the start or start and end of the DRX active time) may not match the XR quasi-periodic service (e.g., at 60fps or 30fps). For example, in the XR service, packets arrive at 60fps every 16.67ms, which may not align with the integer periodicity of the sidelink. Packets arriving at non-integer rates (e.g., arriving at 60fps every 16.67ms) may not fall into the "on" duration of the sidelink DRX cycle of the receiving UE (e.g., the second UE 115-b). To avoid data loss and / or jitter, the non-integer periodicity of the XR service should match the sidelink DRX configuration. In some examples, the sidelink DRX configuration may be selected to match the XR service, for example by adding an offset to the start of the sidelink DRX cycle or using unequal DRX cycles. For example, the additional offset may be indicated via a control message 730 (Layer 1, Layer 2, or Layer 3 signaling) from the network entity 105-a, a control message 735 (Layer 1, Layer 2, or Layer 3 signaling) from the sending UE (first UE 115-a), or via an adjustment of the DRX cycle via a wake-up signal 740.

[0098] In some examples, the network entity 105-a may configure a DRX cycle for the XR service based on the XR service. The network entity 105-a may indicate the DRX cycle to the first UE 115-a via a control message 730, and the first UE 115-a may indicate the DRX cycle to the second UE 115-b via a control message 735. In some examples, the first UE 115-a may configure a DRX cycle for the second UE 115-b based on the XR service and statistics, and the first UE 115-a may indicate the DRX cycle to the second UE 115-b via a control message 735. In some examples, the first UE 115-a may suggest to the second UE 115-b via a control message 735 that the DRX cycle for the XR service be configured, and the second UE 115-b may configure the DRX cycle for the XR service based on the XR service and statistics. In some examples, the first UE 115-a may suggest to the second UE 115-b to configure a DRX cycle for XR traffic via control message 735. The second UE 115-b may relay the suggestion to the network entity 105-a via control message 745, and the network entity 105-a may configure and indicate (via control message 730) the DRX cycle for the XR traffic based on the XR traffic and statistics. The sidelink DRX cycle may be enhanced to match the XR periodic traffic by dynamic signaling, configuring multiple sidelink DRX configurations, or configuring a cyclic pattern of DRX to match the non-integer periodicity of the XR traffic. Enhancements to DRX for matching XR traffic in the Uu link may be applied to sidelink communications on the sidelink communication link 135-a. Additionally or alternatively, the periodicity of periodic configurations such as CG, scheduling requests, and sounding reference signals may be configured to match the periodicity of the XR traffic.

[0099] In the sidelink, the UE (e.g., the first UE 115-a and the second UE 115-b) can sense the channel by decoding the SCI and determining the demodulation reference signal (DMRS) position of the PSSCH (data). Based on the PSCCH DRMS ​​or PSSCH DMRS (based on the sidelink mode), the UE (e.g., the first UE 115-a and / or the second UE 115-b) determines whether future retransmissions of the TB are used / reserved based on RSRP measurement and a configured RSRP threshold (which may be RRC configured). In some examples, the RSRP threshold for XR services may be increased or specifically defined for XR services. For example, when the second UE 115-b determines that the service of the transmitting UE (first UE 115-a) (e.g., based on the service priority indication in the SCI 715) is an XR service, the second UE 115-b may use a higher RSRP threshold. For example, the RSRP threshold may be a function of the traffic of the current transmitting UE (first UE 115-a) and the traffic of the resource sensing UE (second UE 115-b). The RSRP increment (for the increase in XR traffic) may be indicated in control signaling 710 from the network entity 105-a configured with the resource pool set. In some cases, the RSRP increment may be controlled by a control unit in the side link (e.g., a programmable logic controller or a master UE (e.g., one of the first UE 115-a or the second UE 115-b)).

[0100] In some cases, when the RSRP threshold is shared during the RRC connection, the first UE 115-a and the second UE 115-b may define a new RSRP threshold based on the service type (or service priority indication type). A UE sensing the channel (e.g., the first UE 115-a or the second UE 115-b) may avoid resources that may be contention-based when the UE is scheduling XR services or URLLC services.

[0101] In some examples, some configuration grants may be configured by layer 3 signaling (RRC) or layer 2 signaling (e.g., MAC control element (MAC-CE)) for some services (such as URLLC and / or XR) so that URLLC and / or XR may be indicated as high priority services. For example, the configuration grant may be configured by control signaling 710 or control message 730.

[0102] In some examples, the network entity 105-a may reserve a resource pool for XR during a given time interval (e.g., via control signaling 710), for example, based on the arrival of XR traffic for UEs 115 (e.g., a majority of UEs 115) using the resource pool. In some examples, the resource pool may be divided into sub-resource pools, where XR traffic may use a specific sub-resource pool. The control signaling 710 may indicate the sub-resource pool used for the XR traffic. In some examples, each sub-resource pool may have a different DRX configuration so that the DRX configuration of the sub-resource pool used for the XR traffic may match the periodicity of the XR traffic. The control signaling 710 may indicate the DRX configuration for each sub-resource pool.

[0103] In some examples, XR data transmission may be repeated across sub-resource pools. In some examples, multiple sub-slots may be defined for XR traffic (e.g., via control signaling 710), and a transmitting UE (e.g., first UE 115-a) may repeat XR data transmission over more than one sub-slot. In some examples, a default repetition of each TB (e.g., X repetitions configured using layer 1, layer 2, or layer 3 signaling, configured per resource pool, or configured per sub-resource pool) may occur within a slot or across slots.

[0104] In some cases, any UE (e.g., the first UE 115-a or the second UE 115-b) may indicate a resource pool or sub-resource pool to be used for XR services or for high reliability transmission. In some cases, the side link message 720 may be repeated on multiple sub-resource pools or multiple resource pools simultaneously or across time (e.g., redundancy versions (RV) 0 and RV1 of a TB may be sent within a slot spanning two mini-slots or across sub-resource pools on the same mini-slot or different mini-slots).

[0105] Figure 8 An example of a process flow 800 for supporting low latency transmission in a sidelink according to one or more aspects of the present disclosure is illustrated. The process flow 800 may include a first UE 115-c and a second UE 115-d, which may be examples of UE 115 as described herein. The process flow 800 may include a network entity 105-b, which may be an example of a network entity 105 as described herein. In the following description of the process flow 800, operations between the network entity 105-b, the first UE 115-c, and the second UE 115-d may be sent in an order different from the example order shown, or operations performed by the network entity 105-b, the first UE 115-c, and the second UE 115-d may be performed in a different order or at different times. Some operations may also be omitted from the process flow 800, and other operations may be added to the process flow 800.

[0106] At 805, the first UE 115-c and the second UE 115-d may receive control signaling indicating a set of resource pools that can be used for sidelink communications. In some cases, the network entity 105-b may send the control signaling at 805.

[0107] At 810, the first UE 115-c may send and the second UE 115-d may receive an SCI message indicating a reservation of a resource pool in a set of resource pools, wherein the reservation indicates a priority level associated with low-latency data, and wherein the priority level is based on a delay budget associated with the low-latency data.

[0108] At 815, the first UE 115-c may send a sidelink message including low-latency data to the second UE 115-d via the resource pool.

[0109] In some examples, the first UE 115-c may receive second control signaling indicating a second reservation for the resource pool from the third UE prior to sending the SCI message at 810, wherein the second reservation indicates a second priority level that is lower than the priority level. Sending the SCI message at 810 is based on the second priority level being lower than the priority level. In some examples, the second UE 115-b may receive second control signaling indicating a second reservation for the resource pool from the third UE prior to receiving the SCI message at 810, wherein the second reservation indicates a second priority level that is lower than the priority level, and receiving the SCI message is based on the second priority level being lower than the priority level.

[0110] In some examples, the first UE 115-c may send a second control signaling to the second UE 115-d, the second control signaling indicating an offset to be applied to the DRX cycle for the XR service, and the low-latency data is the XR service. In some examples, the first UE 115-c may receive an indication of the offset from the network entity 105-b.

[0111] In some examples, the second UE 115-d may receive (e.g., from the network entity 105-b) second control signaling indicating an offset to be applied to the DRX cycle for the XR traffic, and the low-latency data is the XR traffic.

[0112] In some examples, the first UE 115-c may receive second control signaling indicating an RSRP threshold associated with low-latency traffic (e.g., from the network entity 105-b). The first UE 115-c may measure the RSRP of reference signals associated with resource pools in the set of resource pools. The first UE 115-c may select a resource pool based on the measured RSRP of the reference signals associated with the resource pools satisfying the RSRP threshold associated with the low-latency traffic.

[0113] In some examples, the first UE 115-c may send second control signaling to the second UE 115-d indicating an RSRP threshold associated with the low-latency service.

[0114] In some examples, the first UE 115-c may receive (e.g., from the network entity 105-b) a second control signaling indicating a subset of the set of resource pools associated with the configuration grant for the low-latency service. The first UE 115-c may communicate the low-latency service with the second UE 115-d via the subset. In some examples, the second UE 115-d may receive (e.g., from the network entity 105-b) a second control signaling indicating a subset of the set of resource pools associated with the configuration grant for the low-latency service.

[0115] In some examples, the first UE 115-c and / or the second UE 115-d may receive an indication from the network entity 105-b that the resource pool is associated with the low-latency service during a time interval, and the sidelink message is sent at 815 during the time interval.

[0116] In some examples, the first UE 115 - c may receive, using control signaling at 805 , an indication of a sub-resource pool of a resource pool associated with the XR service, and a DRX cycle associated with the sub-resource pool.

[0117] In some examples, the first UE 115-c may repeat the transmission of the sidelink message via a set of multiple sub-resource pools of a resource pool.

[0118] In some examples, the first UE 115-c and / or the second UE 115-d may receive second control signaling indicating a repetitive pattern for low-latency services across sub-time slots (e.g., from the network entity 105-b), and sending the side link message at 815 may include repeatedly sending the side link message across a set of sub-time slots of the resource pool.

[0119] In some examples, the first UE 115-c may receive second control signaling from the second UE 115-d or the third UE indicating that the resource pool is associated with the low-latency service, and sending the SCI message is based on the second control signaling.

[0120] In some examples, the first UE 115-c may repeatedly send the side link message across multiple resource pools in the set of resource pools, and the SCI message at 810 indicates a second reservation of the multiple resource pools.

[0121] Fig. 9A block diagram 900 of a device 905 supporting low latency transmission in a side link according to one or more aspects of the present disclosure is shown. The device 905 may be an example of aspects of a UE 115 as described herein. The device 905 may include a receiver 910, a transmitter 915, and a communication manager 920. The device 905 may also include a processor. Each of these components may communicate with each other (e.g., via one or more buses).

[0122] The receiver 910 may provide means for receiving information (such as packets, user data, control information, or any combination thereof) associated with various information channels (e.g., control channels, data channels, information channels related to supporting low-latency transmission in the sidelink). The information may be communicated to other components of the device 905. The receiver 910 may utilize a single antenna or a collection of multiple antennas.

[0123] The transmitter 915 may provide means for transmitting signals generated by other components of the device 905. For example, the transmitter 915 may transmit information associated with various information channels (e.g., control channels, data channels, information channels related to supporting low-latency transmission in the side link) (such as packets, user data, control information, or any combination thereof). In some examples, the transmitter 915 may be co-located with the receiver 910 in a transceiver module. The transmitter 915 may utilize a single antenna or a collection of multiple antennas.

[0124] The communication manager 920, the receiver 910, the transmitter 915, or various combinations thereof, or various components thereof, may be examples of means for performing various aspects of supporting low-latency transmission in a sidelink as described herein. For example, the communication manager 920, the receiver 910, the transmitter 915, or various combinations thereof, or components thereof, may support methods for performing one or more of the functions described herein.

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

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

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

[0128] According to the examples disclosed herein, the communication manager 920 may support wireless communication at the first UE. For example, the communication manager 920 may be configured to or otherwise support a component for receiving control signaling indicating a set of resource pools that can be used for sidelink communication. The communication manager 920 may be configured to or otherwise support a component for sending an SCI message indicating a reservation of a resource pool in the set of resource pools, wherein the reservation indicates a priority level associated with low-latency data, and wherein the priority level is based on a delay budget associated with the low-latency data. The communication manager 920 may be configured to or otherwise support a component for sending a sidelink message including low-latency data to a second UE via a resource pool.

[0129] Additionally or alternatively, according to examples as disclosed herein, the communication manager 920 may support wireless communication at the second UE. For example, the communication manager 920 may be configured to or otherwise support a component for receiving control signaling indicating a set of resource pools that can be used for sidelink communication. The communication manager 920 may be configured to or otherwise support a component for receiving an SCI message indicating a reservation of a resource pool in a set of resource pools from a first UE, wherein the reservation indicates a priority level associated with low-latency data, and wherein the priority level is based on a delay budget associated with the low-latency data. The communication manager 920 may be configured to or otherwise support a component for sending a sidelink message including low-latency data from the first UE via a resource pool.

[0130] By including or configuring a communication manager 920 according to examples as described herein, a device 905 (e.g., a processor controlling or otherwise coupled to a receiver 910, a transmitter 915, a communication manager 920, or a combination thereof) may support techniques for more efficiently utilizing communication resources.

[0131] Fig.10 A block diagram 1000 of a device 1005 supporting low latency transmission in a side link according to one or more aspects of the present disclosure is shown. The device 1005 may be an example of aspects of the device 905 or UE 115 as described herein. The device 1005 may include a receiver 1010, a transmitter 1015, and a communication manager 1020. The device 1005 may also include a processor. Each of these components may communicate with each other (e.g., via one or more buses).

[0132] The receiver 1010 may provide means for receiving information (such as packets, user data, control information, or any combination thereof) associated with various information channels (e.g., control channels, data channels, information channels related to supporting low-latency transmission in the sidelink). The information may be communicated to other components of the device 1005. The receiver 1010 may utilize a single antenna or a collection of multiple antennas.

[0133] The transmitter 1015 may provide means for transmitting signals generated by other components of the device 1005. For example, the transmitter 1015 may transmit information associated with various information channels (e.g., control channels, data channels, information channels related to supporting low-latency transmission in the side link) (such as packets, user data, control information, or any combination thereof). In some examples, the transmitter 1015 may be co-located with the receiver 1010 in a transceiver module. The transmitter 1015 may utilize a single antenna or a collection of multiple antennas.

[0134] Device 1005 or its various components may be examples of components for performing various aspects of supporting low-latency transmission in the side link as described herein. For example, communication manager 1020 may include resource pool manager 1025, side link reservation manager 1030, side link transmission manager 1035, side link reception manager 1040, or any combination thereof. Communication manager 1020 may be an example of various aspects of communication manager 920 as described herein. In some examples, communication manager 1020 or its various components may be configured to use or otherwise cooperate with receiver 1010, transmitter 1015, or both to perform various operations (e.g., receive, obtain, monitor, output, send). For example, communication manager 1020 may receive information from receiver 1010, transmit information to transmitter 1015, or integrate with receiver 1010, transmitter 1015, or both to obtain information, output information, or perform various other operations as described herein.

[0135] According to the examples disclosed herein, the communication manager 1020 may support wireless communication at the first UE. The resource pool manager 1025 may be configured to or otherwise support components for receiving control signaling indicating a set of resource pools that can be used for sidelink communication. The sidelink reservation manager 1030 may be configured to or otherwise support components for sending an SCI message indicating a reservation of a resource pool in the set of resource pools, wherein the reservation indicates a priority level associated with low-latency data, and wherein the priority level is based on a delay budget associated with the low-latency data. The sidelink transmission manager 1035 may be configured to or otherwise support components for sending a sidelink message including low-latency data to a second UE via a resource pool.

[0136] Additionally or alternatively, according to examples as disclosed herein, the communication manager 1020 may support wireless communication at the second UE. The resource pool manager 1025 may be configured to or otherwise support components for receiving control signaling indicating a set of resource pools that can be used for sidelink communication. The sidelink reservation manager 1030 may be configured to or otherwise support components for receiving an SCI message indicating a reservation of a resource pool in a set of resource pools from a first UE, wherein the reservation indicates a priority level associated with low-latency data, and wherein the priority level is based on a delay budget associated with the low-latency data. The sidelink reception manager 1040 may be configured to or otherwise support components for sending a sidelink message including low-latency data from a first UE via a resource pool.

[0137] Fig.11A block diagram 1100 of a communication manager 1120 supporting low-latency transmission in a side link according to one or more aspects of the present disclosure is shown. The communication manager 1120 may be an example of aspects of the communication manager 920, the communication manager 1020, or both as described herein. The communication manager 1120 or its various components may be examples of components for performing various aspects of supporting low-latency transmission in a side link as described herein. For example, the communication manager 1120 may include a resource pool manager 1125, a side link reservation manager 1130, a side link transmission manager 1135, a side link reception manager 1140, a DRX manager 1145, an RSRP threshold manager 1150, an RSRP measurement manager 1155, a resource pool selection manager 1160, a CG manager 1165, a low-latency traffic manager 1170, a side link transmission repetition manager 1175, or any combination thereof. Each of these components may communicate directly or indirectly with each other (e.g., via one or more buses).

[0138] According to the examples disclosed herein, the communication manager 1120 may support wireless communication at the first UE. The resource pool manager 1125 may be configured to or otherwise support components for receiving control signaling indicating a set of resource pools that can be used for sidelink communication. The sidelink reservation manager 1130 may be configured to or otherwise support components for sending an SCI message indicating a reservation of a resource pool in the set of resource pools, wherein the reservation indicates a priority level associated with low-latency data, and wherein the priority level is based on a delay budget associated with the low-latency data. The sidelink transmission manager 1135 may be configured to or otherwise support components for sending a sidelink message including low-latency data to a second UE via a resource pool.

[0139] In some examples, the side link reservation manager 1130 may be configured to or otherwise support components for receiving second control signaling from a third UE indicating a second reservation of a resource pool prior to sending the SCI message, wherein the second reservation indicates a second priority level that is lower than the priority level, and wherein sending the SCI message is based on the second priority level being lower than the priority level.

[0140] In some examples, the DRX manager 1145 may be configured or otherwise support components for sending second control signaling to a second UE indicating an offset to be applied to the DRX cycle for XR traffic, the low-latency data comprising XR traffic.

[0141] In some examples, DRX manager 1145 may be configured or otherwise support components for receiving an indication of an offset from a network entity.

[0142] In some examples, RSRP threshold manager 1150 may be configured or otherwise support components for receiving second control signaling indicating an RSRP threshold associated with low-latency traffic. In some examples, RSRP measurement manager 1155 may be configured or otherwise support components for measuring RSRP of reference signals associated with resource pools in a set of resource pools. In some examples, resource pool selection manager 1160 may be configured or otherwise support components for selecting a resource pool based on the measured RSRP of the reference signals associated with the resource pools satisfying the RSRP threshold associated with low-latency traffic.

[0143] In some examples, RSRP threshold manager 1150 may be configured or otherwise support components for sending second control signaling to a second UE indicating an RSRP threshold associated with the low-latency service.

[0144] In some examples, the CG manager 1165 may be configured to or otherwise support a component for receiving a second control signaling indicating a subset of a set of resource pools associated with a configuration grant for low-latency services. In some examples, the low-latency service manager 1170 may be configured to or otherwise support a component for communicating low-latency services with a second UE via the subset.

[0145] In some examples, low-latency traffic manager 1170 may be configured or otherwise support components for receiving an indication from a network entity that a resource pool is associated with low-latency traffic during a time interval during which a sidelink message is sent.

[0146] In some examples, the DRX manager 1145 may be configured or otherwise support components for receiving, using control signaling, an indication of a sub-resource pool of a resource pool associated with the XR service and a DRX cycle associated with the sub-resource pool.

[0147] In some examples, to support sending a side link message, the side link send repetition manager 1175 may be configured or otherwise support components for repeating the sending of the side link message via a set of multiple sub-resource pools of a resource pool.

[0148] In some examples, the sidelink transmit repetition manager 1175 may be configured as or otherwise support components for receiving second control signaling across sub-time slots indicating a repetition pattern for low-latency services, wherein sending the sidelink message includes repeatedly sending the sidelink message across a set of sub-time slots of a resource pool.

[0149] In some examples, the low-latency service manager 1170 may be configured as or otherwise support components for receiving second control signaling from a second UE or a third UE indicating that a resource pool is associated with a low-latency service, wherein sending the SCI message is based on the second control signaling.

[0150] In some examples, the side link transmit repetition manager 1175 may be configured or otherwise support components for repeatedly transmitting a side link message across multiple resource pools of a set of resource pools, wherein the SCI message indicates a second reservation of the multiple resource pools.

[0151] Additionally or alternatively, according to examples as disclosed herein, the communication manager 1120 may support wireless communication at a second UE. In some examples, the resource pool manager 1125 may be configured to or otherwise support components for receiving control signaling indicating a set of resource pools that can be used for sidelink communication. In some examples, the sidelink reservation manager 1130 may be configured to or otherwise support components for receiving an SCI message indicating a reservation of a resource pool in a set of resource pools from a first UE, wherein the reservation indicates a priority level associated with low-latency data, and wherein the priority level is based on a delay budget associated with the low-latency data. The sidelink reception manager 1140 may be configured to or otherwise support components for sending a sidelink message including low-latency data from a first UE via a resource pool.

[0152] In some examples, the side link reservation manager 1130 may be configured to or otherwise support components for receiving second control signaling from a third UE indicating a second reservation for a resource pool prior to receiving the SCI message, wherein the second reservation indicates a second priority level that is lower than the priority level, and wherein receiving the SCI message is based on the second priority level being lower than the priority level.

[0153] In some examples, the DRX manager 1145 may be configured or otherwise support components for receiving second control signaling from the first UE indicating an offset to be applied to the DRX cycle for XR traffic, wherein the low-latency data includes the XR traffic.

[0154] In some examples, the DRX manager 1145 may be configured or otherwise support components for receiving an indication of an offset to be applied to a DRX cycle for XR traffic from a network entity, wherein the low-latency data includes the XR traffic.

[0155] In some examples, RSRP threshold manager 1150 may be configured or otherwise support components for receiving second control signaling from the first UE indicating an RSRP threshold associated with the low-latency service.

[0156] In some examples, the CG manager 1165 may be configured to or otherwise support a component for receiving a second control signaling indicating a subset of a set of resource pools associated with a configuration grant for low-latency services. In some examples, the low-latency service manager 1170 may be configured to or otherwise support a component for communicating low-latency services with the first UE via the subset.

[0157] In some examples, low-latency traffic manager 1170 may be configured or otherwise support components for receiving an indication from a network entity that a resource pool is associated with low-latency traffic during a time interval during which a sidelink message is received.

[0158] In some examples, the DRX manager 1145 may be configured or otherwise support components for receiving, using control signaling, an indication of a sub-resource pool of a resource pool associated with the XR service and a DRX cycle associated with the sub-resource pool.

[0159] In some examples, to support receiving side link messages, side link transmit repetition manager 1175 may be configured or otherwise support components for receiving repeated transmissions of side link messages via a collection of multiple sub-resource pools of a resource pool.

[0160] In some examples, the sidelink transmit repetition manager 1175 may be configured as or otherwise support components for receiving a second control signaling across sub-time slots indicating a repetition pattern for low-latency services, wherein receiving a sidelink message includes repeated transmissions of the sidelink message across a set of sub-time slots of a resource pool.

[0161] In some examples, the low-latency service manager 1170 may be configured as or otherwise support components for sending a second control signaling to the first UE indicating that the resource pool is associated with the low-latency service, wherein sending the SCI message is based on the second control signaling.

[0162] In some examples, the side link transmit repetition manager 1175 may be configured or otherwise support components for receiving repeated transmissions of a side link message across multiple resource pools in a set of resource pools, where the SCI message indicates a second reservation of the multiple resource pools.

[0163] Fig.12A diagram of a system 1200 including a device 1205 supporting low-latency transmission in a sidelink according to one or more aspects of the present disclosure is shown. The device 1205 may be an example of a device 905, a device 1005, or a UE 115 as described herein or include components thereof. The device 1205 may communicate (e.g., wirelessly) with one or more network entities 105, one or more UEs 115, or any combination thereof. The device 1205 may include components for two-way voice and data communications, including components for sending and receiving communications, such as a communication manager 1220, an input / output (I / O) controller 1210, a transceiver 1215, an antenna 1225, a memory 1230, a code 1235, and a processor 1240. These components may be electronically communicated or otherwise coupled (e.g., operatively, communicatively, functionally, electronically, electrically) via one or more buses (e.g., a bus 1245).

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

[0165] In some cases, the device 1205 may include a single antenna 1225. However, in some other cases, the device 1205 may have more than one antenna 1225, which may be capable of concurrently transmitting or receiving multiple wireless transmissions. The transceiver 1215 may communicate bidirectionally via one or more antennas 1225, a wired or wireless link, as described herein. For example, the transceiver 1215 may represent a wireless transceiver and may communicate bidirectionally with another wireless transceiver. The transceiver 1215 may also include a modem for: modulating packets; providing the modulated packets to one or more antennas 1225 for transmission; and demodulating packets received from one or more antennas 1225. The transceiver 1215 or the transceiver 1215 and one or more antennas 1225 may be examples of transmitters 915, transmitters 1015, receivers 910, receivers 1010, or any combination thereof or components thereof as described herein.

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

[0167] Processor 1240 may include an intelligent hardware device (e.g., a general-purpose processor, a DSP, a CPU, a microcontroller, an ASIC, an FPGA, a programmable logic device, a discrete gate or transistor logic component, a discrete hardware component, or any combination thereof). In some cases, processor 1240 may be configured to operate a memory array using a memory controller. In some other cases, the memory controller may be integrated into processor 1240. Processor 1240 may be configured to execute computer-readable instructions stored in a memory (e.g., memory 1230) so that device 1205 performs various functions (e.g., various functions or tasks that support low-latency transmission in the opposite side link). For example, device 1205 or a component of device 1205 may include processor 1240 and memory 1230 coupled to or coupled to processor 1240, and processor 1240 and memory 1230 are configured to perform the various functions described herein.

[0168] According to examples as disclosed herein, the communication manager 1220 may support wireless communication at a first UE. For example, the communication manager 1220 may be configured to or otherwise support components for receiving control signaling indicating a set of resource pools that can be used for sidelink communication. The communication manager 1220 may be configured to or otherwise support components for sending an SCI message indicating a reservation of a resource pool in the set of resource pools, wherein the reservation indicates a priority level associated with low-latency data, and wherein the priority level is based on a delay budget associated with the low-latency data. The communication manager 1220 may be configured to or otherwise support components for sending a sidelink message including low-latency data to a second UE via a resource pool.

[0169] Additionally or alternatively, according to examples as disclosed herein, the communication manager 1220 may support wireless communication at the second UE. For example, the communication manager 1220 may be configured to or otherwise support a component for receiving control signaling indicating a set of resource pools that can be used for sidelink communication. The communication manager 1220 may be configured to or otherwise support a component for receiving an SCI message indicating a reservation of a resource pool in a set of resource pools from a first UE, wherein the reservation indicates a priority level associated with low-latency data, and wherein the priority level is based on a delay budget associated with the low-latency data. The communication manager 1220 may be configured to or otherwise support a component for sending a sidelink message including low-latency data from the first UE via a resource pool.

[0170] By including or configuring a communications manager 1220 according to examples as described herein, the device 1205 may support techniques for improving communications reliability, reducing latency, more efficiently utilizing communications resources, improving coordination between devices, and improving utilization of processing power.

[0171] In some examples, the communication manager 1220 may be configured to perform various operations (e.g., receive, monitor, transmit) using or otherwise cooperating with the transceiver 1215, one or more antennas 1225, or any combination thereof. Although the communication manager 1220 is illustrated as a separate component, in some examples, one or more functions described with reference to the communication manager 1220 may be supported or performed by the processor 1240, the memory 1230, the code 1235, or any combination thereof. For example, the code 1235 may include instructions executable by the processor 1240 to cause the device 1205 to perform various aspects of supporting low-latency transmission in the side link as described herein, or the processor 1240 and the memory 1230 may be otherwise configured to perform or support such operations.

[0172] Fig.13A flowchart illustrating a method 1300 for supporting low-latency transmission in a side link according to one or more aspects of the present disclosure is shown. The operations of the method 1300 may be implemented by a UE or a component thereof as described herein. For example, the operations of the method 1300 may be implemented by a UE or a component thereof as described in reference to Figures 1 to 12 The UE 115 described herein may be executed. In some examples, the UE may execute an instruction set to control the functional elements of the UE to perform the described functions. Additionally or alternatively, the UE may use dedicated hardware to perform various aspects of the described functions.

[0173] At 1305, the method may include receiving control signaling indicating a set of resource pools that can be used for sidelink communication. The operations of 1305 may be performed according to examples as disclosed herein. In some examples, aspects of the operations of 1305 may be performed as described in reference to Fig.11 The resource pool manager 1125 is used to execute.

[0174] At 1310, the method may include sending an SCI message indicating a reservation of a resource pool in a set of resource pools, wherein the reservation indicates a priority level associated with the low-latency data, and wherein the priority level is based on a delay budget associated with the low-latency data. The operations of 1310 may be performed according to examples as disclosed herein. In some examples, aspects of the operations of 1310 may be performed as described in reference Fig.11 The side link reservation manager 1130 is used to execute.

[0175] At 1315, the method may include sending a sidelink message including low-latency data to the second UE via the resource pool. The operations of 1315 may be performed according to examples as disclosed herein. In some examples, aspects of the operations of 1315 may be performed as described in reference to Fig.11 The side link transmission manager 1135 is used to execute.

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

[0177] At 1405, the method may include receiving control signaling indicating a set of resource pools that can be used for sidelink communication. The operations of 1405 may be performed according to examples as disclosed herein. In some examples, aspects of the operations of 1405 may be performed as described in reference to Fig.11The resource pool manager 1125 is used to execute.

[0178] At 1410, the method may include sending an SCI message indicating a reservation of a resource pool in a set of resource pools, wherein the reservation indicates a priority level associated with the low-latency data, and wherein the priority level is based on a delay budget associated with the low-latency data. The operations of 1410 may be performed according to examples as disclosed herein. In some examples, aspects of the operations of 1410 may be performed as described in reference Fig.11 The side link reservation manager 1130 is used to execute.

[0179] At 1415, the method may include sending a second control signaling to the second UE, the second control signaling indicating an offset to be applied to the DRX cycle for the XR service, wherein the low latency data includes the XR service. The operations of 1415 may be performed according to examples as disclosed herein. In some examples, aspects of the operations of 1415 may be performed as described in reference Fig.11 The DRX manager 1145 is used to execute.

[0180] At 1420, the method may include sending a sidelink message including low-latency data to the second UE via the resource pool. The operations of 1420 may be performed according to examples disclosed herein. In some examples, aspects of the operations of 1420 may be performed as described in reference to Fig.11 The side link transmission manager 1135 is used to execute.

[0181] Fig.15 A flowchart illustrating a method 1500 for supporting low-latency transmission in a side link according to one or more aspects of the present disclosure is shown. The operations of the method 1500 may be implemented by a UE or a component thereof as described herein. For example, the operations of the method 1500 may be implemented by a UE or a component thereof as described in reference to Figures 1 to 12 The UE 115 described herein may be executed. In some examples, the UE may execute an instruction set to control the functional elements of the UE to perform the described functions. Additionally or alternatively, the UE may use dedicated hardware to perform various aspects of the described functions.

[0182] At 1505, the method may include receiving control signaling indicating a set of resource pools that can be used for sidelink communication. The operations of 1505 may be performed according to examples as disclosed herein. In some examples, aspects of the operations of 1505 may be performed as described in reference to Fig.11 The resource pool manager 1125 is used to execute.

[0183] At 1510, the method may include receiving an SCI message from a first UE indicating a reservation of a resource pool in a set of resource pools, wherein the reservation indicates a priority level associated with the low-latency data, and wherein the priority level is based on a delay budget associated with the low-latency data. The operations of 1510 may be performed according to examples as disclosed herein. In some examples, aspects of the operations of 1510 may be performed as described in reference Fig.11 The side link reservation manager 1130 is used to execute.

[0184] At 1515, the method may include sending a sidelink message including low-latency data from the first UE via the resource pool. The operations of 1515 may be performed according to examples as disclosed herein. In some examples, aspects of the operations of 1515 may be performed as described in reference to Fig.11 The side link reception manager 1140 is used to execute.

[0185] Fig.16 A flow chart illustrating a method 1600 for supporting low latency transmission in a side link according to one or more aspects of the present disclosure is shown. The operations of the method 1600 may be implemented by a UE or a component thereof as described herein. For example, the operations of the method 1600 may be implemented by a UE or a component thereof as described in reference to Figures 1 to 12 The UE 115 described herein may be executed. In some examples, the UE may execute an instruction set to control the functional elements of the UE to perform the described functions. Additionally or alternatively, the UE may use dedicated hardware to perform various aspects of the described functions.

[0186] At 1605, the method may include receiving control signaling indicating a set of resource pools that can be used for sidelink communication. The operations of 1605 may be performed according to examples as disclosed herein. In some examples, aspects of the operations of 1605 may be performed as described in reference to Fig.11 The resource pool manager 1125 is used to execute.

[0187] At 1610, the method may include receiving an SCI message from a first UE indicating a reservation of a resource pool in a set of resource pools, wherein the reservation indicates a priority level associated with the low-latency data, and wherein the priority level is based on a delay budget associated with the low-latency data. The operations of 1610 may be performed according to examples as disclosed herein. In some examples, aspects of the operations of 1610 may be performed as described in reference to Fig.11 The side link reservation manager 1130 is used to execute.

[0188] At 1615, the method may include sending a sidelink message including low-latency data from the first UE via the resource pool. The operations of 1615 may be performed according to examples as disclosed herein. In some examples, aspects of the operations of 1615 may be performed as described in reference to Fig.11The side link reception manager 1140 is used to execute.

[0189] At 1620, the method may include receiving second control signaling from the first UE, the second control signaling indicating an offset to be applied to the DRX cycle for the XR service, wherein the low latency data includes the XR service. The operations of 1620 may be performed according to examples as disclosed herein. In some examples, aspects of the operations of 1620 may be performed as described in reference Fig.11 The DRX manager 1145 is used to execute.

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

[0191] Aspect 1: A method for performing wireless communications at a first UE, the method comprising: receiving control signaling indicating a set of resource pools that can be used for sidelink communications; sending an SCI message indicating a reservation of a resource pool in the set of resource pools, wherein the reservation indicates a priority level associated with low-latency data, and wherein the priority level is based at least in part on a delay budget associated with the low-latency data; and sending a sidelink message including the low-latency data to a second UE via the resource pool.

[0192] Aspect 2: According to the method described in Aspect 1, the method also includes: before sending the SCI message, receiving a second control signaling indicating a second reservation of the resource pool from a third UE, wherein the second reservation indicates a second priority level lower than the priority level, and wherein sending the SCI message is at least partly based on the second priority level being lower than the priority level.

[0193] Aspect 3: According to the method described in any one of Aspects 1 to 2, the method further includes: sending a second control signaling to the second UE, the second control signaling indicating an offset to be applied to the DRX cycle for the XR service, wherein the low-latency data includes the XR service.

[0194] Aspect 4: The method according to aspect 3 further comprises: receiving an indication of the offset from a network entity.

[0195] Aspect 5: According to the method described in any one of Aspects 1 to 4, the method further includes: receiving a second control signal indicating an RSRP threshold associated with a low-latency service; measuring the RSRP of a reference signal associated with a resource pool in the resource pool set; and selecting the resource pool based at least in part on the RSRP of the reference signal associated with the resource pool satisfying the RSRP threshold associated with the low-latency service.

[0196] Aspect 6: According to the method according to any one of Aspects 1 to 5, the method further includes: sending a second control signaling indicating an RSRP threshold associated with the low-latency service to the second UE.

[0197] Aspect 7: According to the method described in any one of Aspects 1 to 6, the method further includes: receiving a second control signaling indicating a subset of the resource pool set associated with a configuration grant for low-latency services; and communicating the low-latency services with the second UE via the subset.

[0198] Aspect 8: According to the method according to any one of Aspects 1 to 7, the method also includes: receiving an indication from a network entity during a time interval that the resource pool is associated with a low-latency service, wherein the side link message is sent during the time interval.

[0199] Aspect 9: According to the method described in any one of Aspects 1 to 8, the method further includes: using the control signaling to receive an indication of a sub-resource pool of the resource pool associated with the XR service, and a DRX cycle associated with the sub-resource pool.

[0200] Aspect 10: The method according to any one of Aspects 1 to 9, wherein sending the side link message comprises: repeatedly sending the side link message via multiple sub-resource pools of the resource pool.

[0201] Aspect 11: According to the method described in any one of Aspects 1 to 10, the method further includes: receiving a second control signaling indicating a repetition mode for low-latency services across sub-time slots, wherein sending the side link message includes repeatedly sending the side link message across a group of sub-time slots of the resource pool.

[0202] Aspect 12: According to the method described in any one of Aspects 1 to 11, the method further includes: receiving a second control signaling from the second UE or the third UE indicating that the resource pool is associated with a low-latency service, wherein sending the SCI message is at least partially based on the second control signaling.

[0203] Aspect 13: According to the method described in any one of Aspects 1 to 12, the method further comprises: repeatedly sending the side link message across multiple resource pools in the resource pool set, wherein the SCI message indicates a second reservation of the multiple resource pools.

[0204] Aspect 14: A method for performing wireless communications at a second UE, the method comprising: receiving control signaling indicating a set of resource pools that can be used for sidelink communications; receiving an SCI message indicating a reservation of a resource pool in the set of resource pools from a first UE, wherein the reservation indicates a priority level associated with low-latency data, and wherein the priority level is based at least in part on a delay budget associated with the low-latency data; and sending a sidelink message including the low-latency data from the first UE via the resource pool.

[0205] Aspect 15: According to the method described in Aspect 14, the method also includes: before receiving the SCI message, receiving a second control signaling indicating a second reservation of the resource pool from a third UE, wherein the second reservation indicates a second priority level lower than the priority level, and wherein receiving the SCI message is at least partly based on the second priority level being lower than the priority level.

[0206] Aspect 16: According to the method described in any one of Aspects 14 to 15, the method further includes: receiving a second control signaling from the first UE, the second control signaling indicating an offset to be applied to the DRX cycle for the XR service, wherein the low-latency data includes the XR service.

[0207] Aspect 17: According to the method of any one of Aspects 14 to 16, the method further includes: receiving an indication of an offset to be applied to the DRX cycle for the XR service from a network entity, wherein the low-latency data includes the XR service.

[0208] Aspect 18: According to the method of any one of Aspects 14 to 17, the method further includes: receiving, from the first UE, second control signaling indicating an RSRP threshold associated with a low-latency service.

[0209] Aspect 19: According to the method described in any one of Aspects 14 to 18, the method further includes: receiving a second control signaling indicating a subset of the resource pool set associated with a configuration grant for low-latency services; and communicating the low-latency services with the first UE via the subset.

[0210] Aspect 20: According to the method described in any one of Aspects 14 to 19, the method further comprises: receiving an indication from a network entity during a time interval that the resource pool is associated with a low-latency service, wherein the side link message is received during the time interval.

[0211] Aspect 21: According to the method described in any one of Aspects 14 to 20, the method further includes: using the control signaling to receive an indication of a sub-resource pool of the resource pool associated with the XR service, and a DRX cycle associated with the sub-resource pool.

[0212] Aspect 22: The method according to any one of Aspects 14 to 21, wherein receiving the side link message comprises: receiving repeated transmissions of the side link message via multiple sub-resource pools of the resource pool.

[0213] Aspect 23: According to the method described in any one of Aspects 14 to 22, the method further includes: receiving a second control signaling indicating a repetition mode for low-latency services across sub-time slots, wherein receiving the side link message includes receiving repeated transmissions of the side link message across a group of sub-time slots of the resource pool.

[0214] Aspect 24: According to the method described in any one of Aspects 14 to 23, the method further includes: sending a second control signaling to the first UE indicating that the resource pool is associated with a low-latency service, wherein sending the SCI message is at least partially based on the second control signaling.

[0215] Aspect 25: According to the method described in any one of Aspects 14 to 24, the method further comprises: receiving repeated transmissions of the side link message across multiple resource pools of the resource pool set, wherein the SCI message indicates a second reservation of the multiple resource pools.

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

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

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

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

[0220] Aspect 30: An apparatus for wireless communication at a second UE, the apparatus comprising at least one component for performing a method according to any one of aspects 14 to 25.

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

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

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

[0224] The various illustrative blocks and components described in conjunction with the disclosure herein may be implemented or executed using a general purpose processor, DSP, ASIC, CPU, FPGA or other programmable logic device, discrete gate or transistor logic components, discrete hardware components, or any combination thereof designed to perform the functions described herein. A general purpose processor may be a microprocessor, but in an alternative, the processor may be any processor, controller, microcontroller, or state machine. The processor may also be implemented as a combination of computing devices (e.g., a combination of a DSP and a microprocessor, a plurality of microprocessors, one or more microprocessors in conjunction with a DSP core, or any other such configuration).

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

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

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

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

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

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

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

Claims

1. An apparatus for wireless communication at a first user equipment (UE), the apparatus comprising: processor; a memory coupled to the processor; and instructions stored in the memory and executable by the processor to cause the apparatus to: receiving control signaling indicating a set of resource pools that can be used for sidelink communication; sending a sidelink control information message indicating a reservation of a resource pool in the set of resource pools, wherein the reservation indicates a priority level associated with low-latency data, and wherein the priority level is based at least in part on a delay budget associated with the low-latency data; and A side link message including the low-latency data is sent to a second UE via the resource pool.

2. The apparatus of claim 1 , wherein the instructions are further executable by the processor to cause the apparatus to: Prior to sending the sidelink control information message, second control signaling indicating a second reservation of the resource pool is received from a third UE, wherein the second reservation indicates a second priority level lower than the priority level, and wherein sending the sidelink control information message is at least partially based on the second priority level being lower than the priority level.

3. The apparatus of claim 1 , wherein the instructions are further executable by the processor to cause the apparatus to: Second control signaling is sent to the second UE indicating an offset to be applied to a discontinuous reception cycle for an extended reality service, wherein the low-latency data includes the extended reality service.

4. The apparatus of claim 3, wherein the instructions are further executable by the processor to cause the apparatus to: An indication of the offset is received from a network entity.

5. The apparatus of claim 1, wherein the instructions are further executable by the processor to cause the apparatus to: receiving a second control signaling indicating a reference signal reception power threshold associated with a low-latency service; measuring a reference signal received power of a reference signal associated with a resource pool in the set of resource pools; and The resource pool is selected based at least in part on a measured reference signal received power of a reference signal associated with the resource pool satisfying the reference signal received power threshold associated with low latency traffic.

6. The apparatus of claim 1, wherein the instructions are further executable by the processor to cause the apparatus to: Sending second control signaling indicating a reference signal reception power threshold associated with the low-latency service to the second UE.

7. The apparatus of claim 1, wherein the instructions are further executable by the processor to cause the apparatus to: receiving second control signaling indicating a subset of the set of resource pools associated with a configuration grant for low-latency services; and A low-latency service is communicated with the second UE via the subset.

8. The apparatus of claim 1, wherein the instructions are further executable by the processor to cause the apparatus to: An indication is received from a network entity during a time interval during which the sidelink message is sent that the resource pool is associated with low-latency traffic.

9. The apparatus of claim 1, wherein the instructions are further executable by the processor to cause the apparatus to: An indication of a sub-resource pool of the resource pool associated with an extended reality service and a discontinuous reception cycle associated with the sub-resource pool are received using the control signaling.

10. The apparatus of claim 1 , wherein the instructions for sending the sidelink message are executable by the processor to cause the apparatus to: The side link message is repeatedly sent via a plurality of sub-resource pools of the resource pool.

11. The apparatus of claim 1 , wherein the instructions are further executable by the processor to cause the apparatus to: Second control signaling indicating a repetition pattern for low-latency traffic is received across sub-timeslots, wherein sending the sidelink message comprises repeatedly sending the sidelink message across a set of sub-timeslots of the resource pool.

12. The apparatus of claim 1, wherein the instructions are further executable by the processor to cause the apparatus to: Second control signaling is received from the second UE or the third UE indicating that the resource pool is associated with a low-latency service, wherein sending the sidelink control information message is based at least in part on the second control signaling.

13. The apparatus of claim 1, wherein the instructions are further executable by the processor to cause the apparatus to: The sidelink message is repeatedly sent across a plurality of resource pools of the set of resource pools, wherein the sidelink control information message indicates a second reservation of the plurality of resource pools.

14. An apparatus for wireless communication at a second user equipment (UE), the apparatus comprising: processor; a memory coupled to the processor; and instructions stored in the memory and executable by the processor to cause the apparatus to: receiving control signaling indicating a set of resource pools that can be used for sidelink communication; receiving, from a first UE, a sidelink control information message indicating a reservation of a resource pool in the set of resource pools, wherein the reservation indicates a priority level associated with low-latency data, and wherein the priority level is based at least in part on a delay budget associated with the low-latency data; and A sidelink message including the low-latency data is sent from the first UE via the resource pool.

15. The apparatus of claim 14, wherein the instructions are further executable by the processor to cause the apparatus to: Prior to receiving the sidelink control information message, second control signaling indicating a second reservation of the resource pool is received from a third UE, wherein the second reservation indicates a second priority level lower than the priority level, and wherein receiving the sidelink control information message is at least partially based on the second priority level being lower than the priority level.

16. The apparatus of claim 14, wherein the instructions are further executable by the processor to cause the apparatus to: Second control signaling is received from the first UE indicating an offset to be applied to a discontinuous reception cycle for an extended reality service, wherein the low-latency data includes the extended reality service.

17. The apparatus of claim 14, wherein the instructions are further executable by the processor to cause the apparatus to: An indication of an offset to be applied to a discontinuous reception cycle for an augmented reality service is received from a network entity, wherein the low-latency data includes the augmented reality service.

18. The apparatus of claim 14, wherein the instructions are further executable by the processor to cause the apparatus to: Second control signaling indicating a reference signal reception power threshold associated with a low-latency service is received from the first UE.

19. The apparatus of claim 14, wherein the instructions are further executable by the processor to cause the apparatus to: receiving second control signaling indicating a subset of the set of resource pools associated with a configuration grant for low-latency services; and A low-latency service is communicated with the first UE via the subset.

20. The apparatus of claim 14, wherein the instructions are further executable by the processor to cause the apparatus to: An indication is received from a network entity during a time interval during which the sidelink message is received that the resource pool is associated with low-latency traffic.

21. The apparatus of claim 14, wherein the instructions are further executable by the processor to cause the apparatus to: An indication of a sub-resource pool of the resource pool associated with an extended reality service and a discontinuous reception cycle associated with the sub-resource pool are received using the control signaling.

22. The apparatus of claim 14, wherein the instructions for receiving the sidelink message are executable by the processor to cause the apparatus to: Repeated transmissions of the sidelink message are received via a plurality of sub-resource pools of the resource pool.

23. The apparatus of claim 14, wherein the instructions are further executable by the processor to cause the apparatus to: Second control signaling indicating a repetition pattern for low-latency traffic is received across sub-timeslots, wherein receiving the sidelink message comprises receiving repeated transmissions of the sidelink message across a set of sub-timeslots of the resource pool.

24. The apparatus of claim 14, wherein the instructions are further executable by the processor to cause the apparatus to: Second control signaling is sent to the first UE indicating that the resource pool is associated with a low-latency service, wherein sending the sidelink control information message is based at least in part on the second control signaling.

25. The apparatus of claim 14, wherein the instructions are further executable by the processor to cause the apparatus to: Repeated transmissions of the sidelink message are received across a plurality of resource pools of the set of resource pools, wherein the sidelink control information message indicates a second reservation of the plurality of resource pools.

26. A method for wireless communication at a first user equipment (UE), the method comprising: receiving control signaling indicating a set of resource pools that can be used for sidelink communication; sending a sidelink control information message indicating a reservation of a resource pool in the set of resource pools, wherein the reservation indicates a priority level associated with low-latency data, and wherein the priority level is based at least in part on a delay budget associated with the low-latency data; and A side link message including the low-latency data is sent to a second UE via the resource pool.

27. The method according to claim 26, further comprising: Prior to sending the sidelink control information message, second control signaling indicating a second reservation of the resource pool is received from a third UE, wherein the second reservation indicates a second priority level lower than the priority level, and wherein sending the sidelink control information message is at least partially based on the second priority level being lower than the priority level.

28. The method according to claim 26, further comprising: Second control signaling is sent to the second UE indicating an offset to be applied to a discontinuous reception cycle for an extended reality service, wherein the low-latency data includes the extended reality service.

29. The method according to claim 28, further comprising: An indication of the offset is received from a network entity.

30. A method for wireless communication at a second user equipment (UE), the method comprising: receiving control signaling indicating a set of resource pools that can be used for sidelink communication; receiving, from a first UE, a sidelink control information message indicating a reservation of a resource pool in the set of resource pools, wherein the reservation indicates a priority level associated with low-latency data, and wherein the priority level is based at least in part on a delay budget associated with the low-latency data; and A sidelink message including the low-latency data is sent from the first UE via the resource pool.

Images