Independent SL-DRX inactivity timers for positioning cases in SL positioning

Abstract

An apparatus, a method, and a computer program product for SL DRX are provided. An example method may include receiving a SL DRX configuration including a first inactivity timer associated with non-positioning communications and a second inactivity timer associated with positioning communications, where the first inactivity timer corresponds to a first duration and the second inactivity timer corresponds to a second duration. The example method may also include entering a sleep state based on the SL DRX configuration. The example method may also include initiating a wake-up state from the sleep state to receive a message associated with scheduling the SL PRS. The example method may also include, upon receiving the message, triggering continuation of the wake-up state to receive at least one subsequent transmission including the SL PRS, wherein a duration of the continuation of the wake-up state is based on the first duration or the second duration.

Description

[0001] CROSS-REFERENCE TO RELATED APPLICATIONS

[0002] This application claims the benefit of Greek patent application serial number 20220100704, entitled “INDEPENDENT SL-DRX INACTIVITY TIMER FOR THEPOSITIONING USE CASES IN SL POSITIONING” and filed on August 24, 2022, which is expressly incorporated herein by reference in its entirety. Technical Field

[0003] The present disclosure relates generally to communication systems, and more particularly to wireless communication systems with sidelink (SL) communication and positioning. Background Art

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

[0005] 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 continued 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. 5G NR includes services associated with enhanced mobile broadband (eMBB), massive machine type communications (mMTC), and ultra-reliable low latency communications (URLLC). Certain aspects of 5G NR may be based on the 4G Long Term Evolution (LTE) standard. Further improvements to 5G NR technology are needed. In addition, these improvements may also be applicable to other multiple access technologies and telecommunication standards that employ these technologies. Summary of the invention

[0006] 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 is neither intended to identify key or important elements of all aspects, nor to describe 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.

[0007] In one aspect of the present disclosure, a method, a computer-readable medium, and an apparatus at a user equipment (UE) are provided. The apparatus may include a memory and at least one processor coupled to the memory. The memory and the at least one processor coupled to the memory may be configured to receive a SL DRX configuration, the SL DRX configuration including a first inactivity timer associated with non-positioning communication and a second inactivity timer associated with positioning communication, wherein the first inactivity timer corresponds to a first duration, and the second inactivity timer corresponds to a second duration. The memory and the at least one processor coupled to the memory may be further configured to enter a sleep state based on the SL DRX configuration. The memory and the at least one processor coupled to the memory may be further configured to initiate a wake-up state from the sleep state to receive a message associated with scheduling a SL PRS. The memory and the at least one processor coupled to the memory may be further configured to trigger the continuation of the wake-up state upon receiving the message to receive at least one subsequent transmission including the SL PRS, wherein the duration of the continuation of the wake-up state is based on the first duration or the second duration.

[0008] In another aspect of the present disclosure, a method, a computer-readable medium, and an apparatus at a UE are provided. The apparatus may include a memory and at least one processor coupled to the memory. The memory and the at least one processor coupled to the memory may be configured to establish a positioning session with a second UE. The memory and the at least one processor coupled to the memory may be further configured to send a SL DRX configuration, the SL DRX configuration including a first inactivity timer associated with non-positioning communication and a second inactivity timer associated with positioning communication, wherein the first inactivity timer corresponds to a first duration and the second inactivity timer corresponds to a second duration. The memory and the at least one processor coupled to the memory may be further configured to send a message associated with scheduling a SL PRS, wherein at least one subsequent transmission to the UE includes the SL PRS.

[0009] To achieve the aforementioned and related purposes, one or more aspects include the features described in full 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 are only indicative of only some of the various ways in which the principles of the various aspects can be employed. BRIEF DESCRIPTION OF THE DRAWINGS

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

[0011] Figure 2 Example aspects of a side link (SL) slot structure are illustrated.

[0012] Figure 3 is a diagram illustrating an example of a first device and a second device involved in wireless communication based on, for example, a side link.

[0013] Figure 4 is a diagram illustrating an example of UE positioning based on reference signal measurement.

[0014] Figure 5 Example aspects of sidelink communications between devices are illustrated.

[0015] Figure 6 is a diagram illustrating a discontinuous reception (DRX) process.

[0016] Fig. 7A is a diagram illustrating an example of positioning.

[0017] Figure 7B is a diagram illustrating an example of positioning.

[0018] Figure 7C is a diagram illustrating an example of positioning.

[0019] Figure 8 is a diagram illustrating an example process of sidelink-based positioning.

[0020] Fig.9A is a diagram illustrating an example of a positioning peer (pos-peer) selection process for SL co-location.

[0021] Fig. 9B is a diagram illustrating an example of a positioning peer selection process for SL co-location.

[0022] Fig. 10A is a diagram illustrating an example of SL DRX.

[0023] Fig. 10B is a diagram illustrating an example of SL DRX.

[0024] Fig.11is a diagram illustrating an example of SL DRX configuration.

[0025] Fig.12 is a diagram illustrating an example of a DRX configuration.

[0026] Fig.13 is a diagram illustrating example communications between a UE, a network entity (such as a base station or UE), and one or more other UEs.

[0027] Fig.14 is a diagram illustrating an example of SL DRX configuration.

[0028] Fig.15 is a diagram illustrating an example of SL DRX configuration.

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

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

[0031] Fig.18 are diagrams illustrating examples of hardware implementations for example apparatuses and / or network entities. DETAILED DESCRIPTION

[0032] The detailed description set forth below in conjunction with the accompanying drawings is a description of various configurations and does not represent the only configurations with 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 instances, well-known structures and components are shown in block diagram form to avoid blurring these concepts.

[0033] Several aspects of the telecommunication system are also presented with reference to various apparatuses and methods. These apparatuses 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 can 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.

[0034] 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, gate logic components, 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.

[0035] Thus, in one or more example aspects, implementations, and / or use cases, the functions described may be implemented in hardware, software, or any combination thereof. If implemented in software, the functions 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. By way of 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 media that can be used to store computer-executable code in the form of instructions or data structures that can be accessed by a computer.

[0036] Although various aspects, specific implementations and / or use cases are described in this application by way of illustration of some examples, additional or different aspects, specific implementations and use cases may be generated in many different arrangements and scenarios. The various aspects, specific implementations and / or use cases described herein may be implemented across many different platform types, devices, systems, shapes, sizes and packaging arrangements. For example, various aspects, specific implementations and / or use cases may be generated via integrated chip specific implementations and other devices based on non-module components (e.g., end-user devices, vehicles, communication devices, computing devices, industrial equipment, retail / purchase devices, medical devices, devices that enable artificial intelligence (AI), etc.). Although some examples may or may not be specifically for use cases or applications, the examples described may have a wide range of applicability. Various aspects, specific implementations and / or use cases may 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 practical environments, the devices in conjunction 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.

[0037] The deployment of a communication system (such as a 5G NR system) can be arranged in a variety of ways using various components or constituent parts. 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 functionality 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, an access point (AP), a transmit receive point (TRP) or a cell, etc.) can be implemented as an aggregated base station (also referred to as an independent BS or a monolithic BS) or a decomposed base station.

[0038] A converged base station may be configured to utilize a radio protocol stack that is physically or logically integrated within a single RAN node. A decomposed base station may be configured to utilize a protocol stack that is 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).

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

[0040] Figure 1 1 is a diagram 100 illustrating an example of a wireless communication system and 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 respective midhaul links, such as an F1 interface. The DU 130 may communicate with one or more RUs 140 via respective fronthaul links. The RU 140 may communicate with respective 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.

[0041] 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 transmit 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 on a wired transmission medium or to transmit signals to one or more of the other units. Additionally, these units may include a wireless interface that may include a receiver, transmitter, or transceiver (such as an RF transceiver) configured to receive signals on a wireless transmission medium or to transmit signals to one or more of the other units, or both.

[0042] In some aspects, the 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 can be implemented using an interface configured to communicate signals with other control functions hosted by the CU 110. The CU 110 may be configured to handle user plane functionality (i.e., central unit-user plane (CU-UP)), control plane functionality (i.e., central unit-control plane (CU-CP)), or a combination thereof. In some specific implementations, the 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, the CU 110 may be implemented to communicate with the DU 130 for network control and signaling.

[0043] 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.) according to a functional split (such as that defined by 3GPP). In some aspects, DU 130 may also host one or more low PHY layers. Each layer (or module) may be implemented with an interface configured to communicate signals with other layers (and modules) hosted by DU 130 or with control functions hosted by CU 110.

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

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

[0046] 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 via data collection and actions over an interface connecting one or more CUs 110, one or more DUs 130, or both, and O-eNBs with the near-RT RIC 125 (such as via an E2 interface).

[0047] 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 the creation of RAN management policies (such as A1 policies).

[0048] 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 pass 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., 5 MHz, 10 MHz, 15 MHz, 20 MHz, 100 MHz, 400 MHz, etc.) bandwidth. The 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). The component carrier 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).

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

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

[0051] The electromagnetic spectrum is often 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 (interchangeably) referred to 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).

[0052] 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). Bands falling within FR3 may inherit FR1 characteristics and / or FR2 characteristics, thus effectively extending the characteristics of FR1 and / or FR2 to mid-band frequencies. In addition, higher frequency bands are currently being explored to extend 5G NR operations beyond 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.

[0053] In view of the above, unless otherwise specifically stated, if the term "below 6 GHz" or the like is used in this document, 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 specifically stated, if the term "millimeter wave" or the like is used in this document, 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.

[0054] 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 different. The transmit direction and receive direction of the UE 104 may be the same or different.

[0055] 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 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, a converged (monolithic) base station with a baseband unit (BBU) (including a CU and a DU) and a RU, or as a disaggregated base station including one or more of a CU, a DU, and / or a RU.

