Discontinuous reception with implicit indication in sidelink

Abstract

A method of wireless communication at a first UE is disclosed. The method includes obtaining a configuration associated with a DRX cycle of a second UE, where the configuration includes a first indication of a first set of resources and at least one condition, where the first set of resources is different from a second set of resources for the DRX cycle of the second UE. The method also includes transmitting SL data to the second UE via the first set of resources or the second set of resources based on an occurrence of the at least one condition.

Description

Technical Field

[0001] The present disclosure relates generally to communication systems, and more particularly to sidelink communications. Background Art

[0002] Wireless communication systems are widely deployed to provide a variety of telecommunication services, such as telephony, video, data, messaging, and broadcast. Typical wireless communication systems may employ multiple access technologies capable of supporting communication with multiple users by sharing available system resources. Examples of such multiple access technologies include code division multiple access (CDMA) systems, time division multiple access (TDMA) systems, frequency division multiple access (FDMA) systems, orthogonal frequency division multiple access (OFDMA) systems, single carrier frequency division multiple access (SC-FDMA) systems, and time division synchronous code division multiple access (TD-SCDMA) systems.

[0003] These multiple access technologies have been adopted in various telecommunication standards to provide a common protocol that enables different wireless devices to communicate at a city, country, region, and even global level. An example telecommunication standard is 5G New Radio (NR). 5G NR is part of the continuous mobile broadband evolution promulgated by the Third Generation Partnership Project (3GPP) to meet new requirements associated with latency, reliability, security, scalability (e.g., with the Internet of Things (IoT)) and other requirements. 5GNR includes services associated with enhanced mobile broadband (eMBB), massive machine type communication (mMTC), and ultra-reliable low latency communication (URLLC). Certain aspects of 5G NR may be based on 4G Long Term Evolution (LTE) standards. It is necessary to further improve 5G NR technology. In addition, these improvements may also be applicable to other multiple access technologies and telecommunication standards that employ these technologies. Summary of the invention

[0004] A simplified summary of one or more aspects is presented below to provide a basic understanding of these aspects. This summary is not an extensive review of all contemplated aspects. This summary neither identifies the key or important elements of all aspects, nor describes the scope of any or all aspects. Its sole purpose is to present some concepts of one or more aspects in a simplified form as a prelude to a more detailed description presented later.

[0005] In one aspect of the present disclosure, a method, computer-readable medium, and apparatus for wireless communication at a first user equipment (UE) are provided. The apparatus includes a memory and at least one processor coupled to the memory, and based at least in part on information stored in the memory, the at least one processor is configured to: obtain a configuration associated with a discontinuous reception (DRX) cycle of a second UE, wherein the configuration includes a first indication of a first set of resources and at least one condition, wherein the first set of resources is different from a second set of resources for the DRX cycle of the second UE; and send sidelink (SL) data to the second UE via the first set of resources or the second set of resources based on the occurrence of the at least one condition.

[0006] In one aspect of the present disclosure, a method, computer-readable medium, and apparatus for wireless communication at a second user equipment (UE) are provided. The apparatus includes a memory and at least one processor coupled to the memory, and based at least in part on information stored in the memory, the at least one processor is configured to: monitor side link (SL) data via a first set of resources, wherein the first set of resources is different from a second set of resources for a discontinuous reception (DRX) cycle of the second UE; and receive the SL data from the first UE via the first set of resources or the second set of resources based on the occurrence of at least one condition.

[0007] To achieve the aforementioned and related purposes, one or more aspects include the features fully described below and particularly pointed out in the claims. The following description and the accompanying drawings set forth in detail some exemplary features of one or more aspects. However, these features indicate only some of the various ways in which the principles of the various aspects can be employed. BRIEF DESCRIPTION OF THE DRAWINGS

[0008] Figure 1 is a diagram illustrating an example of a wireless communication system and an access network.

[0009] Figure 2A is a diagram illustrating an example of a first frame according to various aspects of the present disclosure.

[0010] Figure 2B is a diagram illustrating an example of downlink (DL) channels within a subframe according to various aspects of the present disclosure.

[0011] Figure 2C is a diagram illustrating an example of a second frame according to various aspects of the present disclosure.

[0012] Figure 2D is a diagram illustrating an example of uplink (UL) channels within a subframe according to various aspects of the present disclosure.

[0013] Figure 3 is a diagram illustrating an example of a base station and a user equipment (UE) in an access network.

[0014] Figure 4 is a diagram illustrating an example of a discontinuous reception (DRX) cycle.

[0015] Figure 5 is a diagram illustrating example communications between a first base station, a transmitting UE (Tx UE), a receiving UE (Rx UE), and a second base station for a sidelink DRX configuration.

[0016] Figure 6 is a diagram illustrating example communications between a Tx UE and an Rx UE for a sidelink DRX configuration.

[0017] Figure 7 is a diagram illustrating various example aspects of a listen-before-talk (LBT) process.

[0018] Figure 8 is a diagram illustrating an example of first level side link control information (SCI-1) and second level side link control information (SCI-2).

[0019] Fig. 9 is a diagram illustrating an example of a DRX on-duration and an extended DRX on-duration.

[0020] Fig.10 is a diagram illustrating examples of an offset, duration, cycle length, and cycle timer associated with an extended DRX On-Duration.

[0021] Fig.11 is a diagram illustrating an example of an extended DRX on-duration of a fixed length.

[0022] Fig.12 is a diagram illustrating an example of an extended DRX on-duration of a dynamic length.

[0023] Fig.13 is a diagram illustrating an example of implicit indication of extended DRX on-duration.

[0024] Fig.14 is a diagram illustrating an example of utilizing an extended DRX on-duration of a fixed length when Sidelink Control Information (SCI) is detected.

[0025] Fig.15 is a diagram illustrating an example of utilizing an extended DRX on-duration of a dynamic length when SCI is detected.

[0026] Fig.16 is a diagram illustrating example communications between a first UE and a second UE.

[0027] Fig.17 is a flow chart of a method of wireless communication.

[0028] Fig.18 is a flow chart of a method of wireless communication.

[0029] Fig.19 is a flow chart of a method of wireless communication.

[0030] Fig. 20 is a flow chart of a method of wireless communication.

[0031] Fig.21 is a diagram illustrating an example of a hardware implementation of an example apparatus.

[0032] Fig. 22 is a diagram illustrating an example of a hardware implementation of an example network entity. DETAILED DESCRIPTION

[0033] The first UE may be configured with a discontinuous reception (DRX) cycle, wherein the first UE may receive packets during the DRX on duration, and wherein the first UE may periodically enter a power saving mode when there is no notification of packet arrival from the base station. The first UE may also utilize the DRX cycle to perform sidelink communication with the second UE. When utilizing the DRX cycle in the sidelink, the Rx UE (e.g., the first UE) may apply restrictions so that resources are within the DRX on duration. If no resources are within the DRX on duration of the RxUE, the implementation of the Rx UE may determine whether the resources are added to the DRX on duration. In addition, in a sidelink unlicensed (SL-U) communication, the Tx UE (e.g., the second UE) may perform an LBT process before transmission. If the LBT process fails, the Tx UE may issue a resource reselection to the Rx UE, or the Tx UE may use a retransmission opportunity for initial transmission. Resource selection based on UE implementation may suffer from interference and may increase the probability of subsequent LBT failures. In addition, frequent resource reselection and / or insufficient resources may hinder throughput. Various techniques related to an enhanced sidelink DRX cycle are described herein. In one example, a first UE obtains a configuration associated with a DRX cycle of a second UE, wherein the configuration includes a first set of resources (e.g., resources associated with a DRX on duration of the second UE) and a first indication of at least one condition, wherein the first set of resources is different from a second set of resources for the DRX cycle of the second UE (e.g., resources associated with an extension of the DRX on duration). The first UE sends SL data to the second UE via the first set of resources or the second set of resources based on the occurrence of the at least one condition. Compared with this configuration, the above technology can improve the communication reliability between the first UE and the second UE. For example, the configuration can reduce the occurrence of resource reselection at the MAC layer and / or can reduce the use of retransmission opportunities for initial transmission. The configuration can also reduce the probability of LBT failure by reducing resource reselection.

[0034] The specific embodiments described below in conjunction with the accompanying drawings are descriptions of various configurations and do not represent the only configurations in which the concepts described herein can be practiced. In order to provide a thorough understanding of the various concepts, the specific embodiments include specific details. However, these concepts can be practiced without these specific details. In some cases, well-known structures and components are shown in block diagram form to avoid obscuring such concepts.

[0035] Several aspects of telecommunication systems are presented with reference to various apparatus and methods. These apparatus and methods are described in the following detailed description and illustrated in the accompanying drawings by various blocks, components, circuits, processes, algorithms, etc. (collectively referred to as "elements"). These elements may be implemented using electronic hardware, computer software, or any combination thereof. Whether these elements are implemented as hardware or software depends on the specific application and the design constraints imposed on the overall system.

[0036] As an example, an element, or any part of an element, or any combination of elements can be implemented as a "processing system", which includes one or more processors. Examples of processors include microprocessors, microcontrollers, graphics processing units (GPUs), central processing units (CPUs), application processors, digital signal processors (DSPs), reduced instruction set computing (RISC) processors, systems on chip (SoCs), baseband processors, field programmable gate arrays (FPGAs), programmable logic devices (PLDs), state machines, gating logic, discrete hardware circuits, and other suitable hardware configured to perform various functionalities described throughout the present disclosure. One or more processors in a processing system can execute software. Whether referred to as software, firmware, middleware, microcode, hardware description language, or other terms, software should be broadly interpreted as meaning instructions, instruction sets, codes, code segments, program codes, programs, subroutines, software components, applications, software applications, software packages, routines, subroutines, objects, executables, threads of execution, procedures, functions, or any combination thereof.

[0037] Thus, in one or more example aspects, specific implementations and / or use cases, the described functionality may be implemented in hardware, software, or any combination thereof. If implemented in software, the functionality may be stored or encoded as one or more instructions or codes on a computer-readable medium. Computer-readable media include computer storage media. Storage media may be any available media that can be accessed by a computer. As an example, such computer-readable media may include random access memory (RAM), read-only memory (ROM), electrically erasable programmable ROM (EEPROM), optical disk storage, magnetic disk storage, other magnetic storage devices, combinations of these types of computer-readable media, or any other medium that can be used to store computer-executable code in the form of instructions or data structures that can be accessed by a computer.

[0038] Although various aspects, specific implementations and / or use cases are described in this application by the illustration of some examples, additional or different aspects, specific implementations and / or use cases may be generated in many different arrangements and scenarios. The various aspects, specific implementations and / or use cases described herein can be implemented across many different platform types, devices, systems, shapes, sizes and packaging arrangements. For example, various aspects, specific implementations and / or use cases can be generated via integrated chip specific implementations and other devices based on non-module components (e.g., end-user devices, vehicles, communication equipment, computing equipment, industrial equipment, retail / purchase equipment, medical equipment, artificial intelligence (AI) enabled devices, etc.). Although some examples may or may not be specifically for use cases or applications, the described examples may have a wide range of applicability. Various aspects, specific implementations and / or use cases may be in the range from chip-level or modular components to non-modular, non-chip-level specific implementations, and further to the range of aggregated, distributed or original equipment manufacturer (OEM) devices or systems in conjunction with one or more technologies herein. In some actual settings, the equipment combined with the various aspects and features described may also include additional components and features for implementing and practicing the claimed and described aspects. For example, the transmission and reception of wireless signals necessarily include multiple components for analog and digital purposes (e.g., hardware components including antennas, RF chains, power amplifiers, modulators, buffers, processors, interleavers, adders / summers, etc.) The various techniques described herein can be practiced in a wide variety of devices of various sizes, shapes, and configurations, chip-level components, systems, distributed arrangements, aggregated or disaggregated components, end-user devices, etc.

[0039] The deployment of a communication system (such as a 5G NR system) can be arranged with various components or constituent parts in a variety of ways. In a 5G NR system or network, a network node, a network entity, a mobility element of a network, a radio access network (RAN) node, a core network node, a network element or network equipment (such as a base station (BS)) or one or more units (or one or more components) performing base station functions can be implemented in an aggregated or decomposed architecture. For example, a BS (such as a Node B (NB), an evolved NB (eNB), an NR BS, a 5G NB (e.g., a gNB), an access point (AP), a transmit receive point (TRP) or a cell, etc.) can be implemented as an aggregated base station (also called an independent BS or a monolithic BS) or a decomposed base station.

[0040] A converged base station may be configured to utilize a radio protocol stack physically or logically integrated within a single RAN node. A decomposed base station may be configured to utilize a protocol stack physically or logically distributed between two or more units, such as one or more central or centralized units (CUs), one or more distributed units (DUs), or one or more radio units (RUs). In some aspects, a CU may be implemented within a RAN node, and one or more DUs may be co-located with the CU, or alternatively, may be geographically or virtually distributed in one or more other RAN nodes. A DU may be implemented to communicate with one or more RUs. Each of a CU, a DU, and a RU may be implemented as a virtual unit, i.e., a virtual central unit (VCU), a virtual distributed unit (VDU), or a virtual radio unit (VRU).

[0041] Base station operation or network design may take into account the aggregated nature of base station functionality. For example, a disaggregated base station may be used in an integrated access backhaul (IAB) network, an open radio access network (O-RAN (network configuration such as that initiated by the O-RAN Alliance)), or a virtualized radio access network (vRAN, also known as a cloud radio access network (C-RAN)). Decomposition may include distributing functions across two or more units at various physical locations, as well as virtually distributing the functions of at least one unit, which may enable flexibility in network design. Various units of a disaggregated base station or disaggregated RAN architecture may be configured for wired or wireless communication with at least one other unit.

[0042] Figure 1 1 is a diagram 100 illustrating an example of a wireless communication system and an access network. The illustrated wireless communication system includes a disaggregated base station architecture. The disaggregated base station architecture may include one or more CUs 110 that may communicate directly with a core network 120 via a backhaul link, or indirectly with the core network 120 through one or more disaggregated base station units, such as a near real-time (near RT) RAN intelligent controller (RIC) 125 via an E2 link, or a non-real-time (non-RT) RIC 115 associated with a service management and orchestration (SMO) framework 105, or both. The CU 110 may communicate with one or more DUs 130 via corresponding midhaul links, such as an F1 interface. The DU 130 may communicate with one or more RUs 140 via corresponding fronthaul links. The RU 140 may communicate with corresponding UEs 104 via one or more radio frequency (RF) access links. In some implementations, a UE 104 may be served simultaneously by multiple RUs 140.

