Relay-assisted remote UE positioning reporting

Abstract

A relay user equipment (UE) may be configured to receive an indication of one or more of at least one first quality of service (QoS) parameter of a first wireless link or at least one second QoS parameter of a second wireless link. The first wireless link may be associated with the relay UE and a network entity. The second wireless link may be associated with the relay UE and at least one remote UE. The at least one first QoS parameter and the at least one second QoS parameter may be associated with a time period. The relay UE may be configured to send a report of at least one positioning measurement over the time period based on one or more of the at least one first QoS parameter or the at least one second QoS parameter.

Description

[0001] CROSS-REFERENCE TO RELATED APPLICATIONS

[0002] This application claims the benefit of Greek patent application serial number 20220100567, filed on July 18, 2022, entitled “RELAY-ASSISTED REMOTE UEPOSITIONING REPORTING”, 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 a relay-assisted remote user equipment (UE) positioning system. 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 continuous mobile broadband evolution promulgated by the Third Generation Partnership Project (3GPP) to meet new requirements associated with latency, reliability, security, scalability (e.g., with the Internet of Things (IoT)) and other requirements. 5GNR includes services associated with enhanced mobile broadband (eMBB), massive machine type communication (mMTC), and ultra-reliable low latency communication (URLLC). Certain aspects of 5G NR may be based on 4G Long Term Evolution (LTE) standards. It is necessary to further improve 5G NR technology. 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 neither identifies the key or important elements of all aspects, nor describes the scope of any or all aspects. Its sole purpose is to present some concepts of one or more aspects in a simplified form as a prelude to a more detailed description presented later.

[0007] In one aspect of the present disclosure, a method, a computer-readable medium, and an apparatus are provided. The apparatus may have a memory and at least one processor coupled to the memory at a relay UE. Based at least in part on information stored in the memory, the at least one processor may be configured to: receive an indication of one or more of at least one first quality of service (QoS) parameter of a first wireless link or at least one second QoS parameter of a second wireless link. The indication may be received from a network entity. The first wireless link may be associated with the relay UE and the network entity. The second wireless link may be associated with the relay UE and at least one remote UE. The at least one first QoS parameter and the at least one second QoS parameter may be associated with a time period. Based at least in part on information stored in the memory, the at least one processor may be configured to: send a report of at least one positioning measurement within the time period based on one or more of the at least one first QoS parameter or the at least one second QoS parameter. The report may be sent to the network entity.

[0008] In one aspect of the present disclosure, a method, a computer-readable medium, and an apparatus are provided. The apparatus may have a memory and at least one processor coupled to the memory at a network entity. Based at least in part on information stored in the memory, the at least one processor may be configured to: send an indication of one or more of at least one first QoS parameter of a first wireless link or at least one second QoS parameter of a second wireless link. The indication may be sent to a relay UE. The first wireless link may be associated with the relay UE and the network entity. The second wireless link may be associated with the relay UE and at least one remote UE. The at least one first QoS parameter and the at least one second QoS parameter may be associated with a time period. Based at least in part on information stored in the memory, the at least one processor may be configured to: obtain a report of at least one positioning measurement within the time period based on one or more of the at least one first QoS parameter or the at least one second QoS parameter. The report may be obtained from the relay UE.

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

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

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

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

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

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

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

[0016] Figure 4 is a diagram illustrating example aspects of a slot structure that may be used for sidelink communications.

[0017] Figure 5 is a diagram illustrating an example of sidelink communications between devices according to various aspects presented herein.

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

[0019] Figure 7 is a diagram illustrating an example of a remote UE configured to perform a positioning session through a relay UE.

[0020] Figure 8 is a diagram illustrating another example of a remote UE configured to perform a positioning session through a relay UE.

[0021] Fig. 9 is a diagram illustrating another example of a remote UE configured to perform a positioning session through a relay UE.

[0022] Fig.10 is a diagram illustrating another example of a remote UE configured to perform a positioning session through a relay UE.

[0023] Fig.11 is a flow chart of a method of wireless communication.

[0024] Fig.12 is another flow chart of a method of wireless communication.

[0025] Fig.13 are diagrams illustrating examples of hardware implementations for example apparatuses and / or network entities.

[0026] Fig.14is a diagram illustrating an example of a hardware implementation for an example network entity.

[0027] Fig.15 is a diagram illustrating an example of a hardware implementation for an example network entity. DETAILED DESCRIPTION

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

[0029] Several aspects of telecommunication systems are 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 may be implemented using electronic hardware, computer software, or any combination thereof. Whether these elements are implemented as hardware or software depends on the specific application and the design constraints imposed on the overall system.

[0030] 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, gated 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.

[0031] Therefore, in one or more example aspects, specific implementations and / or use cases, the described functions 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 may be used to store computer executable code in the form of instructions or data structures that can be accessed by a computer.

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

[0033] The deployment of a communication system (such as a 5G NR system) can be arranged with various components or constituent parts in a variety of ways. In a 5G NR system or network, a network node, a network entity, a mobility element of a network, a radio access network (RAN) node, a core network node, a network element or a network equipment (such as a base station (BS), or one or more units (or one or more components) that perform 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.

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

[0035] Base station operation or network design may take into account the aggregated nature of base station functionality. For example, a disaggregated base station may be used in an integrated access backhaul (IAB) network, an open radio access network (O-RAN (network configuration such as that initiated by the O-RAN Alliance)), or a virtualized radio access network (vRAN, also known as a cloud radio access network (C-RAN)). Decomposition may include distributing 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.

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

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

[0038] In some aspects, CU 110 may host one or more higher layer control functions. Such control functions may include radio resource control (RRC), packet data convergence protocol (PDCP), service data adaptation protocol (SDAP), etc. Each control function may be implemented using an interface that is configured to communicate signals with other control functions hosted by CU 110. 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, CU 110 may be logically split into one or more CU-UP units and one or more CU-CP units. When implemented in an O-RAN configuration, the CU-UP unit may communicate bidirectionally with the CU-CP unit via an interface (such as an E1 interface). As needed, CU 110 may be implemented to communicate with DU 130 for network control and signaling.

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

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

[0041] 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 instantiating 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. Additionally, 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 .

[0042] 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 through an interface (such as via an E2 interface) that connects one or more CUs 110, one or more DUs 130, or both, and the O-eNB with the near-RT RIC 125.

[0043] 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 for performance and employ AI / ML models to perform corrective actions through the SMO framework 105 (such as via reconfiguration of O1) or via creation of RAN management policies (such as A1 policies).

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

[0045] 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 various wireless D2D communication systems, such as Bluetooth, Wi-Fi based on the Institute of Electrical and Electronics Engineers (IEEE) 802.11 standard, LTE, or NR.

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

[0047] The electromagnetic spectrum is typically subdivided into various categories, bands, channels, etc. based on frequency / wavelength. In 5GNR, two initial operating bands have been identified as frequency range designations FR1 (410 MHz-7.125 GHz) and FR2 (24.25 GHz-52.6 GHz). Although a portion of FR1 is greater than 6 GHz, FR1 is often referred to (interchangeably) as the “below 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) identified as the “millimeter wave” band by the International Telecommunication Union (ITU).

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

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

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

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

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

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

[0054] Reference again Figure 1In some aspects, the UE 104 may have a relay communication component 198 configured to receive an indication of one or more of at least one first QoS parameter of the first radio link or at least one second QoS parameter of the second radio link. The indication may be received from a network entity, such as a base station 102. The first radio link may be associated with a relay UE and a network entity. The second radio link may be associated with a relay UE and at least one remote UE. The at least one first QoS parameter and the at least one second QoS parameter may be associated with a time period. The relay communication component 198 may be configured to send a report of at least one positioning measurement within the time period based on one or more of the at least one first QoS parameter or the at least one second QoS parameter. The report may be sent to the network entity. In some aspects, the base station 102 may have a relay configuration component 199 configured to send an indication of one or more of the at least one first QoS parameter of the first radio link or at least one second QoS parameter of the second radio link. The indication may be sent to the relay UE. The first radio link may be associated with the relay UE and a network entity. The second wireless link may be associated with a relay UE and at least one remote UE. The at least one first QoS parameter and the at least one second QoS parameter may be associated with a time period. The relay configuration component 199 may be configured to obtain a report of at least one positioning measurement within the time period based on one or more of the at least one first QoS parameter or the at least one second QoS parameter. The report may be obtained from the relay UE. Although the following description may focus on side link communications, the concepts described herein may be applicable to any D2D communication link. Although the following description may focus on 5G NR or LTE, the concepts described herein may be applicable to other similar fields, such as LTE-A, CDMA, GSM and other wireless technologies.

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

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

[0057]

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

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

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

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

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

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

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

[0065] The transmit (Tx) processor 316 and receive (Rx) processor 370 implement layer 1 functionality associated with various signal processing functions. Layer 1 (which includes the physical (PHY) layer) may include error detection on the transport channel, forward error correction (FEC) coding / decoding of the transport channel, interleaving, rate matching, mapping to the physical channel, modulation / demodulation of the physical channel, and MIMO antenna processing. The Tx processor 316 handles the mapping to the signal constellation based on various modulation schemes (e.g., binary phase shift keying (BPSK), quadrature phase shift keying (QPSK), M-phase shift keying (M-PSK), M-quadrature amplitude modulation (M-QAM)). The coded and modulated symbols can then be split into parallel streams. Each stream can then be mapped to an OFDM subcarrier, multiplexed with a reference signal (e.g., a pilot) in the time 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-coded to generate multiple spatial streams. Channel estimates from a channel estimator 374 may be used to determine the coding and modulation schemes, as well as for spatial processing. Channel estimates may be derived from reference signals and / or channel condition feedback sent by the UE 350. Each spatial stream may then be provided to a different antenna 320 via a separate transmitter 318Tx. Each transmitter 318Tx may modulate a radio frequency (RF) carrier with a corresponding spatial stream for transmission.

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

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

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

[0069] Channel estimates derived by the channel estimator 358 from a reference signal or feedback sent by the base station 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.

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

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