[0056] 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. The AMF 161 is a control node that handles signaling between the UE 104 and the core network 120. The AMF 161 supports registration management, connection management, mobility management, and other functions. The SMF 162 supports session management and other functions. The UPF 163 supports packet routing, packet forwarding, and other functions. The UDM 164 supports the generation of authentication and key agreement (AKA) credentials, user identity handling, access authorization, and subscription management. The 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, the LMF 166, a position determination entity (PDE), a serving mobile location center (SMLC), a mobile positioning center (MPC), etc. The GMLC 165 and the LMF 166 support UE location services. The GMLC 165 provides an interface for clients / applications (e.g., emergency services) to access UE positioning information. The LMF 166 receives measurement results and assistance information from the NG-RAN and the UE 104 via the AMF 161 to calculate the location of the UE 104. The NG-RAN may determine the location of the UE 104 using one or more positioning methods. Positioning the UE 104 may involve signal measurements, position estimation, and optional speed calculations based on these measurements. Signal measurements may be performed by the UE 104 and / or the 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.

[0057] 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 constellation arrangement. One or more of these devices may access the network collectively and / or individually.

[0058] Reference again Figure 1 In some aspects, the UE 104 may include a sidelink DRX configuration component 198. In some aspects, the sidelink DRX configuration component 198 may be configured to receive a SL DRX configuration, the SL DRX configuration including a first inactivity timer associated with non-positioning communication and a second inactivity timer associated with positioning communication, wherein the first inactivity timer corresponds to a first duration and the second inactivity timer corresponds to a second duration. In some aspects, the sidelink DRX configuration component 198 may be further configured to enter a sleep state based on the SL DRX configuration. In some aspects, the sidelink DRX configuration component 198 may be further configured to initiate a wake-up state from the sleep state to receive a message associated with scheduling a SL PRS. In some aspects, the sidelink DRX configuration component 198 may be further configured to trigger a continuation of the wake-up state upon receipt of the message to receive at least one subsequent transmission including the SL PRS, wherein the duration of the continuation of the wake-up state is based on the first duration or the second duration.

[0059] In some aspects, the sidelink DRX configuration component 198 may be configured to establish a positioning session with the second UE. In some aspects, the sidelink DRX configuration component 198 may be further configured to send a SL DRX configuration, the SL DRX configuration including a first inactivity timer associated with non-positioning communication and a second inactivity timer associated with positioning communication, wherein the first inactivity timer corresponds to a first duration and the second inactivity timer corresponds to a second duration. In some aspects, the sidelink DRX configuration component 198 may be further configured to send a message associated with scheduling a SL PRS, wherein at least one subsequent transmission to the UE includes the SL PRS

[0060] Although the following description may focus on 5G NR, the concepts described herein may be applicable to other similar areas such as LTE, LTE-A, CDMA, GSM, and other wireless technologies.

[0061] As described herein, a node (which may be referred to as a node, a network node, a network entity, or a wireless node) may include, may be, or may be included in (e.g., as a component of) a base station (e.g., any base station described herein), a UE (e.g., any UE described herein), a network controller, an apparatus, a device, a computing system, an integrated access and backhaul (IAB) node, a distributed unit (DU), a central unit (CU), a remote / radio unit (RU) (which may also be referred to as a remote radio unit (RRU)), and / or another processing entity configured to perform any of the techniques described herein. For example, the network node may be a UE. For another example, the network node may be a base station or a network entity. As another example, a first network node may be configured to communicate with a second network node or a third network node. In one aspect of this example, the first network node may be a UE, the second network node may be a base station, and the third network node may be a UE. In another aspect of this example, the first network node may be a UE, the second network node may be a base station, and the third network node may be a base station. In yet other aspects of this example, the first network node, the second network node, and the third network node may be different relative to these examples. Similarly, references to UE, base station, apparatus, device, computing system, etc. may include disclosure of UE, base station, apparatus, device, computing system, etc. as a network node. For example, a disclosure that a UE is configured to receive information from a base station also discloses that a first network node is configured to receive information from a second network node. Consistent with the present disclosure, once a specific example is expanded according to the present disclosure (e.g., a UE is configured to receive information from a base station also discloses that a first network node is configured to receive information from a second network node), a broader example of a narrower example may be interpreted in reverse, but in a broad, open-ended manner. In the above example that a UE is configured to receive information from a base station also discloses that a first network node is configured to receive information from a second network node, the first network node may refer to a first UE, a first base station, a first apparatus, a first device, a first computing system, a first group of one or more components, a first processing entity, etc. configured to receive information; and the second network node may refer to a second UE, a second base station, a second apparatus, a second device, a second computing system, a second group of one or more components, a second processing entity, etc.

[0062] As described herein, different terms may be used in various aspects to describe the transmission of information (e.g., any information, signal, etc.). Disclosure of one communication term includes disclosure of other communication terms. For example, a first network node may be described as being configured to send information to a second network node. In this example and consistent with the present disclosure, disclosure that the first network node is configured to send information to the second network node includes disclosure that the first network node is configured to provide, transmit, output, communicate, or send information to the second network node. Similarly, in this example and consistent with the present disclosure, disclosure that the first network node is configured to send information to the second network node includes disclosure that the second network node is configured to receive, obtain, or decode information provided, sent, output, transmitted, or sent by the first network node.

[0063] Figure 2 Diagrams 200 and 210 are included that illustrate example aspects of a slot structure that may be used for sidelink communications (e.g., between UE 104, RSU 107, etc.). In some examples, the slot structure may be within a 5G / NR frame structure. In other examples, the slot structure may be within an LTE frame structure. Although the following description may focus on 5G NR, the concepts described herein may be applicable to other similar areas, such as LTE, LTE-A, CDMA, GSM, and other wireless technologies. Figure 2 The example slot structure in is only an example, and other sidelink communications may have different frame structures and / or different channels for sidelink communications. A frame (10ms) may be divided into 10 equally sized subframes (1ms). Each subframe may include one or more slots. A subframe may also include a microslot, which may include 7, 4, or 2 symbols. Each slot may include 7 or 14 symbols, depending on the slot configuration. For slot configuration 0, each slot may include 14 symbols, and for slot configuration 1, each slot may include 7 symbols. Diagram 200 illustrates a single resource block that may correspond to a single slot transmission of, for example, a 0.5ms transmission time interval (TTI). The physical sidelink control channel may be configured to occupy multiple physical resource blocks (PRBs), for example, 10, 12, 15, 20, or 25 PRBs. The PSCCH may be limited to a single subchannel. For example, the PSCCH duration may be configured to be 2 symbols or 3 symbols. For example, a subchannel may include 10, 15, 20, 25, 50, 75, or 100 PRBs. Resources for sidelink transmissions may be selected from a resource pool including one or more subchannels. As a non-limiting example, a resource pool may include between 1 and 27 subchannels. A PSCCH size may be established for a resource pool, for example, between 10%-100% of a subchannel within a duration of 2 symbols or 3 symbols. Figure 2Diagram 210 in illustrates an example in which the PSCCH occupies approximately 50% of a subchannel as an example of illustrating the concept of the PSCCH occupying a portion of a subchannel. A physical sidelink shared channel (PSSCH) occupies at least one subchannel. In some examples, the PSCCH may include a first portion of sidelink control information (SCI), and the PSSCH may include a second portion of the SCI.