[0043] Each of the units (i.e., CU 110, DU 130, RU 140, and near-RT RIC 125, non-RT RIC 115, and SMO framework 105) may include or be coupled to one or more interfaces configured to receive or send signals, data, or information (collectively, signals) via a wired or wireless transmission medium. Each of the units or an associated processor or controller that provides instructions to the communication interfaces of these units may be configured to communicate with one or more of the other units via a transmission medium. For example, these units may include a wired interface configured to receive signals or send signals to one or more of the other units via a wired transmission medium. Additionally, these units may include a wireless interface that may include a receiver, transmitter, or transceiver (such as an RF transceiver) configured to receive and / or send signals to one or more of the other units via a wireless transmission medium.

[0044] In some aspects, CU 110 may host one or more higher layer control functions. Such control functions may include radio resource control (RRC), packet data convergence protocol (PDCP), service data adaptation protocol (SDAP), etc. Each control function may be implemented using an interface configured to communicate signals with other control functions hosted by CU 110. CU 110 may be configured to handle user plane functions (i.e., central unit-user plane (CU-UP)), control plane functions (i.e., central unit-control plane (CU-CP)), or a combination thereof. In some specific implementations, CU 110 may be logically divided into one or more CU-UP units and one or more CU-CP units. When implemented in an O-RAN configuration, the CU-UP unit may communicate bidirectionally with the CU-CP unit via an interface (such as an E1 interface). As needed, CU 110 may be implemented to communicate with DU 130 for network control and signaling.

[0045] DU 130 may correspond to a logical unit that includes one or more base station functions for controlling the operation of one or more RUs 140. In some aspects, DU 130 may host one or more of a radio link control (RLC) layer, a medium access control (MAC) layer, and one or more high physical (PHY) layers (such as modules for forward error correction (FEC) encoding and decoding, scrambling, modulation and demodulation, etc.) at least in part according to a functional split such as those defined by 3GPP. In some aspects, DU 130 may also host one or more low PHY layers. Each layer (or module) may be implemented using an interface that is configured to communicate signals with other layers (and modules) hosted by DU 130 or with control functions hosted by CU 110.

[0046] The lower layer functions may be implemented by one or more RUs 140. In some deployments, the RU 140 controlled by the DU 130 may correspond to a logical node that hosts RF processing functions or low PHY layer functions (such as performing fast Fourier transform (FFT), inverse FFT (iFFT), digital beamforming, physical random access channel (PRACH) extraction and filtering, etc.) or both based at least in part on functional splitting (such as lower layer functional splitting). In such an architecture, the RU 140 may be implemented to handle over-the-air (OTA) communications with one or more UEs 104. In some specific implementations, real-time and non-real-time aspects of control plane communications and user plane communications with the RU 140 may be controlled by the corresponding DU 130. In some scenarios, this configuration may enable the DU 130 and the CU 110 to be implemented in a cloud-based RAN architecture such as a vRAN architecture.

[0047] The SMO framework 105 may be configured to support RAN deployment and provisioning of non-virtualized network elements and virtualized network elements. For non-virtualized network elements, the SMO framework 105 may be configured to support the deployment of dedicated physical resources for RAN coverage requirements, which may be managed via an operation and maintenance interface (such as an O1 interface). For virtualized network elements, the SMO framework 105 may be configured to interact with a cloud computing platform (such as an open cloud (O-Cloud) 190) to perform network element lifecycle management (such as to instantiate virtualized network elements) via a cloud computing platform interface (such as an O2 interface). Such virtualized network elements may include, but are not limited to, CU 110, DU 130, RU 140, and near-RT RIC 125. In some specific implementations, the SMO framework 105 may communicate with hardware aspects of the 4G RAN, such as an open eNB (O-eNB) 111, via the O1 interface. In addition, in some specific implementations, the SMO framework 105 may communicate directly with one or more RUs 140 via the O1 interface. The SMO framework 105 may also include a non-RT RIC 115 configured to support the functionality of the SMO framework 105 .

[0048] The non-RT RIC 115 may be configured to include logic functions that enable non-real-time control and optimization of RAN elements and resources, artificial intelligence (AI) / machine learning (ML) (AI / ML) workflows including model training and updating, or policy-based guidance of applications / features in the near-RT RIC 125. The non-RT RIC 115 may be coupled to or in communication with the near-RT RIC 125 (such as via an A1 interface). The near-RT RIC 125 may be configured to include logic functions that enable near-real-time control and optimization of RAN elements and resources through data collection and actions on an interface (such as via an E2 interface) that connects one or more CUs 110, one or more DUs 130, or both, and the O-eNB with the near-RT RIC 125.

[0049] In some implementations, in order to generate an AI / ML model to be deployed in the near-RT RIC 125, the non-RT RIC 115 may receive parameters or external enrichment information from an external server. Such information may be utilized by the near-RT RIC 125 and may be received from a non-network data source or from a network function at the SMO framework 105 or the non-RT RIC 115. In some examples, the non-RT RIC 115 or the near-RT RIC 125 may be configured to tune RAN behavior or performance. For example, the non-RT RIC 115 may monitor long-term trends and patterns of performance and employ AI / ML models to perform corrective actions through the SMO framework 105 (such as via reconfiguration of O1) or via creation of RAN management policies (such as A1 policies).

[0050] At least one of the CU 110, the DU 130, and the RU 140 may be referred to as a base station 102. Therefore, the base station 102 may include one or more of the CU 110, the DU 130, and the RU 140 (each component is indicated by a dotted line to indicate that each component may be included in the base station 102 or may not be included in the base station). The base station 102 provides an access point to the core network 120 for the UE 104. The base station 102 may include a macro cell (a high-power cellular base station) and / or a small cell (a low-power cellular base station). Small cells include femto cells, pico cells, and micro cells. A network including both small cells and macro cells may be referred to as a heterogeneous network. A heterogeneous network may also include a home evolved Node B (eNB) (HeNB), which may provide services to a restricted group referred to as a closed subscriber group (CSG). The communication link between RU 140 and UE 104 may include uplink (UL) (also known as reverse link) transmission from UE 104 to RU 140 and / or downlink (DL) (also known as forward link) transmission from RU 140 to UE 104. The communication link may use multiple-input multiple-output (MIMO) antenna technology, including spatial multiplexing, beamforming and / or transmit diversity. The communication link may be through one or more carriers. For each carrier allocated in a carrier aggregation of up to Yx MHz (x component carriers) for transmission in each direction, the base station 102 / UE 104 may use a spectrum of up to Y MHz (e.g., 5MHz, 10MHz, 15MHz, 20MHz, 100MHz, 400MHz, etc.) bandwidth. These carriers may or may not be adjacent to each other. The allocation of carriers may be asymmetric with respect to DL and UL (e.g., more or fewer carriers may be allocated for DL ​​compared to UL). Component carriers may include a primary component carrier and one or more secondary component carriers. The primary component carrier may be referred to as a primary cell (PCell) and the secondary component carrier may be referred to as a secondary cell (SCell).

[0051] Some UEs 104 may communicate with each other using a device-to-device (D2D) communication link 158. The D2D communication link 158 may use DL / UL wireless wide area network (WWAN) spectrum. The D2D communication link 158 may use one or more sidelink channels, such as a physical sidelink broadcast channel (PSBCH), a physical sidelink discovery channel (PSDCH), a physical sidelink shared channel (PSSCH), and a physical sidelink control channel (PSCCH). The D2D communication may be through a variety of wireless D2D communication systems, such as, for example, Bluetooth, Wi-Fi based on the Institute of Electrical and Electronics Engineers (IEEE) 802.11 standard, LTE, or NR.

[0052] The wireless communication system may also include a Wi-Fi AP 150 that communicates with a UE 104 (also referred to as a Wi-Fi station (STA)) via a communication link 154, for example, in a 5 GHz unlicensed spectrum, etc. When communicating in an unlicensed spectrum, the UE 104 / AP 150 may perform a clear channel assessment (CCA) to determine whether a channel is available prior to communication.

[0053] The electromagnetic spectrum is typically subdivided into various categories, bands, channels, etc. based on frequency / wavelength. In 5G NR, two initial operating bands have been identified as frequency range designations FR1 (410 MHz-7.125 GHz) and FR2 (24.25 GHz-52.6 GHz). Although a portion of FR1 is greater than 6 GHz, FR1 is often referred to (interchangeably) as the “sub-6 GHz” band in various documents and articles. A similar naming issue sometimes occurs with respect to FR2, which is often (interchangeably) referred to as the “millimeter wave” band in documents and articles, despite being different from the extremely high frequency (EHF) band (30 GHz–300 GHz) that is identified as the “millimeter wave” band by the International Telecommunication Union (ITU).

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

[0055] In view of the above, unless otherwise specified, if the term "sub-6 GHz" or the like is used herein, it may broadly refer to frequencies that may be less than 6 GHz, may be within FR1, or may include mid-band frequencies. In addition, unless otherwise specified, if the term "millimeter wave" or the like is used herein, it may broadly refer to frequencies that may include mid-band frequencies, may be within FR2, FR4, FR2-2, and / or FR5, or may be within the EHF band.

[0056] The base station 102 and the UE 104 may each include multiple antennas (such as antenna elements, antenna panels, and / or antenna arrays) to facilitate beamforming. The base station 102 may send a beamformed signal 182 to the UE 104 in one or more transmit directions. The UE 104 may receive the beamformed signal from the base station 102 in one or more receive directions. The UE 104 may also send a beamformed signal 184 to the base station 102 in one or more transmit directions. The base station 102 may receive the beamformed signal from the UE 104 in one or more receive directions. The base station 102 / UE 104 may perform beam training to determine the best receive direction and transmit direction for each of the base station 102 / UE 104. The transmit direction and receive direction of the base station 102 may be the same or may not be the same. The transmit direction and receive direction of the UE 104 may be the same or may not be the same.

[0057] The base station 102 may include and / or be referred to as a gNB, a Node B, an eNB, an access point, a base transceiver station, a radio base station, a radio transceiver, a transceiver function, a basic service set (BSS), an extended service set (ESS), a transmit receive point (TRP), a network node, a network entity, a network equipment, or some other suitable term. The base station 102 may be implemented as an integrated access and backhaul (IAB) node, a relay node, a sidelink node, an aggregated (monolithic) base station with a baseband unit (BBU) (including a CU and a DU) and a RU, or as a decomposed base station including one or more of a CU, a DU, and / or a RU. A set of base stations that may include decomposed base stations and / or aggregated base stations may be referred to as a next generation (NG) RAN (NG-RAN).

[0058] The core network 120 may include an access and mobility management function (AMF) 161, a session management function (SMF) 162, a user plane function (UPF) 163, a unified data management (UDM) 164, one or more location servers 168, and other functional entities. AMF 161 is a control node that handles signaling between UE 104 and the core network 120. AMF 161 supports registration management, connection management, mobility management, and other functions. SMF 162 supports session management and other functions. UPF 163 supports packet routing, packet forwarding, and other functions. UDM 164 supports the generation of authentication and key agreement (AKA) credentials, user identity handling, access authorization, and subscription management. One or more location servers 168 are illustrated as including a gateway mobile location center (GMLC) 165 and a location management function (LMF) 166. However, in general, the one or more location servers 168 may include one or more location / positioning servers, which may include one or more of the GMLC 165, LMF 166, position determination entity (PDE), serving mobile location center (SMLC), mobile positioning center (MPC), etc. GMLC 165 and LMF 166 support UE location services. GMLC 165 provides an interface for clients / applications (e.g., emergency services) to access UE positioning information. LMF 166 receives measurement and assistance information from NG-RAN and UE 104 via AMF 161 to calculate the location of UE 104. NG-RAN may determine the location of UE 104 using one or more positioning methods. Positioning UE 104 may involve signal measurements, position estimation, and optional speed calculation based on these measurements. Signal measurements may be performed by UE 104 and / or serving base station 102. The measured signals may be based on a satellite positioning system (SPS) 170 (e.g., one or more of a global navigation satellite system (GNSS), a global positioning system (GPS), a non-terrestrial network (NTN), or other satellite positioning / positioning systems), LTE signals, wireless local area network (WLAN) signals, Bluetooth signals, a terrestrial beacon system (TBS), sensor-based information (e.g., an atmospheric pressure sensor, a motion sensor), an NR enhanced cell ID (NR E-CID) method, NR signals (e.g., multi-round trip time (multi-RTT), DL angle of departure (DL-AoD), DL time difference of arrival (DL-TDOA), UL time difference of arrival (UL-TDOA), and UL angle of arrival (UL-AoA) positioning), and / or one or more of other systems / signals / sensors.

[0059] Examples of UE 104 include cellular phones, smart phones, session initiation protocol (SIP) phones, laptops, personal digital assistants (PDAs), satellite radios, global positioning systems, multimedia devices, video devices, digital audio players (e.g., MP3 players), cameras, game consoles, tablet computers, smart devices, wearable devices, vehicles, electric meters, gas pumps, large or small kitchen appliances, healthcare equipment, implants, sensors / actuators, displays, or any other similarly functional devices. Some of the UEs 104 may be referred to as IoT devices (e.g., parking meters, gas pumps, toasters, vehicles, heart monitors, etc.). UE 104 may also be referred to as stations, mobile stations, subscriber stations, mobile units, subscriber units, wireless units, remote units, mobile devices, wireless devices, wireless communication devices, remote devices, mobile subscriber stations, access terminals, mobile terminals, wireless terminals, remote terminals, mobile phones, user agents, mobile clients, clients, or some other suitable terminology. In some scenarios, the term UE may also be applied to one or more supporting devices, such as in a device cluster arrangement. One or more of these devices may access the network collectively and / or individually.