[0072] At least one of the Tx processor 368, the Rx processor 356, and the controller / processor 359 may be configured to perform Figure 1 The relay communication component 198 combines various aspects.

[0073] At least one of the Tx processor 316, the Rx processor 370, and the controller / processor 375 may be configured to perform Figure 1 The relay configuration component 199 combines various aspects.

[0074] Figure 4 Included are diagrams 400 and 410 illustrating 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. While 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 4 The example time slot structure in is only an example, and other side link communications may have different frame structures and / or different channels for side link communications. A frame (10ms) may be divided into 10 equally sized subframes (1ms). Each subframe may include one or more time slots. A subframe may also include a micro time slot, which may include 7, 4 or 2 symbols. Each time slot may include 7 or 14 symbols, depending on the time slot configuration. For time slot configuration 0, each time slot may include 14 symbols, and for time slot configuration 1, each time slot may include 7 symbols. Schematic diagram 400 illustrates a single resource block transmitted in a single time slot corresponding to a 0.5ms transmission time interval (TTI). The physical side link control channel may be configured to occupy multiple physical resource blocks (PRBs), for example, 10, 12, 15, 20 or 25 PRBs. 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 4Diagram 410 in illustrates an example in which the PSCCH occupies approximately 50% of a subchannel as an example to illustrate the concept of the PSCCH occupying a portion of a subchannel. The physical sidelink shared channel (PSCCH) occupies at least one subchannel. In some examples, the PSCCH may include a first portion of sidelink control information (SCI), and the PSCCH may include a second portion of the SCI.

[0075] 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 4 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 4 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 be different from Figure 4 Examples illustrated in . In some aspects, multiple time slots may be aggregated together.

[0076] Some examples of sidelink communications may include communications that may be from vehicle to vehicle (V2V), vehicle to infrastructure (V2I) (e.g., from a vehicle-based communication device to a road infrastructure node such as a roadside unit (RSU)), vehicle to network (V2N) (e.g., from a vehicle-based communication device to one or more network nodes such as a base station), vehicle to pedestrian (V2P), cellular vehicle-to-everything (C-V2X), and / or combinations thereof, and / or vehicle-based communication devices communicating with other devices, which may be collectively referred to as vehicle-to-everything (V2X) communications. Sidelink communications may be based on V2X or other D2D communications, such as proximity services (ProSe), etc. In addition to the UE, sidelink communications may also be sent and received by other transmitting devices and receiving devices, such as a roadside unit (RSU) 107, etc. The PC5 interface may be used to exchange sidelink communications, such as in conjunction with Figure 4 Although the examples in Figure 4The following description of an example time slot structure may provide an example for sidelink communications in conjunction with 5G NR, but the concepts described herein may be applicable to other similar areas such as LTE, LTE-A, CDMA, GSM, and other wireless technologies.

[0077] Figure 5 An example 500 of sidelink communication between devices is illustrated. The communication may be based on a combination of Figure 4 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 that can be occupied by the data transmission. The SCI can be used by the receiving device to avoid interference by suppressing 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 / alternatively, RSU 507 may receive communications from UE 502, 504, 506, 508 and / or transmit communications 518 to these UEs. One or more of UE 502, 504, 506, 508 or RSU 507 may include, for example, a combination of Figure 1 Relay communication component 198 is described.

[0078] Sidelink communications may be based on resource allocation mechanisms of different types or modes. In another resource allocation mode (which may be referred to herein as "mode 1"), centralized resource allocation may be provided by a network entity. For example, a network entity may determine resources for sidelink communications and may allocate resources to different wireless devices for sidelink transmission. In this first mode, a wireless device may receive an allocation of sidelink resources from a base station. In a second resource allocation mode (which may be referred to herein as "mode 2"), distributed resource allocation may be provided. In mode 2, each wireless device may autonomously determine resources for sidelink transmission. In order to coordinate the selection of sidelink resources by each wireless device, each wireless device may use sensing technology to monitor resource reservations made by other sidelink wireless devices, and may select resources for sidelink transmission from unreserved resources. A device communicating based on a sidelink may determine one or more radio resources used by other devices in the time domain and the frequency domain in order to select transmission resources that avoid conflicts with other devices.

[0079] The sidelink transmissions and / or resource reservations may be periodic or aperiodic, where the wireless device may reserve resources for transmission in the current time slot and up to two future time slots (as discussed below).

[0080] Thus, in a second mode (e.g., Mode 2), individual wireless devices may autonomously select resources for sidelink transmissions, e.g., without a central entity (such as a base station) indicating resources for devices. A first wireless device may reserve the selected resources in order to inform other wireless devices about the resources that the first wireless device intends to use for sidelink transmissions.

[0081] In some examples, resource selection for sidelink communication can be based on a sensing-based mechanism. For example, before selecting resources for data transmission, the wireless device can first determine whether the resources have been reserved by other wireless devices.

[0082] For example, as part of a sensing mechanism for resource allocation mode 2, the wireless device may determine (e.g., sense) whether the selected side link resource has been reserved by other wireless devices before selecting the side link resource for data transmission. If the wireless device determines that the side link resource has not been reserved by other wireless devices, the wireless device may use the selected side link resource to send data, for example, in a PSSCH transmission. The wireless device may estimate or determine which radio resources (e.g., side link resources) may be in use and / or reserved by other wireless devices by detecting and decoding side link control information (SCI) sent by other wireless devices. The wireless device may estimate or determine which radio resources are in use and / or reserved by other wireless devices using a sensing-based resource selection algorithm. The wireless device may receive an SCI from another wireless device, which may include reservation information based on a resource reservation field in the SCI. The wireless device may continuously monitor (e.g., sense) and decode the SCI from a peer wireless device. The SCI may include, for example, reservation information indicating that a particular wireless device has selected a time slot and RB for future transmission. The wireless device may exclude resources used and / or reserved by other wireless devices from a set of candidate resources for sidelink transmission by the wireless device, and the wireless device may select / reserve resources for sidelink transmission from resources that are not used and thus form the set of candidate resources. The wireless device may continuously perform sensing on the SCI with resource reservations in order to maintain a set of candidate resources from which the wireless device may select one or more resources for sidelink transmission. Once the wireless device selects a candidate resource, the wireless device may send an SCI indicating its own reservation of resources for sidelink transmission. The number of resources (e.g., subchannels per subframe) reserved by the wireless device may depend on the size of data to be transmitted by the wireless device. Although this example is described for a wireless device receiving a reservation from another wireless device, a reservation may be received from an RSU or other device communicating based on a sidelink.