[0064] A resource grid may be used to represent the frame structure. Each time slot may include a resource block (RB) (also called 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. Figure 2 As shown, some of the REs may include control information in the PSCCH and some of the REs may include a demodulation RS (DMRS). At least one symbol may be used for feedback. Figure 2 An example is illustrated having two symbols for a physical sidelink feedback channel (PSFCH) with adjacent gap symbols. Symbols before and / or after the feedback may be used for a transition between reception of data and transmission of feedback. The gap enables the device to switch from operating as a transmitting device to preparing to operate as a receiving device, e.g., in a subsequent time slot. As illustrated, data may be sent in the remaining REs. The data may include data messages as described herein. The location of any of the data, DMRS, SCI, feedback, gap symbols, and / or LBT symbols may differ from Figure 2 Illustrated example. In some aspects, multiple time slots may be aggregated together.

[0065] Figure 3 3 is a block diagram of a first wireless communication device 310 communicating with a second wireless communication device 350 based on a side link. In some examples, the devices 310 and 350 may communicate based on V2X or other D2D / ProSe communications. The communication may be based on a side link using a PC5 interface. The devices 310 and 350 may include UEs, RSUs, base stations, etc. Packets may be provided to a controller / processor 375 that implements layer 3 and layer 2 functionality. Various layer functions may include a radio resource control (RRC) layer, a packet data convergence protocol (PDCP) layer, a radio link control (RLC) layer, and a medium access control (MAC) layer.

[0066] The transmit (TX) processor 316 and the 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 transmission channel, forward error correction (FEC) decoding / decoding of the transmission 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 decoded and modulated symbols can then be divided into parallel streams. Subsequently, each stream can be mapped to an OFDM subcarrier, multiplexed with a reference signal (e.g., a pilot) in the time domain and / or frequency domain, and then combined 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-decoded to produce multiple spatial streams. Channel estimates from channel estimator 374 can be used to determine the coding and modulation schemes, as well as for spatial processing. Channel estimates can be derived from reference signals and / or channel condition feedback sent by device 350. Each spatial stream can then be provided to a different antenna 320 via a separate transmitter 318Tx. Each transmitter 318Tx can modulate an RF carrier with a corresponding spatial stream for transmission.

[0067] At the device 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 the 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 device 350. If multiple spatial streams are destined for the device 350, the RX processor 356 can combine them into a single OFDM symbol stream. 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 device 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 device 310. The data and control signals are then provided to controller / processor 359, which implements layer 3 and layer 2 functionality.

[0068] 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. The controller / processor 359 may provide demultiplexing between transport channels and logical channels, packet reassembly, decryption, header decompression, and control signal processing. The controller / processor 359 is also responsible for error detection using an ACK and / or NACK protocol to support HARQ operations.

[0069] Similar to the functions described in conjunction with transmissions performed by the device 310, the controller / processor 359 may provide 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, 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 TBs, demultiplexing of MAC SDUs from TBs, scheduling information reporting, error correction through HARQ, priority handling, and logical channel prioritization.

[0070] Channel estimates derived by the channel estimator 358 from a reference signal or feedback sent by the device 310 may be used by the TX processor 368 to select 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.

[0071] The transmission is processed at the device 310 in a manner similar to that described in conjunction with the receiver functionality at the device 350. Each receiver 318Rx receives the signal through its corresponding antenna 320. Each receiver 318Rx recovers the information modulated onto the RF carrier and provides the information to the RX processor 370.

[0072] 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. The controller / processor 375 provides demultiplexing between transport channels and logical channels, packet reassembly, decryption, header decompression, control signal processing. The controller / processor 375 is also responsible for error detection using ACK and / or NACK protocols to support HARQ operations.

[0073] 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 Aspects related to the sidelink DRX configuration component 198.

[0074] Similarly, at least one of the TX processor 316, the RX processor 370, and the controller / processor 375 may be configured to perform operations related to Figure 1 Aspects related to the sidelink DRX configuration component 198.

[0075] Figure 4 4 is a diagram illustrating an example of UE positioning based on reference signal measurement. UE 404 may be at time T SRS_TX UL-SRS 412 is sent and at time T PRS_RX A DL positioning reference signal (PRS) (DL-PRS) 410 is received. The TRP 406 may be at time T SRS_RX Receive UL-SRS 412 and at time T PRS_TX 410. UE 404 may receive DL-PRS 410 before transmitting UL-SRS 412, or may transmit UL-SRS 412 before receiving DL-PRS 410. In both cases, a positioning server (eg, location server 168) or UE 404 may determine the UL-SRS 412 based on ||T SRS_RX – T PRS_TX | – |T SRS_TX – T PRS_RX || to determine RTT 414. Thus, multi-RTT positioning may utilize UE Rx-Tx time difference measurements (ie, |T SRS_TX – T PRS_RX |) and DL-PRS reference signal received power (RSRP) (DL-PRS-RSRP), and the measured TRP Rx-Tx time difference measurement (ie, |T SRS_RX – T PRS_TX |) and UL-SRS-RSRP. The UE 404 measures the UE Rx-Tx time difference measurement (and optionally the DL-PRS-RSRP of the received signal) using the assistance data received from the positioning server, and TRP 402, 406 measures the gNB Rx-Tx time difference measurement (and optionally the UL-SRS-RSRP of the received signal) using the assistance data received from the positioning server. These measurements may be used at the positioning server or the UE 404 to determine the RTT, which is used to estimate the position of the UE 404. Other methods for determining the RTT are possible, such as, for example, using DL-TDOA and / or UL-TDOA measurements.

[0076] DL-AoD positioning may utilize measured DL-PRS-RSRP of downlink signals received at a UE 404 from multiple TRPs 402, 406. The UE 404 measures the DL-PRS-RSRP of the received signals using assistance data received from a positioning server, and the resulting measurements, along with the departure azimuth angle (A-AoD), departure zenith angle (Z-AoD), and other configuration information, are used to position the UE 404 relative to neighboring TRPs 402, 406.

[0077] DL-TDOA positioning may utilize DL Reference Signal Time Difference (RSTD) (and optionally DL-PRS-RSRP) of downlink signals received from multiple TRPs 402, 406 at the UE 404. The UE 404 measures the DL RSTD (and optionally DL-PRS-RSRP) of the received signals using assistance data received from a positioning server, and the resulting measurements, along with other configuration information, are used to position the UE 404 relative to neighboring TRPs 402, 406.

[0078] UL-TDOA positioning may utilize the UL relative time of arrival (RTOA) (and optionally UL-SRS-RSRP) of uplink signals sent from the UE 404 at multiple TRPs 402, 406. The TRPs 402, 406 measure the UL-RTOA (and optionally UL-SRS-RSRP) of the received signals using assistance data received from a positioning server, and the resulting measurements are used along with other configuration information to estimate the position of the UE 404.

[0079] UL-AoA positioning may utilize the measured azimuth angle of arrival (A-AoA) and zenith angle of arrival (Z-AoA) of uplink signals sent from the UE 404 at multiple TRPs 402, 406. The TRPs 402, 406 measure the A-AoA and Z-AoA of the received signals using assistance data received from a positioning server, and the resulting measurements are used along with other configuration information to estimate the position of the UE 404.

[0080] Additional positioning methods may be used to estimate the position of the UE 404, such as, for example, UE-side UL-AoD and / or DL-AoA. Note that data / measurements from various techniques may be combined in various ways to increase accuracy, determine and / or enhance certainty, supplement / complete measurements, and / or replace / provide missing information.

[0081] In some aspects, instead of using DL PRS and UL PRS, SL PRS can be used, and TRP 402 and TRP 406 can be replaced with other UEs. UE 404 can perform positioning based on SL PRS accordingly.

[0082] Figure 5 An example 500 of sidelink communication between devices is illustrated. The communication may be based on a combination of Figure 2 The time slot structure of various aspects described. For example, UE 502 can send a sidelink transmission 514, for example, including a control channel (e.g., PSCCH) and / or a corresponding data channel (e.g., PSSCH), which can be received by UE 504, 506, 508. The control channel can include information for decoding the data channel (e.g., sidelink control information (SCI)), which includes reservation information, such as information about the time and / or frequency resources reserved for data channel transmission. For example, the SCI can indicate the TTI and the number of RBs to be occupied by the data transmission. The SCI can also be used by the receiving device to avoid interference by avoiding transmission on the reserved resources. In addition to the sidelink reception, UE 502, 504, 506, 508 can each be capable of sidelink transmission. Therefore, UE 504, 506, 508 is illustrated as sending sidelink transmissions 513, 515, 516, 520. The sidelink transmissions 513, 514, 515, 516, 520 may be unicast, broadcast, or multicast to nearby devices. For example, UE 504 may transmit transmissions 513, 515 intended to be received by other UEs within range 501 of UE 504, and UE 506 may transmit transmission 516. Additionally or alternatively, RSU 507 may receive communications from, and / or send communications 518 to, UE 502, 504, 506, 508. One or more of UE 502, 504, 506, 508 or RSU 507 may include, for example, a combination of Figure 1 The sidelink DRX configuration component 198 is described.

[0083] The SCI may include a first level SCI (SCI-1) that may be sent in the PSCCH, and a second level SCI (SCI-2) that may be sent in the PSSCH. As an example, SCI-2 may be mapped to consecutive RBs in the PSSCH starting from the first symbol associated with the PSSCH DM-RS. The format of SCI-2 may be indicated in the first level SCI. SCI-1 may be sent in the PSCCH. Multiple resource elements (REs) may be derived based on SCI-1. The starting position of SCI-2 may be defined and known to the UE. In some aspects, the UE may not blindly decode SCI-2. The SCI-2 format may include one or more of a HARQ process identifier (ID), a new data indicator (NDI), a source ID, a destination ID, a CSI report trigger, etc. The SCI-2 format associated with multicast may also include an area ID indicating the location of the transmitter and a communication range for transmitting feedback. Both SCI-1 and SC_2 may use polarization codes (e.g., PDCCH polarization codes).

[0084] The UE may be configured for DRX by the base station. During the RRC connected state, when there is no data transmission in either direction (UL / DL), the UE may operate using the DRX mode. In DRX mode, the UE begins to discontinuously monitor the PDCCH (or other types of transmissions, such as SCI for the sidelink) channel using sleep and wake-up cycles. When the UE is in the RRC connected state, DRX may also be referred to as connected mode DRX (C-DRX). DRX may save battery power at the UE. In non-DRX mode, the UE monitors the PDCCH in each subframe to check if there is available downlink data. Continuous monitoring of the PDCCH (or other types of transmissions, such as SCI for the sidelink) may drain the battery power of the UE. Although PDCCH is given as an example, sidelink transmissions such as PSSCH or PSCCH carrying SCI may also be applicable.

[0085] The DRX configuration of the UE may be configured by the network using RRC signaling from the base station (such as in an RRC connection setup request or an RRC connection reconfiguration request). The DRX configuration may include configuration of one or more timers and values. In some examples, the DRX configuration may include any of an on-duration timer, a DRX inactivity timer, a DRX retransmission timer, a DRX UL retransmission timer, a long DRX cycle, a value of a DRX start offset, a DRX short cycle timer, and / or a short DRX cycle, etc. The DRX cycle may include periodic repetitions of an on-duration and an off-duration of the UE monitoring the PDCCH (or other types of transmissions, such as SCI for a sidelink) from the base station. Figure 6An example of a DRX cycle 600 is illustrated, which includes a periodic on-duration during which the UE monitors the PDCCH (or other types of transmissions, such as SCI for the sidelink) and an off-duration during which the UE may not monitor the PDCCH (or other types of transmissions, such as SCI for the sidelink). During the off-duration, the UE does not monitor the PDCCH (or other types of transmissions, such as SCI for the sidelink). The UE may enter a sleep mode or a low power mode in which the UE minimizes power consumption by turning off radio frequency (RF) functions and not detecting communications from a base station. The DRX cycle may be a duration of an on-time plus an off-time. In some aspects, the DRX cycle may be calculated based on a subframe time and a cycle offset. In some aspects, the on-duration timer may be the duration of the on-time within a DRX cycle. A UE that is in an off-duration or otherwise not monitoring or receiving transmissions may be referred to as being in a "sleep state". A UE that is in an off-duration or another duration during which the UE may be monitoring and receiving transmissions may be referred to as being in an "awake state". An "awake state" may also be referred to as an "active state" or an "extended active state".

[0086] The on-duration timer may correspond to the number of consecutive PDCCH (or other type of transmission, such as SCI for the sidelink) subframes to be monitored or decoded when the UE wakes up from the off-duration in the DRX cycle. The DRX retransmission timer may correspond to a consecutive number of PDCCH (or other type of transmission, such as SCI for the sidelink) subframes for the UE to monitor when the UE expects a retransmission. The DRX inactivity timer may correspond to the amount of time before the UE can enter the off-duration again after successfully decoding the PDCCH (or other type of transmission, such as SCI for the sidelink). The term "inactivity timer" may refer to a timer corresponding to the amount of time the UE can continue to monitor transmissions after the on-duration and before entering the off-duration when successfully decoding the PDCCH, SCI, or MAC-CE.

[0087] The amount of time may be expressed in terms of a transmit time interval (TTI) duration. After the UE successfully receives downlink data, the DRX inactivity timer may start counting the number of subframes. If uplink or downlink data transmission occurs while the DRX inactivity timer is running, the timer may be restarted. If the DRX inactivity timer expires without uplink or downlink activity, the UE may enter a DRX cycle to achieve power savings. The UE may start with a short DRX cycle. The DRX short cycle may correspond to the first DRX cycle that the UE enters after the DRX inactivity timer successfully expires. The DRX short cycle timer may correspond to multiple consecutive subframes during which the UE follows the short DRX cycle after the DRX inactivity timer has expired. The UE is also able to transition to idle mode DRX based on the RRC inactivity timer. Figure 6 Further illustrated is an example showing an example DRX long cycle 650. A UE may enter a long DRX cycle. Figure 6 Example 650 in also illustrates an example DRX long cycle.

[0088] In some aspects, there may not be a PDCCH (or other type of transmission, such as an SCI for a sidelink) received during a DRX cycle. In some aspects, as shown in example 650, there may be a PDCCH received during a DRX cycle, and the on-time may be extended based on the DRX inactivity timer when the PDCCH (or other type of transmission, such as an SCI for a sidelink) is received. In some aspects, based on a MAC-CE command, the on-time may be extended based on the DRX inactivity timer or less than the DRX inactivity timer.

[0089] The amount of power savings achieved by DRX can be improved based on the specific DRX configuration used. In some wireless communication systems, the UE can send a set of parameters to the network in over-the-air (OTA) UE assistance information (UAI) (by sending the UAI to the network entity), indicating the UE's expected values ​​for one or more of the DRX parameters. The set of parameters may include the UE's DRX expectations for any of a long cycle, an inactivity timer, a short cycle, a short cycle timer, etc. The UE's expectations may involve delay budget, overheating at the UE, DRX configuration, etc. The UE may send the UAI to the network entity in RRC signaling. The UAI may be encoded based on abstract syntax symbol one (ASN1) and may include the UE's DRX expectations related to any of a long cycle, an inactivity timer, a short cycle, a short cycle timer, etc. In some aspects, the DRX parameters for which the UE transmits the UAI may include any of an on-duration timer, a DRX inactivity timer, a DRX retransmission timer, a DRX UL retransmission timer, a long DRX cycle, a value of a DRX start offset, a DRX short cycle timer, and / or a short DRX cycle, etc. The network entity may approve the requested DRX expectation by sending an RRC reconfiguration with the requested DRX parameters to the UE after receiving the DRX expectation from the UE.

[0090] Positioning may be based on a side link between UEs, an access link between a network entity and the UE, or based on both the access link and the side link. Fig. 7A FIG. 700 is a diagram illustrating an example of positioning. Fig. 7A As shown, for positioning related to wireless device 706, a first network entity 704A, a second network entity 704B, and a third network entity 704C may be involved, and they may each be associated with a corresponding RTT or TDOA that may be measured. To further improve the accuracy of the location related to wireless device 706, UE 702 (which may be associated with a location known to the network) may be used as an additional anchor point for positioning of wireless device 706. The sidelink RTT between UE 702 and wireless device 706 may be measured. In diagram 700, sidelink positioning and access link positioning may be used jointly.

[0091] Figure 7B FIG. 750 is a diagram illustrating an example of positioning. Figure 7B As shown, for positioning related to wireless device 756, a first UE 752A, a second UE 752B, and a third UE 752C may be involved, and each may be associated with a corresponding RTT that may be measured. In diagram 750, sidelink positioning may be used. Each of the first UE 752A, the second UE 752B, and the third UE 752C may communicate with a network entity 754.

[0092] Figure 7C FIG. 770 is a diagram illustrating an example of positioning. Figure 7C As shown, for positioning of UE 772, network entity 774 may send PRS to UE 772. If PRS cannot be sent directly from network entity 774 to UE 772 (such as when UE 772 is out of coverage), network entity 774 may send PRS to wireless device 776, and wireless device 776 may relay PRS to UE 772.

[0093] Figure 8 800 is a diagram illustrating an example process for sidelink-based positioning. An assistive UE or a network entity may send a PRS to a target UE, and the target UE may measure the propagation time of the PRS (e.g., based on an Rx-Tx time difference measurement) and generate a measurement report. The target UE may send a PRS to an assistive UE or a network entity, and send another PRS to another assistive UE. The other assistive UE may measure the propagation time of the PRS accordingly and generate a measurement report. Thus, the assistive UE and the second assistive UE or the network entity may jointly facilitate an RTT process for the target UE.

[0094] Sidelink communications may include direct wireless communications between a first device (e.g., a first UE or other sidelink device) and a second device (e.g., a second UE or other sidelink device), for example, without routing by a base station. In a first mode, a UE may receive a resource allocation for sidelink communications from a base station. Sidelink resource allocation from a base station may be referred to as "resource allocation mode 1" or a "centralized" resource allocation mode, for example, where a network entity allocates sidelink resources to multiple sidelink devices. Before exchanging communications, the sidelink devices may perform a discovery process to discover each other. In some wireless communication systems, such as for communication systems that support mode 2 resource allocation, the discovery process may include a first UE (which may be referred to as an announcing UE) broadcasting an announcement message received by a second UE (which may be referred to as a monitoring UE). A discovery process in which an announcing UE broadcasts an announcement message to one or more monitoring UEs may be referred to as mode A sidelink discovery. In another type of discovery process, a first UE (which may be referred to as a discoverer UE) transmits a solicitation message including a discovery request, and a second UE (which may be referred to as a discoverer UE) may receive the request and transmit a response message. The discovery process in which the discoverer UE sends a solicitation message including a discovery request to one or more discoverer UEs may be referred to as mode B sidelink discovery.

[0095] To discover a positioning peer (which may be a peer SL UE used to perform positioning), in mode A, the positioning peer UE may announce its presence by sending a SL-pos discovery message with a positioning flag. In mode B, a target UE that wants to discover a positioning peer UE may initiate with a SL-Pos solicitation message with a positioning-related field. Fig.9A FIG900 is a diagram illustrating an example of a positioning peer selection process for SL co-positioning in Mode A. Fig.9A As shown, the positioning peer UE 904 may send a positioning peer discovery message A 906 to the target UE 902. Upon receiving the positioning peer discovery message A 906, the target UE 902 may send a positioning peer discovery response A 908 to the positioning peer UE 904. The positioning peer UE 904 may also send a positioning peer discovery message B 910 to the target UE 902. Upon receiving the positioning peer discovery message B 910, the target UE 902 may send a positioning peer discovery response B 912 to the positioning peer UE 904 to complete the discovery process, and sidelink positioning may be performed between the target UE 902 and the positioning peer UE 904.

[0096] Fig. 9B FIG950 is a diagram illustrating an example of a positioning peer selection process for SL co-positioning in Mode B. Fig. 9B As shown, the target UE 952 may send a positioning peer solicitation message A 956 to the positioning peer UE 954. Upon receiving the positioning peer solicitation message A 956, the positioning peer UE 954 may send a positioning peer solicitation response message A 958 to the target UE 952. The target UE 952 may also send a positioning peer solicitation message B 960 to the positioning peer UE 954. Upon receiving the positioning peer solicitation message B 960, the positioning peer UE 954 may send a positioning peer solicitation response message B 962 to the target UE 952 to complete the discovery process, and sidelink positioning may be performed between the target UE 952 and the positioning peer UE 954.

[0097] Both the sidelink positioning discovery and solicitation messages may be split into 2 parts to enable a more power efficient approach and handshake between the target UE and potential positioning peer UEs. The target UE may rank the potential positioning peer UEs based on one or more of the following: location quality criteria of the anchor point, channel quality criteria, response time criteria, or mobility state criteria.

[0098] The SL DRX configuration may be unicast based on negotiation between UEs. The SL DRX configuration may also be multicast or broadcast based on quality of service (QoS) and layer 2 (L2) destination identifier (ID). When unicast, the SL DRX configuration may include an on timer, an inactivity timer, a HARQ RTT timer, and a HARQ retransmission timer, and a SL DRX command MAC CE. When multicast, the SL DRX configuration may include an on timer, an inactivity timer, a HARQ RTT timer, and a HARQ retransmission timer. When broadcast, the SL DRX configuration may include an on timer. The SL DRX configuration may also include a Tx profile indicating support for SL DRX. The SL DRX configuration may also include the active time of the Rx UE to indicate the active time of the Rx UE to the PHY layer. The SL DRX configuration may also be associated with a non-relay-related ProSe for supporting ProSe communication and ProSe discovery, and an L3 relay-related ProSe for L3 relay-related ProSe communication and discovery. The SL DRX configuration may also include UE capabilities indicating the ability to use non-SL DRX for SL operation and to use the SL DRX configuration for non-SL (such as UL / DL) communications. The term "SL DRX configuration" may refer to a DRX configuration for positioning or non-positioning SL communications between UEs.

[0099] Fig. 10A 1000 is a diagram illustrating an example of SL DRX in Mode 1 and RRC connection. Fig. 10A As shown, Tx UE 1002A may receive a recommended SL DRX configuration 1006 for Rx UE 1002B in SL UE assistance information from Rx UE 1002B. Tx UE 1002A may forward the recommended SL DRX configuration 1006 to a network entity 1004A serving Rx UE 1002A, and network entity 1004A may determine a SL DRX configuration 1008, which may be the same as or different from the SL DRX configuration 1006. Tx UE 1002A may forward the SL DRX configuration 1008 to Rx UE 1002B. Rx UE 1002B may accept or reject the SL DRX configuration 1008 by sending an accept / reject 1010. If the Rx UE 1002B accepts the SL DRX configuration 1008, the Rx UE 1002B may forward the SL DRX configuration 1008 to the network entity 1004B serving the Rx UE 1002B.

[0100] Fig. 10B 1050 is a diagram illustrating an example of SL DRX in Mode 1 and in RRC Inactive and RRC Idle or in Mode 2. Fig. 10BAs shown, Tx UE 1052A may receive a recommended SL DRX configuration 1056 for Rx UE 1052B in the SL UE assistance information from Rx UE 1052B. Tx UE 1002A may determine a SL DRX configuration 1058, which may be the same as or different from the SL DRX configuration 1056. Tx UE 1052A may forward the SL DRX configuration 1058 to Rx UE 1052B. Rx UE 1002B may accept or reject the SL DRX configuration 1058 by sending an accept / reject 1060.

[0101] The SL DRX configuration may be based on a QoS profile for the L2 destination ID. In the case of multiple QoS profiles, in the SL DRX configuration, the SL DRX cycle length may be a minimum cycle length among the cycle lengths associated with the multiple QoS profiles, the SL DRX on timer may be based on a maximum SL DRX on timer among the SL DRX on timers associated with the multiple QoS profiles, and the SL DRX inactivity timer may be a maximum SL DRX inactivity timer among the SL DRX inactivity timers associated with the multiple QoS profiles. Fig.11 1100 is an example of an illustrative SL DRX configuration. The UE may enter a DRX on duration 1102 and may monitor the SCI. Upon receiving an SCI indicating or scheduling a subsequent transmission, the UE may start a SL DRX inactivity timer 1104 and continue to wake up before the SL DRX inactivity timer 1104 expires. In some aspects, the UE may be configured with a common default sidelink DRX configuration. In some aspects, the common default sidelink DRX configuration may be a default SL DRX configuration for a QoS profile that cannot be mapped to a DRX configuration configured for a dedicated QoS profile. In some aspects, when the UE is in coverage, if the UE is in an RRC connected state, the UE may be configured with a SL DRX configuration for multicast and broadcast based on SIB 12 on a dedicated RRC (e.g., a dedicated RRC for handover). In some aspects, when the UE is in coverage, if the UE is in an RRC inactive / idle state, the UE may be configured with a SL DRX configuration for multicast and broadcast based on SIB 12. In some aspects, if the UE is out of coverage, the UE may be configured with a SL DRX configuration before the UE is out of coverage.

[0102] In some aspects, the UE may maintain a separate inactivity timer for each L2 destination ID. In some aspects, for unicast, the SL DRX inactivity timer may be configured for each pair of L2 source and destination IDs. In some aspects, for multicast, a UE (e.g., an RX UE) may maintain a separate inactivity timer for each L2 destination ID. In some aspects, the UE may (re)start the inactivity timer upon receiving an SCI associated with a new SL data transmission (the first time slot after the SCI), and the UE may be active on the SL as long as at least one of the SL inactivity timers associated with unicast or multicast is running. In some aspects, for the Tx UE, for unicast, the TX UE maintains a timer corresponding to the SL inactivity timer in the RX UE for each pair of L2 source and destination IDs (used to determine the allowable transmission time). In the time slot after the SCI transmission indicating the new data transmission, the Tx UE may (re)start its timer corresponding to the SL inactivity timer at the Rx UE. In some aspects, for multicast, the Tx UE may restart the inactivity timer for the L2 destination ID (used to determine the allowable transmission time) upon receiving new data with the same destination ID. In some aspects, the Tx UE may not restart the inactivity timer upon sending an SCI indicating a retransmission.

[0103] Fig.12 1200 is a diagram illustrating an example of a SL DRX configuration. As shown in 1200, the UE may enter a long DRX cycle. The UE may enter a DRX on-duration 1202 to monitor and receive a PDCCH. Upon receiving a PDCCH 1204, the UE may start a DRX inactivity timer 1206 and continue to be awake until the DRX inactivity timer 1206 expires.

[0104] Fig.13 1300 is a diagram illustrating example communications between UE 1302, UE 1304 (such as an auxiliary UE), and one or more other UEs including UE 1303A, UE 1303B, and UE 1303C, which may also be included in some aspects. In some aspects, the one or more other UEs are not included. In some aspects, UE 1302 may be configured with a SL DRX configuration 1306. In some aspects, UE 1302 may receive the SL DRX configuration 1306 from UE 1304. In some aspects, the SL DRX configuration 1306 may be a SL DRX configuration recommended by UE 1304, which may be accepted or rejected by UE 1302 (in some aspects, with confirmation from the network (e.g., as combined with Fig. 10A ), and in some other aspects, independent of network confirmation (e.g., as combined with Fig. 10BIn some aspects, the SL DRX configuration 1306 may be selected by the UE 1302 and sent to the UE 1304. The UE 1304 may accept or reject the SL DRX configuration 1306 (in some aspects, with confirmation from the network (e.g., as in conjunction with Fig. 10A ), and in some other aspects, independent of network confirmation (e.g., as combined with Fig. 10B In some aspects, the SLDRX configuration 1306 may also be sent to one or more other UEs including UE 1303A, UE 1303B, and UE 1303C.

[0105] In some aspects, the SL DRX configuration 1306 may include two inactivity timers, namely a first inactivity timer associated with non-positioning communication and a second inactivity timer associated with positioning communication. As used herein, the term "non-positioning communication" may refer to data communication that is not part of a positioning session. As used herein, the term "positioning communication" may refer to communication that is part of a positioning session, such as a PRS or measurement results. By way of example, the SL DRX configuration 1306 may also include a cycle length, an on timer, a retransmission timer, an RTT timer, or other parameters that may be included in the SL DRX configuration. At 1308, the UE 1302 may enter a sleep state (e.g., in the off duration) based on the SL DRX configuration 1308. At 1310, the UE 1302 may enter an awake state (e.g., in the on duration). In some aspects, during the awake state, the UE 1302 may receive a message 1312, such as an SCI (e.g., SCI-1) or a MAC-CE associated with a subsequent communication 1314 (e.g., such as scheduling or indicating the subsequent communication). In some aspects, in order to receive subsequent communication 1314, at 1316, UE 1302 may continue to be in an awake state (in the on-duration) based on the first inactivity timer or the second inactivity timer. The second inactivity timer may also be referred to as a "positioning inactivity timer". In some aspects, if the message 1312 indicates that the subsequent communication 1314 includes positioning communication without non-positioning communication, the UE 1302 may continue to be in an awake state (in the on-duration) based on the second inactivity timer at 1316. In some aspects, if the message 1312 indicates that the subsequent communication 1314 includes non-positioning communication without positioning communication, the UE 1302 may continue to be in an awake state (in the on-duration) based on the first inactivity timer at 1316. In some aspects, if the message 1312 indicates that the subsequent communication 1314 includes non-positioning communication and positioning communication, the UE 1302 may continue to be in an awake state (in the on-duration) based on the first inactivity timer at 1316. In some aspects, if the message 1312 indicates that the subsequent communication 1314 includes non-positioned communication and positioned communication, the UE 1302 may continue to be in the awake state (for the on-duration) based on the greater of the first inactivity timer and the second inactivity timer at 1316. In some aspects, in addition to receiving the communication 1314, the UE 1302 may also send the SL-PRS after receiving the message 1312.

[0106] In some aspects, the first inactivity timer or the second inactivity timer may be reset after receiving a PRS (e.g., such as the PRS in communication 1314). In some aspects, the PRS that may trigger the reset of the first inactivity timer or the second inactivity timer may be scheduled or indicated by a PSCCH or PSSCH (e.g., including a higher layer message) for a positioning session (e.g., between at least UE 1302 and UE 1304). In some aspects, the second inactivity timer may be applied to each positioning session (e.g., associated with a destination ID, a source / destination ID pair, a session ID, etc.). In some aspects, the value of the second inactivity timer may also be based on the priority of the positioning session.

[0107] Since two inactivity timers are configured, UE 1302 can wake up for different durations based on whether the upcoming transmission is for positioning. For example, for subsequent non-positioning data communications, the wake-up time of UE 1302 can be greater than 20 milliseconds. For subsequent positioning communications, the wake-up time of UE 1302 can be less than 3 milliseconds. Therefore, aspects provided herein can enable a UE configured with SL DRX to save power by enabling the UE to wake up flexibly based on the type of subsequent communication.

[0108] In some aspects, UE 1302 may be aware of the content in communication 1314 and may accordingly wait to receive the content. For example, UE 1302 may wait for SL-PRS from UE 1304 and one or more other UEs including UE 1303A, UE 1303B, and UE 1303C. In some aspects, UE 1302 may wait for SL-PRS and measurement results from UE 1304 and one or more other UEs including UE 1303A, UE 1303B, and UE 1303C. In some aspects, UE 1302 may wait for measurement results from UE 1304 and one or more other UEs including UE 1303A, UE 1303B, and UE 1303C. In some aspects, UE 1302 may extend the continued wake-up at 1306 (and correspondingly extend the first inactivity timer or the second inactivity timer) after receiving content (e.g., SL-PRS or measurement results from UE 1304 and one or more other UEs including UE 1303A, UE 1303B, and UE 1303C).

[0109] In some aspects, if UE 1302 communicates with UE 1304 and one or more other UEs including UE 1303A, UE 1303B, and UE 1303C via groupcast, UE 1302 may wait for content (e.g., SL-PRS or measurement results) from UE 1304 and one or more other UEs including UE 1303A, UE 1303B, and UE 1303C. In some aspects, UE 1302 may extend the continued wake-up (and correspondingly extend the first inactivity timer or the second inactivity timer) at 1306 to wait for content (e.g., SL-PRS or measurement results) from UE 1304 and one or more other UEs including UE 1303A, UE 1303B, and UE 1303C. In some aspects, a maximum time may be configured for UE 1302, wherein UE 1302 may not continue to wake up (and correspondingly extend the first inactivity timer or the second inactivity timer) beyond the maximum time. In some aspects, UE 1302 may be configured with a minimum number (e.g., corresponding to the number of UEs) so that the UE may stop waiting for content (e.g., SL-PRS or measurement results) from UE 1304 and one or more other UEs including UE 1303A, UE 1303B, and UE 1303C, and stop waking up (and correspondingly extending the first inactivity timer or the second inactivity timer) after receiving the minimum number of SL PRS or measurement results. In some aspects, the maximum time and the minimum number may be configured by a network entity. In some aspects, the maximum time and the minimum number may be configured by UE 1304. In some aspects, the maximum time and the minimum number may be configured without signaling from the network or UE 1304.

[0110] In some aspects, the second inactivity timer can be based on (eg, can be a function of) a positioning QoS (eg, associated with a response time parameter, an accuracy parameter, etc.) for the positioning session.

[0111] Fig.14 1400 is a diagram illustrating an example of a SL DRX configuration. Fig.14 As shown, the SL DRX configuration may configure a DRX on time (e.g., DRX on time 1402) and a DRX off time (e.g., DRX off time 1404). Upon receiving an SCI (e.g., SCI reception at 1406), the UE may start an inactivity timer 1408 and continue to monitor and receive subsequent SL data transmissions until the inactivity timer 1408 expires. The UE may be active on the SL (which may also be referred to as being in an awake state) as long as at least one of the SL inactivity timers associated with unicast or broadcast is running. In some aspects, the inactivity timer may be configured to be between 0 milliseconds and 2560 milliseconds.

[0112] Fig.15 1500 is a diagram illustrating an example of a SL DRX configuration. Fig.15 As shown, the SL DRX configuration may configure a DRX on time (e.g., DRX on time 1502) and a DRX off time (e.g., DRX off time 1504). Upon receiving an SCI that schedules / indicates non-positioned data communication (e.g., SCI reception at 1506), the UE may start a first inactivity timer 1508 and continue to monitor and receive subsequent non-positioned SL data transmissions until the first inactivity timer 1508 expires. The UE may be active on the SL (which may also be referred to as being in an awake state) as long as at least one of the SL inactivity timers associated with unicast or broadcast is running. In some aspects, the first inactivity timer may be configured to be between 0 milliseconds and 2560 milliseconds and may be long enough for non-positioned data reception. Upon receiving an SCI that schedules / indicates a positioned communication (e.g., SCI reception at 1510), the UE may start a second inactivity timer 1512 and continue to monitor and receive subsequent non-positioned SL data transmissions until the second inactivity timer 1512 expires. In some aspects, the second inactivity timer may be configured to be between 0 milliseconds and 10 milliseconds and may be long enough for positioning data reception.By having a separate inactivity timer, the UE may save more power.

[0113] Fig.16 1600 is a flow chart of a method of wireless communication. The method may be performed by a UE (eg, UE 104, UE 1302, apparatus 1804).

[0114] At 1602, the UE may receive a SL DRX configuration including a first inactivity timer associated with non-positioning communication and a second inactivity timer associated with positioning communication, wherein the first inactivity timer corresponds to a first duration and the second inactivity timer corresponds to a second duration. For example, UE 1302 may receive SL DRX configuration 1306, including a first inactivity timer associated with non-positioning communication and a second inactivity timer associated with positioning communication, wherein the first inactivity timer corresponds to a first duration and the second inactivity timer corresponds to a second duration. In some aspects, 1602 may be performed by SL DRX configuration component 198.

[0115] At 1604, the UE may enter a sleep state based on the SL DRX configuration. For example, the UE 1302 may enter a sleep state based on the SL DRX configuration (eg, at 1308). In some aspects, 1604 may be performed by the SL DRX configuration component 198.

[0116] At 1606, the UE may initiate a wake state from the sleep state to receive a message associated with scheduling the SL PRS. For example, the UE 1302 may initiate a wake state from the sleep state (e.g., at 1310) to receive a message associated with scheduling the SL PRS (e.g., 1312). In some aspects, 1606 may be performed by the SL DRX configuration component 198. In some aspects, the second inactivity timer is based on one or more of: a positioning QoS associated with the positioning communication, a response time parameter associated with the positioning QoS, or an accuracy parameter associated with the positioning QoS.

[0117] At 1608, the UE may trigger the continuation of the awake state upon receiving the message to receive at least one subsequent transmission including the SL PRS, wherein the duration of the continuation of the awake state is based on the first duration or the second duration. The term "continuation of the awake state" may refer to continuing to monitor or receive transmissions outside the DRX on-duration. For example, UE1302 may trigger the continuation of the awake state upon receiving the message (e.g., at 1316) to receive at least one subsequent transmission including the SL PRS (e.g., at 1314), wherein the duration of the continuation of the awake state is based on the first duration or the second duration. In some aspects, the UE may trigger the continuation, and may start counting down the first inactivity timer or the second inactivity timer after receiving the message, and the UE may continue to be in the awake state until the first inactivity timer or the second inactivity timer expires. In some aspects, 1608 may be performed by the SL DRX configuration component 198. In some aspects, when the at least one subsequent transmission includes the SL PRS without non-positioning related data, the continuation is based on the second inactivity timer. In some aspects, when the at least one subsequent transmission includes SL PRS and non-positioning related data, the continuation is based on a second inactivity timer. In some aspects, when the at least one subsequent transmission includes SL PRS and non-positioning related data, the continuation is based on the longer of the first duration or the second duration. In some aspects, the first inactivity timer or the second inactivity timer is reset upon receipt of the SL PRS. In some aspects, the SL PRS is scheduled or indicated by the PSCCH or PSSCH for a positioning session associated with the positioning communication. In some aspects, the second inactivity timer is associated with a positioning session associated with the positioning communication, wherein the positioning session is associated with a destination identifier, a source and destination identifier pair, or a session identifier.

[0118] In some aspects, the UE may also receive an indication of content to be received in the at least one subsequent transmission, or determine the content to be received in the at least one subsequent transmission based on the second configuration. In some aspects, the content includes an SL PRS. In some aspects, the content includes an SL PRS and a set of measurement results associated with a group of UEs. In some aspects, the content includes a set of measurement results associated with a group of UEs without an SL PRS. In some aspects, the UE may also trigger the continuation of the wake-up state after the first duration or the second duration upon receiving a subset of the content. In some aspects, the content includes a set of measurement results associated with a group of UEs, and the UE may trigger the continuation of the wake-up state after the first duration or the second duration upon receiving a first subset of the content, wherein the continuation is triggered until a maximum time or until a second subset of the content is received, the second subset of the content including the minimum number of measurement results in the set of measurement results. In some aspects, the second inactivity timer is based on one or more of the following: a positioning QoS associated with positioning communication, a response time parameter associated with the positioning QoS, or an accuracy parameter associated with the positioning QoS.

[0119] Fig.17 1700 is a flow chart of a method of wireless communication. The method may be performed by a UE (eg, UE 104, UE 1304, apparatus 1804).

[0120] At 1702, a UE can establish a positioning session with a second UE. For example, UE 1304 can establish a positioning session with second UE 1302. In some aspects, 1702 can be performed by SL DRX configuration component 198.

[0121] At 1704, the UE may send a SL DRX configuration including a first inactivity timer associated with non-positioning communication and a second inactivity timer associated with positioning communication, wherein the first inactivity timer corresponds to a first duration and the second inactivity timer corresponds to a second duration. For example, UE 1304 may send a SL DRX configuration 1306, including a first inactivity timer associated with non-positioning communication and a second inactivity timer associated with positioning communication, wherein the first inactivity timer corresponds to a first duration and the second inactivity timer corresponds to a second duration. In some aspects, 1704 may be performed by a SL DRX configuration component 198. In some aspects, the second inactivity timer is associated with a positioning session, wherein the positioning session is associated with a destination identifier, a source and destination identifier pair, or a session identifier. In some aspects, the second inactivity timer is based on one or more of the following: a positioning QoS associated with positioning communication, a response time parameter associated with the positioning QoS, or an accuracy parameter associated with the positioning QoS.

[0122] At 1706, the UE may transmit a message associated with scheduling a SL PRS, wherein at least one subsequent transmission to the UE includes the SL PRS. For example, UE 1304 may transmit a message associated with scheduling a SL PRS (e.g., 1312), wherein at least one subsequent transmission to the UE (e.g., 1314) includes the SL PRS. In some aspects, 1706 may be performed by SL DRX configuration component 198. In some aspects, the message is an SCI or a MAC-CE.

[0123] Fig.181800 is a diagram illustrating an example of a hardware implementation for an apparatus 1804. The apparatus 1804 may be a UE, a component of a UE, or may implement UE functionality. In some aspects, the apparatus 1804 may include a cellular baseband processor 1824 (also referred to as a modem) coupled to one or more transceivers 1822 (e.g., a cellular RF transceiver). The cellular baseband processor 1824 may include on-chip memory 1824'. In some aspects, the apparatus 1804 may also include one or more subscriber identity module (SIM) cards 1820 and an application processor 1806 coupled to a secure digital (SD) card 1808 and a screen 1810. The application processor 1806 may include on-chip memory 1806'. In some aspects, the device 1804 may also include a Bluetooth module 1812, a WLAN module 1814, a satellite system module 1816 (e.g., a GNSS module), one or more sensor modules 1818 (e.g., an atmospheric pressure sensor / altimeter; a motion sensor such as an inertial management 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 1826, a power source 1830, and / or a camera 1832. The Bluetooth module 1812, the WLAN module 1814, and the satellite system module 1816 may include an on-chip transceiver (TRX) / receiver (RX). The cellular baseband processor 1824 communicates with the UE 104 and / or with a RU associated with the network entity 1802 through the transceiver 1822 via one or more antennas 1880. The cellular baseband processor 1824 and the application processor 1806 may each include a computer-readable medium / memory 1824', 1806', respectively. The additional memory module 1826 may also be considered a computer-readable medium / memory. Each computer-readable medium / memory 1824', 1806', 1826 may be non-transitory. The cellular baseband processor 1824 and the application processor 1806 are each responsible for general processing, including executing software stored on a computer-readable medium / memory. The software enables the cellular baseband processor 1824 / application processor 1806 to perform various functions described herein when executed by the cellular baseband processor 1824 / application processor 1806. The computer-readable medium / memory may also be used to store data manipulated by the cellular baseband processor 1824 / application processor 1806 when executing the software. The cellular baseband processor 1824 / application processor 1806 may be a component of the device 350 and may include at least one of the memory 360 and / or the TX processor 368, the RX processor 356, and the controller / processor 359.In one configuration, the device 1804 may be a processor chip (modem and / or application) and include only the cellular baseband processor 1824 and / or the application processor 1806, and in another configuration, the device 1804 may be an entire UE (eg, see. Figure 3 350 ) and includes an additional module of device 1804 .

[0124] As discussed herein, the sidelink DRX configuration component 198 may be configured to receive a SL DRX configuration including a first inactivity timer associated with non-positioning communication and a second inactivity timer associated with positioning communication, wherein the first inactivity timer corresponds to a first duration and the second inactivity timer corresponds to a second duration. In some aspects, the sidelink DRX configuration component 198 may be further configured to enter a sleep state based on the SL DRX configuration. In some aspects, the sidelink DRX configuration component 198 may be further configured to initiate a wake-up state from the sleep state to receive a message associated with scheduling a SL PRS. In some aspects, the sidelink DRX configuration component 198 may be further configured to trigger a continuation of the wake-up state upon receipt of the message to receive at least one subsequent transmission including the SL PRS, wherein the duration of the continuation of the wake-up state is based on the first duration or the second duration.

[0125] In some aspects, the sidelink DRX configuration component 198 may be configured to establish a positioning session with the second UE. In some aspects, the sidelink DRX configuration component 198 may be further configured to send a SL DRX configuration, the SL DRX configuration including a first inactivity timer associated with non-positioning communication and a second inactivity timer associated with positioning communication, wherein the first inactivity timer corresponds to a first duration and the second inactivity timer corresponds to a second duration. In some aspects, the sidelink DRX configuration component 198 may be further configured to send a message associated with scheduling a SL PRS, wherein at least one subsequent transmission to the UE includes the SL PRS

[0126] The sidelink DRX configuration component 198 may be within the cellular baseband processor 1824, the application processor 1806, or both the cellular baseband processor 1824 and the application processor 1806. The sidelink DRX configuration component 198 may be one or more hardware components specifically configured to perform the process / algorithm, implemented by one or more processors configured to perform the process / algorithm, stored in a computer-readable medium to be implemented by one or more processors, or some combination thereof. As shown, the device 1804 may include a variety of components configured for various functions. In one configuration, the device 1804 (particularly the cellular baseband processor 1824 and / or the application processor 1806) includes a component for receiving a SL DRX configuration, the SL DRX configuration including a first inactivity timer associated with non-positioning communication and a second inactivity timer associated with positioning communication, wherein the first inactivity timer corresponds to a first duration and the second inactivity timer corresponds to a second duration. In some aspects, the device 1804 may also include a component for entering a sleep state based on the SL DRX configuration. In some aspects, the device 1804 may also include a component for initiating a wake state from a sleep state to receive a message associated with a scheduled SL PRS. In some aspects, the device 1804 may also include a component for triggering the continuation of the wake state to receive at least one subsequent transmission including the SL PRS upon receiving the message, wherein the duration of the continuation of the wake state is based on the first duration or the second duration. In some aspects, the device 1804 may also include a component for receiving an indication of the content to be received in the at least one subsequent transmission or determining the content to be received in the at least one subsequent transmission based on a second configuration. In some aspects, the device 1804 may also include a component for triggering the continuation of the wake state after the first duration or the second duration upon receiving a subset of the content. In some aspects, the device 1804 may also include a component for triggering the continuation of the wake state after the first duration or the second duration after receiving the first subset of the content, wherein the continuation is triggered until a maximum time or until a second subset of the content is received, the second subset of the content including the minimum number of measurement results in the group of measurement results. In some aspects, the apparatus 1804 may also include means for establishing a positioning session with the UE. In some aspects, the apparatus 1804 may also include means for sending a SL DRX configuration, the SL DRX configuration including a first inactivity timer associated with non-positioning communication and a second inactivity timer associated with positioning communication, wherein the first inactivity timer corresponds to a first duration and the second inactivity timer corresponds to a second duration. In some aspects, the apparatus 1804 may also include means for sending a message associated with scheduling a SL PRS, wherein at least one subsequent transmission to the UE includes the SL PRS.The means may be the sidelink DRX configuration component 198 of the apparatus 1804 configured to perform the functions recited by the means. As described herein, the apparatus 1804 may include a TX processor 368, an RX processor 356, and a controller / processor 359. Thus, in one configuration, the means may be the TX processor 368, the RX processor 356, and / or the controller / processor 359 configured to perform the functions recited by the means.

[0127] It should be understood that the specific order or hierarchy of the blocks in the disclosed process / flowchart is only an illustration of the exemplary method. It should be understood that the specific order or hierarchy of the blocks in the process / flowchart can be rearranged based on design preferences. In addition, some blocks can be combined or omitted. The attached method claims provide the elements of each block in a sample order, but are not limited to the specific order or hierarchy provided.

[0128] 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 otherwise specified, 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 specified, 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, and 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, data can be directly received / sent between the first device and the second device, or indirectly received / sent between the first device and the second device through a collection of devices. All structural and functional equivalents of the elements throughout the various aspects described in this disclosure that are known or will be known later 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" 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..."

[0129] 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, conditions, factors, etc.) should be interpreted as "based at least on A" unless specifically stated differently.

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

[0131] Aspect 1 is a device for performing wireless communications at a user equipment (UE), the device comprising: a memory; and at least one processor, the at least one processor being coupled to the memory and, based at least in part on information stored in the memory, the at least one processor being configured to: receive a side link (SL) discontinuous reception (DRX) configuration, the SL DRX configuration comprising a first inactivity timer associated with non-positioning communications and a second inactivity timer associated with positioning communications, wherein the first inactivity timer corresponds to a first duration and the second inactivity timer corresponds to a second duration; enter a sleep state based on the SL DRX configuration; initiate a wake-up state from the sleep state to receive a message associated with a scheduled SL positioning reference signal (PRS); and trigger continuation of the wake-up state upon receipt of the message to receive at least one subsequent transmission including the SL PRS, wherein the duration of the continuation of the wake-up state is based on the first duration or the second duration.

[0132] Aspect 2 is the apparatus according to aspect 1, wherein when the at least one subsequent transmission includes the SL PRS without non-positioning related data, the continuing is based on the second inactivity timer.

[0133] Aspect 3 is an apparatus according to any one of aspects 1 to 2, wherein when the at least one subsequent transmission includes the SL PRS and non-positioning related data, the continuing is based on the first inactivity timer.

[0134] Aspect 4 is an apparatus according to any one of aspects 1 to 3, wherein when the at least one subsequent transmission includes the SL PRS and non-positioning related data, the continuation is based on the longer of the first duration or the second duration.

[0135] Aspect 5 is an apparatus according to any one of aspects 1 to 4, wherein the first inactivity timer or the second inactivity timer is reset when the SL PRS is received.

[0136] Aspect 6 is an apparatus according to any one of Aspects 1 to 5, wherein the SL PRS is scheduled or indicated by a physical sidelink control channel (PSCCH) or a physical sidelink shared channel (PSSCH) for a positioning session associated with the positioning communication.

[0137] Aspect 7 is an apparatus according to any one of aspects 1 to 6, wherein the second inactivity timer is associated with a positioning session associated with the positioning communication, wherein the positioning session is associated with a destination identifier, a source and destination identifier pair, or a session identifier.

[0138] Aspect 8 is an apparatus according to any one of Aspects 1 to 7, wherein the at least one processor is configured to: receive an indication of content to be received in the at least one subsequent transmission, or determine the content to be received in the at least one subsequent transmission based on a second configuration.

[0139] Aspect 9 is an apparatus according to any one of aspects 1 to 8, wherein the content includes the SL PRS.

[0140] Aspect 10 is an apparatus according to any one of aspects 1 to 9, wherein the content includes the SL PRS and a set of measurement results associated with a set of UEs.

[0141] Aspect 11 is an apparatus according to any one of aspects 1 to 10, wherein the content includes a set of measurement results associated with a set of UEs without the SL PRS.

[0142] Aspect 12 is an apparatus according to any one of aspects 1 to 11, wherein the at least one processor is configured to: trigger the continuation of the wake state after the first duration or the second duration upon receiving the subset of the content.

[0143] Aspect 13 is an apparatus according to any one of Aspects 1 to 12, wherein the content includes a set of measurement results associated with a group of UEs, and wherein the at least one processor is configured to: trigger the continuation of the wake-up state after the first duration or the second duration when a first subset of the content is received, wherein the continuation is triggered until a maximum time or until a second subset of the content is received, and the second subset of the content includes the minimum number of measurement results in the set of measurement results.

[0144] Aspect 14 is an apparatus according to any one of aspects 1 to 13, wherein the second inactivity timer is based on one or more of the following: a positioning quality of service (QoS) associated with the positioning communication, a response time parameter associated with the positioning QoS, or an accuracy parameter associated with the positioning QoS.

[0145] Aspect 15 is an apparatus according to any one of aspects 1 to 14, wherein the message is sidelink control information (SCI) or a medium access control (MAC) control element (MAC-CE).

[0146] Aspect 16 is an apparatus according to any one of aspects 1 to 15, the apparatus further comprising a transceiver or an antenna coupled to the at least one processor, and wherein the transceiver or the antenna is configured to receive the at least one subsequent transmission.

[0147] Aspect 17 is an apparatus for performing wireless communications at a user equipment (UE), the apparatus comprising: 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: establish a positioning session with a second user equipment (UE); send a side link (SL) discontinuous reception (DRX) configuration, the SL DRX configuration comprising a first inactivity timer associated with non-positioning communication and a second inactivity timer associated with positioning communication, wherein the first inactivity timer corresponds to a first duration and the second inactivity timer corresponds to a second duration; and send a message associated with a scheduled SL positioning reference signal (PRS), wherein at least one subsequent transmission to the UE includes the SL PRS.

[0148] Aspect 18 is the apparatus according to aspect 17, wherein the second inactivity timer is associated with the positioning session, wherein the positioning session is associated with a destination identifier, a source and destination identifier pair, or a session identifier.

[0149] Aspect 19 is an apparatus according to any one of aspects 17 to 18, wherein the second inactivity timer is based on one or more of the following: a positioning quality of service (QoS) associated with the positioning communication, a response time parameter associated with the positioning QoS, or an accuracy parameter associated with the positioning QoS.

[0150] Aspect 20 is an apparatus according to any one of aspects 17 to 19, wherein the message is sidelink control information (SCI) or a medium access control (MAC) control element (MAC-CE).

[0151] Aspect 21 is an apparatus according to any one of aspects 17 to 20, the apparatus further comprising a transceiver or an antenna coupled to the at least one processor, and wherein the transceiver or the antenna is configured to transmit the at least one subsequent transmission.

[0152] Aspect 22 is an apparatus for wireless communication at a UE, the apparatus comprising: a memory and at least one processor, the at least one processor being coupled to the memory and, based at least in part on information stored in the memory, the at least one processor being configured to perform a method according to any one of aspects 1 to 16. The apparatus may include at least one of a transceiver or an antenna coupled to the at least one processor.

[0153] Aspect 23 is an apparatus for wireless communication, the apparatus comprising means for performing the method according to any one of aspects 1 to 16.

[0154] Aspect 24 is 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 16.

[0155] Aspect 25 is an apparatus for wireless communication at a network entity, the apparatus comprising 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 perform a method according to any one of aspects 17 to 21. The apparatus may include at least one of a transceiver or an antenna coupled to the at least one processor.

[0156] Aspect 26 is an apparatus for wireless communication, the apparatus comprising means for performing the method according to any one of aspects 17 to 21.

[0157] Aspect 27 is 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 17 to 21.

Claims

1. An apparatus for wireless communication at a user equipment (UE), the apparatus comprising: Memory; and 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 configured to: a receive side link (SL) discontinuous reception (DRX) configuration, the SL DRX configuration comprising a first inactivity timer associated with non-positioning communications and a second inactivity timer associated with positioning communications, wherein the first inactivity timer corresponds to a first duration and the second inactivity timer corresponds to a second duration; Entering a sleep state based on the SL DRX configuration; initiating a wake state from the sleep state to receive a message associated with a scheduled SL positioning reference signal (PRS); and A continuation of the awake state is triggered upon receipt of the message to receive at least one subsequent transmission including the SL PRS, wherein a duration of the continuation of the awake state is based on the first duration or the second duration.

2. The apparatus of claim 1, wherein the continuing is based on the second inactivity timer when the at least one subsequent transmission includes the SL PRS without non-positioning related data.

3. The apparatus of claim 1, wherein the continuing is based on the first inactivity timer when the at least one subsequent transmission includes the SL PRS and non-positioning related data.

4. The apparatus of claim 1, wherein when the at least one subsequent transmission includes the SL PRS and non-positioning related data, the continuation is based on a longer of the first duration or the second duration. 5 . The apparatus of claim 1 , wherein the first inactivity timer or the second inactivity timer is reset when the SL PRS is received. 6 . The apparatus of claim 1 , wherein the SL PRS is scheduled or indicated by a physical sidelink control channel (PSCCH) or a physical sidelink shared channel (PSSCH) for a positioning session associated with the positioning communication.

7. The apparatus of claim 1, wherein the second inactivity timer is associated with a positioning session associated with the positioning communication, wherein the positioning session is associated with a destination identifier, a source and destination identifier pair, or a session identifier.

8. The apparatus of claim 1, wherein the at least one processor is configured to receive an indication of content to be received in the at least one subsequent transmission, or to determine the content to be received in the at least one subsequent transmission based on a second configuration.

9. The apparatus of claim 8, wherein the content comprises the SL PRS.

10. The apparatus of claim 8, wherein the content comprises the SL PRS and a set of measurement results associated with a set of UEs.

11. The apparatus of claim 8, wherein the content comprises a set of measurement results associated with a set of UEs without the SL PRS.

12. The apparatus of claim 8, wherein the at least one processor is configured to: The continuation of the awake state after the first duration or the second duration is triggered upon receipt of the subset of the content.

13. The apparatus of claim 12, wherein the content comprises a set of measurement results associated with a set of UEs, and wherein the at least one processor is configured to: The continuation of the wake-up state after the first duration or the second duration is triggered upon receipt of a first subset of the content, wherein the continuation is triggered until a maximum time or until a second subset of the content is received, the second subset of the content including a minimum number of measurement results from the set of measurement results.

14. The apparatus of claim 1, wherein the second inactivity timer is based on one or more of: a positioning quality of service (QoS) associated with the positioning communication, a response time parameter associated with the positioning QoS, or an accuracy parameter associated with the positioning QoS.

15. The apparatus of claim 1, wherein the message is sidelink control information (SCI) or a medium access control (MAC) control element (MAC-CE).

16. The apparatus of claim 1, further comprising a transceiver or an antenna coupled to the at least one processor, and wherein the transceiver or the antenna is configured to receive the at least one subsequent transmission.

17. An apparatus for wireless communication at a user equipment (UE), the apparatus comprising: Memory; and 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 configured to: establishing a positioning session with a second user equipment (UE); transmitting a side link (SL) discontinuous reception (DRX) configuration, the SL DRX configuration comprising a first inactivity timer associated with non-positioning communications and a second inactivity timer associated with positioning communications, wherein the first inactivity timer corresponds to a first duration and the second inactivity timer corresponds to a second duration; as well as A message associated with scheduling a SL positioning reference signal (PRS) is transmitted, wherein at least one subsequent transmission to the UE includes the SL PRS.

18. The apparatus of claim 17, wherein the second inactivity timer is associated with the positioning session, wherein the positioning session is associated with a destination identifier, a source and destination identifier pair, or a session identifier.

19. The apparatus of claim 17, wherein the second inactivity timer is based on one or more of: a positioning quality of service (QoS) associated with the positioning communication, a response time parameter associated with the positioning QoS, or an accuracy parameter associated with the positioning QoS.

20. The apparatus of claim 17, wherein the message is sidelink control information (SCI) or a medium access control (MAC) control element (MAC-CE).

21. The apparatus of claim 17, further comprising a transceiver or an antenna coupled to the at least one processor, and wherein the transceiver or the antenna is configured to transmit the at least one subsequent transmission.

22. A method of wireless communication at a user equipment (UE), the method comprising: a receive side link (SL) discontinuous reception (DRX) configuration, the SL DRX configuration comprising a first inactivity timer associated with non-positioning communications and a second inactivity timer associated with positioning communications, wherein the first inactivity timer corresponds to a first duration and the second inactivity timer corresponds to a second duration; Entering a sleep state based on the SL DRX configuration; initiating a wake state from the sleep state to receive a message associated with a scheduled SL positioning reference signal (PRS); and A continuation of the awake state is triggered upon receipt of the message to receive at least one subsequent transmission including the SL PRS, wherein a duration of the continuation of the awake state is based on the first duration or the second duration.

23. The method of claim 22, wherein the continuing is based on the second inactivity timer when the at least one subsequent transmission includes the SL PRS without non-positioning related data.

24. The method of claim 22, wherein the continuing is based on the first inactivity timer when the at least one subsequent transmission includes the SL PRS and non-positioning related data.

25. The method of claim 22, wherein when the at least one subsequent transmission includes the SL PRS and non-positioning related data, the continuing is based on the longer of the first duration or the second duration.

26. The method of claim 22, wherein the first inactivity timer or the second inactivity timer is reset upon receiving the SL PRS.

27. The method of claim 22, wherein the SL PRS is scheduled or indicated by a physical sidelink control channel (PSCCH) or a physical sidelink shared channel (PSSCH) for a positioning session associated with the positioning communication.

28. The method of claim 22, wherein the second inactivity timer is associated with a positioning session associated with the positioning communication, wherein the positioning session is associated with a destination identifier, a source and destination identifier pair, or a session identifier.

29. The method of claim 22, wherein the message is sidelink control information (SCI) or a medium access control (MAC) control element (MAC-CE).

30. A method of wireless communication at a first user equipment (UE): establishing a positioning session with a second user equipment (UE); a transmitting side link (SL) discontinuous reception (DRX) configuration, the SL DRX configuration comprising a first inactivity timer associated with non-positioning communications and a second inactivity timer associated with positioning communications, wherein the first inactivity timer corresponds to a first duration and the second inactivity timer corresponds to a second duration; and A message associated with scheduling a SL positioning reference signal (PRS) is transmitted, wherein at least one subsequent transmission to the UE includes the SL PRS.

Images