[0060] Reference again Figure 1 , in some aspects, UE 104 may include a DRX component 198 configured to: obtain a configuration associated with a DRX cycle of a second UE, wherein the configuration includes a first indication of a first set of resources and at least one condition, wherein the first set of resources is different from a second set of resources for the DRX cycle of the second UE; and send SL data to the second UE via the first set of resources or the second set of resources based on the occurrence of the at least one condition. In some aspects, the DRX component 198 is configured to monitor SL data via a first set of resources, wherein the first set of resources is different from a second set of resources for the DRX cycle of the second UE; and receive the SL data from the first UE via the first set of resources or the second set of resources based on the occurrence of at least one condition. Although the following description may focus on 5G NR, the concepts described herein may be applicable to other similar fields, such as LTE, LTE-A, CDMA, GSM, and other wireless technologies.

[0061] Figure 2A FIG200 is a diagram illustrating an example of a first subframe within a 5G NR frame structure. Figure 2B FIG230 is a diagram illustrating an example of DL channels within a 5G NR subframe. Figure 2C FIG250 is a diagram illustrating an example of a second subframe within a 5G NR frame structure. Figure 2DFIG280 is a diagram illustrating an example of UL channels within a 5G NR subframe. The 5G NR frame structure may be frequency division duplex (FDD), where for a particular set of subcarriers (carrier system bandwidth), subframes within that subcarrier set are dedicated to either DL or UL, or may be time division duplex (TDD), where for a particular set of subcarriers (carrier system bandwidth), subframes within that subcarrier set are dedicated to both DL and UL. Figure 2A , Figure 2C In the example provided, the 5G NR frame structure is assumed to be TDD, where subframe 4 is configured with slot format 28 (most of which are DL), where D is DL, U is UL, and F is flexible between DL / UL, and subframe 3 is configured with slot format 1 (all of which are UL). Although subframes 3 and 4 are shown as having slot formats 1 and 28, respectively, any particular subframe may be configured with any of the various available slot formats 0-61. Slot formats 0 and 1 are full DL and full UL, respectively. Other slot formats 2-61 include a mix of DL, UL and flexible symbols. The UE is configured with the slot format through the received slot format indicator (SFI) (dynamically configured through DL control information (DCI) or semi-statically / statically configured through radio resource control (RRC) signaling). Note that the following description also applies to the 5G NR frame structure as TDD.

[0062] FIG. 2A to FIG. 2D The frame structure is illustrated, and various aspects of the present disclosure may be applicable to other wireless communication technologies that may have different frame structures and / or different channels. A frame (10ms) may be divided into 10 equally sized subframes (1ms). Each subframe may include one or more time slots. A subframe may also include a microslot, which may include 7, 4, or 2 symbols. Each time slot may include 14 or 12 symbols, depending on whether the cyclic prefix (CP) is normal or extended. For a normal CP, each time slot may include 14 symbols, and for an extended CP, each time slot may include 12 symbols. The symbol on the DL may be a CP orthogonal frequency division multiplexing (OFDM) (CP-OFDM) symbol. The symbol on the UL may be a CP-OFDM symbol (for high throughput scenarios) or a discrete Fourier transform (DFT) extended OFDM (DFT-s-OFDM) symbol (for power-constrained scenarios; limited to single-stream transmission). The number of time slots within a subframe is based on the CP and parameter set. The parameter set defines the subcarrier spacing (SCS) (see Table 1). Symbol length / duration can be scaled with 1 / SCS.

[0063]

[0064] Table 1: Parameter set, SCS and CP

[0065] For normal CP (14 symbols / slot), different parameter sets μ0 to 4 allow 1, 2, 4, 8, and 16 slots per subframe, respectively. For extended CP, parameter set 2 allows 4 slots per subframe. Thus, for normal CP and parameter set μ, there are 14 symbols / slot and 2 μ The subcarrier spacing may be equal to 2μ*15kHz, where μ is parameter set 0 to 4. Thus, the subcarrier spacing for parameter set μ=0 is 15kHz, and the subcarrier spacing for parameter set μ=4 is 240kHz. The symbol length / duration is inversely related to the subcarrier spacing. FIG. 2A to FIG. 2D An example is provided for a normal CP with 14 symbols per slot and a parameter set μ=2 with 4 slots per subframe. The slot duration is 0.25 ms, the subcarrier spacing is 60 kHz, and the symbol duration is about 16.67 μs. Within a frame set, there may be one or more different bandwidth parts (BWPs) that are frequency-division multiplexed (see Figure 2B ). Each BWP may have a specific parameter set and CP (normal or extended).

[0066] A resource grid may be used to represent the frame structure. Each slot includes a resource block (RB) (also referred to as a physical RB (PRB)) extending over 12 consecutive subcarriers. The resource grid is divided into a number of resource elements (REs). The number of bits carried by each RE depends on the modulation scheme.

[0067] like Figure 2A As illustrated, some of the REs carry reference (pilot) signals (RS) for the UE. The RS may include a demodulation RS (DM-RS) (indicated as R for one particular configuration, but other DM-RS configurations are possible) and a channel state information reference signal (CSI-RS) for channel estimation at the UE. The RS may also include a beam measurement RS (BRS), a beam refinement RS (BRRS), and a phase tracking RS (PT-RS).

[0068] Figure 2BExamples of various DL channels within a subframe of a frame are illustrated. A physical downlink control channel (PDCCH) carries DCI within one or more control channel elements (CCEs) (e.g., 1, 2, 4, 8, or 16 CCEs), each CCE including six RE groups (REGs), each REG including 12 consecutive REs in an OFDM symbol of an RB. A PDCCH within a BWP may be referred to as a control resource set (CORESET). The UE is configured to monitor PDCCH candidates in a PDCCH search space (e.g., a common search space, a UE-specific search space) during a PDCCH monitoring opportunity on a CORESET, wherein the PDCCH candidates have different DCI formats and different aggregation levels. Additional BWPs may be located at higher and / or lower frequencies on the channel bandwidth. A primary synchronization signal (PSS) may be within symbol 2 of a particular subframe of a frame. The PSS is used by UE 104 to determine subframe / symbol timing and physical layer identification. A secondary synchronization signal (SSS) may be within symbol 4 of a particular subframe of a frame. The SSS is used by the UE to determine the physical layer cell identity group number and the radio frame timing. Based on the physical layer identity and the physical layer cell identity group number, the UE can determine the physical cell identifier (PCI). Based on the PCI, the UE can determine the location of the DM-RS. The physical broadcast channel (PBCH) carrying the master information block (MIB) can be logically grouped with the PSS and SSS to form a synchronization signal (SS) / PBCH block (also referred to as an SS block (SSB)). The MIB provides the system frame number (SFN) and the number of RBs in the system bandwidth. The physical downlink shared channel (PDSCH) carries user data, broadcast system information not sent over the PBCH (such as the system information block (SIB)), and paging messages.

[0069] like Figure 2C As illustrated, some of the REs carry DM-RS (indicated as R for a particular configuration, but other DM-RS configurations are possible) for channel estimation at the base station. The UE may send a DM-RS for a physical uplink control channel (PUCCH) and a DM-RS for a physical uplink shared channel (PUSCH). The PUSCH DM-RS may be sent in the first or first two symbols of the PUSCH. Depending on whether a short PUCCH or a long PUCCH is sent and depending on the specific PUCCH format used, the PUCCH DM-RS may be sent in different configurations. The UE may send a sounding reference signal (SRS). The SRS may be sent in the last symbol of a subframe. The SRS may have a comb structure, and the UE may send the SRS on one of the comb structures in the comb structure. The SRS may be used by the base station for channel quality estimation to achieve frequency-dependent scheduling of the UL.

[0070] Figure 2DExamples of various UL channels within a subframe of a frame are illustrated. The PUCCH may be located at a position as indicated in one configuration. The PUCCH carries uplink control information (UCI), such as scheduling requests, channel quality indicators (CQI), precoding matrix indicators (PMI), rank indicators (RI), and hybrid automatic repeat request (HARQ) acknowledgement (ACK) (HARQ-ACK) feedback (i.e., one or more HARQ ACK bits indicating one or more ACKs and / or negative ACKs (NACKs)). The PUSCH carries data and may additionally be used to carry a buffer status report (BSR), a power headroom report (PHR), and / or UCI.

[0071] Figure 3 375. The Controller / Processor 375 is a block diagram of a base station 310 in an access network communicating with a UE 350. In the DL, Internet Protocol (IP) packets may be provided to a controller / processor 375. The controller / processor 375 implements layer 3 and layer 2 functionality. Layer 3 includes a radio resource control (RRC) layer, and layer 2 includes a service data adaptation protocol (SDAP) layer, a packet data convergence protocol (PDCP) layer, a radio link control (RLC) layer, and a medium access control (MAC) layer. The controller / processor 375 provides RRC layer functionality associated with broadcasting of system information (e.g., MIB, SIB), RRC connection control (e.g., RRC connection paging, RRC connection establishment, RRC connection modification, and RRC connection release), inter-radio access technology (RAT) mobility, and measurement configuration for UE measurement reporting; PDCP layer functionality associated with header compression / decompression, security (encryption, decryption, integrity protection, integrity verification), and handover support functions; RLC layer functionality associated with transfer of upper layer packet data units (PDUs), error correction through ARQ, concatenation, segmentation and reassembly of RLC service data units (SDUs), re-segmentation of RLC data PDUs, and reordering of RLC data PDUs; and MAC layer functionality associated with mapping between logical channels and transport channels, multiplexing of MAC SDUs onto transport blocks (TBs), demultiplexing of MAC SDUs from TBs, scheduling information reporting, error correction through HARQ, priority handling, and logical channel prioritization.

[0072] The transmit (TX) processor 316 and receive (RX) processor 370 implement layer 1 functionality associated with various signal processing functions. Layer 1 (which includes the physical (PHY) layer) may include error detection on the transport channel, forward error correction (FEC) coding / decoding of the transport channel, interleaving, rate matching, mapping to the physical channel, modulation / demodulation of the physical channel, and MIMO antenna processing. The TX processor 316 handles the mapping to the signal constellation based on various modulation schemes (e.g., binary phase shift keying (BPSK), quadrature phase shift keying (QPSK), M-order phase shift keying (M-PSK), M-order quadrature amplitude modulation (M-QAM)). The coded and modulated symbols may then be separated into parallel streams. Each stream may then be mapped to an OFDM subcarrier, multiplexed with a reference signal (e.g., pilot) in the time and / or frequency domain, and then combined together using an inverse fast Fourier transform (IFFT) to produce a physical channel carrying a time domain OFDM symbol stream. The OFDM stream is spatially pre-coded to generate multiple spatial streams. Channel estimates from a channel estimator 374 may be used to determine the coding and modulation schemes, as well as for spatial processing. Channel estimates may be derived from reference signals and / or channel state feedback sent by the UE 350. Each spatial stream may then be provided to a different antenna 320 via a separate transmitter 318Tx. Each transmitter 318Tx may modulate a radio frequency (RF) carrier for transmission using a corresponding spatial stream.

[0073] At the UE 350, each receiver 354Rx receives a signal through its corresponding antenna 352. Each receiver 354Rx recovers the information modulated onto the RF carrier and provides the information to a receive (RX) processor 356. The TX processor 368 and the RX processor 356 implement layer 1 functionality associated with various signal processing functions. The RX processor 356 can perform spatial processing on the information to recover any spatial stream destined for the UE 350. If multiple spatial streams are destined for the UE 350, they can be combined into a single OFDM symbol stream by the RX processor 356. The RX processor 356 then converts the OFDM symbol stream from the time domain to the frequency domain using a fast Fourier transform (FFT). The frequency domain signal includes a separate OFDM symbol stream for each subcarrier of the OFDM signal. The symbols on each subcarrier and the reference signal are recovered and demodulated by determining the most likely signal constellation point sent by the base station 310. These soft decisions can be based on channel estimates calculated by the channel estimator 358. The soft decisions are then decoded and deinterleaved to recover the data and control signals originally sent on the physical channel by base station 310. The data and control signals are then provided to controller / processor 359, which implements layer 3 and layer 2 functionality.

[0074] The controller / processor 359 may be associated with a memory 360 that stores program codes and data. The memory 360 may be referred to as a computer readable medium. In the UL, the controller / processor 359 provides demultiplexing between transport channels and logical channels, packet reassembly, decryption, header decompression, and control signal processing to recover IP packets. The controller / processor 359 is also responsible for error detection using ACK and / or NACK protocols to support HARQ operations.

[0075] Similar to the functionality described in conjunction with DL transmissions performed by the base station 310, the controller / processor 359 provides RRC layer functionality associated with system information (e.g., MIB, SIB) acquisition, RRC connection, and measurement reporting; PDCP layer functionality associated with header compression / decompression and security (encryption, decryption, integrity protection, integrity verification); RLC layer functionality associated with delivery of upper layer PDUs, error correction through ARQ, concatenation, segmentation and reassembly of RLC SDUs, resegmentation of RLC data PDUs, and reordering of RLC data PDUs; and MAC layer functionality associated with mapping between logical channels and transport channels, multiplexing of MAC SDUs onto TBs, demultiplexing of MAC SDUs from TBs, scheduling information reporting, error correction through HARQ, priority handling, and logical channel prioritization.

[0076] Channel estimates derived by the channel estimator 358 based on a reference signal or feedback sent by the base station 310 may be used by the TX processor 368 to select the appropriate coding and modulation schemes and to facilitate spatial processing. The spatial streams generated by the TX processor 368 may be provided to different antennas 352 via separate transmitters 354Tx. Each transmitter 354Tx may modulate an RF carrier with a corresponding spatial stream for transmission.

[0077] UL transmissions are processed at the base station 310 in a manner similar to that described in conjunction with the receiver functionality at the UE 350. Each receiver 318Rx receives a signal through its respective antenna 320. Each receiver 318Rx recovers information modulated onto an RF carrier and provides the information to the RX processor 370.

[0078] The controller / processor 375 may be associated with a memory 376 that stores program codes and data. The memory 376 may be referred to as a computer readable medium. In the UL, the controller / processor 375 provides demultiplexing between transport channels and logical channels, packet reassembly, decryption, header decompression, control signal processing to recover IP packets. The controller / processor 375 is also responsible for error detection using ACK and / or NACK protocols to support HARQ operations.

[0079] At least one of the TX processor 368, the RX processor 356, and the controller / processor 359 may be configured to perform operations related to Figure 1 Various aspects related to the DRX component 198.