[0083] Figure 6 600 is a diagram illustrating an example of UE positioning based on reference signal measurement. UE 604 may be at time T SRS_TX UL-SRS 612 is sent and at time T PRS_RX Receive a DL positioning reference signal (PRS) (DL-PRS) 610. TRP 606 may be at time T SRS_RX Receive UL-SRS 612 and at time T PRS_TXDL-PRS 610 is sent. UE 604 may receive DL-PRS 610 before sending UL-SRS 612, or may send UL-SRS 612 before receiving DL-PRS 610. In both cases, a positioning server (e.g., location server 168) or UE 604 may determine the UL-SRS 612 based on ||T SRS_RX –T PRS_TX |–|T SRS_TX –T PRS_RX || determines RTT 614. Thus, multi-RTT positioning can utilize UE Rx-Tx time difference measurements (i.e., |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 604 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 602, 606 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 604 to determine the RTT, which is used to estimate the position of the UE 604. Other methods for determining the RTT are possible, such as using DL-TDOA and / or UL-TDOA measurements.

[0084] DL-AoD positioning may utilize the measured DL-PRS-RSRP of downlink signals received from multiple TRPs 602, 606 at the UE 604. The UE 604 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 604 relative to neighboring TRPs 602, 606.

[0085] DL-TDOA positioning can utilize the DL Reference Signal Time Difference (RSTD) (and optionally DL-PRS-RSRP) of downlink signals received from multiple TRPs 602, 606 at the UE 604. The UE 604 uses the assistance data received from the positioning server to measure the DL RSTD (and optionally DL-PRS-RSRP) of the received signals, and the resulting measurements are used together with other configuration information to position the UE 604 relative to neighboring TRPs 602, 606.

[0086] UL-TDOA positioning can utilize the UL relative time of arrival (RTOA) (and optionally UL-SRS-RSRP) of uplink signals sent from UE 604 at multiple TRPs 602, 606. TRPs 602, 606 use assistance data received from a positioning server to measure the UL-RTOA (and optionally UL-SRS-RSRP) of the received signal, and the resulting measurements are used together with other configuration information to estimate the position of UE 604.

[0087] UL-AoA positioning can utilize the measured azimuth angle of arrival (A-AoA) and zenith angle of arrival (Z-AoA) of uplink signals sent from the UE 604 at multiple TRPs 602, 606. The TRPs 602, 606 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 604.

[0088] Additional positioning methods may be used to estimate the position of the UE 604, such as 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.

[0089] Figure 7 7 is a diagram illustrating an example of a remote UE 710 configured to perform a positioning session through a relay UE 702. Each of the relay UE 702 and the remote UE 710 may be a Figure 1 Each of network entity 704, network entity 706, and network entity 708 may be a UE similar to UE 104 in FIG. Figure 1 A base station similar to base station 102 in.

[0090] Each of the relay UE 702, the network entity 704, the network entity 706, the network entity 708, and the remote UE 710 may be located within a common area or range 701 that allows wireless devices to communicate with each other via wireless links. In one aspect, the relay UE 702 may communicate with the network entities 704, 706, and 708 within the area or range 501. The relay UE 702 may communicate with the network entities 704, 706, and 708 using any suitable RF access link, such as a UE to Universal Mobile Telecommunications System (UMTS) Terrestrial Radio Access Network (UE-UTRAN or Uu) link. The relay UE 702 may communicate with the network entity 704 using a Uu link 705, may communicate with the network entity 706 using a Uu link 707, and may communicate with the network entity 708 using a Uu link 709. The relay UE 702 may use the Uu links 705, 707, and 709 to perform positioning by calculating round trip time (RTT) and / or time difference of arrival (TDOA) measurements. In one aspect, the LMF may use the Uu link 705 to send PRS from the network entity 704 to the relay UE 702 to perform positioning measurements over a period of time (such as RTT or TDOA). In one aspect, the LMF may use the Uu link 707 to send PRS from the network entity 706 to the relay UE 702 to perform positioning measurements over a period of time (such as RTT or TDOA). In one aspect, the LMF may use the Uu link 709 to send PRS from the network entity 708 to the relay UE 702 to perform positioning measurements over a period of time (such as RTT or TDOA). Each of the network entities 704, 706, and 708 may act as a location anchor point for the relay UE 702 to determine its position using one or more positioning measurements. The LMF or relay UE 702 may use positioning measurements to determine the position of the relay UE 702, which may then be used to perform positioning for a remote UE, such as remote UE 710, that may be configured to communicate with the relay UE 702 via a sidelink.

[0091] The relay UE 702 may communicate with the remote UE 710 using any suitable RF access link, such as a PC5 link 711, also referred to as a side link. The relay UE 702 may have a known location, such as a location known to the relay UE 702 or known to a network entity, such as a location management function (LMF). The known location of the relay UE 702 may provide an anchor point to the remote UE 710 to provide side link positioning assistance to the remote UE 710. The relay UE 702 or the remote UE 710 may use the PC5 link 711 to calculate positioning measurements, such as the side link RTT. For example, the relay UE 702 may use the PC5 link 711 to send a PRS to the remote UE 710, the remote UE 710 may perform positioning measurements on the PRS (such as RTT), and the results of the measurement report may be returned to the relay UE 702.

[0092] In one aspect, the remote UE 710 may communicate with one or more of the network entities 704, 706, and 708 within the area or range 501. The remote UE 710 may communicate with the network entities 704, 706, and 708 using any suitable RF access link, such as a Uu link similar to the Uu links 705, 707, and 709. The remote UE 710 may perform positioning by calculating RTT and / or TDOA measurements using such Uu links. In one aspect, the LMF may send PRS from the network entity 704 to the remote UE 710 to perform positioning measurements within a period of time, such as RTT or TDOA. In one aspect, the LMF may send PRS from the network entity 706 to the remote UE 710 to perform positioning measurements within a period of time, such as RTT or TDOA. In one aspect, the LMF may send PRS from the network entity 708 to the remote UE 710 to perform positioning measurements within a period of time, such as RTT or TDOA. Each of the network entities 704, 706, and 708 may act as a location anchor point for the remote UE 710 to determine its location using one or more positioning measurements. The LMF or the remote UE 710 may determine the location of the remote UE 710 using the positioning measurements.

[0093] The remote UE 710 may use the relay UE 702 as an additional anchor point to improve its positioning. For example, the remote UE 710 and / or the relay UE 702 may use the PC5 link 711 to perform positioning measurements on the PRS (such as RTT) sent by the relay UE 702 to the remote UE 710 to improve the positioning calculation of the remote UE 710. In some aspects, for example, due to obstruction or other adverse network conditions, the remote UE 710 may not be able to communicate with some of the network entities 704, 706, or 708, thereby improving the usefulness of using the relay UE 702 to perform positioning measurements using the PC5 link 711. In other words, the relay UE 702 may provide additional positioning measurements (such as RTT measurements) to assist the positioning of the remote UE 710. The LMF communicating with the remote UE 710 via the relay UE 702 may be configured to use the relay UE 702 as an anchor UE that transmits a sidelink PRS (SL-PRS) that may be transmitted by the relay UE 702 to the remote UE 710. The remote UE 710 may be configured to perform measurement reporting on the SL-PRS from the relay UE 702.

[0094] UE (such as relay UE 702 and / or remote UE 710) may be configured to use any suitable means to discover which positioning peer (Pos-Peer) UEs may be near the target UE. In the first discovery mode (which may be referred to as "mode A" in this article), the Pos-Peer UE may announce its existence to one or more target UEs by sending (e.g., via side link broadcast, unicast or multicast) a side link positioning (SL-Pos) discovery message with a positioning flag. The UE receiving the SL-Pos discovery message may send a discovery response back to the Pos-Peer UE to establish a side link positioning setting. In the second discovery mode (which may be referred to as "mode B" in this article), the target UE is configured to discover the Pos-Peer UE by initiating (e.g., via side link broadcast, unicast or multicast) a SL-POS solicitation message with one or more fields related to positioning. The Pos-Peer UE receiving this solicitation may provide a solicitation response to the target UE to establish a side link positioning setting. Both the SL-Pos discovery message and / or the SL-Pos solicitation message may be split into two or more parts to provide a more power efficient aspect. In response to the Pos-Peer discovery message, the Pos-Peer discovery response, the Pos-Peer solicitation message, or the Pos-Peer solicitation response, a handshake may be performed between the target UE and the Pos-Peer UE. The target UE may be configured to rank one or more potential Pos-Peer UEs based on at least one of a quality criterion of the anchor location, a channel quality criterion, a response time criterion, or a mobility state criterion.

[0095] The relay UE 702 may be configured to handle an end-to-end (E2E) QoS configuration for the remote UE 710. In one aspect, the relay UE 702 may be configured with a Uu to PC5 QoS mapping. For example, a network entity (such as the network entity 704) may provide at least one of a 5G QoS indicator (5QI) mapping table, a PC5 5QI (PQI) mapping table, or a PQI packet data budget (PDB) adjustment factor to the relay UE 702. Such configuration may be provided by the network entity via an RRC configuration. The relay UE 702 may be configured to map the Uu QoS configured by the network entity (such as the network entity 704) to the PC5 QoS using such a mapping table. The remote UE 710 may be configured to send a PC5 QoS context to the relay UE 702. Such a PC5 QoS context may indicate an E2E QoS condition to the relay UE 702. In response to receiving the PC5 QoS context from the remote UE 710, the relay UE 702 may send one or more of the QoS conditions to the network entity using a UE-initiated protocol data unit (PDU) session modification. In one aspect, the relay UE 702 may be configured to support reflective QoS on a Uu link, such as the Uu link 705.

[0096] For example, the network entity 704 may configure the QoS of the Uu PDB to 75ms. The relay UE 702 may map the QoS of the Uu PDB 75ms to the QoS of the PC5 PDB 25ms. The relay UE 702 may then add the two results to configure the QoS of the E2E PDB 100ms. In other words, the relay UE 702 may be configured to process the E2E QoS configuration for the remote UE 710 by increasing the QoS latency of the configured PDB using one or more mapping tables that map the QoS of the Uu PDB to the QoS of the PC5 PDB.

[0097] Although relay UE 702 may be able to use a mapping table to increase QoS latency, such a mapping table may not be used for positioning of remote UE 710 relative to relay UE 702 because the RTT value changes as relay UE 702 changes its location and / or as remote UE 710 changes its location. A network entity, such as network entity 704, may be configured to provide response time QoS parameters for a Uu link, such as Uu link 705, and for a side link, such as PC5 link 711.

[0098] In one aspect, a relay UE may be configured to receive an indication of one or more of at least one first QoS parameter of a first radio link or at least one second QoS parameter of a second radio link. The relay UE may receive the indication from a network entity. The first radio link may be associated with the relay UE and the network entity. The second radio link may be associated with the relay UE and at least one remote UE. The at least one first QoS parameter and the at least one second QoS parameter may be associated with a time period. The relay UE may be configured to send a report of at least one positioning measurement within the time period based on one or more of the at least one first QoS parameter or the at least one second QoS parameter. The report may be sent to the network entity.

[0099] In one aspect, a network entity may be configured to send an indication of one or more of at least one first QoS parameter of a first radio link or at least one second QoS parameter of a second radio link. The indication may be output to a relay UE. The first radio link may be associated with the relay UE and the network entity. The second radio link may be associated with the relay UE and at least one remote UE. The at least one first QoS parameter and the at least one second QoS parameter may be associated with a time period. The network entity may be configured to obtain a report of at least one positioning measurement within the time period based on one or more of the at least one first QoS parameter or the at least one second QoS parameter. The report may be obtained from the relay UE.

[0100] Figure 8 800 is a diagram illustrating an example of a remote UE 806 configured to perform a positioning session with a network entity 802 via a relay UE 804. One or more of the remote UEs 808, 810, and 812 may serve as additional anchor points for the remote UE 806. Each of the relay UE 804, the remote UE 806, the remote UE 808, the remote UE 810, and the remote UE 812 may be an additional anchor point associated with the remote UE 806. Figure 1 The network entity 802 may be a UE similar to the UE 104 in FIG. Figure 1 The network entity 802 may include a LMF.

[0101] Each of the network entity 802 and the relay UE 804 may be located in a common area or range 801 that allows wireless devices to communicate with each other via wireless links. The relay UE 804 may communicate with the network entity 802 via a Uu link 803. The relay UE 804 may perform positioning by calculating RTT and / or TDOA measurements using the Uu link 803. Remote UEs 806, 808, 810, and 812 may be outside the area or range 801, thereby preventing the network entity 802 from communicating with any of the remote UEs 806, 808, 810, and 812 via the Uu link.

[0102] Relay UE 804 may communicate with remote UE 806 via PC5 link 805. Remote UE 806 may communicate with remote UE 808 via PC5 link 807. Remote UE 806 may communicate with remote UE 810 via PC5 link 809. Remote UE 806 may communicate with remote UE 812 via PC5 link 811. The response time conditions for remote UE 806 may vary depending on: (1) Uu link 803 between UE 804 and network entity 802, which may include a backhaul network to the LMF; (2) PC5 link 805 between relay UE 804 and remote UE 806; and (3) PC5 links 807, 809, and 811 between remote UE 806 and remote UEs 808, 810, and 812, respectively.

[0103] In one aspect, the network entity 802 may be configured to provide a QoS response time for the Uu link 803 and / or the PC5 link 805. The response time for the Uu link 803 may be calculated as the response time between the relay UE 804 and the TRP of the network entity 802. The response time for the Uu link 803 may be calculated as the response time between the relay UE 804 and the LMF of the network entity 802. The network entity 802 may provide one or more QoS parameters for the Uu link 803 and / or the PC5 link 805. In one aspect, the one or more QoS parameters may be provided by the LMF of the network entity 802. The LMF of the network entity 802 may provide the one or more QoS parameters to the relay UE 804 in the assistance data (AD). In one aspect, the QoS parameters may be provided in the RRC configuration or as part of the PRS.

[0104] In one aspect, the network entity 802 may provide the E2E response time (e.g., the sum of the response time for the Uu link 803 and the response time for the PC5 link 805) to the relay UE 804. The network entity 802 may provide the response time for the PC5 link 805 to the relay UE 804. The relay UE 804 may calculate the response time for the Uu link 803 by subtracting the response time for the PC5 link 805 from the E2E response time.

[0105] In one aspect, the network entity 802 may provide the E2E response time (e.g., the sum of the response time for the Uu link 803 and the response time for the PC5 link 805) to the relay UE 804. The network entity 802 may provide the response time for the Uu link 803 to the relay UE 804. The relay UE 804 may calculate the response time for the PC5 link 805 by subtracting the response time for the Uu link 803 from the E2E response time.

[0106] In one aspect, the network entity 802 may provide the response time for the Uu link 803 to the relay UE 804. The network entity 802 may provide the response time for the PC5 link 805 to the relay UE 804. The relay UE 804 may calculate the E2E response time by summing the response time for the Uu link 803 and the response time for the PC5 link 805.

[0107] In one aspect, the network entity 802 may provide the relay UE 804 with an aggregate response time. The aggregate response time may be the sum of the side link measurement period, the response time for the PC5 link 805, and the response time for the Uu link 803. The network entity 802 may assume an upper limit for the response time for the PC5 link 805 and the response time for the Uu link 803. Such an upper limit may be predetermined by a configuration (such as an RRC configuration) or as auxiliary data (AD). The response time may be selected by an index to a table provided by the RRC or AD. The relay UE 804 may be configured to calculate the response time for the PC5 link 805 and the response time for the Uu link 803 based on the aggregate response time. In one aspect, the relay UE 804 may subtract the upper limit for the response time for the PC5 link 805 from the aggregate response time to determine the response time for the Uu link 803. In one aspect, the relay UE 804 may subtract the upper limit for the response time for the Uu link 803 from the aggregate response time to determine the response time for the PC5 link 805. In one aspect, the relay UE 804 may subtract an upper limit on the response time for the Uu link 803 and an upper limit on the response time for the PC5 link 805 from the aggregate response time to determine a side link (SL) response time.

[0108] The relay UE 804 may use at least one of the individual QoS response time for the Uu link 803, the response time for the PC5 link 805, the E2E response time, or the SL response time to perform positioning measurements within the time period. In one aspect, the relay UE 804 may perform positioning measurements on the RTT of the Uu link 803 based on the response time for the Uu link 803. In one aspect, the relay UE 804 may perform positioning measurements on the RTT of the PC5 link 805 based on the response time for the PC5 link 805. In one aspect, the relay UE 804 may provide the response time for the PC5 link 805 to the remote UE 806. The remote UE 806 may perform positioning measurements on the RTT of the PC5 link 805 based on the response time for the PC5 link 805, and may send a corresponding measurement report to the relay UE 804. The relay UE 804 may forward the report from the remote UE 806 to the network entity 802. In one aspect, the relay UE 804 may provide the SL response time to the remote UE 806, which may perform positioning measurements on the RTT of at least one of the PC5 link 807, the PC5 link 809, or the PC5 link 811 based on the SL response time, and may send a corresponding measurement report to the relay UE 804. The relay UE 804 may forward the report from the remote UE 806 to the network entity 802. In one aspect, the relay UE 804 may provide the SL response time to the remote UE 806, which may provide the SL response time to at least one of the remote UE 808, the remote UE 810, or the remote UE 812. At least one of the remote UE 808, the remote UE 810, or the remote UE 812 may perform positioning measurements on the RTT of at least one of the PC5 link 807, the PC5 link 809, or the PC5 link 811, respectively, based on the SL response time, and may send a corresponding measurement report to the remote UE 806. The remote UE 806 may forward the measurement report to the relay UE 804, which may forward the report to the network entity 802. The UE that did not independently meet the response time may indicate in the report that the QoS response time was not met. In some aspects, an error code or error cause may be sent from the relay UE 904 or the remote UE 906 to the network entity 902 to indicate that a QoS parameter (e.g., PC5 response time, Uu response time, E2E response time, or SL response time) was successfully met or that a QoS parameter was not met. In one embodiment, the error code or error cause may be a message to the relay UE or the remote UE that "no measurements could be made." In response, the network entity 902 may change PRS configuration parameters such as periodicity, repetition factor, bandwidth (BW), or combined symbol options based on the indication.

[0109] The relay UE 804 may aggregate the measurement reports to determine whether the E2E response time has been met. In one aspect, the E2E response time between the network entity 802 and the remote UE 806 may be determined based on the sum of the RTT of the Uu link 803 and the RTT of the PC5 link 805. In one aspect, the E2E response time between the network entity 802 and the remote UE 808 may be determined based on the sum of the RTT of the Uu link 803, the RTT of the PC5 link 805, and the RTT of the PC5 link 807.

[0110] Fig. 9 900 is a diagram illustrating an example of a remote UE 906 configured to perform a positioning session with a network entity 902 via one of relay UEs 904, 922, and 924. One or more of the remote UEs 908, 910, and 912 may serve as additional anchor points for the remote UE 906. Each of the relay UE 904, the relay UE 922, the relay UE 924, the remote UE 906, the remote UE 908, the remote UE 910, and the remote UE 912 may be an additional anchor point associated with the remote UE 906. Figure 1 The network entity 902 may be a UE similar to the UE 104 in FIG. Figure 1 The network entity 902 may include a LMF.

[0111] Each of the network entity 902, the relay UE 904, the relay UE 922, and the relay UE 924 may be located in a common area or range 901 that allows wireless devices to communicate with each other via wireless links. The relay UE 904 may communicate with the network entity 902 via a Uu link 903. The relay UE 904 may perform positioning by calculating RTT and / or TDOA measurements using the Uu link 903. The relay UE 922 may communicate with the network entity 902 via a Uu link 923. The relay UE 922 may perform positioning by calculating RTT and / or TDOA measurements using the Uu link 923. The relay UE 924 may communicate with the network entity 902 via a Uu link 925. The relay UE 924 may perform positioning by calculating RTT and / or TDOA measurements using the Uu link 925. The remote UEs 906, 908, 910, and 912 may be outside of the area or range 901, thereby preventing the network entity 902 from communicating with any of the remote UEs 906, 908, 910, and 912 via the Uu link.

[0112] Relay UE 904 may communicate with remote UE 906 via PC5 link 905. Remote UE 906 may communicate with remote UE 908 via PC5 link 907. Remote UE 906 may communicate with remote UE 910 via PC5 link 909. Remote UE 906 may communicate with remote UE 912 via PC5 link 911. The response time conditions for remote UE 906 may vary depending on: (1) Uu link 903 between relay UE 904 and network entity 902, which may include a backhaul network to the LMF; (2) PC5 link 905 between relay UE 904 and remote UE 906; and (3) PC5 links 907, 909, and 911 between remote UE 906 and remote UEs 908, 910, and 912, respectively.

[0113] The network entity 902 may select a relay UE from relay UEs 904, 922, and 924 based on the QoS of the Uu link and the PC5 link. Each of the relay UEs 904, 922, and 924 may have different capabilities and channel conditions relative to each other. The QoS responses (e.g., RTT or TDOA measurements) for the Uu link 903 with the relay UE 904, for the Uu link 923 with the relay UE 922, or for the Uu link 925 with the relay UE 924 may be different from each other. For example, the RTT of the Uu link 903 may be better than the RTT of the Uu link 923. Similarly, the PC5 links between the relay UE and the remote UE may also be different from each other. One or more of the relay UEs 904, 922, and 924 may maintain a copy of the QoS parameters in a memory, and this information may be provided to the remote UE or the network entity 902 for selecting a relay UE for the remote UE. A remote UE, such as remote UE 906, may select a relay UE from relay UEs 904, 922, and 924 to determine which one has the best response time. For example, the lowest E2E response time between network entity 902 and remote UE 906. In some aspects, network entity 902 may perform an analysis of the E2E response time and may provide an indication to remote UE 906 to select a relay with a response time suggested by network entity 902. In response to receiving the indication to select a relay with a better response time, remote UE 906 may reselect a relay UE (e.g., may switch from relay UE 904 to relay UE 922) before performing positioning measurements.

[0114] In one aspect, the remote UE may query the response time for the Uu link from the relay UE. Such a query may be used to perform the above calculations. In one aspect, the remote UE 906 may send a query to the relay UE 904 via the PC5 link 905 to retrieve the response time of the Uu link 903. In one aspect, the remote UE 906 may send a query to the relay UE 922 to retrieve the response time of the Uu link 923. In one aspect, the remote UE 906 may send a query to the relay UE 924 to retrieve the response time of the Uu link 925. In some aspects, the relay UE 904 may provide response times for multiple Uu links, such as the response time (e.g., RTT) of the Uu link 903, the response time of the Uu link 923, and the response time of the Uu link 925. In some aspects, the relay UE 904 may provide the E2E response time and the response time for the Uu link 903, thereby allowing the remote UE 906 to calculate the response time for the PC5 link 905 by subtracting the response time for the Uu link 903 from the E2E response time.

[0115] In one aspect, the remote UE may provide the Uu QoS response time to the network entity. For example, the remote UE 906 may provide the Uu QoS response time to the LMF of the network entity 902 as part of the location start request. The remote UE 906 may send a long term evolution (LTE) positioning protocol (LPP) transmission with a response time for the Uu link 903 to the network entity 902 via the relay UE 904. The response time for the Uu link 903 may be queried from the relay UE 904. The basic response time for the Uu link 903 may be provided to the LMF of the network entity 902 as part of the LPP signaling. In one aspect, the response time for the Uu link may be part of a request AD message or a capability exchange procedure. In response to receiving the response time for the Uu link, the network entity 902 may add the response time for the Uu link to the response time for the PC5 link to determine the E2E response time. In one aspect, the network entity 902 may determine the PRS configuration based on the response time for the Uu link received from the remote UE 906. In one aspect, the network entity 902 may output a PRS configuration having a lower periodicity PRS configuration in response to the Uu link response time being equal to or greater than a threshold response time (e.g., 160 ms), or may output a PRS configuration having a higher periodicity PRS configuration in response to the Uu link response time being equal to or less than a threshold response time (e.g., 160 ms). The lower periodicity PRS configuration may have a lower periodicity than the higher periodicity PRS configuration. The PRS configuration may be output to the remote UE 906.

[0116] Fig.101000 is a diagram illustrating an example of a remote UE 1006 configured to perform a positioning session with a network entity 1002 via a relay UE 1032 and a relay UE 1004. One or more of the remote UEs 1008, 1010, and 1012 may serve as additional anchor points for the remote UE 1006. Each of the relay UE 1004, the remote UE 1006, the relay UE 1032, the remote UE 1008, the remote UE 1010, and the remote UE 1012 may be an additional anchor point associated with the remote UE 1006. Figure 1 The network entity 1002 may be a UE similar to the UE 104 in FIG. Figure 1 The network entity 1002 may include a LMF.

[0117] Each of the network entity 1002 and the relay UE 1004 may be located in a common area or range 1001 that allows wireless devices to communicate with each other via wireless links. The relay UE 1004 may communicate with the network entity 1002 via a Uu link 1003. The relay UE 1004 may perform positioning by calculating RTT and / or TDOA measurements using the Uu link 1003. Remote UEs 1006, 1008, 1010, and 1012 and the relay UE 1032 may be outside the area or range 1001, thereby preventing the network entity 1002 from communicating with any of the remote UEs 1006, 1008, 1010, and 1012 via a Uu link.

[0118] Relay UE 1004 may communicate with relay UE 1032 via PC5 link 1005. Relay UE 1032 may communicate with remote UE 1006 via PC5 link 1033. Remote UE 1006 may communicate with remote UE 1008 via PC5 link 1007. Remote UE 1006 may communicate with remote UE 1010 via PC5 link 1009. Remote UE 1006 may communicate with remote UE 1012 via PC5 link 1011. The response time conditions for the remote UE 1006 may vary depending on: (1) the Uu link 1003 between the UE 1004 and the network entity 1002, which Uu link may include a backhaul network to the LMF; (2) the PC5 link 1005 between the relay UE 1004 and the remote UE 1006; and (3) the PC5 links 1007, 1009 and 1011 between the remote UE 1006 and the remote UEs 1008, 1010 and 1012, respectively.

[0119] The target positioning UE may provide UE rank information to the network entity 1002. The UE rank may include the rank of how many relays are involved in the positioning session. Fig.10In the example, two relay UEs (relay UE 1004 and relay UE 1032) are used, thereby providing a UE order of two, and in Fig. 9 In the embodiment of the present invention, one relay UE (relay UE 904) is used, thereby providing a UE order of one. In other aspects, three, four or more orders may be used. The network entity 902 may provide a limit on the maximum order that can be used for the positioning system, such as positioning measurements. A remote UE (such as remote UE 1006) may be configured to select the minimum UE order for the remote UE. For example, in the case where the remote UE 1006 has a path with a UE order of three and a path with a UE order of two, the remote UE 1006 will select the path with a UE order of two because two is less than three.

[0120] Fig.11 1100 is a flow chart of a method of wireless communication. The method may be performed by a relay UE (e.g., UE 104, UE 350, UE 506, UE 502, UE 508, UE 604; relay UE 702, relay UE 804, relay UE 904, relay UE 922, relay UE 924, relay UE 100, relay UE 10324; remote UE 710, remote UE 806, remote UE 808, remote UE 810, remote UE 812, remote UE 906, remote UE 908, remote UE 910, remote UE 912, remote UE 1006, remote UE 1008, remote UE 1010, remote UE 1012; device 1304). At 1102, the relay UE may receive an indication of one or more of at least one first QoS parameter of a first radio link or at least one second QoS parameter of a second radio link. The first radio link may be associated with the relay UE and a network entity. The second radio link may be associated with the relay UE and at least one remote UE. The at least one first QoS parameter and the at least one second QoS parameter may be associated with a time period. For example, 1102 may be performed by Fig.13 Component 198 in is used for execution.

[0121] At 1104, the relay UE may send a report of at least one positioning measurement within the time period based on one or more of the at least one first QoS parameter or the at least one second QoS parameter. Fig.13 Component 198 in is used for execution.

[0122] At 1106, the relay UE may select the at least one remote UE based on one or more of the first wireless link, the second wireless link, or at least one measured real-time response time between the relay UE and the at least one remote UE. For example, 1106 may be performed by Fig.13Component 198 in is used to execute.

[0123] At 1108, the relay UE may receive a query for a first QoS response time associated with the at least one first QoS parameter from the at least one remote UE. Fig.13 Component 198 in is used to execute.

[0124] At 1110, the relay UE may send the first QoS response time associated with the at least one first QoS parameter to the at least one remote UE. For example, 1110 may be performed by Fig.13 Component 198 in is used to execute.

[0125] At 1112, the relay UE may receive a second indication of a first update to one or more of the at least one first QoS parameters of the first radio link or a second update to one or more of the at least one second QoS parameters of the second radio link based on the report. The time period may include at least one of the following: a first response time between the relay UE and the network entity, a second response time between the relay UE and the at least one remote UE, or an E2E response time between the network entity and the at least one remote UE. For example, 1112 may be Fig.13 Component 198 in is used to execute.

[0126] Fig.12 1200 is a flowchart of a method of wireless communication. The method may be performed by a network entity (e.g., base station 102, base station 310; TRP 602, TRP 606; network entity 704, network entity 706, network entity 708, network entity 802, network entity 902, network entity 1002, network entity 1302, network entity 1402, network entity 1560). At 1202, the network entity may send an indication of one or more of at least one first QoS parameter of a first radio link or at least one second QoS parameter of a second radio link. The first radio link may be associated with a relay UE and the network entity. The second radio link may be associated with the relay UE and at least one remote UE. The at least one first QoS parameter and the at least one second QoS parameter may be associated with a time period. For example, 1202 may be performed by Fig.14 Component 199 in is used for execution.

[0127] At 1204, the network entity may obtain a report of at least one positioning measurement within the time period based on one or more of the at least one first QoS parameter or the at least one second QoS parameter. Fig.14 Component 199 in is used for execution.

[0128] At 1206, the network entity may obtain, from the at least one remote UE, a configuration for transmitting data packets associated with the at least one positioning measurement. Fig.14 Component 199 in is used for execution.

[0129] At 1208, the network entity may obtain an LPP transmission including a Uu link response time to the network entity from the at least one remote UE. Based on the Uu link response time to the network entity, the at least one second QoS parameter of the second radio link may include a second response time between the relay UE and the at least one remote UE. For example, 1202 may be performed by Fig.14 Component 199 in is used for execution.

[0130] At 1210, the network entity may send a first PRS configuration including a lower periodicity PRS configuration in response to the Uu link response time being equal to or greater than a threshold response time, or send a second PRS configuration including a higher periodicity PRS configuration in response to the Uu link response time being equal to or less than the threshold response time. The lower periodicity PRS configuration may have a lower periodicity than the higher periodicity PRS configuration. For example, 1202 may be performed by Fig.14 Component 199 in is used for execution.

[0131] Fig.131300 is a diagram illustrating an example of a hardware implementation for an apparatus 1304. The apparatus 1304 may be a UE, may be a component of a UE, or may implement UE functionality. In some aspects, the apparatus 1304 may include a cellular baseband processor 1324 (also referred to as a modem) coupled to one or more transceivers 1322 (e.g., a cellular RF transceiver). The cellular baseband processor 1324 may include on-chip memory 1324'. In some aspects, the apparatus 1304 may also include one or more subscriber identity module (SIM) cards 1320 and an application processor 1306 coupled to a secure digital (SD) card 1308 and a screen 1310. The application processor 1306 may include on-chip memory 1306'. In some aspects, the device 1304 may also include a Bluetooth module 1312, a WLAN module 1314, an SPS module 1316 (e.g., a GNSS module), one or more sensor modules 1318 (e.g., an atmospheric pressure sensor / altimeter; a motion sensor (such as an inertial management unit (IMU), a gyroscope and / or an accelerometer, a magnetometer, audio, and / or other technologies for positioning), an additional memory module 1326, a power source 1330, and / or a camera 1332. The Bluetooth module 1312, the WLAN module 1314, and the SPS module 1316 may include an on-chip transceiver (TRX) (or in some cases, only a receiver (Rx)). The Bluetooth module 1312, the WLAN module 1314, and the SPS module 1316 may include their own dedicated antennas and / or communicate using an antenna 1380. The cellular baseband processor 1324 communicates with the UE through the transceiver 1322 via one or more antennas 1380. 104 and / or communicate with RUs associated with the network entity 1302. The cellular baseband processor 1324 and the application processor 1306 may each include a computer-readable medium / memory 1324', 1306', respectively. The additional memory module 1326 may also be considered a computer-readable medium / memory. Each computer-readable medium / memory 1324', 1306', 1326 may be non-transitory. The cellular baseband processor 1324 and the application processor 1306 are each responsible for general processing, including executing software stored on a computer-readable medium / memory. The software, when executed by the cellular baseband processor 1324 / application processor 1306, enables the cellular baseband processor 1324 / application processor 1306 to perform the various functions described above. The computer-readable medium / memory may also be used to store data manipulated by the cellular baseband processor 1324 / application processor 1306 when executing the software. The cellular baseband processor 1324 / application processor 1306 may be a UE 350 and may include a memory 360 and / or at least one of a Tx processor 368 , an Rx processor 356 , and a controller / processor 359 .In one configuration, the device 1304 may be a processor chip (modem and / or applications) and include only the cellular baseband processor 1324 and / or the application processor 1306, and in another configuration, the device 1304 may be an entire UE (eg, see. Figure 3 350) and includes additional modules of device 1304.

[0132] As discussed above, component 198 may be configured to receive an indication of one or more of at least one first QoS parameter of a first radio link or at least one second QoS parameter of a second radio link. The indication may be received from a network entity. The first radio link may be associated with the relay UE and the network entity. The second radio link may be associated with the relay UE and at least one remote UE. The at least one first QoS parameter and the at least one second QoS parameter may be associated with a time period. Component 198 may be configured to send a report of at least one positioning measurement within the time period based on one or more of the at least one first QoS parameter or the at least one second QoS parameter. The report may be sent to the network entity. Component 198 may be within the cellular baseband processor 1324, the application processor 1306, or within both the cellular baseband processor 1324 and the application processor 1306. 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 for implementation by one or more processors, or some combination thereof. As shown, the device 1304 may include a variety of components configured for various functions. In one configuration, the device 1304 (and in particular the cellular baseband processor 1324 and / or the application processor 1306) includes a component for receiving an indication of one or more of at least one first QoS parameter of the first radio link or at least one second QoS parameter of the second radio link. The device 1304 may include a component for sending a report of at least one positioning measurement within a time period based on the at least one first QoS parameter or the at least one second QoS parameter. The device 1304 may include a component for sending a request for one or more of the at least one first QoS parameter or the at least one second QoS parameter. The device 1304 may include a component for indicating at least one positioning measurement based on the measured RTT being less than or equal to the time period. The device 1304 may include a component for indicating at least one positioning measurement based on the measured RTT being less than or equal to the sum of the first response time between the relay UE and the network entity and the second measured response time between the relay UE and at least one remote UE. The apparatus 1304 may include means for performing at least one positioning measurement within a time period based on at least one of the at least one first QoS parameter or the at least one second QoS parameter. The apparatus 1304 may include means for sending a configuration of data packet transmission associated with the at least one positioning measurement to at least one remote UE. The apparatus 1304 may include means for selecting at least one remote UE based on one or more of the first wireless link or the second wireless link. The apparatus 1304 may include means for selecting at least one remote UE further based on at least one measured real-time response time between the relay UE and the at least one remote UE.The apparatus 1304 may include a component for receiving a query for a first QoS response time associated with at least one first QoS parameter from at least one remote UE. The apparatus 1304 may include a component for sending the first QoS response time associated with at least one first QoS parameter to at least one remote UE. The apparatus 1304 may include a component for receiving a report of at least one positioning measurement from at least one remote UE. The apparatus 1304 may include a component for sending the report by forwarding the report from the at least one remote UE to a network entity. The apparatus 1304 may include a component for receiving a second indication of a first update of one or more of at least one first QoS parameters of the first radio link or a second update of one or more of at least one second QoS parameters of the second radio link based on the report. The apparatus 1304 may include a component for receiving a maximum UE order for the report. The apparatus 1304 may include a component for selecting at least one remote UE based on the maximum UE order for the report. The component may be a component 198 of the apparatus 1304 configured to perform the functions recited by the component. As described above, the device 1304 may include a Tx processor 368, an Rx processor 356, and a controller / processor 359. Thus, in one configuration, these components may be the Tx processor 368, the Rx processor 356, and / or the controller / processor 359 configured to perform the functions recited by these components.

[0133] Fig.141400 is a diagram illustrating an example of a hardware implementation for a network entity 1402. The network entity 1402 may be a BS, may be a component of a BS, or may implement BS functionality. The network entity 1402 may include at least one of a CU 1410, a DU 1430, or a RU 1440. For example, depending on the layer functionality processed by the component 199, the network entity 1402 may include a CU 1410; both a CU 1410 and a DU 1430; each of the CU 1410, the DU 1430, and the RU 1440; the DU 1430; both a DU 1430 and a RU 1440; or the RU 1440. The CU 1410 may include a CU processor 1412. The CU processor 1412 may include an on-chip memory 1412'. In some aspects, the CU 1410 may also include an additional memory module 1414 and a communication interface 1418. CU1410 communicates with DU 1430 via a midhaul link (such as an F1 interface). DU 1430 may include a DU processor 1432. DU processor 1432 may include on-chip memory 1432'. In some aspects, DU 1430 may also include an additional memory module 1434 and a communication interface 1438. DU 1430 communicates with RU 1440 via a fronthaul link. RU 1440 may include a RU processor 1442. RU processor 1442 may include on-chip memory 1442'. In some aspects, RU 1440 may also include an additional memory module 1444, one or more transceivers 1446, an antenna 1480, and a communication interface 1448. RU 1440 communicates with UE 104. On-chip memory 1412', 1432', 1442' and additional memory modules 1414, 1434, 1444 may each be considered a computer-readable medium / memory. Each computer readable medium / memory may be non-transitory. Each of processors 1412, 1432, 1442 is responsible for general processing, including executing software stored on the computer readable medium / memory. The software, when executed by the corresponding processor, causes the processor to perform the various functions described above. The computer readable medium / memory may also be used to store data manipulated by the processor when executing the software.

[0134] As discussed above, component 199 may be configured to send an indication of one or more of at least one first QoS parameter of the first radio link or at least one second QoS parameter of the second radio link. The indication may be sent to a relay UE. The first radio link may be associated with the relay UE and the network entity. The second radio link may be associated with the relay UE and at least one remote UE. The at least one first QoS parameter and the at least one second QoS parameter may be associated with a time period. Component 199 may be configured to obtain a report of at least one positioning measurement within the time period based on one or more of the at least one first QoS parameter or the at least one second QoS parameter. The report may be obtained from the relay UE. Component 199 may be within one or more processors of one or more of CU 1410, DU 1430, and RU 1440. Component 199 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 for implementation by one or more processors, or some combination thereof. Network entity 1402 may include a variety of components configured for various functions. In one configuration, the network entity 1402 includes means for sending an indication of one or more of at least one first QoS parameter of the first radio link or at least one second QoS parameter of the second radio link. The network entity 1402 may include means for obtaining a report of at least one positioning measurement within a time period based on the at least one first QoS parameter or the at least one second QoS parameter. The network entity 1402 may include means for receiving a request for one or more of the at least one first QoS parameter or the at least one second QoS parameter. The network entity 1402 may include means for obtaining a configuration of a data packet transmission associated with at least one positioning measurement from at least one remote UE. The network entity 1402 may include means for obtaining an LPP transmission including a Uu link response time to the network entity from at least one remote UE. The network entity 1402 may include means for sending a first PRS configuration having a lower periodicity PRS configuration in response to the Uu link response time being equal to or greater than a threshold response time. The network entity 1402 may include means for sending a second PRS configuration including a higher periodicity PRS configuration in response to the Uu link response time being equal to or less than a threshold response time. The network entity 1402 may include means for sending a maximum UE rank for reporting to the relay UE based on the number of UE rank of the relay associated with each positioning measurement in at least one positioning measurement. The means may be a component 199 of the network entity 1402 configured to perform the functions recited by the means. As described above, the network entity 1402 may include a Tx processor 316, an Rx processor 370, and a controller / processor 375.Thus, in one configuration, these components may be the Tx processor 316, the Rx processor 370, and / or the controller / processor 375 configured to perform the functions recited by these components.

[0135] Fig.15 1500 is an example of a hardware implementation for a network entity 1560. In one example, the network entity 1560 may be within the core network 120. The network entity 1560 may include a network processor 1512. The network processor 1512 may include an on-chip memory 1512'. In some aspects, the network entity 1560 may also include an additional memory module 1514. The network entity 1560 communicates with the CU 1502 directly (e.g., backhaul link) or indirectly (e.g., through the RIC) via a network interface 1580. The on-chip memory 1512' and the additional memory module 1514 may each be considered as a computer-readable medium / memory. Each computer-readable medium / memory may be non-transitory. The processor 1512 is responsible for general processing, including executing software stored on a computer-readable medium / memory. The software, when executed by the corresponding processor, enables the processor to perform the various functions described above. The computer-readable medium / memory may also be used to store data manipulated by the processor when executing the software.

[0136] As discussed above, component 199 may be configured to send an indication of one or more of at least one first QoS parameter of the first radio link or at least one second QoS parameter of the second radio link. The indication may be sent to a relay UE. The first radio link may be associated with the relay UE and the network entity. The second radio link may be associated with the relay UE and at least one remote UE. The at least one first QoS parameter and the at least one second QoS parameter may be associated with a time period. Component 199 may be configured to obtain a report of at least one positioning measurement within the time period based on one or more of the at least one first QoS parameter or the at least one second QoS parameter. The report may be obtained from the relay UE. Component 199 may be within processor 1512. Component 199 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 so as to be implemented by one or more processors, or some combination thereof. Component 199 may be a component of the LMF or may be configured to communicate with the LMF and receive instructions from the LMF. Network entity 1560 may include a variety of components configured for various functions. In one configuration, the network entity 1560 includes means for obtaining, from at least one remote UE, an LPP transmission including a Uu link response time to the network entity. The network entity 1560 may include means for transmitting a first PRS configuration having a lower periodicity PRS configuration in response to the Uu link response time being equal to or greater than a threshold response time. The network entity 1560 may include means for transmitting a second PRS configuration including a higher periodicity PRS configuration in response to the Uu link response time being equal to or less than the threshold response time. The network entity 1560 may include means for transmitting to the relay UE a maximum UE rank for reporting based on a number of UE rank of the relay associated with each positioning measurement in at least one positioning measurement. The means may be a component 199 of the network entity 1560 configured to perform the functions recited by the means.

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

[0138] 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, which may include multiple A, multiple B, or multiple C. Specifically, combinations such as "at least one of A, B, or C", "one or more of A, B, or C", "at least one of A, B, and C", "one or more of A, B, and C", and "A, B, C, or any combination thereof" may be only A, only B, only C, A and B, A and C, B and C, or A and B and C, where any such combination may contain one or more members of A, B, or C. A set should be interpreted as a set of elements, where the number of elements is one or more. Thus, for a set of X, X will include one or more elements. If the first device receives data from the second device or sends data to the second device, the data may be received / sent directly between the first device and the second device, or indirectly between the first device and the second device through a collection of devices. All structural and functional equivalents of the elements of the various aspects described throughout the present disclosure that are known or will later be known to a person of ordinary skill in the art are expressly incorporated herein by reference and are covered by the claims. In addition, nothing disclosed herein is intended to be dedicated to the public, regardless of whether such disclosure is explicitly stated in the claims. Words such as "module", "mechanism", "element", "device", etc. cannot replace the word "component". Therefore, no claim element will be understood as a component plus function unless the element is explicitly stated using the phrase "component for..."

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

[0140] A device configured to "output" data (such as, transmit, signal or message) may, for example, transmit the data with a transceiver, or may transmit the data to a device that transmits the data. A device configured to "obtain" data (such as, transmit, signal or message) may, for example, receive the data with a transceiver, or may obtain the data from a device that receives the data.

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

[0142] Aspect 1 is a method for wireless communication at a relay UE, wherein the method may include: receiving an indication of one or more of at least one first quality of service (QoS) parameter of a first wireless link or at least one second QoS parameter of a second wireless link. The first wireless link may be associated with the relay UE and a network entity. The second wireless link may be associated with the relay UE and at least one remote UE. The at least one first QoS parameter and the at least one second QoS parameter may be associated with a time period. The method may include: sending a report of at least one positioning measurement within the time period based on one or more of the at least one first QoS parameter or the at least one second QoS parameter.

[0143] Aspect 2 is a method according to aspect 1, wherein the method may include: sending a request for one or more of the at least one first QoS parameter or the at least one second QoS parameter.

[0144] Aspect 3 is a method according to any one of aspects 1 and 2, wherein the at least one first QoS parameter may include one or more of a first QoS response time or a first data packet budget. The at least one second QoS parameter may include one or more of a second QoS response time or a second data packet budget.

[0145] Aspect 4 is a method according to any one of aspects 1 to 3, wherein the first wireless link may include a UE to Universal Mobile Telecommunications System (UMTS) Terrestrial Radio Access Network (UE-UTRAN or Uu) link. The second wireless link may include a side link.

[0146] Aspect 5 is a method according to any one of aspects 1 to 4, wherein the time period may include one or more of a first response time associated with the at least one first QoS parameter or a second response time associated with the at least one second QoS parameter.

[0147] Aspect 6 is a method according to aspect 5, wherein the first response time may be the same time as the second response time, or the first response time may be different from the second response time.

[0148] Aspect 7 is a method according to any one of aspects 1 to 6, wherein the at least one second QoS parameter of the second radio link may include a second response time between the relay UE and the at least one remote UE. The indication may also include an E2E response time between the network entity and the at least one remote UE. The at least one first QoS parameter of the first radio link may be calculated as a difference between the E2E response time and the second response time.

[0149] Aspect 8 is a method according to any one of aspects 1 to 7, wherein the at least one first QoS parameter of the first radio link may include a first response time between the relay UE and the network entity. The indication may also include an E2E response time between the network entity and the at least one remote UE. The at least one second QoS parameter of the second radio link may be calculated as a difference between the E2E response time and the first response time.

[0150] Aspect 9 is a method according to any one of aspects 1 to 8, wherein the at least one first QoS parameter of the first radio link may include a first response time between the relay UE and the network entity. The at least one second QoS parameter of the second radio link may include a second response time between the relay UE and the at least one remote UE.

[0151] Aspect 10 is a method according to aspect 9, wherein the indication may further include a sidelink measurement period for measuring a real-time response time of the at least one positioning measurement.

[0152] Aspect 11 is a method according to any one of aspects 1 to 10, wherein the method may include: indicating the at least one positioning measurement based on a measured round trip time (RTT) being less than or equal to the time period.

[0153] Aspect 12 is a method according to any one of Aspects 1 to 11, wherein the method may include: indicating the at least one positioning measurement based on the measured RTT being less than or equal to the sum of the first response time between the relay UE and the network entity and the second measured response time between the relay UE and the at least one remote UE.

[0154] Aspect 13 is a method according to any one of aspects 1 to 12, wherein the method may include: performing the at least one positioning measurement within the time period based on at least one of the at least one first QoS parameter or the at least one second QoS parameter. The report may be sent based on the at least one positioning measurement performed.

[0155] Aspect 14 is a method according to any one of aspects 1 to 13, wherein the method may include: sending a configuration of data packet transmission associated with the at least one positioning measurement to the at least one remote UE.

[0156] Aspect 15 is a method according to any one of aspects 1 to 14, wherein the method may include: selecting the at least one remote UE based on one or more of the first wireless link or the second wireless link.

[0157] Aspect 16 is a method according to aspect 15, wherein the method may include: selecting the at least one remote UE further based on at least one measured real-time response time between the relay UE and the at least one remote UE.

[0158] Aspect 17 is a method according to any one of aspects 1 to 16, wherein the method may include: receiving a query for a first QoS response time associated with the at least one first QoS parameter from the at least one remote UE. The method may include: sending the first QoS response time associated with the at least one first QoS parameter to the at least one remote UE.

[0159] Aspect 18 is a method according to aspect 17, wherein the method may include: receiving the report of the at least one positioning measurement from the at least one remote UE. The time period may be based on the first QoS response time. Sending the report may include forwarding the report from the at least one remote UE to the network entity.

[0160] Aspect 19 is a method according to any one of Aspects 1 to 18, wherein the time period may include at least one of the following: a first response time between the relay UE and the network entity, a second response time between the relay UE and the at least one remote UE, or an E2E response time between the network entity and the at least one remote UE.

[0161] Aspect 20 is a method according to Aspect 19, wherein the method may include: receiving a second indication of a first update to one or more of the at least one first QoS parameters of the first wireless link or a second update to one or more of the at least one second QoS parameters of the second wireless link based on the report.

[0162] Aspect 21 is a method according to any one of aspects 1 to 20, wherein the method may include receiving a maximum UE order for the report. The method may include selecting the at least one remote UE based on the maximum UE order for the report.

[0163] Aspect 22 is a method according to any one of aspects 1 to 21, wherein the report may also include a UE rank number of relays associated with each positioning measurement in the at least one positioning measurement.

[0164] Aspect 23 is a method according to any one of Aspects 1 to 22, wherein the report may include a second indication of performing the at least one positioning measurement at the relay UE or the at least one remote UE, or wherein the report may include a third indication of a lack of time or resources for performing the at least one positioning measurement.

[0165] Aspect 24 is a method of wireless communication at a network entity, wherein the method may include: sending an indication of one or more of at least one first QoS parameter of a first wireless link or at least one second QoS parameter of a second wireless link. The first wireless link may be associated with a relay UE and the network entity. The second wireless link may be associated with the relay UE and at least one remote UE. The at least one first QoS parameter and the at least one second QoS parameter may be associated with a time period. The method may include: obtaining a report of at least one positioning measurement within the time period based on one or more of the at least one first QoS parameter or the at least one second QoS parameter.

[0166] Aspect 25 is a method according to aspect 24, wherein the method may include: receiving a request for one or more of the at least one first QoS parameter or the at least one second QoS parameter.

[0167] Aspect 26 is a method according to any one of aspects 24 and 25, wherein the at least one first QoS parameter may include one or more of a first QoS response time or a first data packet budget. The at least one second QoS parameter may include one or more of a second QoS response time or a second data packet budget.

[0168] Aspect 27 is a method according to any one of aspects 24 to 26, wherein the first wireless link may include a Uu link. The second wireless link may include a side link.

[0169] Aspect 28 is a method according to any one of aspects 24 to 27, wherein the time period may include one or more of a first response time associated with the at least one first QoS parameter or a second response time associated with the at least one second QoS parameter.

[0170] Aspect 29 is a method according to aspect 28, wherein the first response time may be the same time as the second response time, or the first response time may be different from the second response time.

[0171] Aspect 30 is a method according to any one of aspects 24 to 29, wherein the at least one second QoS parameter of the second radio link may include a second response time between the relay UE and the at least one remote UE. The indication may also include an E2E response time between the network entity and the at least one remote UE.

[0172] Aspect 31 is a method according to any one of aspects 24 to 30, wherein the at least one first QoS parameter of the first radio link may include a first response time between the relay UE and the network entity. The indication may also include an E2E response time between the network entity and the at least one remote UE.

[0173] Aspect 32 is a method according to any one of aspects 24 to 31, wherein the at least one first QoS parameter of the first radio link may include a first response time between the relay UE and the network entity. The at least one second QoS parameter of the second radio link may include a second response time between the relay UE and the at least one remote UE.

[0174] Aspect 33 is a method according to aspect 32, wherein the indication may also include a sidelink measurement period for measuring a real-time response time of the at least one positioning measurement.

[0175] Aspect 34 is a method according to any one of aspects 24 to 33, wherein the report may include a second indication that the measured RTT is less than or equal to the time period.

[0176] Aspect 35 is a method according to any one of Aspects 24 to 34, wherein the at least one positioning measurement may be based on a measured RTT being less than or equal to the sum of a first response time between the relay UE and the network entity and a second measured response time between the relay UE and the at least one remote UE.

[0177] Aspect 36 is a method according to any one of aspects 24 to 35, wherein the method may include: obtaining, from the at least one remote UE, a configuration of data packet transmission associated with the at least one positioning measurement.

[0178] Aspect 37 is a method according to any one of aspects 24 to 36, wherein the report may be obtained from the relay UE. The at least one positioning measurement may be measured from the at least one remote UE.

[0179] Aspect 38 is a method according to any one of Aspects 24 to 37, wherein the time period may include at least one of the following: a first response time between the relay UE and the network entity, a second response time between the relay UE and the at least one remote UE, or an E2E response time between the network entity and the at least one remote UE.

[0180] Aspect 39 is a method according to aspect 38, wherein the method may include: sending a second indication of a first update to one or more of the at least one first QoS parameters of the first wireless link or a second update to one or more of the at least one second QoS parameters of the second wireless link based on the report.

[0181] Aspect 40 is a method according to any one of aspects 24 to 39, wherein the method may include: obtaining a Long Term Evolution (LTE) Positioning Protocol (LPP) transmission including a Uu link response time to the network entity from the at least one remote UE. Based on the Uu link response time to the network entity, the at least one second QoS parameter of the second radio link may include a second response time between the relay UE and the at least one remote UE.

[0182] Aspect 41 is a method according to aspect 40, wherein the method may include: in response to the Uu link response time being equal to or greater than a threshold response time, sending a first PRS configuration including a lower periodicity positioning reference signal (PRS) configuration, or the method may include: in response to the Uu link response time being equal to or less than the threshold response time, sending a second PRS configuration including a higher periodicity PRS configuration. The lower periodicity PRS configuration may have a lower periodicity than the higher periodicity PRS configuration.

[0183] Aspect 42 is a method according to any one of aspects 24 to 41, wherein the report may also include a UE rank number of relays associated with each positioning measurement in the at least one positioning measurement.

[0184] Aspect 43 is a method according to aspect 42, wherein the method may include: sending a maximum UE rank for the report to the relay UE based on the UE rank number of the relay associated with each positioning measurement in the at least one positioning measurement.

[0185] Aspect 44 is a method according to any one of Aspects 24 to 43, wherein the report may include a second indication of performing the at least one positioning measurement at the relay UE or the at least one remote UE, or wherein the report includes a third indication of a lack of time or resources for performing the at least one positioning measurement.

[0186] Aspect 45 is an apparatus for wireless communication, the apparatus comprising: at least one memory; and at least one processor, the at least one processor being coupled to the at least one memory, and being configured, alone or in any combination, to implement any one of Aspects 1 to 44 based at least in part on information stored in the at least one memory.

[0187] Aspect 46 is the apparatus of aspect 45, the apparatus further comprising at least one of an antenna or a transceiver coupled to the at least one processor.

[0188] Aspect 47 is an apparatus for wireless communication, the apparatus comprising means for implementing any one of aspects 1 to 44.

[0189] Aspect 48 is a computer-readable medium (e.g., a non-transitory computer-readable medium) storing computer-executable code, wherein the code, when executed by at least one processor, causes the at least one processor to implement any one of Aspects 1 to 44, alone or in any combination.

Claims

1. An apparatus for wireless communication at a relay user equipment (UE), 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: receiving an indication of one or more of at least one first quality of service (QoS) parameter of a first radio link or at least one second QoS parameter of a second radio link, wherein the first radio link is associated with the relay UE and a network entity, wherein the second radio link is associated with the relay UE and at least one remote UE, wherein the at least one first QoS parameter and the at least one second QoS parameter are associated with a time period; and Based on one or more of the at least one first QoS parameter or the at least one second QoS parameter, a report of at least one positioning measurement is sent within the time period.

2. The apparatus of claim 1 , further comprising a transceiver coupled to the at least one processor, wherein the at least one processor is further configured to: A request for one or more of the at least one first QoS parameter or the at least one second QoS parameter is sent via the transceiver.

3. The apparatus of claim 1 , wherein the at least one first QoS parameter comprises one or more of a first QoS response time or a first data packet budget, and wherein the at least one second QoS parameter comprises one or more of a second QoS response time or a second data packet budget.

4. The apparatus of claim 1, wherein the first wireless link comprises a UE to Universal Mobile Telecommunications System (UMTS) Terrestrial Radio Access Network (UE-UTRAN / Uu) link, and the second wireless link comprises a side link.

5. The apparatus of claim 1, wherein the time period comprises one or more of a first response time associated with the at least one first QoS parameter or a second response time associated with the at least one second QoS parameter. 6 . The apparatus of claim 5 , wherein the first response time is the same time as the second response time, or the first response time is different from the second response time.

7. The apparatus of claim 1 , wherein the at least one second QoS parameter of the second radio link comprises a second response time between the relay UE and the at least one remote UE, wherein the indication further comprises an end-to-end (E2E) response time between the network entity and the at least one remote UE, and wherein the at least one first QoS parameter of the first radio link is calculated as a difference between the E2E response time and the second response time.

8. The apparatus of claim 1 , wherein the at least one first QoS parameter of the first radio link comprises a first response time between the relay UE and the network entity, wherein the indication further comprises an end-to-end (E2E) response time between the network entity and the at least one remote UE, and wherein the at least one second QoS parameter of the second radio link is calculated as a difference between the E2E response time and the first response time.

9. The apparatus of claim 1 , wherein the at least one first QoS parameter of the first wireless link comprises a first response time between the relay UE and the network entity, and wherein the at least one second QoS parameter of the second wireless link comprises a second response time between the relay UE and the at least one remote UE.

10. The apparatus of claim 9, wherein the indication further comprises a sidelink measurement period for measuring a real-time response time of the at least one positioning measurement.

11. The apparatus of claim 1 , wherein the at least one processor is further configured to: The at least one positioning measurement is indicated based on a measured round trip time (RTT) being less than or equal to the time period.

12. The apparatus of claim 1, wherein the at least one processor is further configured to: The at least one positioning measurement is indicated based on a measured RTT being less than or equal to a sum of a first response time between the relay UE and the network entity and a second measured response time between the relay UE and the at least one remote UE.

13. The apparatus of claim 1, wherein the at least one processor is further configured to: Based on at least one of the at least one first QoS parameter or the at least one second QoS parameter, the at least one positioning measurement is performed within the time period, wherein the report is sent based on the at least one positioning measurement performed.

14. The apparatus of claim 1, wherein the at least one processor is further configured to: A configuration of data packet transmission associated with the at least one positioning measurement is transmitted to the at least one remote UE.

15. The apparatus of claim 1, wherein the at least one processor is further configured to: The at least one remote UE is selected based on one or more of the first wireless link or the second wireless link.

16. The apparatus of claim 15, wherein the at least one processor is further configured to: The at least one remote UE is selected further based on at least one measured real-time response time between the relay UE and the at least one remote UE.

17. The apparatus of claim 1, wherein the at least one processor is further configured to: receiving, from the at least one remote UE, a query for a first QoS response time associated with the at least one first QoS parameter; and The first QoS response time associated with the at least one first QoS parameter is sent to the at least one remote UE.

18. The apparatus of claim 17, wherein the at least one processor is further configured to: The report of the at least one positioning measurement is received from the at least one remote UE, wherein the time period is based on the first QoS response time, wherein the at least one processor is further configured to send the report by forwarding the report from the at least one remote UE to the network entity.

19. The apparatus of claim 1, wherein the time period comprises at least one of: a first response time between the relay UE and the network entity, a second response time between the relay UE and the at least one remote UE, or an end-to-end (E2E) response time between the network entity and the at least one remote UE.

20. The apparatus of claim 19, wherein the at least one processor is further configured to: A second indication of a first update to one or more of the at least one first QoS parameters for the first radio link or a second update to one or more of the at least one second QoS parameters for the second radio link is received based on the report.

21. The apparatus of claim 1, wherein the at least one processor is further configured to: receiving a maximum UE rank for the report; and The at least one remote UE is selected based on the maximum UE rank for the report.

22. The apparatus of claim 1, wherein the report further comprises a UE rank number of relays associated with each of the at least one positioning measurement.

23. The apparatus of claim 1, wherein the report comprises a second indication of performing the at least one positioning measurement at the relay UE or the at least one remote UE, or wherein the report comprises a third indication of lack of time or resources for performing the at least one positioning measurement.

24. An apparatus for wireless communication at a network entity, 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: sending an indication of one or more of at least one first quality of service (QoS) parameter of a first radio link or at least one second QoS parameter of a second radio link, wherein the first radio link is associated with a relay UE and the network entity, wherein the second radio link is associated with the relay UE and at least one remote UE, wherein the at least one first QoS parameter and the at least one second QoS parameter are associated with a time period; and A report of at least one positioning measurement is obtained within the time period based on one or more of the at least one first QoS parameter or the at least one second QoS parameter.

25. The apparatus of claim 24, further comprising a transceiver coupled to the at least one processor, wherein the at least one processor is further configured to: A configuration of data packet transmission associated with the at least one positioning measurement is obtained from the at least one remote UE.

26. The apparatus of claim 24, wherein the at least one processor is further configured to: Obtaining a Long Term Evolution (LTE) Positioning Protocol (LPP) transmission including a Uu link response time to the network entity from the at least one remote UE, wherein the at least one second QoS parameter of the second wireless link includes a second response time between the relay UE and the at least one remote UE based on the Uu link response time to the network entity.

27. The apparatus of claim 26, wherein the at least one processor is further configured to: sending a first positioning reference signal (PRS) configuration comprising a lower periodicity PRS configuration in response to the Uu link response time being equal to or greater than a threshold response time; or A second PRS configuration including a higher periodicity PRS configuration is transmitted in response to the Uu link response time being equal to or less than the threshold response time, wherein the lower periodicity PRS configuration has a lower periodicity than the higher periodicity PRS configuration.

28. The apparatus of claim 24, wherein the report further comprises a UE rank number of relays associated with each of the at least one positioning measurement.

29. A method for wireless communication at a relay user equipment (UE), comprising: receiving an indication of one or more of at least one first quality of service (QoS) parameter of a first radio link or at least one second QoS parameter of a second radio link, wherein the first radio link is associated with the relay UE and a network entity, wherein the second radio link is associated with the relay UE and at least one remote UE, wherein the at least one first QoS parameter and the at least one second QoS parameter are associated with a time period; and Based on one or more of the at least one first QoS parameter or the at least one second QoS parameter, a report of at least one positioning measurement is sent within the time period.

30. A method for wireless communication at a network entity, comprising: sending an indication of one or more of at least one first quality of service (QoS) parameter of a first radio link or at least one second QoS parameter of a second radio link, wherein the first radio link is associated with a relay UE and the network entity, wherein the second radio link is associated with the relay UE and at least one remote UE, wherein the at least one first QoS parameter and the at least one second QoS parameter are associated with a time period; and A report of at least one positioning measurement is obtained within the time period based on one or more of the at least one first QoS parameter or the at least one second QoS parameter.

Images