[0080] Figure 4 400 is an example of an illustrated DRX cycle. When the UE is configured with a DRX cycle, the UE may not continuously monitor the PDCCH for PDCCH transmissions. The DRX cycle may be characterized by an on-duration and an inactivity timer. The on-duration may refer to the duration that the UE waits to receive a PDCCH transmission after waking up. If the UE successfully decodes a PDCCH transmission during the on-duration, the UE may remain awake and start the inactivity timer. The inactivity timer may refer to the duration that the UE waits to successfully decode a PDCCH transmission from the last successful decoding of a previous PDCCH transmission. If the UE does not successfully decode a PDCCH transmission during the duration of the inactivity timer, the UE may be placed in a dormant state. The UE may restart the inactivity timer after a single successful decoding of a PDCCH transmission. The UE may not restart the inactivity timer for retransmissions of a PDCCH transmission. If a SL UE is configured with a DRX cycle, a PDCCH providing SL permission may be transmitted to the UE during the UE's active time.

[0081] The UE may be configured with a (long) DRX cycle 404. During the long DRX on duration 402 of the (long) DRX cycle 404, the UE may monitor data (e.g., downlink data such as downlink control signaling, or sidelink data such as sidelink control signaling). In one example, the UE may monitor the PDCCH or PSCCH for transmissions during the long DRX on duration 402. If the UE successfully decodes a transmission (e.g., a PDCCH transmission or a PSCCH transmission) during the long DRX on duration 402, the UE may remain awake and start an inactivity timer 405 (e.g., specified in milliseconds). When the UE is not within the long DRX on duration 402 of the (long) DRX cycle 404, and if the UE does not successfully decode a transmission during the duration associated with the inactivity timer 405, the UE may sleep with the receiver circuitry turned off. This may allow for a reduction in the power consumption of the UE. In one example, a relatively longer DRX cycle may achieve a relatively greater reduction in power consumption compared to a relatively shorter DRX cycle.

[0082] In addition to the (long) DRX cycle 404, the UE may also be configured with a short DRX cycle 406. During the short DRX on duration 403 of the short DRX cycle 406, the UE may monitor transmissions (e.g., PDCCH transmissions or PSCCH transmissions). The short DRX cycle 406 may have a shorter duration than the (long) DRX cycle 404. In one example, the UE may follow the (long) DRX cycle 404 until the UE is scheduled for the short DRX cycle 406. In this example, the UE may follow the short DRX cycle 406 for a period of time (in addition to following the (long) DRX cycle 404). The (long) DRX cycle 404 may be associated with reduced power consumption; however, the (long) DRX cycle may be associated with increased latency in receiving data. When an inactivity timer expires (e.g., an inactivity timer 405), the short DRX cycle 406 may be activated. The short DRX cycle 406 may be associated with reducing latency in receiving data. The short DRX cycle 406 may be useful in Internet Protocol (IP) voice related scenarios.

[0083] The UE may be configured with a connected mode DRX (C-DRX) mechanism, which may enable the UE (e.g., a mobile UE) to periodically enter a power saving mode (i.e., a sleep mode). During the power saving mode, the UE may shut down the main circuit when there is no notification of packet arrival. The UE may wake up (i.e., leave the sleep mode) to periodically check for packet arrival. To prevent data loss, the UE and the network may have a predefined protocol regarding the periodic transition of the UE between a sleep state and a non-sleep state (i.e., a wake state). In one example, the UE may receive DRX configuration parameters in a DL RRC configuration message transmitted by the network (e.g., via a base station such as a gNB).

[0084] Figure 5 500 is a diagram illustrating example communications between a first base station 502, a Tx UE 504, an Rx UE 506, and a second base station 508 for a sidelink DRX configuration (e.g., a C-DRX sidelink configuration). The communications in diagram 500 may be associated with a unicast (i.e., negotiated between UEs) sidelink DRX configuration. In one example, the Tx UE 504 and / or the Rx UE 506 may be in an RRC connected state. At 510, the Rx UE 506 may send sidelink (SL) UE assistance information to the Tx UE 504. The SL UE assistance information may include an indication of one or more DRX cycle lengths, one or more DRX cycle offsets, and one or more DRX on durations. In other words, the SL UE assistance information may be a desired SL DRX configuration.

[0085] At 512, the Tx UE 504 may forward the SL UE assistance information to the first base station 502 (e.g., the first gNB). At 514, the first base station 502 may determine the SL DRX configuration for the Rx UE 506, and the first base station 502 may send the SL DRX configuration to the Tx UE 504. The first base station 502 may determine the SL DRX configuration for the Rx UE 506 based on the SL UE assistance information. In one aspect, at 516, the first base station 502 may align the SL DRX cycle with the DRX cycle of the Tx UE 504 (e.g., "aligning the SL DRX with the Tx UE UE-UTRAN (Uu) DRX").

[0086] At 518, the Tx UE 504 may send a SL DRX configuration (i.e., Rx UE SL DRX) to the Rx UE 506 via a PC-5 RRC message. PC-5 may refer to an interface for sidelink communication. The PC-5 interface may support SL vehicle-to-everything (V2X) communications for NR and LTE. At 520, the Rx UE 506 may send a message to the Tx UE 504 indicating whether the SL DRX configuration is accepted or rejected. At 522, if the SL DRX configuration is accepted by the Rx UE 506, the Rx UE 506 may send the SL DRX configuration to the second base station 508 (e.g., a second gNB). In one aspect, at 524, the second base station 508 may align the DRX cycle of the Rx UE 506 with the SLDRX cycle (e.g., "aligning the Rx UE Uu DRX with the SL DRX").

[0087] Figure 6 600 is a diagram illustrating an example communication between a Tx UE 504 and an Rx UE 506 for a sidelink DRX configuration. The communication in diagram 600 may be associated with a unicast (i.e., negotiated between UEs) sidelink DRX configuration. In one example, the Tx UE 504 and / or the Rx UE 506 may be in an RRC inactive state or an RRC idle state. In another example, the communication in diagram 600 may be applicable when the UE is in coverage (IC) or out of coverage (OoC) of a base station.

[0088] At 602, the Rx UE 506 may send SL UE assistance information to the Tx UE 504. The SL UE assistance information may include indications of one or more DRX cycle lengths, one or more DRX cycle offsets, and one or more DRX on durations. In other words, the SL UE assistance information may be the desired SL DRX configuration. At 604, the Tx UE 504 may determine the SL DRX configuration for the Rx UE 506. The Tx UE 504 may determine the SL DRX configuration based on the SL UE assistance information. The Tx UE 504 may determine the SL DRX configuration based on the implementation of the Tx UE 504 and / or the Rx UE 506. In one example, the implementation of the Rx UE 506 may be used to derive an inactivity timer associated with the SL DRX configuration. At 606, the Tx UE 504 may send the SL DRX configuration (i.e., Rx UE SL DRX) to the Rx UE 506 via a PC-5RRC message. At 608 , the Rx UE 506 may send a message to the Tx UE 504 indicating whether the SL DRX configuration is accepted or rejected.

[0089] Figure 7 700 is a diagram illustrating various example aspects associated with an LBT procedure. Diagram 700 includes a first example 702 depicting an LBT procedure. During the LBT procedure, the UE may avoid transmitting data 704 when the channel is unavailable, i.e., the UE may monitor the channel and determine that the channel is unavailable based on the monitoring. The LBT procedure may be used for sidelink communications between UEs. The LBT procedure may be a type 1 LBT procedure, which may be used to initiate one or more transmissions with the same channel occupancy time (COT).

[0090] When the UE determines that the channel is available at least within the delay period 706, the UE may initiate a backoff process 708. In one example, the delay period 706 may be within the range of 16+9*n. In one example, for the downlink, n may be 1, 3, or 7, and for the uplink, n may be 2, 3, or 7. In one example, n may be specified in a downlink channel access priority class (CAPC) table or an uplink CAPC table. If the energy received during the delay period is less than a threshold, the UE may determine that the channel is available. The backoff process 708 may include initializing a backoff counter with a random number within a contention window (CW). The random number may be within the range from zero to CW. The random number may represent the duration that the channel is available before data can be sent through the channel. The backoff counter may be decremented at specific intervals. Whenever the backoff counter is decremented, the UE may determine whether the channel is idle (i.e., whether the channel is available) within the time period. If the channel is idle, the backoff counter may be decremented again. If the channel is not idle, the UE may wait until the channel is idle before resuming the backoff counter. When the backoff counter reaches zero, the UE may proceed with data transmission 710 .

[0091] Diagram 700 also includes a second example 712 depicting an example of a COT 714. After a successful dynamic or semi-static channel access procedure, the channel may be used during the COT 714. During the COT 714, one or more transmit bursts (e.g., for uplink or downlink) may be exchanged between devices (e.g., between UEs).

[0092] The second example 712 depicts a first transmit burst 716 and a second transmit burst 718 that may be separated by a gap 720. Depending on the size of the gap 720, the UE may utilize different types of channel access procedures (e.g., different types of Type 2 LBT procedures). The second example 712 depicts a table 722 detailing the gap sizes and corresponding Type 2 LBT procedures. If the size of the gap 720 is greater than or equal to 25 μs, the device (e.g., UE) may utilize a Type 2A LBT procedure. In one example, the device (e.g., a base station such as a gNB) may send a DL transmission immediately after sensing that the channel is idle for a sensing interval of 25 μs. If the size of the gap 720 is greater than or equal to 16 μs and less than 25 μs, the device may utilize a cyclic prefix (CP) extension to maintain a 16 μs gap, and the device may utilize a Type 2B LBT procedure. In one example, the device (e.g., a base station such as a gNB) may send a DL transmission immediately after sensing that the channel is idle for a duration of 16 μs. If the size of the gap 720 is less than or equal to 16 μs, the device may utilize a Type 2C LBT procedure. In one example, if a device (e.g., a base station such as a gNB) follows a Type 2C LBT procedure, the device may not sense the channel prior to a DL transmission. A DL transmission may have a duration less than or equal to 584 μs.

[0093] In one example, a type 1 LBT process may be performed prior to the transmission of the first transmit burst 716. A type 2A, type 2B, or type 2C LBT process may be performed prior to the transmission of the second transmit burst 718 based on the size of the gap 720. In one example, the first transmit burst 716 may be a downlink transmission, and the second transmit burst 718 may be an uplink transmission. In another example, the first transmit burst 716 and the second transmit burst 718 may be communications exchanged between UEs in sidelink communications. In addition, type 2A, type 2B, and type 2C LBT processes may be used for sidelink communications between UEs.

[0094] Figure 8 800 is a diagram illustrating an example of SCI-1 802 and SCI-2 804. SCI-1 802 may be referred to as a first level SCI, and SCI-2 804 may be referred to as a second level SCI. SCI-1 802 may also be referred to as "SCI format 1," and SCI-2 804 may also be referred to as "SCI format 2." In general, SCI-1 802 may include information that may be used by a UE to decode information in SCI-2 804.

[0095] SCI-1 802 may be carried on a PSCCH associated with a PSSCH. SCI-1 802 may include information for demodulation / detection of the PSSCH. SCI-1 802 may include a priority indication 806. SCI-1 802 may include an indication of a frequency resource assignment 808 for the UE. SCI-1 802 may include an indication of a time resource assignment 810. SCI-1 802 may include an indication of a resource reservation period 812. SCI-1 802 may include an indication of a DM-RS pattern 814. SCI-1 802 may include an indication of an SCI-2 format 816 of an SCI-2 (e.g., SCI-2 804) to be received. In one example, SCI-2 804 may be one of a plurality of formats, and SCI-2 format 816 may indicate such a format. SCI-1 802 may include a modulation and coding scheme 818. SCI-1 802 may include a reserved portion 820. The SCI-1 802 may include a beta offset indicator 822. The SCI-1 802 may include a DM-RS port number 824.

[0096] The SCI-2 804 may be carried on the PSSCH. The SCI-2 804 may include a HARQ process identifier (ID) 826. The SCI-2 804 may include a new data indicator 828. The SCI-2 804 may include an indication of a redundancy version 830. The SCI-2 804 may include a source ID 832 corresponding to a UE that is a source of the SCI-2 804 (i.e., a UE that sends the SCI-2 804). The SCI-2 804 may include a destination ID 834 corresponding to a UE (or a group of UEs) that is an intended destination of the SCI-2 804 (i.e., a UE that will receive the SCI-2 804). The SCI-2 804 may include a channel state information (CSI) request 836.

[0097] As described above, the UE may use the C-DRX cycle for sidelink communication in order to save power. When the physical layer is indicated from the medium access control (MAC) layer for candidate resource selection during the active time of the Rx UE, restrictions may be applied in the physical layer so that at least a subset of the candidate resources reported to the MAC layer may be located within the indicated active time of the Rx UE. If the candidate resource is not within the active time of the Rx UE, the Rx UE may add at least one resource (e.g., based on the implementation of the Rx UE) during the active time. In an unlicensed band sidelink (SL-U), the UE may perform an LBT process before transmission. In one example, the UE may first select a set of resources (e.g., time and frequency resources), and the UE may then fail the LBT procedure, which may trigger an LBT failure at the MAC layer of the UE. The UE may handle the LBT failure in different ways. In a first example, the UE may handle the LBT failure by issuing a resource reselection at the MAC layer. In a second example, the UE may handle the LBT failure by using a retransmission opportunity for initial transmission. If C-DRX is used in SL-U, the resources selected by the UE implementation may be affected by interference. Therefore, the probability of failure of the LBT process may be higher.In addition, frequent resource reselection and / or resource shortage may hinder the throughput at the UE.

[0098] Various techniques related to an enhanced sidelink DRX cycle are described herein. In one example, a first UE obtains a configuration associated with a DRX cycle of a second UE, wherein the configuration includes a first set of resources (e.g., resources associated with a DRX on duration of the second UE) and a first indication of at least one condition, wherein the first set of resources is different from a second set of resources for the DRX cycle of the second UE (e.g., resources associated with an extension of the DRX on duration). The first UE sends SL data to the second UE via the first set of resources or the second set of resources based on the occurrence of the at least one condition. Compared with this configuration, the above technology can improve the communication reliability between the first UE and the second UE. For example, the configuration can reduce the occurrence of resource reselection at the MAC layer and / or can reduce the use of retransmission opportunities for initial transmission. The configuration can also reduce the probability of LBT failure by reducing resource reselection.

[0099] Fig. 9900 is a diagram illustrating an example of a DRX on-duration and an extended DRX on-duration. Diagram 900 depicts DRX cycle n, DRX cycle n+1, and DRX cycle n+2, where n is an integer. The Tx UE may select a set of additional candidate resources as an alternative in the resource selection process within the extended DRX on-duration. When an implicit indication is met in the DRX on-duration, the DRX on-duration extension may be activated. If the Tx UE fails the LBT procedure or the Tx UE does not have sufficient resources for transmission, the DRX on-duration extension may be activated, and the Tx UE may communicate with the Rx UE using the additional candidate resources without utilizing resource reselection. If the LBT procedure fails before the selected resource in the extended DRX on-duration, the Tx UE may trigger resource reselection.

[0100] As shown in diagram 900, at 906, the Rx UE (e.g., Rx UE 506) may detect SCI within the DRX on duration 902. In one example, the DRX on duration 902 may correspond to the above-mentioned long DRX on duration 402. Therefore, the extended DRX on duration 904 may not be activated. In other words, when the implicit condition is not met, the extended DRX on duration 904 may not be activated.

[0101] At 908, the Rx UE may not detect the SCI during the DRX On Duration 902. Therefore, at 910, the extended DRX On Duration 904 may be activated. In other words, when an implicit condition (e.g., failure to detect the SCI) is met, the extended DRX On Duration 904 may be activated. The Rx UE and the Tx UE (e.g., the Tx UE 504) may communicate via resources associated with the extended DRX On Duration 904 without utilizing resource reselection.

[0102] In one example, at 912, the Rx UE may not detect SCI during the DRX On Duration 902. Therefore, at 914, the extended DRX On Duration 904 may be activated. In other words, when an implicit condition (e.g., failure to detect SCI) is met, the extended DRX On Duration 904 may be activated. In this example, at 916, during the extended DRX On Duration 904, the LBT procedure may fail. In this example, at 918, the Tx UE may trigger resource reselection based on the failure of the LBT procedure.

[0103] Fig.101 is a diagram 1000 showing an example of an offset 1002, a duration 1004, a cycle length 1006, and a cycle timer 1008 associated with an extended DRX On Duration 904. The offset 1002 may refer to a time difference between a start point of the extended DRX On Duration 904 and a start point of the DRX On Duration 902. The duration 1004 may refer to an active time of the extended DRX On Duration 904. The cycle length 1006 may refer to a period of the extended DRX On Duration 904. The cycle timer 1008 may refer to the number of DRX On Duration extensions between two DRX On Durations. In one example, the cycle timer 1008 may be equal to three. Multiple DRX On Duration extensions may be associated with an LBT diversity gain that may mitigate LBT failures.

[0104] Fig.11 1100 is a diagram illustrating an example of an extended DRX on duration of a fixed length. The extended DRX on duration 904 may be configured via a PC-5 RRC configuration message. In one example, the PC-5 RRC configuration message may indicate the offset 1002, duration 1004, cycle length 1006, and / or cycle timer 1008 described above. In one example, a Tx UE (e.g., Tx UE 504) may determine the extended DRX on duration 904 of an associated Rx UE (e.g., Rx UE 506).

[0105] The time period (i.e., duration) of the extended DRX on duration 904 may be fixed. In one example, the time period of the extended DRX on duration 904 may be directly configured via a parameter in a PC-5 RRC configuration message. When an implicit indication (e.g., condition) is met within the DRX on duration 902, the Rx UE may immediately extend the DRX on duration with a value from the PC-5 RRC configuration message.

[0106] As shown in diagram 1100, an implicit indication may occur at 1102. In other words, a condition may occur at 1102. In response to the implicit indication, the UE (e.g., Rx UE 506) may activate the extended DRX on-duration 904. The extended DRX on-duration 904 may be based on the PC-5 RRC configuration value 1104.

[0107] Fig.121200 is a diagram illustrating an example of an extended DRX on duration of dynamic length. The time period (i.e., duration) of the extended DRX on duration 904 may be changed dynamically. In one example, the time period of the total active time may be configured via a parameter in a PC-5 RRC configuration message. When an implicit indication is met (e.g., when a condition occurs), in the DRX on duration 902, the Rx UE (e.g., Rx UE 506) may extend the DRX on duration 902 according to the following equation (I).

[0108] (I)T DRX_Extension =T Configured_DRX -T Active_in_DRX_on-duration

[0109] In equation (I), T DRX_Extension The extended DRX on-duration 904 may refer to a time period (ie, duration), T Configured_DRX may refer to a time period (ie, duration) of the DRX on-duration configured via a PC-5 RRC message, and T Active_in_DRX_on-duration It may refer to the amount of time spent in the DRX On Duration 902 when the implicit indication occurs. The total active time in the DRX On Duration 902 and the extended DRX On Duration 904 may be equal to the configured DRX On Duration.

[0110] As shown in diagram 1200, an implicit indication may occur at 1202 within the DRX On Duration 902. In other words, a condition may occur at 1202. In response to the implicit indication, the UE (e.g., Rx UE 506) may extend the DRX On Duration based on the PC-5 RRC configuration value 1204 according to equation (1) above.

[0111] Fig.13 1300 is a diagram illustrating an example of an extended DRX on-duration implicit indication 1302. The extended DRX on-duration implicit indication 1302 may be referred to as a “condition” or an “implicit condition”. The extended DRX on-duration implicit indication 1302 may include a first implicit indication 1304, a second implicit indication 1306, a third implicit indication 1308, a fourth implicit indication 1310, and a fifth implicit indication 1312. When the indication in the extended DRX on-duration implicit indication 1302 occurs / is satisfied, the UE may extend the DRX on-duration, i.e., the UE may activate the extended DRX on-duration (e.g., the extended DRX on-duration 904).

[0112] In the first implicit indication 1304, the Rx UE (e.g., Rx UE 506) may fail to detect SCI-2 (e.g., SCI-2 804) during the DRX on duration (e.g., DRX on duration 902), wherein the source ID of SCI-2 (e.g., source ID 832) matches the Tx UE (e.g., Tx UE 504). When the first implicit indication 1304 occurs / satisfied, the Rx UE may extend the DRX on duration after the end point of the DRX on duration. In one example, the Rx UE may extend the DRX on duration as described above. Fig.11 or Fig.12 The DRX on duration is extended as described in the description of .

[0113] In the second implicit indication 1306, the Rx UE (e.g., Rx UE 506) may fail to detect SCI-2 (e.g., SCI-2 804) during the DRX on duration (e.g., DRX on duration 902), wherein the source ID (e.g., source ID 832) of SCI-2 matches the Tx UE (e.g., Tx UE 504), and the destination ID (e.g., destination ID 834) matches the Rx UE. When the second implicit indication 1306 occurs / satisfied, the Rx UE may extend the DRX on duration after the end point of the DRX on duration. In one example, the Rx UE may extend the DRX on duration as described above. Fig.11 or Fig.12 The DRX on duration is extended as described in the description of .

[0114] In the third implicit indication 1308, the Rx UE (e.g., Rx UE 506) may fail to detect SCI-1 (e.g., SCI-1 802) during the DRX on duration (e.g., DRX on duration 902). When the third implicit indication 1308 occurs / satisfied, the Rx UE may extend the DRX on duration after the end point of the DRX on duration. In one example, the Rx UE may Fig.11 or Fig.12 The DRX on duration is extended as described in the description of .

[0115] The third implicit indication 1308 may be associated with fewer UE wake-ups than the first implicit indication 1304 and / or the second implicit indication 1306. The third implicit indication 1308 may be associated with fewer radio wake-ups than the first implicit indication 1304 and the second implicit indication 1306. The third implicit indication 1308 may be used for inter-radio access technology (inter-RAT) contention. In SL-U, if the Tx UE is able to perform a transmission, the Tx UE may transmit SCI-1. However, if the Wi-Fi radio acquires a channel, the Tx UE may not transmit a SL-U transmission, and the Tx UE may not transmit SCI-1, and the Rx UE may extend the DRX on duration. If the extended DRX on duration is longer than the transmission end point associated with the Wi-Fi transmission, the SL-U device transmitting in the SL-U may perform the transmission and thereby reduce latency. If the SL-U UE detects SCI-1, at least one SL-U UE (e.g., UE A) may be transmitting and there may be no Wi-Fi transmission. In one example, if there is relaxed COT sharing, UE A can share the COT with the intended transmitter (e.g., UE B) so that UE B can perform transmission to the Rx UE in the DRX on duration without extending the DRX on duration.

[0116] In the fourth implicit indication 1310, the Rx UE (e.g., Rx UE 506) may detect SCI-2 (e.g., SCI-2 804) during the DRX on duration (e.g., DRX on duration 902), wherein the source ID of SCI-2 (e.g., source ID 832) matches the Tx UE (e.g., Tx UE 504). When the fourth implicit indication 1310 occurs / satisfied, the Rx UE may activate the DRX on duration extension (e.g., the extended DRX on duration 904). In one example, the Rx UE may, as described above, Fig.11 or Fig.12 The DRX on-duration is extended as described in the description of . The Rx UE may monitor the SCI (eg, the second SCI-2) until the extended DRX on-duration ends.

[0117] In the fifth implicit indication 1312, the Rx UE (e.g., Rx UE 506) may detect SCI-2 (e.g., SCI-2 804) during the DRX on duration (e.g., DRX on duration 902), wherein the source ID (e.g., source ID 832) of SCI-2 matches the Tx UE (e.g., Tx UE 504), and the destination ID (e.g., destination ID 834) matches the Rx UE. When the fifth implicit indication 1312 occurs / satisfied, the Rx UE may activate the DRX on duration extension (e.g., the extended DRX on duration 904). In one example, the Rx UE may, as described above, Fig.11 or Fig.12 The DRX on-duration is extended as described in the description of . The Rx UE may monitor the SCI (eg, the second SCI-2) until the extended DRX on-duration ends.

[0118] Fig.14 1400 is a diagram illustrating an example of utilizing an extended DRX on-duration of a fixed length when SCI is detected. Aspects of diagram 1400 may correspond to the fourth implicit indication 1310 or the fifth implicit indication 1312 described above. For an extended DRX on-duration of a fixed length (e.g., such as described above in Fig.11 ), the Rx UE (e.g., the Rx UE 506) may activate the first extended DRX on duration 1408 immediately after detecting the first SCI-2 at 1402. If the Rx UE detects the second SCI-2 at 1404 (during the DRX on duration 902 or during the first extended DRX on duration 1408), the Rx UE may activate the second extended DRX on duration 1410. The first extended DRX on duration 1408 and the second extended DRX on duration 1410 may be based on the PC-5 RRC configuration value 1406.

[0119] Fig.15 FIG1500 is a diagram illustrating an example of utilizing an extended DRX on-duration of a dynamic length when SCI is detected. Aspects of diagram 1500 may correspond to the fourth implicit indication 1310 or the fifth implicit indication 1312 described above. Fig.12In the example of FIG. 1500 , the Rx UE (e.g., the Rx UE 506) may activate the extended DRX on duration 904 at the end of the DRX on duration 902. In the example depicted in FIG. 1500 , the Rx UE may receive a first SCI-2 at 1502 and a second SCI-2 at 1504. The active time in the DRX on duration may be determined based on the first SCI-2 (i.e., the first detected SCI-2). The extended DRX on duration 904 may be based on the PC-5 RRC configuration value 1506.

[0120] Fig.16 1600 is a diagram illustrating an example communication between a first UE 1602 and a second UE 1604. In one example, the first UE 1602 may be a Tx UE 504 and the second UE 1604 may be a Rx UE 506.

[0121] At 1608, the first UE 1602 may obtain a configuration associated with a DRX cycle of the second UE 1604. The configuration may indicate a first resource and a second resource (e.g., a time resource and a frequency resource). The configuration may also indicate a condition (i.e., an implicit indication). The condition may be or include one or more of the extended DRX on duration implicit indications 1302. In one example, the first resource may be associated with a DRX on duration (e.g., DRX on duration 902), and the second resource may be associated with an extension of the DRX on duration (e.g., extended DRX on duration 904). In one aspect, at 1610, the first UE 1602 may send the configuration to the second UE 1604.

[0122] At 1612, the first UE 1602 may send an indication of the condition (e.g., an implicit indication) via an SCI or PC-5 RRC message. In one example, if the condition corresponds to the first implicit indication 1304, the second implicit indication 1306, the fourth implicit indication 1310, or the fifth implicit indication 1312, the first UE 1602 may send an indication of the condition via SCI-2. In another example, if the condition corresponds to the first implicit indication 1304, the second implicit indication 1306, the third implicit indication 1308, the fourth implicit indication 1310, or the fifth implicit indication 1312, the first UE 1602 may send an indication of the condition via a PC-5 RRC configuration message. At 1614, the second UE 1604 may monitor SL data from the first UE 1602 via the first resource. The second UE 1604 may monitor SL data based on the configuration. In one example, monitoring the SL data via the first resource may include monitoring the SL data during a DRX on-duration (eg, the DRX on-duration 902 ).

[0123] At 1616, the second UE detects an occurrence of a condition. The condition may be or include one or more of the extended DRX on duration implicit indication 1302. In a first example, at 1616A, the second UE 1604 may fail to detect SCI-2 (e.g., SCI-2 804). For example, the second UE 1604 may fail to detect SCI-2 during the DRX on duration (e.g., DRX on duration 902). In a second example, at 1616B, the second UE 1604 may fail to detect SCI-1 (e.g., SCI-1 802). For example, the second UE 1604 may fail to detect SCI-1 during the DRX on duration (e.g., DRX on duration 902). In a third example, at 1616C, the second UE 1604 may detect SCI-2 (e.g., SCI-2 804). For example, the second UE 1604 may detect SCI-2 during the DRX on duration (e.g., the DRX on duration 902). In one aspect, at 1618, the second UE 1604 may determine a time period for an extension of the DRX on duration (e.g., the extended DRX on duration 904). In one example, the second UE 1604 may determine the time period for an extension of the DRX on duration (e.g., the extended DRX on duration 904). Fig.12 In one aspect, at 1620, the second UE 1604 may use an extended time period for the DRX on duration, where the time period may be included in the configuration. In one example, the second UE 1604 may utilize an extension of a fixed length of the DRX on duration, as described above in Fig.11As described in the description.

[0124] At 1622, the second UE 1604 may monitor SL data via the second resource. The second resource may be associated with an extension of the DRX on duration (e.g., the extended DRX on duration 904). The second resource may be associated with the time period determined at 1618 or the time period used from the configuration at 1620. At 1624, the first UE 1602 may send SL data via the first resource or the second resource. In one example, the SL data may include SL control signaling.

[0125] Fig.17 1700 is a flow chart of a method of wireless communication. The method may be performed by a first UE (e.g., UE 104, UE 350, Tx UE 504, first UE 1602, device 2104). The method may be associated with various advantages at the first UE, such as improving communication reliability with a second UE. For example, the method may be associated with reduced resource reselection by the first UE. In one example, the method may be performed by DRX component 198.

[0126] At 1702, the first UE obtains a configuration associated with a DRX cycle of a second UE, wherein the configuration includes a first indication of a first set of resources and at least one condition, wherein the first set of resources is different from a second set of resources for the DRX cycle of the second UE. Fig.16 At 1608, it is shown that the first UE 1602 can obtain a configuration associated with a DRX cycle of the second UE 1604, wherein the configuration indicates a first resource and a second resource. In one example, the DRX cycle can be Figure 4 The (long) DRX cycle 404 is shown. In another example, the DRX cycle may be Fig. 9 In one example, the at least one condition may be one or more of the extended DRX on-duration implicit indications 1302. In one example, 1702 may be performed by the DRX component 198.

[0127] At 1704, the first UE sends SL data to the second UE via the first set of resources or the second set of resources based on the occurrence of the at least one condition. Fig.16 At 1624, it is shown that the first UE 1602 can send SL data to the second UE 1604 via the first resource or the second resource. In one example, 1704 can be performed by the DRX component 198.

[0128] Fig.181800 is a flow chart of a method of wireless communication. The method may be performed by a first UE (e.g., UE 104, UE 350, Tx UE 504, first UE 1602, device 2104). The method may be associated with various advantages at the first UE, such as improving communication reliability with a second UE. For example, the method may be associated with reduced resource reselection by the first UE. In one example, the method (including various aspects described below) may be performed by a DRX component 198.

[0129] At 1802, a first UE obtains a configuration associated with a DRX cycle of a second UE, wherein the configuration includes a first indication of a first set of resources and at least one condition, wherein the first set of resources is different from a second set of resources for the DRX cycle of the second UE. Fig.16 At 1608, it is shown that the first UE 1602 can obtain a configuration associated with a DRX cycle of the second UE 1604, wherein the configuration indicates a first resource and a second resource. In one example, the DRX cycle can be Figure 4 The (long) DRX cycle 404 is shown. In another example, the DRX cycle may be Fig. 9 In one example, the condition may be one or more of the extended DRX on-duration implicit indications 1302. In one example, 1802 may be performed by the DRX component 198.

[0130] At 1806, the first UE sends SL data to the second UE via the first set of resources or the second set of resources based on the occurrence of the at least one condition. Fig.16 At 1624, it is shown that the first UE 1602 can send SL data to the second UE 1604 via the first resource or the second resource. In one example, 1806 can be performed by the DRX component 198.

[0131] In one aspect, the first set of resources may be associated with a DRX on duration of the second UE, wherein the second set of resources may be associated with an extension of the DRX on duration. For example, the first set of resources may be associated with the DRX on duration 902, and the second set of resources may be associated with the extended DRX on duration 904.

[0132] In one aspect, the extension of the DRX on-duration may be triggered by a second indication. Fig.16 1616A shows that the extension of the DRX on duration can be triggered by the SCI-2 not being detected. In another example, Fig.161616B shows that the extension of the DRX on duration can be triggered by the SCI-1 not being detected. In another example, Fig.16 1616C shows that the extension of the DRX on-duration may be triggered by the detection of SCI-2.

[0133] In one aspect, the second set of resources may be activated based on the second indication.For example, resources corresponding to the extended DRX on-duration 904 may be activated based on the second indication.

[0134] In one aspect, the extended time period of the DRX on-duration may be included in the configuration, or the extended time period of the DRX on-duration may be based on a difference between a first time period of the configured DRX on-duration and a second time period corresponding to an active time in the DRX on-duration. For example, the configuration obtained by the first UE 1602 may include the extended time period of the DRX on-duration. In another example, Fig.11 The extended time period of DRX on duration 904 may be fixed. In yet another example, Fig.12 It is shown that the extended time period of the DRX On Duration 904 may be dynamic and based on the implicit indication occurring at 1202 and the PC-5 RRC configuration value 1204 .

[0135] In one aspect, the at least one condition may include: the second UE does not detect SCI-1 during the DRX on duration, the second UE does not detect SCI-2 during the DRX on duration, or the second UE detects SCI-2 during the DRX on duration. Fig.16 At 1616A, it is shown that the condition may include that SCI-2 is not detected. In another example, Fig.16 At 1616B, it is shown that the condition may include that SCI-1 is not detected. In another example, Fig.16 At 1616C, it is shown that the condition may include SCI-2 being detected. In another example, SCI-1 may be SCI-1 802, and SCI-2 may be SCI-2 804. In another example, the at least one condition may be one or more of the first implicit indication 1304, the second implicit indication 1306, the third implicit indication 1308, the fourth implicit indication 1310, or the fifth implicit indication 1312.

[0136] In one aspect, SCI-2 may include a second indication of a source ID corresponding to the first UE. For example, Fig.13 It is shown that in the first implicit indication 1304, the source ID of SCI-2 can match the Tx UE (e.g., the first UE 1602). In another example, Fig.13It is shown that in the fourth implicit indication 1310 , the source ID of SCI-2 may match the Tx UE. In another example, the source ID may be the source ID 832 of SCI-2 804 .

[0137] In one aspect, SCI-2 may include a second indication of a source ID corresponding to the first UE and a destination ID corresponding to the second UE. Fig.13 It is shown that in the second implicit indication 1306, the source ID of SCI-2 can match the Tx UE (e.g., the first UE 1602), and the destination ID of SCI-2 can match the Rx UE (e.g., the second UE 1604). In another example, Fig.13 It is shown that in the fifth implicit indication 1312, the source ID of SCI-2 can match the Tx UE and the destination ID of SCI-2 can match the Rx UE. In another example, the source ID can be the source ID 832 of SCI-2 804 and the destination ID can be the destination ID 834.

[0138] In one aspect, the extension of the DRX on duration may be activated immediately when the second UE detects SCI-2 during the DRX on duration, or the extension of the DRX on duration may be activated when the second UE detects SCI-2 during the DRX on duration and after the DRX on duration has expired. Fig.14 It is shown that the first extended DRX on-duration 1408 and the second extended DRX on-duration 1410 can be activated immediately when SCI-2 is detected at 1402 and 1404. In another example, Fig.15 It is shown that the extended DRX On Duration 904 may be activated at 1502 when the second UE detects SCI-2 and after the DRX On Duration 902 has expired.

[0139] In one aspect, at 1803, the first UE may send a configuration associated with the DRX cycle to the second UE before sending the SL data. For example, Fig.16 At 1610 it is shown that the first UE 1602 can send a configuration associated with a DRX cycle of the second UE 1604 before sending SL data at 1624. In one example, 1803 can be performed by the DRX component 198.

[0140] In one aspect, the SL data may be SL control signaling. For example, Fig.16 At 1624 it is shown that the SL data may be SL control signaling.

[0141] In one aspect, at 1804, the first UE may send a second indication of the at least one condition to the second UE via SCI or PC-5 RRC signaling. Fig.16 At 1612, it is shown that the first UE 1602 can send an indication of the condition to the second UE 1604 via SCI or PC-5 RRC signaling. In one example, 1804 can be performed by the DRX component 198.

[0142] Fig.19 1900 is a flow chart of a method of wireless communication. The method may be performed by a second UE (e.g., UE 104, UE 350, Rx UE 506, second UE 1604, device 2104). The method may be associated with various advantages at the second UE, such as improving communication reliability with the first UE. In one example, the method may be performed by DRX component 198.

[0143] At 1902, a second UE monitors SL data via a first set of resources, wherein the first set of resources is different from a second set of resources for a DRX cycle of the second UE. Fig.16 At 1614, it is shown that the second UE 1604 can monitor SL data via the first resource. In one example, the DRX cycle can be Figure 4 The (long) DRX cycle 404 is shown. In another example, the DRX cycle may be Fig. 9 In one example, 1902 may be performed by the DRX component 198.

[0144] At 1904, the second UE receives SL data from the first UE via the first set of resources or the second set of resources based on the occurrence of at least one condition. Fig.16 At 1624, it is shown that the second UE 1604 can receive SL data from the first UE 1602 via the first resource or the second resource. In one example, the at least one condition can be one or more of the extended DRX on-duration implicit indications 1302. In one example, 1904 can be performed by the DRX component 198.

[0145] Fig. 20 2000 is a flow chart of a method of wireless communication. The method may be performed by a second UE (e.g., UE 104, UE 350, Rx UE 506, second UE 1604, device 2104). The method may be associated with various advantages at the second UE, such as improving communication reliability with the first UE. In one example, the method (including various aspects described below) may be performed by the DRX component 198.

[0146] At 2006, the second UE monitors SL data via a first set of resources, wherein the first set of resources is different from a second set of resources for a DRX cycle of the second UE. Fig.16 At 1614, it is shown that the second UE 1604 can monitor SL data via the first resource. In one example, the DRX cycle can be Figure 4 The (long) DRX cycle 404 is shown. In another example, the DRX cycle may be Fig. 9 In one example, 2006 may be performed by the DRX component 198.

[0147] At 2014, the second UE receives SL data from the first UE via the first set of resources or the second set of resources based on the occurrence of at least one condition. Fig.16 At 1624, it is shown that the second UE 1604 can receive SL data from the first UE 1602 via the first resource or the second resource. In one example, the at least one condition can be one or more of the extended DRX on-duration implicit indications 1302. In one example, 2014 can be performed by the DRX component 198.

[0148] In one aspect, the first set of resources may be associated with a DRX on duration of the second UE, wherein the second set of resources may be associated with an extension of the DRX on duration. For example, the first set of resources may be associated with the DRX on duration 902, and the second set of resources may be associated with the extended DRX on duration 904.

[0149] In one aspect, the extension of the DRX on-duration may be triggered by a second indication. Fig.16 1616A shows that the extension of the DRX on duration can be triggered by the SCI-2 not being detected. In another example, Fig.16 1616B shows that the extension of the DRX on duration can be triggered by the SCI-1 not being detected. In another example, Fig.16 1616C shows that the extension of the DRX on-duration may be triggered by the detection of SCI-2.

[0150] In one aspect, the second set of resources may be activated based on the second indication.For example, resources corresponding to the extended DRX on-duration 904 may be activated based on the second indication.

[0151] In one aspect, the extended time period of the DRX on-duration may be included in a configuration associated with the DRX cycle of the second UE. For example, the configuration sent by the second UE 1604 may include the extended time period of the DRX on-duration. In another example, Fig.11 It is shown that the extended time period of the DRX On Duration 904 may be fixed.

[0152] In one aspect, at 2008, the second UE may determine an extended time period of the DRX On Duration based on a difference between a configured first time period of the DRX On Duration and a second time period corresponding to an active time in the DRX On Duration. Fig.16 At 1620, it is shown that the second UE 1604 can determine an extended time period of the DRX On Duration (e.g., a difference between a first time period based on the configured DRX On Duration and a second time period corresponding to an active time in the DRX On Duration). In another example, Fig.12 It is shown that the extended time period of the DRX OnDuration 904 can be dynamic and based on the implicit indication occurring at 1202 and the PC-5 RRC configuration value 1204. In one example, 2008 can be performed by the DRX component 198.

[0153] In one aspect, at 2010, the second UE may detect the occurrence of the at least one condition. For example, Fig.16 The second UE 1604 can detect the occurrence of the condition at 1616. In one example, 2010 can be performed by the DRX component 198.

[0154] In one aspect, at 2012, the second UE may monitor SL data via a second set of resources based on detecting the occurrence of the at least one condition. Fig.16 At 1622 it is shown that the second UE 1604 can monitor SL data via the second resource upon detecting the occurrence of the condition at 1616. In one example, 2012 can be performed by the DRX component 198.

[0155] In one aspect, the at least one condition may include: the second UE does not detect SCI-1 during the DRX on duration, the second UE does not detect SCI-2 during the DRX on duration, or the second UE detects SCI-2 during the DRX on duration. Fig.16 At 1616A, it is shown that the condition may include that SCI-2 is not detected. In another example, Fig.16 At 1616B, it is shown that the condition may include that SCI-1 is not detected. In another example, Fig.16At 1616C, it is shown that the condition may include SCI-2 being detected. In another example, SCI-1 may be SCI-1 802, and SCI-2 may be SCI-2 804. In another example, the at least one condition may be one or more of the first implicit indication 1304, the second implicit indication 1306, the third implicit indication 1308, the fourth implicit indication 1310, or the fifth implicit indication 1312.

[0156] In one aspect, SCI-2 may include a second indication of a source ID corresponding to the first UE. For example, Fig.13 It is shown that in the first implicit indication 1304, the source ID of SCI-2 can match the Tx UE (e.g., the first UE 1602). In another example, Fig.13 It is shown that in the fourth implicit indication 1310 , the source ID of SCI-2 may match the Tx UE. In another example, the source ID may be the source ID 832 of SCI-2 804 .

[0157] In one aspect, SCI-2 may include a second indication of a source ID corresponding to the first UE and a destination ID corresponding to the second UE. Fig.13 It is shown that in the second implicit indication 1306, the source ID of SCI-2 can match the Tx UE (e.g., the first UE 1602), and the destination ID of SCI-2 can match the Rx UE (e.g., the second UE 1604). In another example, Fig.13 It is shown that in the fifth implicit indication 1312, the source ID of SCI-2 can match the Tx UE and the destination ID of SCI-2 can match the Rx UE. In another example, the source ID can be the source ID 832 of SCI-2 804 and the destination ID can be the destination ID 834.

[0158] In one aspect, the extension of the DRX on duration may be activated immediately when the second UE detects SCI-2 during the DRX on duration, or the extension of the DRX on duration may be activated when the second UE detects SCI-2 during the DRX on duration and after the DRX on duration has expired. Fig.14 It is shown that the first extended DRX on-duration 1408 and the second extended DRX on-duration 1410 can be activated immediately when SCI-2 is detected at 1402 and 1404. In another example, Fig.15 It is shown that the extended DRX On Duration 904 may be activated at 1502 when the second UE detects SCI-2 and after the DRX On Duration 902 has expired.

[0159] In one aspect, at 2002, the second UE may receive a configuration associated with a DRX cycle from the first UE before receiving the SL data. For example, Fig.16 At 1610 it is shown that the second UE 1604 can receive a configuration associated with a DRX cycle before receiving the SL data at 1624. In one example, 2002 can be performed by the DRX component 198.

[0160] In one aspect, the SL data may be SL control signaling. For example, Fig.16 At 1624 it is shown that the SL data may be SL control signaling.

[0161] In one aspect, at 2004, the second UE may receive a second indication of the at least one condition via SCI or PC-5 RRC signaling. For example, Fig.16 At 1612, it is shown that the second UE 1604 can receive an indication of the condition from the first UE 1602 via SCI or PC-5 RRC signaling. In one example, 2004 can be performed by the DRX component 198.

[0162] Fig.212100 is an example of a hardware implementation of an example device 2104. The device 2104 may be a UE, a component of a UE, or may implement UE functionality. In some aspects, the device 2104 may include a cellular baseband processor 2124 (also referred to as a modem) coupled to one or more transceivers 2122 (e.g., a cellular RF transceiver). The cellular baseband processor 2124 may include on-chip memory 2124'. In some aspects, the device 2104 may also include one or more subscriber identity module (SIM) cards 2120 and an application processor 2106 coupled to a secure digital (SD) card 2108 and a screen 2110. The application processor 2106 may include on-chip memory 2106'. In some aspects, the device 2104 may also include a Bluetooth module 2112, a WLAN module 2114, an SPS module 2116 (e.g., a GNSS module), one or more sensor modules 2118 (e.g., an atmospheric pressure sensor / altimeter; a motion sensor such as an inertial measurement unit (IMU), a gyroscope, and / or an accelerometer; light detection and ranging (LIDAR), radio-aided detection and ranging (RADAR), sound navigation and ranging (SONAR), a magnetometer, audio, and / or other technologies for positioning), an additional memory module 2126, a power source 2130, and / or a camera 2132. The Bluetooth module 2112, the WLAN module 2114, and the SPS module 2116 may include an on-chip transceiver (TRX) (or in some cases, only a receiver (RX)). The Bluetooth module 2112, the WLAN module 2114, and the SPS module 2116 may include their own dedicated antennas and / or communicate using antennas 2180. The cellular baseband processor 2124 communicates with the UE 104 and / or the RU associated with the network entity 2102 through the transceiver 2122 via one or more antennas 2180. The cellular baseband processor 2124 and the application processor 2106 may each include a computer-readable medium / memory 2124', 2106', respectively. The additional memory module 2126 may also be considered as a computer-readable medium / memory. Each computer-readable medium / memory 2124', 2106', 2126 may be non-transitory. The cellular baseband processor 2124 and the application processor 2106 are each responsible for general processing, including executing software stored on a computer-readable medium / memory. The software enables the cellular baseband processor 2124 / application processor 2106 to perform the various functions described above when executed by the cellular baseband processor 2124 / application processor 2106. The computer-readable medium / memory can also be used to store data manipulated by the cellular baseband processor 2124 / application processor 2106 when executing the software.The cellular baseband processor 2124 / application processor 2106 may be a component of the UE 350 and may include the memory 360 and / or at least one of the TX processor 368, the RX processor 356, and the controller / processor 359. In one configuration, the device 2104 may be a processor chip (modem and / or application) and include only the cellular baseband processor 2124 and / or the application processor 2106, and in another configuration, the device 2104 may be the entire UE (e.g., see. Figure 3 350) and includes additional modules of device 2104.

[0163] As described above, the DRX component 198 is configured to obtain a configuration associated with the DRX cycle of the second UE, wherein the configuration includes a first indication of a first set of resources and at least one condition, wherein the first set of resources is different from a second set of resources for the DRX cycle of the second UE. The DRX component 198 is configured to send SL data to the second UE via the first set of resources or the second set of resources based on the occurrence of the at least one condition. The DRX component 198 is configured to send the configuration associated with the DRX cycle to the second UE before sending the SL data. The DRX component 198 is configured to send a second indication of the at least one condition to the second UE via SCI or PC-5RRC signaling. The DRX component 198 is configured to monitor SL data via a first set of resources, wherein the first set of resources is different from a second set of resources for the DRX cycle of the second UE. The DRX component 198 is configured to receive SL data from the first UE via the first set of resources or the second set of resources based on the occurrence of at least one condition. The DRX component 198 is configured to determine the extended time period of the DRX on-duration based on the difference between the first time period of the configured DRX on-duration and the second time period corresponding to the active time in the DRX on-duration. The DRX component 198 is configured to detect the occurrence of the at least one condition. The DRX component 198 is configured to monitor the SL data via the second set of resources based on detecting the occurrence of the at least one condition. The DRX component 198 is configured to receive a configuration associated with the DRX cycle from the first UE before receiving the SL data. The DRX component 198 is configured to receive a second indication of the at least one condition via SCI or PC-5RRC signaling. The DRX component 198 may be within the cellular baseband processor 2124, the application processor 2106, or both the cellular baseband processor 2124 and the application processor 2106. The DRX component 198 may be one or more hardware components, which are specifically configured to execute the process / algorithm, implemented by one or more processors configured to execute the process / algorithm, stored in a computer-readable medium so as to be implemented by one or more processors, or some combination of the above. As shown, the apparatus 2104 may include various components configured for various functions. In one configuration, the apparatus 2104, in particular the cellular baseband processor 2124 and / or the application processor 2106, includes a component for obtaining a configuration associated with a DRX cycle of a second UE, wherein the configuration includes a first indication of a first set of resources and at least one condition, wherein the first set of resources is different from a second set of resources for the DRX cycle of the second UE.In one configuration, the device 2104, in particular the cellular baseband processor 2124 and / or the application processor 2106, includes a component for sending SL data to the second UE via a first set of resources or a second set of resources based on the occurrence of the at least one condition. In one configuration, the component for obtaining a configuration associated with the DRX cycle of the second UE includes a component for sending the configuration associated with the DRX cycle to the second UE before sending the SL data. In one configuration, the device 2104, in particular the cellular baseband processor 2124 and / or the application processor 2106 includes a component for sending a second indication of the at least one condition to the second UE via SCI or PC-5RRC signaling. In one configuration, the device 2104, in particular the cellular baseband processor 2124 and / or the application processor 2106 includes a component for monitoring SL data via a first set of resources, wherein the first set of resources is different from a second set of resources for the DRX cycle of the second UE. In one configuration, the device 2104, in particular the cellular baseband processor 2124 and / or the application processor 2106, includes a component for receiving SL data from the first UE via a first set of resources or a second set of resources based on the occurrence of at least one condition. In one configuration, the device 2104, in particular the cellular baseband processor 2124 and / or the application processor 2106, includes a component for determining an extended time period of the DRX on duration based on a difference between a first time period of the configured DRX on duration and a second time period corresponding to an active time in the DRX on duration. In one configuration, the device 2104, in particular the cellular baseband processor 2124 and / or the application processor 2106, includes a component for detecting the occurrence of the at least one condition. In one configuration, the device 2104, in particular the cellular baseband processor 2124 and / or the application processor 2106, includes a component for monitoring SL data via the second set of resources based on detecting the occurrence of the at least one condition. In one configuration, the device 2104, in particular the cellular baseband processor 2124 and / or the application processor 2106, includes a component for receiving a configuration associated with the DRX cycle from the first UE before receiving the SL data. In one configuration, the device 2104, in particular the cellular baseband processor 2124 and / or the application processor 2106 includes a component for receiving a second indication of the at least one condition via SCI or PC-5RRC signaling. The component may be a DRX component 198 of the device 2104 configured to perform the functions recited by the component. As described above, the device 2104 may include a TX processor 368, an RX processor 356, and a controller / processor 359. Therefore, in one configuration, the component may be a TX processor 368, an RX processor 356, and / or a controller / processor 359 configured to perform the functions recited by the component.

[0164] Fig. 22 2200 is an example of a hardware implementation of a network entity 2202. The network entity 2202 may be a BS, a component of a BS, or may implement BS functionality. The network entity 2202 may include at least one of a CU 2210, a DU 2230, or a RU 2240. The network entity 2202 may include: a CU 2210; both a CU 2210 and a DU 2230; each of a CU 2210, a DU 2230, and a RU 2240; a DU 2230; both a DU 2230 and a RU 2240; or a RU 2240. The CU 2210 may include a CU processor 2212. The CU processor 2212 may include an on-chip memory 2212'. In some aspects, the CU 2210 may also include an additional memory module 2214 and a communication interface 2218. The CU 2210 communicates with the DU 2230 via a midhaul link such as an F1 interface. DU 2230 may include a DU processor 2232. DU processor 2232 may include on-chip memory 2232'. In some aspects, DU 2230 may also include an additional memory module 2234 and a communication interface 2238. DU 2230 communicates with RU 2240 via a fronthaul link. RU 2240 may include a RU processor 2242. RU processor 2242 may include on-chip memory 2242'. In some aspects, RU 2240 may also include an additional memory module 2244, one or more transceivers 2246, an antenna 2280, and a communication interface 2248. RU 2240 communicates with UE 104. On-chip memory 2212', 2232', 2242' and additional memory modules 2214, 2234, 2244 may each be considered a computer-readable medium / memory. Each computer-readable medium / memory may be non-transitory. Each of the processors 2212, 2232, 2242 is responsible for general processing, including executing software stored on a computer-readable medium / memory. The software, when executed by the corresponding processor, causes the processor to perform the various functions described above. The computer-readable medium / memory can also be used to store data manipulated by the processor when executing the software.

[0165] As described above, the UE may use the C-DRX cycle for sidelink communication in order to save power. When the physical layer is indicated from the medium access control (MAC) layer for candidate resource selection during the active time of the Rx UE, restrictions may be applied in the physical layer so that at least a subset of the candidate resources reported to the MAC layer may be located within the indicated active time of the Rx UE. If the candidate resource is not within the active time of the Rx UE, the Rx UE may add at least one resource (e.g., based on the implementation of the Rx UE) during the active time. In an unlicensed band sidelink (SL-U), the UE may perform an LBT process before transmission. In one example, the UE may first select a set of resources (e.g., time and frequency resources), and the UE may then fail the LBT procedure, which may trigger an LBT failure at the MAC layer of the UE. The UE may handle the LBT failure in different ways. In a first example, the UE may handle the LBT failure by issuing a resource reselection at the MAC layer. In a second example, the UE may handle the LBT failure by using a retransmission opportunity for initial transmission. If C-DRX is used in SL-U, the resources selected by the UE implementation may be affected by interference. Therefore, the probability of failure of the LBT process may be higher.In addition, frequent resource reselection and / or resource shortage may hinder the throughput at the UE.

[0166] Various techniques related to an enhanced sidelink DRX cycle are described herein. In one example, a first UE obtains a configuration associated with a DRX cycle of a second UE, wherein the configuration includes a first set of resources (e.g., resources associated with a DRX on duration of the second UE) and a first indication of at least one condition, wherein the first set of resources is different from a second set of resources for the DRX cycle of the second UE (e.g., resources associated with an extension of the DRX on duration). The first UE sends SL data to the second UE via the first set of resources or the second set of resources based on the occurrence of the at least one condition. Compared with this configuration, the above technology can improve the communication reliability between the first UE and the second UE. For example, the configuration can reduce the occurrence of resource reselection at the MAC layer and / or can reduce the use of retransmission opportunities for initial transmission. The configuration can also reduce the probability of LBT failure by reducing resource reselection.

[0167] It should be understood that the specific order or hierarchy of the blocks in the disclosed process / flowchart is merely an illustration of the exemplary method. It should be understood that the specific order or hierarchy of the blocks in the process / flowchart may be rearranged based on design preferences. Further, some blocks may be combined or omitted. The attached method claims provide the elements of the various blocks in a sample order, but are not limited to the specific order or hierarchy provided.

[0168] The foregoing description is provided to enable any person skilled in the art to practice the various aspects described herein. Various modifications to these aspects will be apparent to those skilled in the art, and the general principles defined herein can be applied to other aspects. Therefore, the claims are not limited to the various aspects described herein, but should be given the full scope consistent with the language claims. Unless specifically stated otherwise, reference to an element in the singular form does not mean "one and only one", but "one or more". Terms such as "if", "when" and "while" do not mean a direct temporal relationship or reaction. That is, these phrases, such as "when ......", do not mean an immediate action in response to the occurrence of an action or during the occurrence of an action, but simply imply that if the conditions are met, the action will occur, but no specific or immediate time limit is required for the occurrence of the action. The word "exemplary" is used herein to mean "used as an example, instance, or illustration". Any aspect described as "exemplary" herein is not necessarily interpreted as being preferred or having advantages over other aspects. Unless otherwise specifically stated, the term "some" refers to one or more. Combinations such as "at least one of A, B, or C", "one or more of A, B, or C", "at least one of A, B and C", "one or more of A, B, and C", and "A, B, C, or any combination thereof" include any combination of A, B, and / or C, which may include multiple A, multiple B, or multiple C. Specifically, combinations such as "at least one of A, B, or C", "one or more of A, B, or C", "at least one of A, B, and C", "one or more of A, B, and C", and "A, B, C, or any combination thereof" may be only A, only B, only C, A and B, A and C, B and C, or A and B and C, where any such combination may contain one or more members of A, B, or C. A set should be interpreted as a set of elements, where the number of elements is one or more. Thus, for a set of X, X will include one or more elements. If the first device receives data from the second device or sends data to the second device, the data may be received / sent directly between the first device and the second device, or indirectly between the first device and the second device through a collection of devices. All structural and functional equivalents of the elements of the various aspects described throughout the present disclosure that are known or will later be known to a person of ordinary skill in the art are expressly incorporated herein by reference and are covered by the claims. In addition, nothing disclosed herein is intended to be dedicated to the public, regardless of whether such disclosure is explicitly stated in the claims. Words such as "module", "mechanism", "element", "device", etc. cannot replace the word "component". Therefore, no claim element will be understood as a component plus function unless the element is explicitly stated using the phrase "component for..."

[0169] As used herein, the phrase "based on" should not be interpreted as referring to a closed set of information, one or more conditions, one or more factors, etc. In other words, the phrase "based on A" (where "A" can be information, a condition, a factor, etc.) should be interpreted as "based at least on A" unless specifically stated differently.

[0170] The following aspects are merely illustrative and may be combined with other aspects or teachings described herein without limitation.

[0171] Aspect 1 is a method for performing wireless communications at a first user equipment (UE), the method comprising: obtaining a configuration associated with a discontinuous reception (DRX) cycle of a second UE, wherein the configuration comprises a first indication of a first set of resources and at least one condition, wherein the first set of resources is different from a second set of resources for the DRX cycle of the second UE; and based on the occurrence of the at least one condition, sending side link (SL) data to the second UE via the first set of resources or the second set of resources.

[0172] Aspect 2 is a method according to aspect 1, wherein the first set of resources is associated with a DRX on-duration of the second UE, and wherein the second set of resources is associated with an extension of the DRX on-duration.

[0173] Aspect 3 is a method according to aspect 2, wherein the extension of the DRX on-duration is triggered via a second indication.

[0174] Aspect 4 is a method according to aspect 3, wherein the second set of resources is activated based on the second indication.

[0175] Aspect 5 is a method according to any one of Aspects 2 to 4, wherein the extended time period of the DRX on duration is included in the configuration, or the extended time period of the DRX on duration is based on the difference between a first time period of the configured DRX on duration and a second time period corresponding to an active time in the DRX on duration.

[0176] Aspect 6 is a method according to any one of Aspects 2 to 5, wherein the at least one condition includes: the second UE does not detect the first-level sidelink control information (SCI-1) during the DRX on-duration, the second UE does not detect the second-level sidelink control information (SCI-2) during the DRX on-duration, or the second UE detects the SCI-2 during the DRX on-duration.

[0177] Aspect 7 is a method according to aspect 6, wherein the SCI-2 includes a second indication of a source identifier (ID) corresponding to the first UE.

[0178] Aspect 8 is a method according to aspect 6, wherein the SCI-2 includes a second indication of a source identifier (ID) corresponding to the first UE and a destination ID corresponding to the second UE.

[0179] Aspect 9 is a method according to any one of Aspects 6 to 7 or Aspects 6 and 8, wherein the extension of the DRX on duration is activated immediately when the second UE detects the SCI-2 during the DRX on duration, or wherein the extension of the DRX on duration is activated when the second UE detects the SCI-2 during the DRX on duration and after the DRX on duration has expired.

[0180] Aspect 10 is a method according to aspects 1 to 9, the method further comprising: before sending the SL data, sending the configuration associated with the DRX cycle to the second UE.

[0181] Aspect 11 is a method according to any one of aspects 1 to 10, wherein the SL data is SL control signaling.

[0182] Aspect 12 is a method according to any one of Aspects 1 to 11, the method further comprising: sending a second indication of the at least one condition to the second UE via sidelink control information (SCI) or PC-5 radio resource control (RRC) signaling.

[0183] Aspect 13 is an apparatus for wireless communication at a first UE, the apparatus comprising a memory and at least one processor, the at least one processor being coupled to the memory and being configured to perform a method according to any one of Aspects 1 to 12 based at least in part on information stored in the memory.

[0184] Aspect 14 is an apparatus for wireless communication, the apparatus comprising means for performing the method according to any one of aspects 1 to 12.

[0185] Aspect 15 is a device according to Aspect 13 or 14, wherein the device also includes at least one of a transceiver or an antenna coupled to the at least one processor, wherein the at least one processor is configured to send the SL data via at least one of the transceiver or the antenna.

[0186] Aspect 16 is a computer-readable medium (eg, a non-transitory computer-readable medium) comprising instructions which, when executed by an apparatus, cause the apparatus to perform the method according to any one of aspects 1 to 12.

[0187] Aspect 17 is a method for performing wireless communications at a second user equipment (UE), the method comprising: monitoring side link (SL) data via a first set of resources, wherein the first set of resources is different from a second set of resources for a discontinuous reception (DRX) cycle of the second UE; and receiving the SL data from the first UE via the first set of resources or the second set of resources based on the occurrence of at least one condition.

[0188] Aspect 18 is a method according to aspect 17, wherein the first set of resources is associated with a DRX on duration of the second UE, and wherein the second set of resources is associated with an extension of the DRX on duration.

[0189] Aspect 19 is a method according to aspect 18, wherein the extension of the DRX on-duration is triggered via a second indication.

[0190] Aspect 20 is a method according to aspect 19, wherein the second set of resources is activated based on the second indication.

[0191] Aspect 21 is a method according to any one of aspects 18 to 20, wherein the extended time period of the DRX On-Duration is included in a configuration associated with the DRX cycle of the second UE.

[0192] Aspect 22 is a method according to any one of Aspects 18 to 21, the method further comprising: determining the extended time period of the DRX on duration based on the difference between a first time period of the configured DRX on duration and a second time period corresponding to an active time in the DRX on duration.

[0193] Aspect 23 is a method according to any one of Aspects 18 to 22, the method further comprising: detecting the occurrence of the at least one condition; and monitoring the SL data via the second set of resources based on detecting the occurrence of the at least one condition.

[0194] Aspect 24 is a method according to Aspect 23, wherein the at least one condition includes: the second UE does not detect the first-level sidelink control information (SCI-1) during the DRX on duration, the second UE does not detect the second-level sidelink control information (SCI-2) during the DRX on duration, or the second UE detects the SCI-2 during the DRX on duration.

[0195] Aspect 25 is a method according to aspect 24, wherein the SCI-2 includes a second indication of a source identifier (ID) corresponding to the first UE.

[0196] Aspect 26 is a method according to aspect 24, wherein the SCI-2 includes a second indication of a source identifier (ID) corresponding to the first UE and a destination ID corresponding to the second UE.

[0197] Aspect 27 is a method according to any one of Aspects 24 to 25 or Aspects 24 and 26, wherein the extension of the DRX on duration is activated immediately when the second UE detects the SCI-2 during the DRX on duration, or wherein the extension of the DRX on duration is activated when the second UE detects the SCI-2 during the DRX on duration and after the DRX on duration has expired.

[0198] Aspect 28 is a method according to any one of aspects 17 to 27, the method further comprising: before receiving the SL data, receiving a configuration associated with the DRX cycle from the first UE.

[0199] Aspect 29 is a method according to any one of aspects 17 to 28, wherein the SL data is SL control signaling.

[0200] Aspect 30 is a method according to any one of aspects 17 to 29, the method further comprising: receiving a second indication of the at least one condition via sidelink control information (SCI) or PC-5 radio resource control (RRC) signaling.

[0201] Aspect 31 is an apparatus for wireless communication at a second UE, the apparatus comprising a memory and at least one processor, the at least one processor being coupled to the memory and being configured to perform a method according to any one of Aspects 17 to 30 based at least in part on information stored in the memory.

[0202] Aspect 32 is an apparatus for wireless communication, the apparatus comprising means for performing a method according to any one of aspects 17 to 30.

[0203] Aspect 33 is a device according to Aspect 31 or 32, wherein the device also includes at least one of a transceiver or an antenna coupled to the at least one processor, wherein the at least one processor is configured to receive the SL data via at least one of the transceiver or the antenna.

[0204] Aspect 34 is a computer-readable medium (e.g., a non-transitory computer-readable medium), the computer-readable medium comprising instructions, which, when executed by an apparatus, cause the apparatus to perform a method according to any one of aspects 17 to 30.

Claims

1. An apparatus for wireless communication at a first user equipment (UE), the apparatus comprising: Memory; as well as at least one processor coupled to the memory and based at least in part on the information stored in the memory, the at least one processor is configured to: obtaining a configuration associated with a discontinuous reception (DRX) cycle of a second UE, wherein the configuration comprises a first indication of a first set of resources and at least one condition, wherein the first set of resources is different from a second set of resources for the DRX cycle of the second UE; as well as Based on the occurrence of the at least one condition, sidelink (SL) data is sent to the second UE via the first set of resources or the second set of resources.

2. The apparatus of claim 1, wherein the first set of resources is associated with a DRX on-duration of the second UE, and wherein the second set of resources is associated with an extension of the DRX on-duration. 3 . The apparatus according to claim 2 , wherein the extension of the DRX on-duration is configured to be triggered via a second indication. The apparatus of claim 3 , wherein the second set of resources is configured to be activated based on the second indication.

5. The apparatus of claim 2 , wherein the extended time period of the DRX On Duration is included in the configuration, or the extended time period of the DRX On Duration is based on a difference between a first time period of a configured DRX On Duration and a second time period corresponding to an active time in the DRX On Duration.

6. The apparatus of claim 2, wherein the at least one condition comprises: The second UE does not detect first-level sidelink control information (SCI-1) during the DRX on duration, and the second UE does not detect second-level sidelink control information (SCI-2) during the DRX on duration, or The second UE detects the SCI-2 during the DRX on-duration.

7. The apparatus of claim 6, wherein the SCI-2 comprises a second indication of a source identifier (ID) corresponding to the first UE.

8. The apparatus of claim 6, wherein the SCI-2 comprises a second indication of a source identifier (ID) corresponding to the first UE and a destination ID corresponding to the second UE.

9. The apparatus of claim 6, wherein the extension of the DRX on duration is configured to be activated immediately when the SCI-2 is detected during the DRX on duration, or wherein the extension of the DRX on duration is configured to be activated when the SCI-2 is detected during the DRX on duration and after the DRX on duration has expired.

10. The apparatus of claim 1, wherein the at least one processor is further configured to: Before sending the SL data, the configuration associated with the DRX cycle is sent to the second UE. The apparatus according to claim 1 , wherein the SL data is SL control signaling.

12. The apparatus of claim 1, wherein the at least one processor is further configured to: A second indication of the at least one condition is sent to the second UE via sidelink control information (SCI) or PC-5 radio resource control (RRC) signaling.

13. The apparatus according to claim 1, further comprising: At least one of a transceiver or an antenna coupled to the at least one processor, wherein to send the SL data, the at least one processor is configured to send the SL data via at least one of the transceiver or the antenna.

14. A method of wireless communication at a first user equipment (UE), the method comprising: obtaining a configuration associated with a discontinuous reception (DRX) cycle of a second UE, wherein the configuration comprises a first indication of a first set of resources and at least one condition, wherein the first set of resources is different from a second set of resources for the DRX cycle of the second UE; as well as Based on the occurrence of the at least one condition, sidelink (SL) data is sent to the second UE via the first set of resources or the second set of resources.

15. An apparatus for wireless communication at a second user equipment (UE), the apparatus comprising: Memory; as well as at least one processor coupled to the memory and based at least in part on the information stored in the memory, the at least one processor is configured to: monitoring side link (SL) data via a first set of resources, wherein the first set of resources is different from a second set of resources of a discontinuous reception (DRX) cycle for the second UE; as well as Based on the occurrence of at least one condition, the SL data is received from the first UE via the first set of resources or the second set of resources.

16. The apparatus of claim 15, wherein the first set of resources is associated with a DRX On Duration of the second UE, wherein the second set of resources is associated with an extension of the DRX On Duration. 17 . The apparatus of claim 16 , wherein the extension of the DRX On-Duration is configured to be triggered via a second indication.

18. The apparatus of claim 17, wherein the second set of resources is configured to be activated based on the second indication.

19. The apparatus of claim 16, wherein the extended time period of the DRX On-Duration is included in a configuration associated with the DRX cycle of the second UE.

20. The apparatus of claim 16, wherein the at least one processor is further configured to: The extended time period of the DRX On Duration is determined based on a difference between a first time period of a configured DRX On Duration and a second time period corresponding to an active time in the DRX On Duration.

21. The apparatus of claim 16, wherein the at least one processor is further configured to: detecting said occurrence of said at least one condition; and Based on detecting the occurrence of the at least one condition, monitoring the SL data via the second set of resources.

22. The apparatus of claim 21, wherein the at least one condition comprises: The second UE does not detect first-level sidelink control information (SCI-1) during the DRX on duration, and the second UE does not detect second-level sidelink control information (SCI-2) during the DRX on duration, or The second UE detects the SCI-2 during the DRX on-duration.

23. The apparatus of claim 22, wherein the SCI-2 comprises a second indication of a source identifier (ID) corresponding to the first UE.

24. The apparatus of claim 22, wherein the SCI-2 comprises a second indication of a source identifier (ID) corresponding to the first UE and a destination ID corresponding to the second UE.

25. The apparatus of claim 22, wherein the extension of the DRX on duration is configured to be activated immediately when the at least one processor is configured to detect the SCI-2 during the DRX on duration, or wherein the extension of the DRX on duration is configured to be activated when the at least one processor is configured to detect the SCI-2 during the DRX on duration and after the DRX on duration has expired.

26. The apparatus of claim 15, wherein the at least one processor is further configured to: Prior to receiving the SL data, a configuration associated with the DRX cycle is received from the first UE.

27. The apparatus of claim 15, wherein the SL data is SL control signaling.

28. The apparatus of claim 15, wherein the at least one processor is further configured to: A second indication of the at least one condition is received via Sidelink Control Information (SCI) or PC-5 Radio Resource Control (RRC) signaling.

29. The apparatus according to claim 15, further comprising: At least one of a transceiver or an antenna coupled to the at least one processor, wherein to receive the SL data, the at least one processor is configured to receive the SL data via at least one of the transceiver or the antenna.

30. A method of wireless communication at a second user equipment (UE), the method comprising: monitoring side link (SL) data via a first set of resources, wherein the first set of resources is different from a second set of resources of a discontinuous reception (DRX) cycle for the second UE; as well as Based on the occurrence of at least one condition, the SL data is received from the first UE via the first set of resources or the second set of resources.

Images