Side link receive-transmit time difference measurement type

Abstract

In an aspect, a user equipment (UE) transmits a capability indication indicating that the UE is able to perform a first sidelink (SL) receive-transmit (Rx-Tx) time difference measurement type and a second SL Rx-Tx time difference measurement type to a positioning estimation entity (PDE). The PDE sends a measurement request to perform one or more SL Rx-Tx time difference measurements for the UE. The UE determines a SL Rx-Tx time difference measurement type to use based on an explicit network designation SL Rx-Tx time difference measurement type or an autonomous selection at the UE. The UE sends a measurement report to the PDE, which receives the measurement report and is capable of determining the SL Rx-Tx time difference measurement type used by the UE.

Description

Technical Field

[0001] All aspects of this disclosure relate to wireless communications. Background Technology

[0002] Wireless communication systems have evolved through many generations, including first-generation analog radiotelephone service (1G), second-generation (2G) digital radiotelephone service (including transitional 2.5G and 2.75G networks), third-generation (3G) high-speed data, wireless services with internet capabilities, and fourth-generation (4G) services (e.g., Long Term Evolution (LTE) or WiMax). Currently, many different types of wireless communication systems are in use, including cellular systems and Personal Communication Services (PCS) systems. Known examples of cellular systems include cellular analog Advanced Mobile Phone Systems (AMPS), as well as digital cellular systems based on Code Division Multiple Access (CDMA), Frequency Division Multiple Access (FDMA), Time Division Multiple Access (TDMA), Global System for Mobile Communications (GSM), and others.

[0003] The fifth-generation (5G) wireless standard, known as New Radio (NR), delivers higher data speeds, more connections, better coverage, and other improvements. According to the Next Generation Mobile Networks Alliance (NGC), the 5G standard is designed to provide higher data rates, more accurate positioning (e.g., based on Location Reference Signals (RS-P), such as downlink, uplink, or sidelink Location Reference Signals (PRS)), and other technological enhancements compared to previous standards. These enhancements, along with the use of higher frequency bands, advancements in the PRS process and technology, and the high-density deployment of 5G, enable high-accuracy positioning based on 5G. Summary of the Invention

[0004] The following is a simplified summary of the invention relating to one or more aspects disclosed herein. Therefore, this summary should not be considered an exhaustive overview relating to all conceptual aspects, nor should it be considered to identify key or decisive elements relating to all conceptual aspects or to depict the scope associated with any particular aspect. Thus, the sole purpose of this summary is to present, in a concise form, certain concepts relating to one or more aspects involving the mechanisms disclosed herein, prior to the detailed description presented below.

[0005] In one aspect, a method of operating a user equipment (UE) includes: transmitting a capability indication indicating that the UE is capable of performing a first side-link (SL) receive-transmit (Rx-Tx) time difference measurement type and a second SLRx-Tx time difference measurement type to a positioning estimation entity, wherein the first SL Rx-Tx time difference measurement type is based on a first time difference between: (i) a UE receive timing associated with a first subframe including a first positioning reference signal (PRS) from another device, and (ii) a first UE transmit timing of a second subframe including a second PRS transmitted by the UE, and wherein the second SLRx-Tx time difference measurement type is based on a second time difference between: (i) the UE receive timing associated with the first subframe including the first PRS from the other device, and (iii) a second UE transmit timing of a third subframe that is after the first subframe and is temporally closest to the first subframe; receiving a measurement request for performing one or more SL Rx-Tx time difference measurements for the UE; and determining whether the measurement is based on the first SL Rx-Tx time difference measurement type or the second SL Rx-Tx time difference measurement type. The determination is based on an explicit network-specified SL Rx-Tx time difference measurement type associated with the measurement request, or the determination includes an autonomous selection at the UE based on one or more rules associated with one or more criteria; the determination is performed according to the determined SL Rx-Tx time difference measurement type; and a measurement report is sent to the positioning estimation entity, the measurement report including measurement information based on the one or more SL Rx-Tx time difference measurements.

[0006] In one aspect, a method of operating a location estimation entity includes: receiving a capability indication that instructs a user equipment (UE) to perform a first sidelink (SL) receive-transmit (Rx-Tx) time difference measurement type and a second SL Rx-Tx time difference measurement type to the location estimation entity, wherein the first SL Rx-Tx time difference measurement type is based on a first time difference between: (i) a UE receive timing associated with a first subframe including a first location reference signal (PRS) from another device, and (ii) a first UE transmit timing of a second subframe including a second PRS transmitted by the UE, and wherein the second SL Rx-Tx time difference measurement type is based on a second time difference between: (i) the UE receive timing associated with the first subframe including the first PRS from the other device, and (iii) a second UE transmit timing of a third subframe that is after the first subframe and is temporally closest to the first subframe; sending a measurement request to perform one or more SL Rx-Tx time difference measurements for the UE; and receiving a measurement report, the measurement report including measurements based on one or more SL Rx-Tx time difference measurements. Measurement information of Rx-Tx time difference measurement; and determining whether the measurement information is based on the first SL Rx-Tx time difference measurement type or the second SL Rx-Tx time difference measurement type.

[0007] In one aspect, a user equipment (UE) includes: a memory; and at least one processor communicatively coupled to the memory, the at least one processor being configured to: transmit a capability indication indicating that the UE is capable of performing a first side-link (SL) receive-transmit (Rx-Tx) time difference measurement type and a second SLRx-Tx time difference measurement type to a positioning estimation entity, wherein the first SL Rx-Tx time difference measurement type is based on a first time difference between: (i) a UE receive timing associated with a first subframe including a first positioning reference signal (PRS) from another device, and (ii) a first UE transmit timing of a second subframe including a second PRS transmitted by the UE, and wherein the second SLRx-Tx time difference measurement type is based on a second time difference between: (i) the UE receive timing associated with the first subframe including the first PRS from the other device, and (iii) a second UE transmit timing of a third subframe that is after the first subframe and temporally closest to the first subframe; and receive one or more SLs performed for the UE. The measurement request includes: a measurement request for Rx-Tx time difference measurement; determining whether to perform the one or more SL Rx-Tx time difference measurements based on the first SL Rx-Tx time difference measurement type or the second SL Rx-Tx time difference measurement type, wherein the determination is based on an explicit network-specified SL Rx-Tx time difference measurement type associated with the measurement request, or wherein the determination includes an autonomous selection at the UE based on one or more rules associated with one or more criteria; performing the one or more SL Rx-Tx time difference measurements based on the determined SL Rx-Tx time difference measurement type; and sending a measurement report to a positioning estimation entity, the measurement report including measurement information based on the one or more SL Rx-Tx time difference measurements.

[0008] In one aspect, a location estimation entity includes: a memory; and at least one processor communicatively coupled to the memory, the at least one processor being configured to: a reception capability indication indicating that a user equipment (UE) is capable of performing a first side-link (SL) receive-transmit (Rx-Tx) time difference measurement type and a second SL Rx-Tx time difference measurement type on the location estimation entity, wherein the first SL Rx-Tx time difference measurement type is based on a first time difference between: (i) a UE reception timing associated with a first subframe including a first location reference signal (PRS) from another device, and (ii) a first UE transmission timing of a second subframe including a second PRS transmitted by the UE, and wherein the second SL Rx-Tx time difference measurement type is based on a second time difference between: (i) the UE reception timing associated with the first subframe including the first PRS from the other device, and (iii) a second UE transmission timing of a third subframe that is after the first subframe and temporally closest to the first subframe; and transmitting one or more SLs for the UE. The measurement request for Rx-Tx time difference measurement; receiving a measurement report including measurement information based on one or more SL Rx-Tx time difference measurements; and determining whether the measurement information is based on the first SL Rx-Tx time difference measurement type or the second SL Rx-Tx time difference measurement type.

[0009] In one aspect, a user equipment (UE) includes: components for transmitting a capability indication indicating that the UE is capable of performing a first side-link (SL) receive-transmit (Rx-Tx) time difference measurement type and a second SL Rx-Tx time difference measurement type to a positioning estimation entity, wherein the first SL Rx-Tx time difference measurement type is based on a first time difference between: (i) a UE receive timing associated with a first subframe including a first positioning reference signal (PRS) from another device, and (ii) a first UE transmit timing of a second subframe including a second PRS transmitted by the UE, and wherein the second SL Rx-Tx time difference measurement type is based on a second time difference between: (i) the UE receive timing associated with the first subframe including the first PRS from the other device, and (iii) a second UE transmit timing of a third subframe that is after the first subframe and is temporally closest to the first subframe; components for receiving a measurement request for performing one or more SL Rx-Tx time difference measurements for the UE; and components for determining whether the measurement is based on the first SL Rx-Tx time difference measurement type or the second SL Rx-Tx time difference measurement type. The components include: a component for performing one or more SL Rx-Tx time difference measurements based on an explicit network-specified SL Rx-Tx time difference measurement type associated with the measurement request; or a component for performing one or more SL Rx-Tx time difference measurements based on an Rx-Tx time difference measurement type associated with the measurement request, wherein the determination is based on an autonomous selection at the UE based on one or more rules associated with one or more criteria; a component for performing one or more SL Rx-Tx time difference measurements according to the determined SL Rx-Tx time difference measurement type; and a component for sending a measurement report to a positioning estimation entity, the measurement report including measurement information based on the one or more SL Rx-Tx time difference measurements.

[0010] In one aspect, a positioning estimation entity includes: components for receiving capability indication, the capability indication indicating that a user equipment (UE) is capable of performing a first side-link (SL) receive-transmit (Rx-Tx) time difference measurement type and a second SL Rx-Tx time difference measurement type to the positioning estimation entity, wherein the first SL Rx-Tx time difference measurement type is based on a first time difference between: (i) a UE receive timing associated with a first subframe including a first positioning reference signal (PRS) from another device, and (ii) a first UE transmit timing of a second subframe including a second PRS transmitted by the UE, and wherein the second SL Rx-Tx time difference measurement type is based on a second time difference between: (i) the UE receive timing associated with the first subframe including the first PRS from the other device, and (iii) a second UE transmit timing of a third subframe that is after the first subframe and is temporally closest to the first subframe; components for transmitting a measurement request for performing one or more SL Rx-Tx time difference measurements for the UE; and components for receiving a measurement report, the measurement report including measurements based on one or more SL Rx-Tx time difference measurements. Measurement information for Rx-Tx time difference measurement; and a component for determining whether the measurement information is based on the first SL Rx-Tx time difference measurement type or the second SL Rx-Tx time difference measurement type.

[0011] In one aspect, a non-transitory computer-readable medium storing computer-executable instructions, which, when executed by a user equipment (UE), cause the UE to: transmit a capability indication indicating that the UE is capable of performing a first side-link (SL) receive-transmit (Rx-Tx) time difference measurement type and a second SL Rx-Tx time difference measurement type to a positioning estimation entity, wherein the first SL Rx-Tx time difference measurement type is based on a first time difference between: (i) a UE receive timing associated with a first subframe including a first positioning reference signal (PRS) from another device, and (ii) a first UE transmit timing of a second subframe including a second PRS transmitted by the UE, and wherein the second SL Rx-Tx time difference measurement type is based on a second time difference between: (i) the UE receive timing associated with the first subframe including the first PRS from the other device, and (iii) a second UE transmit timing of a third subframe that is after the first subframe and is temporally closest to the first subframe; receive one or more SLs performed for the UE. The measurement request includes: a measurement request for Rx-Tx time difference measurement; determining whether to perform the one or more SL Rx-Tx time difference measurements based on the first SL Rx-Tx time difference measurement type or the second SL Rx-Tx time difference measurement type, wherein the determination is based on an explicit network-specified SL Rx-Tx time difference measurement type associated with the measurement request, or wherein the determination includes an autonomous selection at the UE based on one or more rules associated with one or more criteria; performing the one or more SL Rx-Tx time difference measurements based on the determined SL Rx-Tx time difference measurement type; and sending a measurement report to a positioning estimation entity, the measurement report including measurement information based on the one or more SL Rx-Tx time difference measurements.

[0012] In one aspect, a non-transitory computer-readable medium storing computer-executable instructions, which, when executed by a positioning estimation entity, cause the positioning estimation entity to: indicate a reception capability, the capability indicating a user equipment (UE) capable of performing a first side-link (SL) receive-transmit (Rx-Tx) time difference measurement type and a second SL Rx-Tx time difference measurement type to the positioning estimation entity, wherein the first SL Rx-Tx time difference measurement type is based on a first time difference between: (i) a UE reception timing associated with a first subframe including a first positioning reference signal (PRS) from another device, and (ii) a first UE transmission timing including a second subframe including a second PRS transmitted by the UE, and wherein the second SL Rx-Tx time difference measurement type is based on a second time difference between: (i) the UE reception timing associated with the first subframe including the first PRS from the other device, and (iii) a second UE transmission timing following the first subframe and being temporally closest to the first subframe; and transmit one or more SLs for the UE. The measurement request for Rx-Tx time difference measurement; receiving a measurement report including measurement information based on one or more SL Rx-Tx time difference measurements; and determining whether the measurement information is based on the first SL Rx-Tx time difference measurement type or the second SL Rx-Tx time difference measurement type.

[0013] Based on the accompanying drawings and detailed description, other objects and advantages associated with the aspects disclosed herein will be apparent to those skilled in the art. Attached Figure Description

[0014] The accompanying drawings are provided to help describe various aspects of this disclosure, and are provided for illustrative purposes only and not to limit the various aspects.

[0015] Figure 1 Example wireless communication systems according to various aspects of this disclosure are illustrated.

[0016] Figure 2A , Figure 2B and Figure 2C Example wireless network architectures based on various aspects of this disclosure are illustrated.

[0017] Figure 3A , Figure 3B and Figure 3C It is a simplified block diagram of several examples of components that can be used in user equipment (UE), base stations and network entities and configured to support communications as taught herein.

[0018] Figure 4 This is a diagram illustrating an example frame structure according to various aspects of this disclosure.

[0019] Figure 5 This is a diagram illustrating various downlink channels within example downlink time slots according to various aspects of this disclosure.

[0020] Figure 6 This is a diagram illustrating various uplink channels within example uplink time slots according to various aspects of this disclosure.

[0021] Figure 7 Examples of various positioning methods supported in new radios (NR) according to various aspects of this disclosure are illustrated.

[0022] Figure 8 This is a diagram illustrating an example round-trip time (RTT) procedure for determining the location of a UE according to various aspects of this disclosure.

[0023] Figure 9 This is a diagram illustrating example timing of RTT measurement signals exchanged between a base station and a UE according to various aspects of this disclosure.

[0024] Figure 10A and Figure 10B Various scenarios of interest are illustrated according to aspects of this disclosure, including sidelink-only localization or combined Uu and sidelink localization.

[0025] Figure 11A and Figure 11B This is a diagram illustrating example sidelink time slot structures with and without feedback resources according to various aspects of this disclosure.

[0026] Figure 12 This is a diagram illustrating an example of a location resource pool configured within a sidelink resource pool for communication, according to various aspects of this disclosure.

[0027] Figure 13 An exemplary process of communication according to one aspect of this disclosure is illustrated.

[0028] Figure 14 An exemplary process of communication according to one aspect of this disclosure is illustrated. Detailed Implementation

[0029] Various aspects of this disclosure are provided in the following description and accompanying drawings of various examples provided for illustrative purposes. Alternative aspects may be devised without departing from the scope of this disclosure. Additionally, well-known elements of this disclosure will not be described in detail or will be omitted so as not to obscure the relevant details of this disclosure.

[0030] Various aspects involve the side link (SL) receive-transmit (Rx-Tx) SLRx-Tx time difference capability of the positioning estimation entity (such as LMF for network-assisted positioning estimation or UE or another UE for UE-based positioning estimation).

[0031] Specific aspects of the subject matter described in this disclosure can be implemented to achieve one or more of the following potential advantages. Aspects of this disclosure relate to the determination of the SL Rx-Tx time difference measurement type (e.g., Option 1 or Option 2) in scenarios where the UE supports both Options 1 to 2 (or Option 3). In some aspects, the determination of the SL Rx-Tx time difference measurement type can be based on an explicit network specification of the SL Rx-Tx time difference measurement type associated with the measurement request, or at the UE, based on an autonomous selection of one or more rules associated with one or more criteria. Such aspects can provide various technical advantages, such as greater flexibility in reporting SL Rx-Tx time difference measurements for SL-based positioning estimation for the UE. For example, in some scenarios, one SL Rx-Tx time difference measurement type may be more suitable than another (e.g., based on criteria such as UE mobility, inter-subframe time difference, RSRP variation, etc.), and selecting a more suitable SL Rx-Tx time difference measurement type may result in less positioning latency, higher positioning accuracy, less power consumption at the UE, etc.

[0032] The terms “exemplary” and / or “example” are used herein to mean “serving as an example, instance, or illustration.” Any aspect described herein as “exemplary” and / or “example” is not necessarily to be construed as superior to or better than other aspects. Similarly, the term “aspects of this disclosure” does not require that all aspects of this disclosure include the features, advantages, or modes of operation discussed.

[0033] Those skilled in the art will understand that any of a variety of different techniques and methods can be used to represent the information and signals described below. For example, data, instructions, commands, information, signals, bits, symbols, and chips that may be mentioned throughout the following description can be represented by voltage, current, electromagnetic waves, magnetic fields or magnetic particles, light fields or optical particles, or any combination thereof, depending in part on the specific application, in part on the desired design, in part on the corresponding technology, and so on.

[0034] Furthermore, many aspects are described according to a sequence of actions to be performed by elements of, for example, a computing device. It will be appreciated that the various actions described herein can be performed by specific circuitry (e.g., an application-specific integrated circuit (ASIC)), by program instructions executed by one or more processors, or by a combination of both. Additionally, the sequence of actions described herein can be considered to be entirely embodied in any form of non-transitory computer-readable storage medium storing a corresponding set of computer instructions that, when executed, will cause or command the associated processor of the device to perform the functionality described herein. Therefore, various aspects of this disclosure can be embodied in a variety of different forms, all of which are contemplated within the scope of the claimed subject matter. Furthermore, for each aspect described herein, any corresponding form of any such aspect may be described herein as, for example, "logic configured to perform the described actions."

[0035] As used herein, unless otherwise stated, the terms “User Equipment” (UE) and “Base Station” are not intended to be specific or otherwise limited to any particular Radio Access Technology (RAT). In general, a UE can be any wireless communication device used by a user to communicate over a wireless communication network (e.g., mobile phone, router, tablet computer, laptop computer, consumer asset positioning device, wearable device (e.g., smartwatch, glasses, augmented reality (AR) / virtual reality (VR) headset, etc.), vehicle (e.g., car, motorcycle, bicycle, etc.), Internet of Things (IoT) device, etc.). A UE can be mobile or can (e.g., at certain times) be stationary and can communicate with a Radio Access Network (RAN). As used herein, the term “UE” can be interchangeably referred to as “Access Terminal” or “AT,” “Client Equipment,” “Wireless Equipment,” “Subscriber Equipment,” “Subscriber Terminal,” “Subscriber Station,” “User Terminal” or “UT,” “Mobile Equipment,” “Mobile Terminal,” “Mobile Station,” or variations thereof. Overall, a UE can communicate with the core network via the RAN, and through the core network, a UE can connect to external networks (such as the Internet) and other UEs. Of course, other mechanisms for connecting to the core network and / or the Internet are also possible for the UE, such as through wired access networks, wireless local area network (WLAN) networks (e.g., based on the Institute of Electrical and Electronics Engineers (IEEE) 802.11 standard, etc.).

[0036] A base station may operate according to one of several RATs to communicate with the UE, depending on the network in which it is deployed, and may alternatively be referred to as an Access Point (AP), Network Node, Node B, Evolved Node B (eNB), Next Generation eNB (ng-eNB), New Radio (NR) Node B (also referred to as gNB or gNodeB), etc. The base station may primarily be used to support the UE's radio access, including supporting data, voice, and / or signaling connections for the supported UE. In some systems, the base station may only provide edge node signaling functions, while in others, it may provide additional control and / or network management functions. The communication link through which the UE can transmit signals to the base station is called an uplink (UL) channel (e.g., reverse traffic channel, reverse control channel, access channel, etc.). The communication link through which the base station can transmit signals to the UE is called a downlink (DL) or forward link channel (e.g., paging channel, control channel, broadcast channel, forward traffic channel, etc.). As used herein, the term "traffic channel (TCH)" may refer to an uplink / reverse traffic channel or a downlink / forward traffic channel.

[0037] The term "base station" can refer to a single physical transmit / receive point (TRP) or multiple physical TRPs that may be co-located or non-co-located. For example, when the term "base station" refers to a single physical TRP, the physical TRP can be the antenna of the base station corresponding to a cell (or several cell sectors) of the base station. When the term "base station" refers to multiple co-located physical TRPs, the physical TRP can be the antenna array of the base station (e.g., as in a multiple-input multiple-output (MIMO) system or where the base station employs beamforming). When the term "base station" refers to multiple non-co-located physical TRPs, the physical TRP can be a distributed antenna system (DAS) (a network of spatially separated antennas connected via a transmission medium to a common source) or a remote radio headend (RRH) (a remote base station connected to the serving base station). Alternatively, a non-co-located physical TRP can be the serving base station from which the UE receives measurement reports and a neighboring base station where the UE is measuring its reference radio frequency (RF) signal. Because, as used herein, a TRP is the point by which a base station transmits and receives radio signals, references to transmitting from or receiving at a base station should be understood to refer to a specific TRP of the base station.

[0038] In some specific implementations supporting UE positioning, the base station may not support the UE's radio access (e.g., it may not support data, voice, and / or signaling connections for the UE), but may instead transmit reference signals to the UE for measurement and / or receive and measure signals transmitted by the UE. Such a base station may be referred to as a positioning beacon (e.g., in the case of transmitting signals to the UE) and / or as a location measurement unit (e.g., in the case of receiving and measuring signals from the UE).

[0039] An “RF signal” refers to an electromagnetic wave of a given frequency that transmits information across the space between a transmitter and a receiver. As used herein, a transmitter may send a single “RF signal” or multiple “RF signals” to a receiver. However, due to the propagation characteristics of RF signals through multipath channels, a receiver may receive multiple “RF signals” corresponding to each transmitted RF signal. The same transmitted RF signal on different paths between the transmitter and receiver may be referred to as a “multipath” RF signal. As used herein, an RF signal may also be referred to as a “wireless signal” or simply a “signal” where the context clearly indicates that the term “signal” refers to a wireless signal or an RF signal.

[0040] Figure 2A An example wireless network architecture 200 is illustrated. For instance, the 5GC 210 (also referred to as the Next Generation Core (NGC)) can be functionally viewed as control plane (C-plane) functions 214 (e.g., UE registration, authentication, network access, gateway selection, etc.) and user plane (U-plane) functions 212 (e.g., UE gateway functions, access to data networks, IP routing, etc.), which work together to form the core network. The user plane interface (NG-U) 213 and the control plane interface (NG-C) 215 connect the gNB 222 to the 5GC 210, specifically to user plane functions 212 and control plane functions 214, respectively. In an additional configuration, the ng-eNB 224 can also connect to the 5GC 210 via the NG-C 215 to the control plane function 214 and the NG-U 213 to the user plane function 212. Furthermore, the ng-eNB 224 can communicate directly with the gNB 222 via a backhaul connection 223. In some configurations, the next-generation RAN (NG-RAN) 220 may have one or more gNBs 222, while other configurations include one or more of both ng-eNBs 224 and gNBs 222. Either or both of the gNBs 222 or ng-eNBs 224 can communicate with one or more UEs 204 (e.g., any of the UEs described herein).

[0041] Another optional aspect may include a location server 230 that can communicate with the 5GC 210 to provide location assistance to the UE 204. The location server 230 may be implemented as multiple separate servers (e.g., physically separate servers, different software modules on a single server, different software modules distributed across multiple physical servers, etc.), or alternatively, each may correspond to a single server. The location server 230 may be configured to support one or more location services for the UE 204 that can be connected to the location server 230 via the core network, the 5GC 210, and / or via the Internet (not illustrated). Furthermore, the location server 230 may be integrated into a component of the core network, or alternatively, may be located outside the core network (e.g., a third-party server, such as an original equipment manufacturer (OEM) server or a service server).

[0042] Figure 2B Another example wireless network architecture 240.5GC 260 is illustrated (which can correspond to...). Figure 2AThe 5GC210 in the document can be functionally considered as a control plane function provided by the Access and Mobility Management Function (AMF) 264 and a user plane function provided by the User Plane Function (UPF) 262, which work together to form the core network (i.e., 5GC 260). The functions of AMF264 include: registration management, connection management, reachability management, mobility management, lawful interception, transmission of session management (SM) messages between one or more UEs 204 (e.g., any of the UEs described herein) and the Session Management Function (SMF) 266, transparent proxy service for routing SM messages, access authentication and access authorization, transmission of short message service (SMS) messages between UE 204 and the Short Message Service Function (SMSF) (not shown), and Security Anchoring Functionality (SEAF). AMF264 also interacts with the Authentication Server Function (AUSF) (not shown) and UE 204, and receives an intermediate key established as a result of the UE 204's authentication process. In the case of UMTS (Universal Mobile Telecommunications System) Subscriber Identity Module (USIM) authentication, AMF 264 retrieves security material from the AMF. AMF 264 also includes Security Context Management (SCM). The SCM receives a key from the SEAF and uses this key to derive an access network-specific key. AMF 264 functionality also includes location service management for regulatory services, transmission of location service messages between UE 204 and Location Management Function (LMF) 270 (which acts as location server 230), transmission of location service messages between NG-RAN 220 and LMF 270, Evolved Packet System (EPS) bearer identifier allocation for EPS interoperability, and UE 204 mobility event notification. Furthermore, AMF 264 also supports non-3GPP... ® (Third Generation Partner Program) Access network functionality.

[0043] The functions of UPF 262 include: acting as an anchor point for intra-RAT / inter-RAT mobility (where applicable), acting as an external Protocol Data Unit (PDU) session point interconnecting to a data network (not shown), providing packet routing and forwarding, packet inspection, user plane policy rule enforcement (e.g., gating, redirection, traffic steering), lawful interception (user plane collection), traffic usage reporting, quality of service (QoS) handling for user plane (e.g., uplink / downlink rate enforcement, reflective QoS marking in downlink), uplink traffic verification (Service Data Flow (SDF) to QoS flow mapping), transport-level packet marking in uplink and downlink, downlink packet buffering and downlink data notification triggering, and delivering and forwarding one or more "end markers" to the source RAN node. UPF 262 can also support the delivery of location service messages between UE 204 and location servers (such as SLP 272) on the user plane.

[0044] The functions of SMF 266 include session management, UE Internet Protocol (IP) address allocation and management, selection and control of user plane functions, service orientation configuration at UPF 262 for routing services to the correct destination, partial control of policy enforcement and QoS, and downlink data notification. The interface through which SMF 266 communicates with AMF 264 is called the N11 interface.

[0045] Another optional aspect may include an LMF 270, which can communicate with the 5GC 260 to provide location assistance to the UE 204. The LMF 270 can be implemented as multiple separate servers (e.g., physically separate servers, different software modules on a single server, different software modules distributed across multiple physical servers, etc.), or alternatively, each can correspond to a single server. The LMF 270 can be configured to support one or more location services for the UE 204, which can connect to the LMF 270 via the core network, the 5GC 260, and / or via the Internet (not illustrated). SLP 272 can support similar functions to LMF 270, but while LMF 270 can communicate with AMF 264, NG-RAN 220, and UE 204 on the control plane (e.g., using interfaces and protocols designed to deliver signaling messages rather than voice or data), SLP 272 can communicate with UE 204 and external clients (e.g., third-party server 274) on the user plane (e.g., using protocols designed to carry voice and / or data, such as Transmit Control Protocol (TCP) and / or IP).

[0046] Another optional aspect may include a third-party server 274, which can communicate with LMF 270, SLP 272, 5GC 260 (e.g., via AMF 264 and / or UPF 262), NG-RAN 220, and / or UE 204 to obtain location information (e.g., location estimation) of UE 204. Therefore, in some cases, the third-party server 274 may be referred to as a Location Services (LCS) client or an external client. The third-party server 274 may be implemented as multiple separate servers (e.g., physically separate servers, different software modules on a single server, different software modules distributed across multiple physical servers, etc.), or alternatively, each may correspond to a single server.

[0047] User plane interface 263 and control plane interface 265 connect 5GC 260, and specifically connect UPF 262 and AMF 264 to one or more gNB 222 and / or ng-eNB 224 in NG-RAN 220. The interface between gNB 222 and / or ng-eNB 224 and AMF 264 is referred to as the "N2" interface, while the interface between gNB 222 and / or ng-eNB 224 and UPF 262 is referred to as the "N3" interface. The gNB 222 and / or ng-eNB 224 of NG-RAN 220 can communicate directly with each other via backhaul connection 223, referred to as the "Xn-C" interface. One or more of gNB 222 and / or ng-eNB 224 can communicate with one or more UEs 204 via a radio interface referred to as the "Uu" interface.

[0048] The functionality of the gNB 222 can be divided among the gNB Central Unit (gNB-CU) 226, one or more gNB Distributed Units (gNB-DU) 228, and one or more gNB Radio Units (gNB-RU) 229. The gNB-CU 226 is a logical node that includes base station functions other than those specifically allocated to the gNB-DU 228, including user data delivery, mobility control, radio access network sharing, location, session management, etc. More specifically, the gNB-CU 226 typically hosts the Radio Resource Control (RRC), Serving Data Adaptation Protocol (SDAP), and Packet Data Convergence Protocol (PDCP) protocols of the gNB 222. The gNB-DU 228 is a logical node that typically hosts the Radio Link Control (RLC) and Media Access Control (MAC) layers of the gNB 222. Its operation is controlled by the gNB-CU 226. One gNB-DU 228 can support one or more cells, and a cell is supported by only one gNB-DU 228. The interface 232 between gNB-CU 226 and one or more gNB-DU 228 is referred to as the "F1" interface. The physical (PHY) layer functionality of gNB 222 is typically managed by one or more independent gNB-RU 229s, which perform functions such as power amplification and signal transmission / reception. The interface between gNB-DU 228 and gNB-RU 229 is referred to as the "Fx" interface. Therefore, UE 204 communicates with gNB-CU 226 via the RRC, SDAP, and PDCP layers, with gNB-DU 228 via the RLC and MAC layers, and with gNB-RU 229 via the PHY layer.

[0049] The deployment of communication systems such as 5G NR systems can be arranged in a variety of ways using various components or parts. In a 5G NR system or network, network nodes, network entities, network mobility elements, RAN nodes, core network nodes, network elements, or network equipment (such as base stations or one or more units (or components) performing base station functions) can be implemented in aggregated or decomposed architectures. For example, base stations (such as Node B (NB), evolved NB (eNB), NR base stations, 5GNB, access points (APs), transmit / receive points (TRPs), or cells, etc.) can be implemented as aggregated base stations (also known as standalone base stations or monolithic base stations) or decomposed base stations.

[0050] Aggregated base stations can be configured to utilize a radio protocol stack that is physically or logically integrated within a single RAN node. Decentralized base stations can be configured to utilize a protocol stack that is physically or logically distributed across 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, the CU can be implemented within a RAN node, and one or more DUs can be co-located with the CU, or alternatively, can be geographically or virtually distributed across one or more other RAN nodes. DUs can be implemented to communicate with one or more RUs. Each of the CU, DU, and RU can also be implemented as a virtual unit, namely a virtual central unit (VCU), a virtual distributed unit (VDU), or a virtual radio unit (VRU).

[0051] Base station type operation or network design can consider the aggregation characteristics of base station functionality. For example, decomposed base stations can be used in Integrated Access Backhaul (IAB) networks, Open Radio Access Networks (O-RAN) (such as those developed by the O-RAN Alliance), and other similar networks. ® This can be used in proposed network configurations or virtualized radio access networks (vRAN, also known as cloud radio access networks (C-RAN)). Decomposition can include distributing functionality across two or more units in various physical locations, as well as virtually distributing the functionality of at least one unit, which allows for flexibility in network design. Various units in a decomposed base station or decomposed RAN architecture can be configured to communicate wirelessly with at least one other unit.

[0052] Figure 2C An example disaggregated base station architecture 250 according to various aspects of this disclosure is illustrated. The disaggregated base station architecture 250 may include one or more central units (CUs) 280 (e.g., gNB-CU 226) that can communicate directly with the core network 267 (e.g., 5GC 210, 5GC 260) via a backhaul link, or indirectly with the core network 267 via one or more disaggregated base station units (such as a near real-time (near-RT) RAN Intelligent Controller (RIC) 259 via an E2 link or a non-real-time (non-RT) RIC 257 associated with a Service Management and Orchestration (SMO) framework 255, or both). CUs 280 may communicate with one or more duplex units (DUs) 285 (e.g., gNB-DU 228) via a corresponding midhaul link (such as an F1 interface). DUs 285 may communicate with one or more radio units (RUs) 287 (e.g., gNB-RU 229) via a corresponding fronthaul link. RU 287 can communicate with the corresponding UE 204 via one or more radio frequency (RF) access links. In some implementations, UE 204 can be served by multiple RU 287s simultaneously.

[0053] Each of the units (i.e., CU 280, DU 285, RU 287, and near-RT RIC 259, non-RT RIC 257, and SMO frame 255) may include or be coupled to one or more interfaces configured to receive or transmit signals, data, or information (collectively, signals) via wired or wireless transmission media. Each of the units, or an associated processor or controller providing instructions to the communication interfaces of these units, may be configured to communicate with one or more other units via transmission media. For example, these units may include wired interfaces configured to receive signals or transmit signals to one or more other units via wired transmission media. Additionally, these units may include wireless interfaces that may include receivers, transmitters, or transceivers (such as RF transceivers) configured to receive signals or transmit signals to one or more other units, or both, via wireless transmission media.

[0054] In some aspects, the CU 280 can host one or more higher-level control functions. Such control functions may include RRC, PDCP, Serving Data Adaptation Protocol (SDAP), etc. Each control function can be implemented using an interface configured to communicate signaling with other control functions hosted by the CU 280. The CU 280 can 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 implementations, the CU 280 can 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 units can communicate bidirectionally with the CU-CP units via an interface such as an E1 interface. The CU 280 can be implemented to communicate with the DU 285 for network control and signaling, as needed.

[0055] DU 285 may correspond to a logic unit that includes one or more base station functions for controlling the operation of one or more RU 287s. In some aspects, DU 285 may be at least partially based on functional partitioning (such as that provided by the 3rd Generation Partnership Project (3GPP)). ® The DU285 is functionally partitioned to host one or more of the RLC layer, MAC layer, and one or more high-PHY layers (such as modules for forward error correction (FEC) encoding and decoding, scrambling, modulation, and demodulation). In some respects, the DU285 may further host one or more low-PHY layers. Each layer (or module) may be implemented using an interface configured to communicate signals with other layers (and modules) hosted by the DU285 or with control functions hosted by the CU280.

[0056] Lower-layer functionality can be implemented by one or more RU 287s. In some deployments, an RU287 controlled by a DU 285 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, or Physical Random Access Channel (PRACH) extraction and filtering, or both, based at least in part on functional decomposition (such as lower-layer functional decomposition). In such architectures, the RU 287 may be implemented to handle over-the-air (OTA) communications with one or more UE 204s. In some specific implementations, the real-time and non-real-time aspects of control plane and user plane communications with the RU 287 may be controlled by the corresponding DU 285. In some scenarios, this configuration enables the implementation of the DU 285 and CU 280 in cloud-based RAN architectures such as vRAN architectures.

[0057] SMO framework 255 can be configured to support RAN deployment and provisioning of both non-virtualized and virtualized network elements. For non-virtualized network elements, SMO framework 255 can be configured to support the deployment of dedicated physical resources for RAN coverage requirements, which can be managed via operation and maintenance interfaces such as the O1 interface. For virtualized network elements, SMO framework 255 can be configured to interact with cloud computing platforms such as Open Cloud (O-Cloud) 269 to perform network element lifecycle management (such as instantiating virtualized network elements) via cloud computing platform interfaces such as the O2 interface. Such virtualized network elements may include, but are not limited to, CU 280, DU 285, RU 287, and near-RT RIC 259. In some implementations, SMO framework 255 can communicate with the hardware aspects of the 4G RAN (such as Open eNB (O-eNB) 261) via the O1 interface. Additionally, in some implementations, SMO framework 255 can communicate directly with one or more RU 287s via the O1 interface. SMO framework 255 may also include a non-RT RIC 257 configured to support the functionality of SMO framework 255.

[0058] The non-RT RIC 257 can be configured to include logical functions enabling non-real-time control and optimization of RAN elements and resources, including artificial intelligence / machine learning (AI / ML) workflows for model training and updates, or policy-based guidance for applications / features in the near-RT RIC 259. The non-RT RIC 257 can be coupled to or communicate with the near-RT RIC 259, such as via an A1 interface. The near-RT RIC 259 can be configured to include logical functions enabling near real-time control and optimization of RAN elements and resources via an interface, such as via an E2 interface, through data collection and action, connecting one or more CU 280s, one or more DU 285s, or both, and O-eNBs to the near-RT RIC 259.

[0059] In some implementations, to generate AI / ML models to be deployed in the near-RT RIC 259, the non-RT RIC 257 may receive parameters or external enrichment information from an external server. This information can be utilized by the near-RT RIC 259 and may be received from non-network data sources or network functions at the SMO framework 255 or the non-RT RIC 257. In some examples, the non-RT RIC 257 or the near-RT RIC 259 may be configured to tune RAN behavior or performance. For example, the non-RT RIC 257 may monitor long-term trends and patterns in performance and employ AI / ML models to perform corrective actions via the SMO framework 255 (such as reconfiguration via O1) or by creating RAN management policies (such as A1 policies).

[0060] Figure 3A , Figure 3B and Figure 3C Examples are shown that can be incorporated into UE 302 (which may correspond to any UE described herein), base station 304 (which may correspond to any base station described herein), and network entity 306 (which may correspond to or embody any network function described herein, including location server 230 and LMF 270, or alternatively may be independent of...). Figure 2A and Figure 2BSeveral example components (represented by corresponding boxes) in the NG-RAN 220 and / or 5GC 210 / 260 infrastructure (such as private networks) depicted herein support the operation as described herein. It should be understood that these components may be implemented in different specific implementations in different types of devices (e.g., in ASICs, in System-on-Chip (SoCs), etc.). The illustrated components may also be incorporated into other devices in a communication system. For example, other devices in the system may include components similar to those described as providing similar functionality. Furthermore, a given device may contain one or more of these components. For example, a device may include multiple transceiver components that enable the device to operate on multiple carriers and / or communicate via different technologies.

[0061] UE 302 and base station 304 each include one or more Wireless Wide Area Network (WWAN) transceivers 310 and 350, which provide components (e.g., components for transmitting, components for receiving, components for measuring, components for tuning, components for blocking transmission, etc.) for communicating via one or more wireless communication networks (not shown) (such as NR networks, LTE networks, GSM networks, etc.). WWAN transceivers 310 and 350 may each be connected to one or more antennas 316 and 356 for communicating with other network nodes (such as other UEs, access points, base stations (e.g., eNB, gNB), etc.) via at least one designated RAT (e.g., NR, LTE, GSM, etc.) through a wireless communication medium of interest (e.g., a time / frequency resource set in a specific spectrum). WWAN transceivers 310 and 350 can be configured in different ways to transmit and encode signals 318 and 358 (e.g., messages, indications, information, etc.) according to a specified RAT, and conversely, to receive and decode signals 318 and 358 (e.g., messages, indications, information, pilots, etc.). Specifically, WWAN transceivers 310 and 350 each include: one or more transmitters 314 and 354 for transmitting and encoding signals 318 and 358, respectively, and one or more receivers 312 and 352 for receiving and decoding signals 318 and 358, respectively.

[0062] In at least some cases, UE 302 and base station 304 each also include one or more short-range radio transceivers 320 and 360, respectively. The short-range radio transceivers 320 and 360 can be connected to one or more antennas 326 and 366, respectively, and provide access via a wireless communication medium of interest through at least one designated RAT (e.g., Wi-Fi, LTE Direct, Bluetooth). ® ZIGBEE ® Z-WAVE® The short-range transceivers 320 and 360 can be configured in various ways to communicate with other network nodes (such as other UEs, access points, base stations, etc.) using PC5, Dedicated Short Range Communication (DSRC), Wireless Access for Vehicle Environments (WAVE), Near Field Communication (NFC), Ultra Wideband (UWB), etc.) and other network nodes (such as other UEs, access points, base stations, etc.). These components include (e.g., components for transmitting, components for receiving, components for measuring, components for tuning, components for blocking transmission, etc.). The short-range transceivers 320 and 360 can be configured in different ways to transmit and encode signals 328 and 368 (e.g., messages, indications, information, etc.) according to a specified RAT, and conversely, to receive and decode signals 328 and 368 (e.g., messages, indications, information, pilots, etc.). Specifically, the short-range transceivers 320 and 360 each include: one or more transmitters 324 and 364 for transmitting and encoding signals 328 and 368, respectively; and one or more receivers 322 and 362 for receiving and decoding signals 328 and 368, respectively. As specific examples, the short-range wireless transceivers 320 and 360 can be Wi-Fi transceivers, Bluetooth transceivers, etc. ® Transceiver, Zigbee ® and / or Z-WAVE ® Transceivers, NFC transceivers, UWB transceivers, or vehicle-to-vehicle (V2V) and / or vehicle-to-everything (V2X) transceivers.

[0063] In at least some cases, UE 302 and base station 304 also include satellite signal receivers 330 and 370. Satellite signal receivers 330 and 370 may be connected to one or more antennas 336 and 376, respectively, and may provide components for receiving and / or measuring satellite positioning / communication signals 338 and 378, respectively. Where satellite signal receivers 330 and 370 are satellite positioning system receivers, satellite positioning / communication signals 338 and 378 may be Global Positioning System (GPS) signals, Global Navigation Satellite System (GLONASS) signals, etc. ® The signals received by satellite signal receivers 330 and 370 may include Galileo signals, BeiDou signals, Indian Regional Navigation Satellite System (NAVIC), Quasi-Zenith Satellite System (QZSS), etc. When satellite signal receivers 330 and 370 are non-terrestrial network (NTN) receivers, satellite positioning / communication signals 338 and 378 may be communication signals originating from a 5G network (e.g., carrying control and / or user data). Satellite signal receivers 330 and 370 may include any suitable hardware and / or software for receiving and processing satellite positioning / communication signals 338 and 378, respectively. Satellite signal receivers 330 and 370 may request information and operations from other systems as needed, and in at least some cases, perform calculations using measurements obtained by any suitable satellite positioning system algorithm to determine the locations of UE 302 and base station 304, respectively.

[0064] Base station 304 and network entity 306 each include one or more network transceivers 380 and 390, which provide components (e.g., transmitting components, receiving components, etc.) for communicating with other network entities (e.g., other base stations 304, other network entities 306). For example, base station 304 may use one or more network transceivers 380 to communicate with other base stations 304 or network entities 306 via one or more wired or wireless backhaul links. Similarly, network entity 306 may use one or more network transceivers 390 to communicate with one or more base stations 304 via one or more wired or wireless backhaul links, or to communicate with other network entities 306 via one or more wired or wireless core network interfaces.

[0065] Transceivers can be configured to communicate via wired or wireless links. A transceiver (whether wired or wireless) includes transmitter circuitry (e.g., transmitters 314, 324, 354, 364) and receiver circuitry (e.g., receivers 312, 322, 352, 362). In some embodiments, the transceiver may be an integrated device (e.g., implementing transmitter and receiver circuitry in a single device), in some embodiments it may include separate transmitter and receiver circuitry, or in other embodiments it may be implemented in a different manner. The transmitter and receiver circuitry of a wired transceiver (e.g., network transceivers 380 and 390 in some embodiments) may be coupled to one or more wired network interface ports. Wireless transmitter circuitry (e.g., transmitters 314, 324, 354, 364) may include or be coupled to multiple antennas (e.g., antennas 316, 326, 356, 366), such as an antenna array, which allows the corresponding device (e.g., UE 302, base station 304) to perform transmit beamforming, as described herein. Similarly, wireless receiver circuitry (e.g., receivers 312, 322, 352, 362) may include or be coupled to multiple antennas (e.g., antennas 316, 326, 356, 366), such as an antenna array, which allows the corresponding device (e.g., UE 302, base station 304) to perform receive beamforming, as described herein. In one aspect, the transmitter and receiver circuitry may share the same multiple antennas (e.g., antennas 316, 326, 356, 366), such that the corresponding device may perform only receive or only transmit at a given time, rather than both receive and transmit simultaneously. Wireless transceivers (e.g., WWAN transceivers 310 and 350, short-range wireless transceivers 320 and 360) may also include network listening modules (NLMs) for performing various measurements.

[0066] As used herein, various wireless transceivers (e.g., transceivers 310, 320, 350, and 360 in some specific embodiments, and network transceivers 380 and 390) and wired transceivers (e.g., network transceivers 380 and 390 in some specific embodiments) are generally referred to as "transceiver," "at least one transceiver," or "one or more transceivers." Therefore, whether a particular transceiver is a wired or wireless transceiver can be inferred from the type of communication performed. For example, backhaul communication between network devices or servers typically involves signaling via a wired transceiver, while wireless communication between a UE (e.g., UE 302) and a base station (e.g., base station 304) will typically involve signaling via a wireless transceiver.

[0067] UE 302, base station 304, and network entity 306 also include other components that can be used in conjunction with the operations disclosed herein. UE 302, base station 304, and network entity 306 each include one or more processors 332, 384, and 394 for providing functionality related to, for example, wireless communication, and for providing other processing functionality. Thus, processors 332, 384, and 394 may provide components for processing, such as components for determining, components for calculating, components for receiving, components for transmitting, components for indicating, etc. In one aspect, processors 332, 384, and 394 may include, for example, one or more general-purpose processors, multi-core processors, central processing units (CPUs), ASICs, digital signal processors (DSPs), field-programmable gate arrays (FPGAs), other programmable logic devices or processing circuits, or various combinations thereof.

[0068] UE 302, base station 304, and network entity 306 each include memory circuitry implementing memories 340, 386, and 396 (e.g., each including a memory device) for maintaining information (e.g., information indicating reserved resources, thresholds, parameters, etc.). Therefore, memories 340, 386, and 396 can provide components for storage, retrieval, maintenance, etc. In some cases, UE 302, base station 304, and network entity 306 may each include SL Rx-Tx components 342, 388, and 398. SL Rx-Tx components 342, 388, and 398 may be hardware circuitry that is part of or coupled to processors 332, 384, and 394, respectively, which, when executed, enables UE 302, base station 304, and network entity 306 to perform the functionality described herein. In other respects, SL Rx-Tx components 342, 388, and 398 may be external to processors 332, 384, and 394 (e.g., may be part of a modem processing system, may be integrated with another processing system, etc.). Alternatively, SL Rx-Tx components 342, 388, and 398 may be memory modules stored in memories 340, 386, and 396, respectively, which, when executed by processors 332, 384, and 394 (or modem processing system, another processing system, etc.), enable UE 302, base station 304, and network entity 306 to perform the functionality described herein. Figure 3A Possible locations of the SL Rx-Tx component 342 are illustrated. The SL Rx-Tx component may be part of, for example, one or more WWAN transceivers 310, memory 340, one or more processors 332, or any combination thereof, or may be a standalone component. Figure 3B Possible locations of the SL Rx-Tx component 388 are illustrated. The SL Rx-Tx component may be part of, for example, one or more WWAN transceivers 350, memory 386, one or more processors 384, or any combination thereof, or may be a standalone component. Figure 3C Possible locations of the SL Rx-Tx component 398 are illustrated. The SL Rx-Tx component may be part of, for example, one or more network transceivers 390, memory 396, one or more processors 394, or any combination thereof, or may be a standalone component.

[0069] UE 302 may include one or more sensors 344 coupled to one or more processors 332 to provide components for sensing or detecting motion and / or orientation information independent of motion data derived from signals received by one or more WWAN transceivers 310, one or more short-range wireless transceivers 320, and / or satellite signal receivers 330. By way of example, sensor 344 may include accelerometers (e.g., microelectromechanical systems (MEMS) devices), gyroscopes, geomagnetic sensors (e.g., compasses), altimeters (e.g., barometric altimeters), and / or any other type of motion detection sensor. Furthermore, sensor 344 may include multiple different types of devices and combine their outputs to provide motion information. For example, sensor 344 may use a combination of multi-axis accelerometers and orientation sensors to provide the ability to calculate positioning in two-dimensional (2D) and / or three-dimensional (3D) coordinate systems.

[0070] In addition, UE 302 includes a user interface 346 that provides components for providing instructions to a user (e.g., audible and / or visual instructions) and / or for receiving user input (e.g., when the user actuates a sensing device such as a keypad, touchscreen, microphone, etc.). Although not shown, base station 304 and network entity 306 may also include user interfaces.

[0071] Referring more specifically to one or more processors 384, in the downlink, IP packets from network entity 306 can be provided to processor 384. One or more processors 384 can implement functionality for the RRC layer, Packet Data Convergence Protocol (PDCP) layer, Radio Link Control (RLC) layer, and Media Access Control (MAC) layer. One or more processors 384 may provide: RRC layer functionality associated with broadcasting system information (e.g., Master Information Block (MIB), System Information Block (SIB)), RRC connection control (e.g., RRC connection paging, RRC connection establishment, RRC connection modification, and RRC connection release), inter-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 the delivery of upper-layer PDUs, error correction via Automatic Repeat Request (ARQ), concatenation, segmentation, and reassembly of RLC Service Data Units (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, scheduling information reporting, error correction, priority handling, and logical channel priority ordering.

[0072] Transmitter 354 and receiver 352 implement Layer 1 (L1) functionality associated with various signal processing functions. Layer 1, including the physical (PHY) layer, may include: error detection on the transport channel, forward error correction (FEC) decoding / decoding of the transport channel, interleaving, rate matching, mapping to the physical channel, modulation / demodulation of the physical channel, and MIMO antenna processing. Transmitter 354 processes 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-QAM). The decoded and modulated symbols can then be divided into parallel streams. Each stream can then be mapped to Orthogonal Frequency Division Multiplexing (OFDM) subcarriers, multiplexed with a reference signal (e.g., pilot) in the time and / or frequency domains, and then combined using an Inverse Fast Fourier Transform (IFFT) to produce a physical channel carrying a stream of time-domain OFDM symbols. The OFDM symbol stream is spatially pre-decoded to generate multiple spatial streams. Channel estimates from a channel estimator can be used to determine the decoding and modulation schemes, as well as for spatial processing. These channel estimates can be derived from a reference signal transmitted by UE 302 and / or channel condition feedback. Each spatial stream can then be provided to one or more different antennas 356. Transmitter 354 can utilize the corresponding spatial stream to modulate an RF carrier for transmission.

[0073] At UE 302, receiver 312 receives signals via its corresponding antenna 316. Receiver 312 recovers the information modulated onto the RF carrier and provides this information to one or more processors 332. Transmitter 314 and receiver 312 implement Layer 1 functionality associated with various signal processing functions. Receiver 312 can perform spatial processing on the information to recover any spatial stream destined for UE 302. If multiple spatial streams are destined for UE 302, they can be combined by receiver 312 into a single OFDM symbol stream. Receiver 312 then uses a Fast Fourier Transform (FFT) to transform the OFDM symbol stream from the time domain to the frequency domain. The frequency domain signal includes a separate OFDM symbol stream for each subcarrier of the OFDM signal. The symbols on each subcarrier, along with the reference signal, are recovered and demodulated by determining the most probable signal constellation points transmitted by base station 304. These soft decisions can be based on channel estimates calculated by a channel estimator. The soft decisions are then decoded and deinterleaved to recover the data and control signals originally transmitted by base station 304 on the physical channel. Then, data and control signals are provided to one or more processors 332, which implement layer 3 (L3) and layer 2 (L2) functionality.

[0074] In the downlink, one or more processors 332 provide demultiplexing, packet reassembly, decryption, header decompression, and control signal processing between the transport and logical channels to recover IP packets from the core network. One or more processors 332 are also responsible for error detection.

[0075] Similar to the functionality described in conjunction with downlink transmissions performed by base station 304, one or more processors 332 provide: RRC layer functionality associated with system information (e.g., MIB, SIB) acquisition, RRC connectivity, and measurement reporting; PDCP layer functionality associated with header compression / decompression and security (encryption, decryption, integrity protection, integrity verification); RLC layer functionality associated with the delivery of upper-layer PDUs, error correction via 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 transport blocks (TBs), demultiplexing of MAC SDUs from TBs, scheduling information reporting, error correction via Hybrid Automatic Repeat Request (HARQ), priority handling, and logical channel priority ordering.

[0076] The channel estimate derived by the channel estimator from the reference signal or feedback transmitted by the base station 304 can be used by the transmitter 314 to select an appropriate decoding and modulation scheme and facilitates spatial processing. The spatial stream generated by the transmitter 314 can be provided to different antennas 316. The transmitter 314 can use the corresponding spatial stream to modulate the RF carrier for transmission.

[0077] Uplink transmissions are processed at base station 304 in a manner similar to that described in conjunction with the receiver function at UE 302. Receiver 352 receives signals via its corresponding antenna 356. Receiver 352 recovers the information modulated onto the RF carrier and provides this information to one or more processors 384.

[0078] In the uplink, one or more processors 384 provide demultiplexing, packet reassembly, decryption, header decompression, and control signal processing between the transport channel and the logical channel to recover IP packets from UE 302. IP packets from one or more processors 384 can be provided to the core network. One or more processors 384 are also responsible for error detection.

[0079] For convenience, UE 302, base station 304 and / or network entity 306 are in Figure 3A , Figure 3B and Figure 3CThe document is shown as including various components that can be configured according to the various examples described herein. However, it should be understood that the illustrated components may have different functionalities in different designs. In particular, Figures 3A to 3C Various components are optional in alternative configurations, and various aspects include configurations that can vary due to design choices, cost, equipment usage, or other considerations. For example, in Figure 3A In certain cases, specific implementations of UE 302 may omit WWAN transceiver 310 (e.g., wearable devices, tablets, personal computers (PCs), or laptops may have Wi-Fi and / or Bluetooth). ® (e.g., cellular only), or the short-range wireless transceiver 320 can be omitted (e.g., cellular only), or the satellite signal receiver 330 can be omitted, or the sensor 344 can be omitted, etc. For example, in Figure 3B In certain cases, specific implementations of base station 304 may omit WWAN transceiver 350 (e.g., a Wi-Fi "hotspot" access point without cellular capabilities), or short-range wireless transceiver 360 (e.g., cellular only), or satellite signal receiver 370, etc. For the sake of brevity, examples of various alternative configurations are not provided herein, but will be readily understood by those skilled in the art.

[0080] Various components of UE 302, base station 304, and network entity 306 can be communicatively coupled to each other via data buses 334, 382, ​​and 392, respectively. In one aspect, data buses 334, 382, ​​and 392 can form or be part of the communication interfaces of UE 302, base station 304, and network entity 306, respectively. For example, in cases where different logical entities are embodied in the same device (e.g., gNB and location server functionality integrated into the same base station 304), data buses 334, 382, ​​and 392 can provide communication between these different logical entities.

[0081] Figure 3A , Figure 3B and Figure 3C The components can be implemented in various ways. In some specific implementations, Figure 3A , Figure 3B and Figure 3CThe components can be implemented in one or more circuits, such as, for example, one or more processors and / or one or more ASICs (which may include one or more processors). Here, each circuit may use and / or incorporate at least one memory component for storing information or executable code used by the circuit to provide that functionality. For example, some or all of the functionalities represented by blocks 310 to 346 may be implemented by the processor and memory components of UE 302 (e.g., by executing appropriate code and / or by appropriate configuration of the processor components). Similarly, some or all of the functionalities represented by blocks 350 to 388 may be implemented by the processor and memory components of base station 304 (e.g., by executing appropriate code and / or by appropriate configuration of the processor components). Furthermore, some or all of the functionalities represented by blocks 390 to 398 may be implemented by the processor and memory components of network entity 306 (e.g., by executing appropriate code and / or by appropriate configuration of the processor components). For simplicity, various operations, actions, and / or functions are described herein as being performed "by the UE," "by the base station," "by the network entity," etc. However, it should be understood that such operations, actions and / or functions can actually be performed by specific components or combinations of components of the UE 302, base station 304, network entity 306, etc. (such as processors 332, 384, 394, transceivers 310, 320, 350 and 360, memory 340, 386 and 396, SL Rx-Tx components 342, 388 and 398, etc.).

[0082] In some designs, network entity 306 may be implemented as a core network component. In other designs, network entity 306 may operate differently from the network operator or cellular network infrastructure (e.g., NG RAN 220 and / or 5GC 210 / 260). For example, network entity 306 may be a component of a private network that can be configured to communicate with UE 302 via base station 304 or independently of base station 304 (e.g., via a non-cellular communication link, such as Wi-Fi).

[0083] Various frame structures can be used to support downlink and uplink transmission between network nodes (e.g., base stations and UEs). Figure 4 Figure 400 illustrates an example frame structure according to various aspects of this disclosure. The frame structure may be a downlink or uplink frame structure. Other wireless communication technologies may have different frame structures and / or different channels.

[0084] LTE (and in some cases NR) uses Orthogonal Frequency Division Multiplexing (OFDM) on the downlink and Single-Carrier Frequency Division Multiplexing (SC-FDM) on the uplink. However, unlike LTE, NR also has the option to use OFDM on the uplink. OFDM and SC-FDM divide the system bandwidth into multiple (K) orthogonal subcarriers, which are often referred to as tones, frequency slots, etc. Each subcarrier can be modulated using data. Generally, modulation symbols are transmitted using OFDM in the frequency domain and SC-FDM in the time domain. The spacing between adjacent subcarriers can be fixed, and the total number of subcarriers (K) can depend on the system bandwidth. For example, the subcarrier spacing can be 15 kHz, and the minimum resource allocation (resource block) can be 12 subcarriers (or 180 kHz). Therefore, for system bandwidths of 1.25 MHz, 2.5 MHz, 5 MHz, 10 MHz, or 20 MHz, the nominal Fast Fourier Transform (FFT) size can be equal to 128, 256, 512, 1024, or 2048, respectively. The system bandwidth can also be divided into subbands. For example, a subband can cover 1.08 MHz (i.e., 6 resource blocks), and for system bandwidths of 1.25 MHz, 2.5 MHz, 5 MHz, 10 MHz, or 20 MHz, there can be 1, 2, 4, 8, or 16 subbands, respectively.

[0085] LTE supports a single set of parameters (subcarrier spacing (SCS), symbol length, etc.). In contrast, NR can support multiple sets of parameters (µ), for example, subcarrier spacings of 15kHz (µ=0), 30kHz (µ=1), 60kHz (µ=2), 120kHz (µ=3), and 240kHz (µ=4) or larger can be available. Within each subcarrier spacing, there are 14 symbols per time slot. For a 15kHz SCS (µ=0), there is one time slot per subframe, 10 time slots per frame, a time slot duration of 1 millisecond (ms), a symbol duration of 66.7 microseconds (µs), and a maximum nominal system bandwidth (in MHz) of 4K FFT size. For a 30kHz SCS (µ=1), there are two time slots per subframe, 20 time slots per frame, a time slot duration of 0.5ms, a symbol duration of 33.3µs, and a maximum nominal system bandwidth (in MHz) of 4K FFT size. For a 60kHz SCS (µ=2), there are four time slots per subframe, 40 time slots per frame, a time slot duration of 0.25ms, a symbol duration of 16.7µs, and a maximum nominal system bandwidth (in MHz) of 4K FFT size. For a 120kHz SCS (µ=3), there are eight time slots per subframe, 80 time slots per frame, a time slot duration of 0.125ms, a symbol duration of 8.33µs, and a maximum nominal system bandwidth (in MHz) of 4K FFT size. For a 240kHz SCS (µ=4), there are 16 time slots per subframe, 160 time slots per frame, a time slot duration of 0.0625ms, a symbol duration of 4.17µs, and a maximum nominal system bandwidth (in MHz) of 4K FFT size.

[0086] exist Figure 4 In the example, a parameter set of 15kHz is used. Therefore, in the time domain, a 10ms frame is divided into 10 equal-sized subframes, each 1ms long, and each subframe includes one time slot. Figure 4 In the diagram, time is represented horizontally (on the X-axis), with time increasing from left to right, while frequency is represented vertically (on the Y-axis), with frequency increasing (or decreasing) from bottom to top.

[0087] A resource grid can be used to represent time slots, each time slot comprising one or more concurrent resource blocks (RBs) (also known as physical RBs (PRBs)) in the frequency domain. The resource grid is further divided into multiple resource elements (REs). An RE can correspond to a symbol length in the time domain and a subcarrier in the frequency domain. Figure 4In the parameter set, for a normal cyclic prefix, the RB can contain 12 consecutive subcarriers in the frequency domain and seven consecutive symbols in the time domain, for a total of 84 REs. For an extended cyclic prefix, the RB can contain 12 consecutive subcarriers in the frequency domain and six consecutive symbols in the time domain, for a total of 72 REs. The number of bits carried by each RE depends on the modulation scheme.

[0088] Some REs may carry reference (pilot) signals (RS). These reference signals may include positioning reference signals (PRS), tracking reference signals (TRS), phase tracking reference signals (PTRS), cell-specific reference signals (CRS), channel state information reference signals (CSI-RS), demodulation reference signals (DMRS), primary synchronization signals (PSS), secondary synchronization signals (SSS), synchronization signal blocks (SSB), sounding reference signals (SRS), etc., depending on whether the illustrated frame structure is used for uplink or downlink communication. Figure 4 An example location of a RE (labeled "R") carrying a reference signal is shown.

[0089] Figure 5 This is Figure 500, illustrating various downlink channels within an example downlink time slot. Figure 5 In this diagram, time is represented horizontally (on the X-axis), increasing from left to right, while frequency is represented vertically (on the Y-axis), increasing (or decreasing) from bottom to top. Figure 5 In the example, a parameter set of 15 kHz is used. Therefore, in the time domain, the illustrated time slot length is one millisecond (ms), divided into 14 symbols.

[0090] In NR, the channel bandwidth or system bandwidth is divided into multiple bandwidth portions (BWPs). A BWP is a set of adjacent RBs selected from a subset of common RBs for a given set of parameters on a given carrier. Generally, a maximum of four BWPs can be specified in both the downlink and uplink. That is, a UE can be configured to have up to four BWPs in the downlink and up to four BWPs in the uplink. Only one BWP (uplink or downlink) can be active at a given time, meaning the UE can only receive or transmit on one BWP at a time. On the downlink, the bandwidth of each BWP should be equal to or greater than the bandwidth of the SSB, but it may or may not contain an SSB.

[0091] refer to Figure 5The Primary Synchronization Signal (PSS) is used by the UE to determine subframe / symbol timing and physical layer identity. The Secondary Synchronization Signal (SSS) is used by the UE to determine the physical layer cell identity group number and radio frame timing. Based on the physical layer identity and physical layer cell identity group number, the UE can determine the PCI. Based on the PCI, the UE can determine the location of the aforementioned DL-RS. The Physical Broadcast Channel (PBCH) carrying the Master Information Block (MIB) can be logically grouped with the PSS and SSS to form an SSB (also known as SS / PBCH). The MIB provides the number of RBs in the downlink system bandwidth and the System Frame Number (SFN). The Physical Downlink Shared Channel (PDSCH) carries user data, broadcast system information not transmitted via the PBCH (such as System Information Block (SIB)), and paging messages.

[0092] The Physical Downlink Control Channel (PDCCH) carries Downlink Control Information (DCI) within one or more Control Channel Elements (CCEs). Each CCE includes one or more RE Group (REG) bundles (which can span multiple symbols in the time domain). Each REG bundle includes one or more REGs, and each REG corresponds to 12 resource elements (one resource block) in the frequency domain and one OFDM symbol in the time domain. The physical resource set used to carry the PDCCH / DCI is called the Control Resource Set (CORESET) in NR. In NR, the PDCCH is confined to a single CORESET and transmitted along with its own DMRS. This enables UE-specific beamforming for the PDCCH.

[0093] exist Figure 5 In the example, each BWP has one CORESET, and this CORESET spans three symbols in the time domain (although it can be only one or two symbols). Unlike the LTE control channel, which occupies the entire system bandwidth, in NR, the PDCCH channel is localized to a specific region (i.e., CORESET) in the frequency domain. Therefore, Figure 5 The frequency components of the PDCCH shown are illustrated as fewer than a single BWP in the frequency domain. Note that although the illustrated CORESETs are contiguous in the frequency domain, they do not need to be contiguous. Furthermore, a CORESET can span fewer than three symbols in the time domain.

[0094] The DCI within the PDCCH carries information about uplink resource allocation (persistent and non-persistent) and a description of the downlink data sent to the UE (referred to as uplink grant and downlink grant, respectively). More specifically, the DCI indicates the resources scheduled for downlink data channels (e.g., PDSCH) and uplink data channels (e.g., Physical Uplink Shared Channel (PUSCH)). Multiple (e.g., up to eight) DCIs can be configured in the PDCCH, and these DCIs can have one of several formats. For example, different DCI formats exist for uplink scheduling, downlink scheduling, uplink transmit power control (TPC), etc. The PDCCH can be transmitted by 1, 2, 4, 8, or 16 CCEs to accommodate different DCI payload sizes or decoding rates.

[0095] The set of resource elements (REs) used for PRS transmission is called a "PRS resource". The set of resource elements can span multiple PRBs in the frequency domain and span "N" (such as one or more) consecutive symbols within a time slot in the time domain. In a given OFDM symbol in the time domain, the PRS resource occupies a consecutive PRB in the frequency domain.

[0096] The transmission of PRS resources within a given PRB has a specific comb tooth size (also known as "comb tooth density"). The comb tooth size "N" represents the subcarrier spacing (or frequency / tone spacing) within each symbol of the PRS resource configuration. Specifically, for a comb tooth size "N", the PRS is transmitted in every Nth subcarrier of a symbol within the PRB. For example, for comb tooth-4, for each symbol of the PRS resource configuration, the RE corresponding to every fourth subcarrier (such as subcarriers 0, 4, 8) is used to transmit the PRS resource. Currently, for DL-PRS, comb tooth sizes of comb tooth-2, comb tooth-4, comb tooth-6, and comb tooth-12 are supported. Figure 6 An example PRS resource configuration for comb-4 (which spans four symbols) is shown. That is, the location of the shaded RE (marked as "R") indicates the comb-4 PRS resource configuration.

[0097] Currently, DL-PRS resources can span 2, 4, 6, or 12 consecutive symbols within a time slot using a full-frequency-domain interleaved mode. DL-PRS resources can be configured in any downlink or flexible (FL) symbol configured by a higher layer within a time slot. For all REs of a given DL-PRS resource, there may be a constant energy per resource element (EPRE). The following are the per-symbol frequency offsets for comb sizes 2, 4, 6, and 12 on 2, 4, 6, and 12 symbols. 2-symbol comb-2: {0, 1}; 4-symbol comb-2: {0, 1, 0, 1}; 6-symbol comb-2: {0, 1, 0, 1, 0, 1}; 12-symbol comb-2: {0, 1, 0, 1, 0, 1, 0, 1, 0, 1, 0, 1}; 4-symbol comb-4: {0, 2, 1, 3} (as in...). Figure 6 (In the examples); 12-symbol comb-4: {0,2, 1, 3, 0, 2, 1, 3, 0, 2, 1, 3}; 6-symbol comb-6: {0, 3, 1, 4, 2, 5}; 12-symbol comb-6: {0, 3, 1, 4, 2, 5, 0, 3, 1, 4, 2, 5}; and 12-symbol comb-12: {0, 6, 3, 9, 1, 7, 4, 10, 2, 8, 5, 11}.

[0098] A “PRS resource set” is a collection of PRS resources used to transmit PRS signals, where each PRS resource has a PRS resource ID. Furthermore, PRS resources in a PRS resource set are associated with the same TRP. A PRS resource set is identified by a PRS resource set ID and associated with a specific TRP (identified by a TRP ID). Additionally, PRS resources in a PRS resource set share the same periodicity, common silent mode configuration, and the same repetition factor (such as “PRS-ResourceRepetitionFactor”) across time slots. Periodicity is the time from the first repetition of the first PRS resource in the first PRS instance to the same first repetition of the same first PRS resource in the next PRS instance. The periodicity can have a length chosen from the following: 2^µ*{4, 5, 8, 10, 16, 20, 32, 40, 64, 80, 160, 320, 640, 1280, 2560, 5120, 10240} time slots, where µ = 0, 1, 2, 3. The repetition factor can have a length chosen from {1, 2, 4, 6, 8, 16, 32} time slots.

[0099] In a PRS resource set, a PRS resource ID is associated with a single beam (or beam ID) transmitted from a single TRP (where one TRP can transmit one or more beams). That is, each PRS resource in a PRS resource set can be transmitted on a different beam, and therefore, a "PRS resource" (or simply "resource") can also be referred to as a "beam." It should be noted that this does not imply whether the UE knows the TRP and beam on which it transmits the PRS.

[0100] A “PRS instance” or “PRS timing” is an instance of a periodically repeating time window (such as a group of one or more consecutive time slots) in which a PRS is expected to be sent. A PRS timing may also be referred to as a “PRS positioning timing,” “PRS positioning instance,” “positioning timing,” “positioning instance,” “positioning repetition,” or simply “timing,” “instance,” or “repetition.”

[0101] A “positioning frequency layer” (also simply “frequency layer”) is a collection of one or more PRS resource sets with identical values ​​for certain parameters across one or more TRPs. Specifically, the collection of PRS resource sets has the same subcarrier spacing and cyclic prefix (CP) type (meaning that all parameter sets supported for the Physical Downlink Shared Channel (PDSCH) are also supported by the PRS), the same point A, the same downlink PRS bandwidth, the same starting PRB (and center frequency), and the same comb size. The point A parameter takes the value of the parameter “ARFCN-ValueNR” (where “ARFCN” stands for “Absolute Radio Channel Number”) and is an identifier / code specifying a pair of physical radio channels used for transmission and reception. The downlink PRS bandwidth can have a granularity of four PRBs, with a minimum of 24 PRBs and a maximum of 272 PRBs. Currently, up to four frequency layers have been defined, and up to two PRS resource sets can be configured per frequency layer per TRP.

[0102] The concept of a frequency layer is somewhat similar to that of component carriers and bandwidth portions (BWPs), but the difference is that component carriers and BWPs are used by a single base station (or macrocell base station and small cell base station) to transmit data channels, while a frequency layer is used by several (usually three or more) base stations to transmit PRS. A UE can indicate the number of frequency layers it can support when transmitting its positioning capabilities to the network (such as during an LTE Positioning Protocol (LPP) session). For example, a UE can indicate whether it can support one or four positioning frequency layers.

[0103] It should be noted that the terms "location reference signal" and "PRS" generally refer to specific reference signals used for positioning in NR and LTE systems. However, as used herein, the terms "location reference signal" and "PRS" can also refer to any type of reference signal that can be used for positioning, such as, but not limited to, PRS, TRS, PTRS, CRS, CSI-RS, DMRS, PSS, SSS, SSB, SRS, UL-PRS, etc., as defined in LTE and NR. Furthermore, the terms "location reference signal" and "PRS" can refer to downlink positioning reference signals, uplink positioning reference signals, or sidelink positioning reference signals, unless otherwise indicated by the context. If further distinction is needed regarding the type of PRS, downlink positioning reference signals can be referred to as "DL-PRS," uplink positioning reference signals (e.g., SRS used for positioning, i.e., PTRS) as "UL-PRS," and sidelink positioning reference signals as "SL-PRS." Furthermore, for signals that can be transmitted in the downlink, uplink, and / or sidelink (e.g., DMRS), these signals may be preceded by "DL", "UL", or "SL" to distinguish the direction. For example, "UL-DMRS" may be different from "DL-DMRS".

[0104] Figure 6 This is a diagram 600 illustrating various uplink channels within an example uplink timeslot. In Figure 6 In this diagram, time is represented horizontally (on the X-axis), increasing from left to right, while frequency is represented vertically (on the Y-axis), increasing (or decreasing) from bottom to top. Figure 6 In the example, a parameter set of 15 kHz is used. Therefore, in the time domain, the illustrated time slot length is one millisecond (ms), divided into 14 symbols.

[0105] The Random Access Channel (RACH) (also known as the Physical Random Access Channel (PRACH)) can be configured based on the PRACH to operate within one or more time slots within a frame. A PRACH may include six consecutive RB pairs within a time slot. The PRACH allows the UE to perform initial system access and achieve uplink synchronization. The Physical Uplink Control Channel (PUCCH) may be located at the edge of the uplink system bandwidth. The PUCCH carries uplink control information (UCI), such as scheduling requests, CSI reports, channel quality indicators (CQI), pre-decoding matrix indicators (PMI), rank indicators (RI), and HARQ ACK / NACK feedback. The Physical Uplink Shared Channel (PUSCH) carries data and may additionally be used to carry buffer status reports (BSR), power clearance reports (PHR), and / or UCI.

[0106] On the one hand, Figure 4The reference signal carried on the RE marked "R" can be the SRS. The SRS transmitted by the UE can be used by the base station to obtain the Channel State Information (CSI) used to transmit the UE. The CSI describes how the RF signal propagates from the UE to the base station and represents the combined effects of scattering, attenuation, and power decay with distance. The system uses the SRS for resource scheduling, link adaptation, massive MIMO, beam management, etc.

[0107] The set of REs used for SRS transmission is called an "SRS resource" and is identified by the parameter "SRS-ResourceId". The set of resource elements can span multiple PRBs in the frequency domain and span "N" (e.g., one or more) consecutive symbols within a time slot in the time domain. In a given OFDM symbol, SRS resources occupy one or more consecutive PRBs. An "SRS resource set" is a group of SRS resources used for SRS signal transmission and is identified by the SRS resource set ID ("SRS-ResourceSetId").

[0108] The transmission of SRS resources within a given PRB has a specific comb size (also known as "comb density"). The comb size "N" represents the subcarrier spacing (or frequency / tone spacing) within each symbol of the SRS resource configuration. Specifically, for a comb size "N", SRS is transmitted in every Nth subcarrier of a symbol within the PRB. For example, for comb size -4, for each symbol of the SRS resource configuration, the RE corresponding to every fourth subcarrier (such as subcarriers 0, 4, 8) is used to transmit the SRS of the SRS resource. Figure 4 In the example, the illustrated SRS is comb tooth-4 spanning four symbols. That is, the position of the shaded SRS RE indicates the SRS resource configuration of comb tooth-4.

[0109] Currently, SRS resources with comb tooth sizes of 2, 4, or 8 can span 1, 2, 4, 8, or 12 consecutive symbols within a time slot. The following are the symbol-by-symbol frequency offsets for the currently supported SRS comb tooth patterns: 1-symbol comb tooth-2: {0}; 2-symbol comb tooth-2: {0, 1}; 2-symbol comb tooth-4: {0, 2}; 4-symbol comb tooth-2: {0, 1, 0, 1}; 4-symbol comb tooth-4: {0, 2, 1, 3} (as in...). Figure 4(In the examples); 8-symbol comb-4: {0, 2, 1, 3, 0, 2, 1, 3}; 12-symbol comb-4: {0, 2, 1, 3, 0, 2, 1, 3, 0, 2, 1, 3}; 4-symbol comb-8: {0, 4, 2, 6}; 8-symbol comb-8: {0, 4, 2, 6, 1, 5, 3, 7}; and 12-symbol comb-8: {0, 4, 2, 6, 1, 5, 3, 7, 0, 4, 2, 6}.

[0110] Generally, as mentioned above, the UE transmits an SRS so that the receiving base station (serving base station or neighboring base station) can measure the channel quality (i.e., CSI) between the UE and the base station. However, the SRS can also be specifically configured as an uplink positioning reference signal for uplink-based positioning procedures, such as uplink time difference of arrival (UL-TDOA), round-trip time (RTT), uplink angle of arrival (UL-AoA), etc. As used herein, the term "SRS" can refer to an SRS configured for channel quality measurement or an SRS configured for positioning purposes. When it is necessary to distinguish between the two types of SRS, the former may be referred to herein as "SRS for communication" and / or the latter as "SRS for positioning" or "positioning SRS".

[0111] Several enhancements to the previously defined SRS have been proposed for “Location-Specific SRS” (also known as “UL-PRS”), such as new interleaving patterns within SRS resources (other than single symbol / comb-2), new comb types for SRS, new sequences of SRS, a larger set of SRS resources per component carrier, and a larger number of SRS resources per component carrier. Furthermore, the parameters “SpatialRelationInfo” and “PathLossReference” are configured based on the downlink reference signal or SSB from the adjacent TRP. Further, an SRS resource can be transmitted outside the active BWP, and an SRS resource can span multiple component carriers. Moreover, SRS can be configured in RRC connected state and transmitted only within the active BWP. Additionally, there may be no frequency hopping, no repetition factor, a single antenna port, and new SRS lengths (e.g., 8 and 12 symbols). Open-loop power control may also exist, but closed-loop power control is not possible, and comb-8 (i.e., SRS transmitted every eighth subcarrier in the same symbol) can be used. Finally, the UE can transmit from multiple SRS resources using the same transmit beam for UL-AoA. All of these are features outside the current SRS framework, which is configured via higher-level RRC signaling (and potentially triggered or activated via MAC control elements (MAC-CE) or downlink control information (DCI)).

[0112] NR supports various cellular network-based positioning technologies, including downlink-based positioning methods, uplink-based positioning methods, and positioning methods based on both downlink and uplink. Downlink-based positioning methods include Observed Time Difference of Arrival (OTDOA) in LTE, Downlink Time Difference of Arrival (DL-TDOA) in NR, and Downlink Angle of Departure (DL-AoD) in NR. Figure 7 Examples of various positioning methods according to aspects of this disclosure are illustrated. In the OTDOA or DL-TDOA positioning process illustrated in scenario 710, the UE measures the difference between the times of arrival (ToA) of reference signals (e.g., positioning reference signals (PRS)) received from paired base stations (referred to as reference signal time difference (RSTD) or time difference of arrival (TDOA) measurement) and reports these differences to the positioning entity. More specifically, the UE receives identifiers (IDs) of a reference base station (e.g., a serving base station) and multiple non-reference base stations in auxiliary data. The UE then measures the RSTD between the reference base station and each non-reference base station. Based on the known locations of the base stations involved and the RSTD measurement, the positioning entity (e.g., a UE for UE-based positioning or a location server for UE-assisted positioning) can estimate the UE's location.

[0113] For the DL-AoD positioning illustrated in scenario 720, the positioning entity uses measurement reports from the UE regarding the received signal strength of multiple downlink transmitted beams to determine the angle between the UE and the transmitting base station. The positioning entity can then estimate the UE's position based on the determined angle and the known location of the transmitting base station.

[0114] Uplink-based positioning methods include uplink time difference of arrival (UL-TDOA) and uplink angle of arrival (UL-AoA). UL-TDOA is similar to DL-TDOA, but is based on uplink reference signals (e.g., sounding reference signals (SRS)) transmitted by the UE to multiple base stations. Specifically, the UE transmits one or more uplink reference signals, which are measured by a reference base station and multiple non-reference base stations. Each base station then reports the reception time of the reference signal (referred to as relative time of arrival (RTOA)) to a positioning entity (e.g., a location server) that knows the location and relative timing of the base stations involved. Based on the received-receive (Rx-Rx) time difference between the reported RTOA of the reference base station and the reported RTOA of each non-reference base station, the known location of the base stations, and their known timing offsets, the positioning entity can use the TDOA to estimate the UE's location.

[0115] For UL-AoA positioning, one or more base stations measure the received signal strength of one or more uplink reference signals (e.g., SRS) received from the UE on one or more uplink receive beams. The positioning entity uses the signal strength measurement and the angle of the receive beam to determine the angle between the UE and the base station. Based on the determined angle and the known location of the base station, the positioning entity can then estimate the location of the UE.

[0116] Downlink and uplink-based positioning methods include Enhanced Cell ID (E-CID) positioning and Multiple Round-Trip Time (RTT) positioning (also known as "Multi-Cell RTT" and "Multi-RTT"). During RTT, a first entity (e.g., a base station or a UE) sends a first RTT-related signal (e.g., PRS or SRS) to a second entity (e.g., a UE or a base station), which then sends a second RTT-related signal (e.g., SRS or PRS) back to the first entity. Each entity measures the time difference between the time of arrival (ToA) of the received RTT-related signal and the time of transmission of the transmitted RTT-related signal. This time difference is called the receive-to-transmit (Rx-Tx) time difference. The Rx-Tx time difference measurement can be performed or adjusted to include only the time difference between the nearest time slot boundary of the received signal and the transmitted signal. The two entities can then transmit their Rx-Tx time difference measurements to a location server (e.g., LMF 270), which calculates the round-trip time (RTT) between the two entities based on these two Rx-Tx time difference measurements (e.g., calculated as the sum of the two Rx-Tx time difference measurements). Alternatively, one entity can transmit its Rx-Tx time difference measurement to another entity, which then calculates the RTT. The distance between the two entities can be determined based on the RTT and a known signal speed (e.g., the speed of light). For the multi-RTT positioning illustrated in scenario 730, a first entity (e.g., a UE or base station) performs an RTT positioning process with multiple second entities (e.g., multiple base stations or UEs) to enable the location of the first entity to be determined based on the distance to the second entities and the known location of the second entities (e.g., using polygonal measurements). RTT and multi-RTT methods can be combined with other positioning technologies (such as UL-AoA and DL-AoD) to improve location accuracy, as illustrated in scenario 740.

[0117] The E-CID positioning method is based on Radio Resource Management (RRM) measurements. In E-CID, the UE reports the serving cell ID, timing advance (TA), identifiers of detected neighboring base stations, estimated timing, and signal strength. The UE's location is then estimated based on this information and the known locations of the base stations.

[0118] To assist in positioning operations, a location server (e.g., location server 230, LMF 270, SLP 272) may provide auxiliary data to the UE. For example, auxiliary data may include the identifier of the base station (or the cell / TRP of the base station) from which the reference signal is measured, reference signal configuration parameters (e.g., including the number of consecutive time slots of the PRS, the periodicity of consecutive time slots of the PRS, silence sequences, frequency hopping sequences, reference signal identifiers, reference signal bandwidth, etc.), and / or other parameters applicable to a particular positioning method. Alternatively, auxiliary data may originate directly from the base station itself (e.g., in periodically broadcast overhead messages, etc.). In some cases, the UE may be able to detect neighboring network nodes without using auxiliary data.

[0119] In the case of OTDOA or DL-TDOA positioning procedures, auxiliary data may also include the expected RSTD value and the associated uncertainty or search window around the expected RSTD. In some cases, the expected RSTD value may range from + / - 500 microseconds (µs). In some cases, when any of the resources used for positioning measurements is in FR1, the uncertainty of the expected RSTD may range from + / - 32 µs. In other cases, when all resources used for positioning measurements are in FR2, the uncertainty of the expected RSTD may range from + / - 8 µs.

[0120] Location estimates can be referred to by other names, such as location estimation, location, positioning, fixed location, etc. Location estimates can be geodesic and include coordinates (e.g., latitude, longitude, and possible elevation), or they can be municipal and include street addresses, postal addresses, or some other verbal description of the location. Location estimates can be further defined relative to some other known location or in absolute terms (e.g., using latitude, longitude, and possible elevation). Location estimates can include expected errors or uncertainties (e.g., by including the area or volume that the location is expected to include at a specified or default confidence level).

[0121] In NR, precise timing synchronization across the network may not be necessary. Instead, coarse timing synchronization across base stations (e.g., within the cyclic prefix (CP) duration of Orthogonal Frequency Division Multiplexing (OFDM) symbols) may be sufficient. RTT-based methods typically require only coarse timing synchronization and are therefore the preferred positioning method in NR.

[0122] Figure 8 An example wireless communication system 800 according to various aspects of this disclosure is illustrated. Figure 8In the example, UE 804 (e.g., any UE described herein) is attempting to calculate an estimate of its location, or assisting another entity (e.g., a base station or core network component, another UE, a location server, a third-party application, etc.) in calculating an estimate of its location. UE 804 may transmit and receive radio signals from multiple network nodes (labeled "nodes") 802-1, 802-2, and 802-3 (collectively, network nodes 802). Network node 802 may include one or more base stations (e.g., any base station described herein), one or more reconfigurable smart displays (RIS), one or more location beacons, one or more UEs (e.g., connected via sidelinks), etc.

[0123] In network-centric RTT positioning, the serving base station (e.g., one of the network nodes 802) instructs the UE 804 to measure RTT measurement signals (e.g., PRS) from two or more adjacent network nodes 802 (and typically from the serving base station, as at least three network nodes 802 are required for two-dimensional location estimation). The involved network nodes 802 transmit RTT measurement signals on low-reuse resources allocated by the network (e.g., resources used by network nodes 802 to transmit system information, where network node 802 is a base station). The UE 804 records the time of arrival (also referred to as the reception time or arrival time) of each RTT measurement signal relative to the current downlink timing of the UE 804 (e.g., as derived by the UE 804 from downlink signals received from its serving base station) and transmits common or individual RTT response signals (e.g., SRS) to the involved network nodes 802 on resources allocated by its serving base station. If UE 804 is not the location entity, it reports to the location entity that it has received a transmit (Rx-Tx) time difference measurement. This UE Rx-Tx time difference measurement indicates the time difference between the arrival time of each RTT measurement signal at UE 804 and the transmission time of the RTT response signal. Each involved network node 802 also reports to the location entity a network node Rx-Tx time difference measurement (also referred to as a base station (BS) or gNB Rx-Tx time difference measurement), which indicates the difference between the transmission time of the RTT measurement signal and the reception time of the RTT response signal.

[0124] The UE-centric RTT positioning process is similar to the network-based process, except that UE 804 (e.g., on resources allocated by the serving base station) transmits an uplink RTT measurement signal. This uplink RTT measurement signal is measured by multiple network nodes 802 adjacent to UE 804. Each involved network node 802 responds using a downlink RTT response signal and reports a network node Rx-Tx time difference measurement to the positioning entity. This network node Rx-Tx time difference measurement indicates the time difference between the arrival time of the RTT measurement signal at network node 802 and the transmission time of the RTT response signal. If UE 804 is not the positioning entity, then the UE reports a UE Rx-Tx time difference measurement for each network node 802, which indicates the difference between the transmission time of the RTT measurement signal and the reception time of the RTT response signal.

[0125] To determine the location (x, y) of UE 804, the positioning entity needs to know the location of network node 802, which can be represented in the reference coordinate system as (x_k, y_y), where... Figure 8 In the example, k=1, 2, 3. When UE 804 is the location entity, a location server that knows the network geometry (e.g., location server 230, LMF 270, SLP 272) can provide UE 804 with the location of the network node 802 involved.

[0126] The positioning entity determines each distance 810 (d_k, where k=1, 2, 3) between UE 804 and the corresponding network node 802 based on UE Rx-Tx time difference measurements, network node Rx-Tx time difference measurements, and the speed of light, as shown in the following reference. Figure 9 Further as described. Specifically, in Figure 8 In the example, the distance 810-1 between UE 804 and network node 802-1 is d_1, the distance 810-2 between UE 804 and network node 802-2 is d_2, and the distance 810-3 between UE 804 and network node 802-3 is d_3. Once each distance 810 is determined, the locating entity can solve for the position (x, y) of UE 804 using various known geometric techniques such as trilateration. Figure 8 It can be seen that the position of UE 804 is ideally located at the common intersection of three semicircles, each semicircle is defined by a radius dk and a center (x_k, y_k), where k=1, 2, 3.

[0127] Figure 9This is a diagram 900 illustrating example timing of RTT measurement signals exchanged between a network node 902 (labeled "Node") and a UE 904 according to various aspects of this disclosure. UE 904 can be any of the UEs described herein. Network node 902 can be a base station (e.g., any of the base stations described herein), a RIS, a location beacon, or another UE (e.g., connected via a side link).

[0128] exist Figure 9 In the example, network node 902 (labeled "BS") transmits an RTT measurement signal 910 (e.g., PRS) to UE 904 at time T_1. The RTT measurement signal 910 has a propagation delay T_Prop as it travels from network node 902 to UE 904. At time T_2 (the time when the RTT measurement signal 910 is received at UE 904), UE 904 measures the RTT measurement signal 910. After a certain UE processing time, UE 904 sends an RTT response signal 920 (e.g., SRS) at time T_3. After the propagation delay T_Prop, network node 902 measures the RTT response signal 920 from UE 904 at time T_4 (the time when the RTT response signal 920 is received at network node 902).

[0129] UE 904 reports the difference between time T_3 and time T_2 to the positioning entity (i.e., the Rx-Tx time difference measurement of UE 904, shown as UE_Rx-Tx 912). Similarly, network node 902 reports the difference between time T_4 and time T_1 to the positioning entity (i.e., the Rx-Tx time difference measurement of network node 902, shown as Node_Rx-Tx 922). Using these measurements and the known speed of light, the positioning entity can calculate the distance to UE 904 as d = 1 / 2*c*(Node_Rx-Tx – UE_Rx-Tx) = 1 / 2*c*(T_4 – T_1) – 1 / 2*c*(T_3 – T_2), where c is the speed of light.

[0130] Based on the known location of network node 902 and the distances between UE 904 and network node 902 (and at least two other network nodes 902), the location entity can calculate the location of UE 904. For example... Figure 8 As shown, UE 904 is located at the common intersection of three semicircles, each semicircle being defined by the radius of the distance between UE 904 and the corresponding network node 902.

[0131] On the one hand, the location entity can use a two-dimensional coordinate system to calculate the position of the UE 804 / 904; however, the aspects disclosed herein are not limited to this and can also be applied to determining the position using a three-dimensional coordinate system when additional dimensions are desired. Additionally, although Figure 8 An example is given of a UE 804 and three network nodes 802, and Figure 9 An example of a UE 904 and a network node 902 is shown, but it should be understood that there may be more UEs 804 / 904 and more network nodes 802 / 902.

[0132] NR supports or enables various sidelink positioning technologies. Figure 10A Various scenarios of interest, including sidelink-only positioning or combined Uu and sidelink positioning, are illustrated according to various aspects of this disclosure. In scenario 1010, at least one peer UE with a known location can improve the Uu-based positioning of a target UE by providing additional anchors (e.g., using sidelink round-trip time (RTT) (SL-RTT)). In scenario 1020, a low-end (e.g., a reduced-capability or “RedCap”) target UE can obtain assistance from a high-end UE to determine its location using, for example, a sidelink positioning and ranging process with the high-end UE. Compared to the low-end UE, the high-end UE may have more capabilities, such as more sensors, a faster processor, more memory, more antenna elements, higher transmit power capabilities, access to additional frequency bands, or any combination thereof. In scenario 1030, a relay UE (e.g., with a known location) participates in the positioning estimation of a remote UE without performing uplink positioning reference signal (PRS) transmission via the Uu interface. Scenario 1040 illustrates joint localization of multiple UEs. Specifically, in scenario 1040, two UEs with unknown locations can jointly localize under non-line-of-sight (NLOS) conditions by utilizing constraints from nearby UEs.

[0133] Figure 10B Additional scenarios of interest are illustrated according to various aspects of this disclosure, including sidelink-only or combined Uu and sidelink positioning. In scenario 1050, a UE used for public safety (e.g., by police, firefighters, etc.) may perform peer-to-peer (P2P) positioning and ranging for public safety and other purposes. For example, in scenario 1050, a public safety UE may be outside network coverage and use sidelink positioning technology to determine the location or relative distance and relative positioning between public safety UEs. Similarly, scenario 1060 illustrates multiple UEs outside coverage and using sidelink positioning technology (such as SL-RTT) to determine their location or relative distance and relative positioning.

[0134] Sidelink communication occurs within transmit or receive resource pools. In the frequency domain, the smallest unit of resource allocation is a subchannel (e.g., a set of consecutive PRBs in the frequency domain). In the time domain, resource allocation is performed within a time slot interval. However, some time slots are unavailable for sidelinks, and some time slots contain feedback resources. Furthermore, sidelink resources can be (pre-)configured to occupy fewer than 14 symbols in a time slot.

[0135] Configure sidelink resources at the Radio Resource Control (RRC) layer. RRC configuration can be pre-configured (e.g., pre-loaded on the UE) or configured (e.g., from the serving base station).

[0136] The NR side link supports Hybrid Automatic Repeat Request (HARQ) retransmission. Figure 11A This is a diagram 1100 illustrating an example time slot structure without feedback resources based on various aspects of this disclosure. Figure 11A In the example, time is represented horizontally and frequency vertically. In the time domain, the length of each block is one Orthogonal Frequency Division Multiplexing (OFDM) symbol, and 14 symbols constitute a time slot. In the frequency domain, the height of each block is a subchannel. Currently, the (pre-)configured subchannel size can be selected from a set of {10, 15, 20, 25, 50, 75, 100} Physical Resource Blocks (PRBs).

[0137] For side-link time slots, the first symbol is a repetition of the previous symbol and is used for automatic gain control (AGC) settings. This is in Figure 11A This is illustrated using vertical and horizontal hashing. For example... Figure 11A As shown, for sidelinks, the Physical Sidelink Control Channel (PSCCH) and the Physical Sidelink Shared Channel (PSSCH) are transmitted in the same time slot. Similar to the Physical Downlink Control Channel (PDCCH), the PSCCH carries control information about sidelink resource allocation and a description of the sidelink data sent to the UE. Likewise, similar to the Physical Downlink Shared Channel (PDSCH), the PSSCH carries the UE's user data. Figure 11A In the example, the PSCCH occupies half the bandwidth of the sub-channel and only takes up three symbols. Finally, the gap symbol appears after the PSSCH.

[0138] Figure 11B This is a diagram 1150 illustrating an example time-slot structure with feedback resources based on various aspects of this disclosure. Figure 11B In the example, time is represented horizontally and frequency is represented vertically. In the time domain, the length of each block is one OFDM symbol, and 14 symbols constitute a time slot. In the frequency domain, the height of each block is a subchannel.

[0139] Figure 11BThe illustrated time slot structure and Figure 11A The illustrated time slot structures are similar, but the difference is... Figure 11B The illustrated time slot structure includes feedback resources. Specifically, the last two symbols of the time slot are dedicated to the Physical Side Link Feedback Channel (PSFCH). The first PSFCH symbol is a repetition of the second PSFCH symbol used for AGC setup. In addition to the gap symbol following the PSFCH, there is a gap symbol after the two PSFCH symbols. Currently, the resources used for the PSFCH can be configured periodically from a set of {0, 1, 2, 4} time slots.

[0140] The first 13 symbols of a time slot in the time domain and the allocated sub-channels in the frequency domain form a sidelink resource pool. The sidelink resource pool may include resources for sidelink communication (transmission and / or reception), sidelink positioning (referred to as the resource pool for positioning (RP-P)), or both communication and positioning. A resource pool configured for both communication and positioning is referred to as a "shared" resource pool. In a shared resource pool, the RP-P is indicated by offset, periodicity, the number of consecutive symbols within a time slot (e.g., as few as one symbol), and / or bandwidth within component carriers (or bandwidth across multiple component carriers). Furthermore, the RP-P may be associated with a region or with a distance from a reference location.

[0141] A base station (or UE, depending on the resource allocation mode) may assign one or more resource configurations from the RP-P to another UE. Additionally or alternatively, a UE (e.g., a relay or remote UE) may request one or more RP-P configurations, and the UE may include one or more of the following in the request: (1) the UE's location information (or area identifier); (2) periodicity; (3) bandwidth; (4) offset; (5) number of symbols; and (6) whether a configuration with "low interference" is required (which can be determined by the assigned quality of service (QoS) or priority).

[0142] The base station or UE can configure / assign rate matching resources or RP-Ps for rate matching / silencing to the sidelink UE, such that when there is a conflict between the assigned resource and another resource pool containing data (PSSCH) and / or control (PSCCH), the sidelink UE is expected to perform rate matching / silencing / punching of data, DMRS, and / or CSI-RS within the conflicting resource. This will achieve orthogonality between positioning and data transmission to increase the coverage of PRS signals.

[0143] Figure 12 Figure 1200 illustrates an example of a location-based resource pool configured within a sidelink resource pool (i.e., a shared resource pool) for communication, according to various aspects of this disclosure. Figure 12In the example, time is represented horizontally and frequency is represented vertically. In the time domain, the length of each block is one Orthogonal Frequency Division Multiplexing (OFDM) symbol, and 14 symbols constitute a time slot. In the frequency domain, the height of each block is a subchannel.

[0144] exist Figure 12 In the example, the entire time slot (excluding the first and last symbols) can be a resource pool for sidelink communication. That is, any symbol other than the first and last can be allocated for sidelink communication. However, the RP-P is allocated in the last four pre-gap symbols of the time slot. Therefore, non-sidelink positioning data (such as User Data (PSSCH), CSI-RS, and control information) can only be sent in the first eight AGC symbols, not in the last four pre-gap symbols, to prevent conflicts with the configured RP-P. Non-sidelink positioning data that would normally be sent in the last four pre-gap symbols can be pruned or silenced, or rate-matched non-sidelink data that typically spans more than eight AGC symbols can be used to accommodate eight AGC symbols.

[0145] Sidelink Positioning Reference Signal (SL-PRS) has been defined to support sidelink positioning procedures between UEs. Similar to Downlink PRS (DL-PRS), SL-PRS resources consist of one or more resource elements (i.e., an OFDM symbol in the time domain and a subcarrier in the frequency domain). SL-PRS resources are designed with a comb-based pattern to enable Fast Fourier Transform (FFT) based processing at the receiver. SL-PRS resources consist of uninterleaved or only partially interleaved resource elements in the frequency domain to provide small Time of Arrival (TOA) uncertainties and reduced overhead for each SL-PRS resource. SL-PRS can also be associated with specific RP-Ps (e.g., some SL-PRSs can be allocated in some RP-Ps). SL-PRS is also defined with intra-slot repetition ( Figure 12 (not shown in the image) to allow for combined gain (if needed). RP-P inter-UE coordination may also exist to provide dynamic SL-PRS and data multiplexing while minimizing SL-PRS collisions.

[0146] In some designs, the UE Rx-Tx time difference (T UE-RX-TX () can be defined as follows, for example:

[0147] On the one hand, regarding the UE Rx-Tx time difference (T) UE-RX-TX This definition ensures the UE Rx-Tx time difference (T) UE-RX-TX The migration range is from -0.5ms to 0.5ms.

[0148] In some designs, the gNB Rx-Tx time difference (T gNB-RX-TX () can be defined as follows, for example:

[0149] On the one hand, regarding the time difference (T) of gNB Rx-Tx gNB-RX-TX This definition ensures the time difference (T) between gNB Rx and Tx. gNB-RX-TX The migration range is from -0.5ms to 0.5ms.

[0150] For side links, the SL Rx-Tx time difference (T) SL-RX-TX It can be measured in different ways.

[0151] In the first example (“Option 1”), the UE may be able to measure the SL Rx-Tx time difference (T) based on the actual SL-PRS transmission time. SL-RX-TX ). SL Rx-Tx time difference (T) under option 1 SL-RX-TX In the example of ), SL Rx-Tx time difference (T SL-RX-TX ) can be defined as mod(TUE-RX–TUE-TX+0.5ms, 1ms) – 0.5ms, where: TUE-RX is the UE reception timing defined by the path first detected in time from another UE in sidelink subframe #i; TUE-TX is the UE transmission timing of the side link subframe #j in which the UE transmits SL-PRS.

[0152] It should be noted that SL-PRS may not be sent at every configured SL-PRS timing. Therefore, the position of subframe #j in Option 1 is not guaranteed, because a number of transmission subframes without SL-PRS transmission may occur between subframe #i and subframe #j.

[0153] In the second example (“Option 2”), similar to the UE Rx-Tx time difference (in 3GPP Releases 16-17), the UE may be able to measure the SL Rx-Tx time difference (TUE-RX – TUE-TX) defined as TUE-RX–TUE-TX. SL-RX-TX ),in: TUE-RX is a sidelink subframe from another Tx UE defined by the path detected first in time. i UE reception timing; TUE-TX is the UE transmission timing of the sidelink subframe #j that is closest in time to the subframe #i received from the Tx UE.

[0154] Note that in some designs, subframe #j can be subframe #i. Here, the sidelink subframe #j may not include the configured SL-PRS timing. Furthermore, even if the SL-PRS timing is configured in the sidelink subframe #j, the UE may not activate the SL-PRS timing (i.e., transmit SL-PRS during that SL-PRS timing).

[0155] In the third example (“Option 3”), the UE may be able to measure the SL Rx-Tx time difference (T) based on both Option 1 and Option 2. SL-RX-TX ).

[0156] In some designs, the UE can report SL Rx-Tx time difference capability (i.e., support for one or more of options 1, 2, or 3) to a positioning estimation entity (such as an LMF for network-assisted positioning estimation or a UE or another UE for UE-based positioning estimation). In some designs, SL Rx-Tx time difference capability can be defined by frequency band.

[0157] Various aspects of this disclosure relate to the determination of the SL Rx-Tx time difference measurement type (e.g., Option 1 or Option 2) in scenarios where the UE supports both Options 1 and 2 (or Option 3). In some aspects, the determination of the SL Rx-Tx time difference measurement type may be based on an explicit network specification of the SL Rx-Tx time difference measurement type associated with the measurement request, or on an autonomous selection at the UE based on one or more rules associated with one or more criteria. Such aspects can provide various technical advantages, such as greater flexibility in reporting SL Rx-Tx time difference measurements for SL-based positioning estimation used by the UE. For example, in some scenarios, one SL Rx-Tx time difference measurement type may be more suitable than another (e.g., based on criteria such as UE mobility, inter-subframe time difference, RSRP variation, etc.), and selecting a more suitable SL Rx-Tx time difference measurement type may result in less positioning latency, higher positioning accuracy, less power consumption at the UE, etc.

[0158] Figure 13 An exemplary process 1300 of communication according to one aspect of this disclosure is illustrated. Figure 13 The process 1300 is performed by a UE such as UE 302.

[0159] refer to Figure 13At 1310, UE 302 (e.g., transmitter 314 or 324, etc.) transmits a capability indication indicating that the UE is capable of performing a first side-link (SL) receive-transmit (Rx-Tx) time difference measurement type and a second SL Rx-Tx time difference measurement type to a positioning estimation entity. In some designs (e.g., see Option 1 above), the first SL Rx-Tx time difference measurement type is based on a first time difference between: (i) the UE receive timing associated with a first subframe including a first positioning reference signal (PRS) from another device, and (ii) the first UE transmit timing of a second subframe including a second PRS transmitted by the UE. In some designs (e.g., see Option 2 above), the second SL Rx-Tx time difference measurement type is based on a second time difference between: (i) the UE receive timing associated with the first subframe including the first PRS from the other device, and (iii) the second UE transmit timing of a third subframe that follows the first subframe and is temporally closest to the first subframe.

[0160] refer to Figure 13 At 1320, UE 302 (e.g., receiver 312 or 322, etc.) receives a measurement request to perform one or more SL Rx-Tx time difference measurements for the UE. For example, the measurement request may be received from a positioning estimation entity.

[0161] refer to Figure 13 At 1330, UE 302 (e.g., processor 332, SL Rx-Tx component 342, etc.) determines whether to perform the one or more SL Rx-Tx time difference measurements based on the first SL Rx-Tx time difference measurement type or the second SL Rx-Tx time difference measurement type. In some designs, this determination is based on an explicit network-specified SL Rx-Tx time difference measurement type associated with the measurement request. In other designs, this determination includes an autonomous selection at the UE based on one or more rules associated with one or more criteria.

[0162] refer to Figure 13 At 1340, UE 302 (e.g., receiver 312 or 322, transmitter 314 or 324, processor 332, SL Rx-Tx component 342, etc.) performs one or more SL Rx-Tx time difference measurements according to the determined SL Rx-Tx time difference measurement type.

[0163] refer to Figure 13 At 1350, UE 302 (e.g., transmitter 314 or 324, etc.) sends a measurement report to the positioning estimation entity, which includes measurement information based on the one or more SL Rx-Tx time difference measurements.

[0164] Figure 14 An exemplary process 1400 of communication according to one aspect of this disclosure is illustrated. Figure 14 The process 1400 is performed by a location estimation entity. In some designs, this location estimation entity may correspond to a network component (e.g., an LMF integrated in a gNB / BS 304 or O-RAN component, or a remote location server (such as network entity 306)). In other designs, the location estimation entity may correspond to another UE (e.g., a sidelink-anchored UE) or the target UE itself (e.g., for UE-based location estimation, in which case any Rx / Tx operation between the UE and the location estimation entity may correspond to information transfer between different logical components of the UE via the data bus, etc.). On the other hand, Figure 14 The process of locating and estimating the entity at 1400 can be compared with the same Figure 13 The process at the UE is executed in parallel for process 1300.

[0165] refer to Figure 14 At 1410, a location estimation entity (e.g., receiver 312 or 322 or 352 or 362, or data bus 334 or data bus 382, ​​or network transceiver 380 or 390, etc.) provides a reception capability indication that instructs the user equipment (UE) to perform a first side-link (SL) receive-transmit (Rx-Tx) time difference measurement type and a second SL Rx-Tx time difference measurement type to the location estimation entity. In some designs (e.g., see Option 1 above), the first SL Rx-Tx time difference measurement type is based on a first time difference between: (i) the UE receive timing associated with a first subframe including a first location reference signal (PRS) from another device, and (ii) the first UE transmit timing of a second subframe including a second PRS transmitted by the UE. In some designs (e.g., see Option 2 above), the second SL Rx-Tx time difference measurement type is based on a second time difference between the following two: (i) the UE reception timing associated with the first subframe including the first PRS from the other device, and (iii) the second UE transmission timing of the third subframe that is after the first subframe and is closest in time to the first subframe.

[0166] refer to Figure 14 At 1420, the positioning estimation entity (e.g., transmitter 314 or 324 or 354 or 364, data bus 334 or data bus 382, ​​network transceiver 380 or 390, etc.) sends a measurement request to perform one or more SL Rx-Tx time difference measurements for the UE.

[0167] refer to Figure 14At 1430, the positioning estimation entity (e.g., receiver 312 or 322 or 352 or 362, or data bus 334 or data bus 382, ​​or network transceiver 380 or 390, etc.) receives a measurement report that includes measurement information based on one or more SL Rx-Tx time difference measurements.

[0168] refer to Figure 14 At 1440, the positioning estimation entity (e.g., processor 332, 384, or 394, SL Rx-Tx component 342, 388, or 398, etc.) determines whether the measurement information is based on the first SL Rx-Tx time difference measurement type or the second SL Rx-Tx time difference measurement type. In one respect, this measurement information can then be used to help derive the positioning estimate of the UE.

[0169] refer to Figures 13 to 14 In some designs, this determination at 1330 is based on the explicit network specification of the SL Rx-Tx time difference measurement type associated with the measurement request. For example, the UE or LMF may transmit an explicit request to the target UE to determine whether to perform the measurement or report the measurement according to one SL Rx-Tx time difference measurement definition or another.

[0170] refer to Figures 13 to 14 In some designs, one or more rules may include selecting the default SL Rx-Tx time difference measurement type when the measurement request is not associated with the explicitly specified network-specified SL Rx-Tx time difference measurement type. For example, if the measurement request does not include information about whether one SL Rx-Tx time difference measurement definition or another should be used, then one SL Rx-Tx time difference measurement definition (e.g., option 2) may be considered a conventional definition and should be used by default.

[0171] refer to Figures 13 to 14In some designs, the one or more criteria may include the time difference between the first subframe and the second subframe. On the other hand, the one or more rules may include selecting the first SL Rx-Tx time difference measurement type if the time difference exceeds a time difference threshold, and selecting the second SL Rx-Tx time difference measurement type if the time difference does not exceed the time difference threshold. For example, if the SL-PRS Tx is too far from the SL-PRS Rx (e.g., the threshold may be configured by the network, configured by another UE, or may be pre-configured or specified), the UE uses option 1 to report the measurement. In some designs, if the SL-PRS Tx is discarded and the UE is expected to use option 2, the UE may alternatively use option 1 to report the measurement (e.g., the network or another UE configures the measurement UE for such behavior).

[0172] refer to Figures 13 to 14 In some designs, the one or more criteria may include UE mobility. In another, the one or more rules may include selecting a first SLRx-Tx time difference measurement type when the UE mobility exceeds a UE mobility threshold, and selecting a second SLRx-Tx time difference measurement type when the UE mobility does not exceed the UE mobility threshold. For example, a UE in a high mobility scenario may specifically choose to use Option 1, as Option 1 is more robust to high UE mobility. UE mobility thresholds (e.g., slow, medium, high) may be configured for the UE regarding mobility. In other designs, the one or more criteria may include Reference Signal Received Power (RSRP) variation. In another, the one or more rules may include selecting a first SLRx-Tx time difference measurement type when the RSRP variation exceeds an RSRP variation threshold, and selecting a second SLRx-Tx time difference measurement type when the RSRP variation does not exceed the RSRP variation threshold.

[0173] refer to Figures 13 to 14 In some designs, the one or more criteria may include timing variation parameters. On the other hand, the one or more rules may include: selecting the first SL Rx-Tx time difference measurement type when a timing variation is performed, and selecting the second SL Rx-Tx time difference measurement type when the timing variation is not performed. In some designs, the timing variation parameter is associated with timing variations in response to a timing advance (TA) command, autonomous adjustments made by the UE, or a combination thereof. For example, if there is a location change between the Rx and Tx of the SL-PRS (e.g., the UE receives a TA command, or the UE performs an autonomous adjustment), the UE may define it using option 1 instead of option 2.

[0174] refer to Figures 13 to 14 In some designs, the one or more criteria may include a measurement difference between two of the following: (i) the UE reception timing associated with the first subframe including the first PRS from the other device, and (iii) the second UE transmission timing of the third subframe. On the other hand, the one or more rules may include selecting the first SL Rx-Tx time difference measurement type if the measurement difference exceeds a measurement difference threshold, and selecting the second SL Rx-Tx time difference measurement type if the measurement difference does not exceed the measurement difference threshold. For example, if the measurement difference generated using different definitions is greater than the threshold, the UE needs to select to report the measurement using the definition of Option 1. This threshold may be configured by the network, configured by another UE, or may be pre-configured or specified (predefined in the standard).

[0175] refer to Figures 13 to 14 In some designs, the one or more criteria, the one or more rules, or both include at least one criterion, at least one rule, or both, which are: predefined, or pre-configured before initiating the location session of the UE, or configured by the location estimation entity, network component, or another UE for the location session, or any combination thereof.

[0176] refer to Figures 13 to 14 In some designs, the determined SL Rx-Tx time difference measurement type is associated with a resource pool, or with an SL-PRS resource or SL-PRS resource set. For example, one or more SL Rx-Tx time difference measurement types or definitions can be pre-configured at the resource pool level. Similarly, one or more SL Rx-Tx time difference measurement types or definitions can be pre-configured at the SL-PRS resource level or SL-PRS resource set level.

[0177] refer to Figures 13 to 14In some designs, this determination is performed autonomously at the UE based on one or more rules associated with the one or more criteria, and the measurement report includes an indication of the determined SL Rx-Tx time difference measurement type. In some designs, this indication of the determined SL Rx-Tx time difference measurement type is based on whether the measurement information includes a timestamp associated with the UE transmission timing. In another example, if the measurement information includes the timestamp, the indication indicates the first SL Rx-Tx time difference measurement type, and if the measurement information does not include the timestamp, the indication indicates the second SL Rx-Tx time difference measurement type. For example, if the UE includes a timestamp for SL-PRS transmission associated with the UE Rx-Tx measurement, then it is assumed that Option 1 is used.

[0178] refer to Figures 13 to 14 In some designs, all measurement information in the measurement report is associated with a determined SLRx-Tx time difference measurement type. For example, the UE might need to select a single definition for all SLRx-Tx measurements included in the measurement report. Alternatively, in another example, the measurement report may also include additional measurement information based on at least one SLRx-Tx time difference measurement according to a corresponding SLRx-Tx time difference measurement type other than the determined SLRx-Tx time difference measurement type. In this case, the UE may be able to select different SLRx-Tx time difference measurement types or definitions for different SLRx-Tx measurements in the same measurement report.

[0179] refer to Figures 13 to 14In some designs, the determined SL Rx-Tx time difference measurement type is the first SL Rx-Tx time difference measurement type. In one example, for each of the one or more SL Rx-Tx time difference measurements according to the first SL Rx-Tx time difference measurement type: the first PRS and the second PRS are SL-PRS, or the first PRS is a downlink PRS (DL-PRS) and the second PRS is an SL-PRS, or the first PRS is an SL-PRS and the second PRS is an uplink (UL-PRS). In some designs, the determined SL Rx-Tx time difference measurement type is the second SL Rx-Tx time difference measurement type. In one example, for each of the one or more SL Rx-Tx time difference measurements according to the second SL Rx-Tx time difference measurement type: the first PRS is an SL-PRS and the third subframe is configured for SL, or the first PRS is a downlink PRS (DL-PRS) and the third subframe is configured for SL, or the first PRS is an SL-PRS and the third subframe is configured for uplink (UL). In other words, the SL Rx-Tx time difference measurement (of either type) may be based solely on an SL-PRS measurement (or subframe), or alternatively on an SL-PRS measurement / subframe and a Uu (DL or UL) PRS measurement or subframe.

[0180] refer to Figures 13 to 14 In some designs, the positioning estimation entity pre-configures one or more rules for the UE, which are associated with one or more criteria for selecting the autonomous SL Rx-Tx time difference measurement type at the UE.

[0181] As can be seen in the detailed description above, different features are grouped together in the examples. This manner of disclosure should not be construed as an intention to include more features in the example clauses than are expressly mentioned in each clause. Rather, the various aspects of this disclosure may include fewer features than those in the individual example clauses disclosed. Therefore, the following clauses should be regarded accordingly as incorporated into the description, where each clause may serve as a separate example. Although each dependent clause may refer in the clause to a specific combination with one of the other clauses, the aspect of that dependent clause is not limited to that specific combination. It should be understood that other example clauses may also include combinations of aspects of a dependent clause with the subject matter of any other dependent or independent clause, or combinations of any feature with other dependent and independent clauses. The various aspects disclosed herein expressly include these combinations unless expressly stated or readily inferred that a particular combination is not intended for use (e.g., contradictory aspects, such as defining an element as both an electrical insulator and an electrical conductor). Furthermore, it is contemplated that aspects of a clause may be included in any other independent clause, even if that clause does not directly depend on the independent clause.

[0182] Specific implementation examples are described in the following numbered clauses.

[0183] Clause 1. A method of operating a user equipment (UE), the method comprising: transmitting a capability indication indicating that the UE is capable of performing a first side-link (SL) receive-transmit (Rx-Tx) time difference measurement type and a second SL Rx-Tx time difference measurement type to a positioning estimation entity, wherein the first SL Rx-Tx time difference measurement type is based on a first time difference between: (i) a UE receive timing associated with a first subframe including a first positioning reference signal (PRS) from another device, and (ii) a first UE transmit timing of a second subframe including a second PRS transmitted by the UE, and wherein the second SL Rx-Tx time difference measurement type is based on a second time difference between: (i) the UE receive timing associated with the first subframe including the first PRS from the other device, and (iii) a second UE transmit timing of a third subframe following the first subframe and being temporally closest to the first subframe; receiving a measurement request for performing one or more SL Rx-Tx time difference measurements for the UE; and determining whether the measurement is based on the first SL Rx-Tx time difference measurement type or the second SL Rx-Tx time difference measurement type. The determination is based on an explicit network-specified SL Rx-Tx time difference measurement type associated with the measurement request, or the determination includes an autonomous selection at the UE based on one or more rules associated with one or more criteria; the determination is performed according to the determined SL Rx-Tx time difference measurement type; and a measurement report is sent to a positioning estimation entity, the measurement report including measurement information based on the one or more SL Rx-Tx time difference measurements.

[0184] Clause 2. The method according to Clause 1, wherein the determination is based on the explicit network specification of the SL Rx-Tx time difference measurement type associated with the measurement request.

[0185] Clause 3. The method according to any one of Clauses 1 to 2, wherein one or more of the rules include: selecting the default SL Rx-Tx time difference measurement type when the measurement request is not associated with the explicit network-specified SL Rx-Tx time difference measurement type.

[0186] Clause 4. The method according to any one of Clauses 1 to 3, wherein the one or more criteria include the time difference between the first subframe and the second subframe.

[0187] Clause 5. The method according to Clause 4, wherein one or more rules include: selecting the first SL Rx-Tx time difference measurement type when the time difference exceeds a time difference threshold, and selecting the second SL Rx-Tx time difference measurement type when the time difference does not exceed the time difference threshold.

[0188] Clause 6. The method according to any one of Clauses 1 to 5, wherein one or more of the criteria include UE mobility.

[0189] Clause 7. The method according to Clause 6, wherein one or more rules include: selecting the first SL Rx-Tx time difference measurement type when the UE mobility exceeds the UE mobility threshold, and selecting the second SL Rx-Tx time difference measurement type when the UE mobility does not exceed the UE mobility threshold.

[0190] Clause 8. The method according to any one of Clauses 1 to 7, wherein one or more of the criteria include a variation in the reference signal received power (RSRP).

[0191] Clause 9. The method according to Clause 8, wherein one or more rules include: selecting the first SL Rx-Tx time difference measurement type when the RSRP change exceeds the RSRP change threshold, and selecting the second SL Rx-Tx time difference measurement type when the RSRP change does not exceed the RSRP change threshold.

[0192] Clause 10. The method according to any one of Clauses 1 to 9, wherein the one or more criteria include a timing variation parameter.

[0193] Clause 11. The method according to Clause 10, wherein the one or more rules include: selecting the first SL Rx-Tx time difference measurement type when a timing change is performed, and selecting the second SL Rx-Tx time difference measurement type when the timing change is not performed.

[0194] Clause 12. The method according to any one of Clauses 10 to 11, wherein the timing change parameter is associated with a timing change in response to a timing advance (TA) command, an autonomous adjustment performed by the UE, or a combination thereof.

[0195] Clause 13. The method according to any one of Clauses 1 to 12, wherein the one or more criteria include the difference between the following two measurements: (i) the UE reception timing associated with the first subframe including the first PRS from the other device, and (iii) the second UE transmission timing of the third subframe.

[0196] Clause 14. The method according to Clause 13, wherein one or more rules include: selecting the first SL Rx-Tx time difference measurement type when the measurement difference exceeds a measurement difference threshold, and selecting the second SL Rx-Tx time difference measurement type when the measurement difference does not exceed the measurement difference threshold.

[0197] Clause 15. The method according to any one of Clauses 1 to 14, wherein the one or more criteria, the one or more rules, or both comprise at least one criterion, at least one rule, or both, and the at least one criterion, the at least one rule, or both are: predefined, or pre-configured prior to initiating a location session for the UE, or configured by the location estimation entity, network component, or another UE for the location session, or any combination thereof.

[0198] Clause 16. The method according to any one of Clauses 1 to 15, wherein the determined SL Rx-Tx time difference measurement type is associated with a resource pool, or wherein the determined SL Rx-Tx time difference measurement type is associated with an SL-PRS resource or an SL-PRS resource set.

[0199] Clause 17. The method according to any one of Clauses 1 to 16, wherein the determination is performed autonomously at the UE based on the one or more rules associated with the one or more criteria, and wherein the measurement report includes an indication of the determined SL Rx-Tx time difference measurement type.

[0200] Clause 18. The method according to Clause 17, wherein the indication of the determined SL Rx-Tx time difference measurement type is based on whether the measurement information includes a timestamp associated with the UE transmission timing.

[0201] Clause 19. The method according to Clause 18, wherein if the measurement information includes the timestamp, the indication indicates the first SL Rx-Tx time difference measurement type, and wherein if the measurement information does not include the timestamp, the indication indicates the second SL Rx-Tx time difference measurement type.

[0202] Clause 20. The method according to any one of Clauses 1 to 19, wherein all measurement information in the measurement report is associated with the determined SL Rx-Tx time difference measurement type, or wherein the measurement report further includes additional measurement information based on at least one SL Rx-Tx time difference measurement according to a corresponding SL Rx-Tx time difference measurement type other than the determined SL Rx-Tx time difference measurement type.

[0203] Clause 21. The method according to any one of Clauses 1 to 20, wherein the determined SL Rx-Tx time difference measurement type is the first SL Rx-Tx time difference measurement type.

[0204] Clause 22. The method according to Clause 21, wherein for each of the one or more SL Rx-Tx time difference measurements according to the first SL Rx-Tx time difference measurement type: the first PRS and the second PRS are SL-PRS, or the first PRS is a downlink PRS (DL-PRS) and the second PRS is SL-PRS, or the first PRS is SL-PRS and the second PRS is uplink (UL-PRS).

[0205] Clause 23. The method according to any one of Clauses 1 to 22, wherein the determined SL Rx-Tx time difference measurement type is the second SL Rx-Tx time difference measurement type.

[0206] Clause 24. The method according to any one of Clauses 21 to 23, wherein, for each of the one or more SL Rx-Tx time difference measurements according to the second SL Rx-Tx time difference measurement type: the first PRS is an SL-PRS and the third subframe is configured for SL, or the first PRS is a downlink PRS (DL-PRS) and the third subframe is configured for SL, or the first PRS is an SL-PRS and the third subframe is configured for uplink (UL).

[0207] Clause 25. A method of operating a positioning estimation entity, the method comprising: receiving a capability indication, the capability indication indicating that a user equipment (UE) is capable of performing a first side-link (SL) receive-transmit (Rx-Tx) time difference measurement type and a second SL Rx-Tx time difference measurement type to the positioning estimation entity, wherein the first SL Rx-Tx time difference measurement type is based on a first time difference between: (i) a UE receive timing associated with a first subframe including a first positioning reference signal (PRS) from another device, and (ii) a first UE transmit timing of a second subframe including a second PRS transmitted by the UE, and wherein the second SL Rx-Tx time difference measurement type is based on a second time difference between: (i) the UE receive timing associated with the first subframe including the first PRS from the other device, and (iii) a second UE transmit timing of a third subframe following the first subframe and being temporally closest to the first subframe; sending a measurement request to perform one or more SL Rx-Tx time difference measurements for the UE; receiving a measurement report, the measurement report including measurements based on one or more SL... The measurement information of Rx-Tx time difference measurement; and determining whether the measurement information is based on the first SL Rx-Tx time difference measurement type or the second SL Rx-Tx time difference measurement type.

[0208] Clause 26. The method according to Clause 25, wherein the determination is based on which of the first SL Rx-Tx time difference measurement type or the second SL Rx-Tx time difference measurement type is explicitly specified to the UE by the positioning estimation entity, or wherein the determination is based on an indication in the measurement report.

[0209] Clause 27. The method according to any one of Clauses 25 to 26, the method further comprising: presetting one or more rules for the UE, the one or more rules being associated with one or more criteria for autonomous SL Rx-Tx time difference measurement type selection at the UE.

[0210] Clause 28. The method according to any one of Clauses 25 to 27, wherein the determined SL Rx-Tx time difference measurement type is the first SL Rx-Tx time difference measurement type, and for each of the one or more SL Rx-Tx time difference measurements according to the first SL Rx-Tx time difference measurement type: the first PRS and the second PRS are SL-PRS, or the first PRS is a downlink PRS (DL-PRS) and the second PRS is an SL-PRS, or the first PRS is an SL-PRS and the second PRS is an uplink PRS (UL-PRS), or wherein the determined SL Rx-Tx time difference measurement type is the second SL Rx-Tx time difference measurement type, and for each of the one or more SL Rx-Tx time difference measurements according to the second SL Rx-Tx time difference measurement type: the first PRS and the second PRS are ... the first PRS is an SL-PRS and the second PRS is an uplink PRS Rx-Tx time difference measurement: The first PRS is SL-PRS and the third subframe is configured for SL, or the first PRS is DL-PRS and the third subframe is configured for SL, or the first PRS is SL-PRS and the third subframe is configured for UL.

[0211] Clause 29. A user equipment (UE) comprising: a memory; and at least one processor communicatively coupled to the memory, the at least one processor being configured to: transmit a capability indication indicating that the UE is capable of performing a first side-link (SL) receive-transmit (Rx-Tx) time difference measurement type and a second SL Rx-Tx time difference measurement type to a positioning estimation entity, wherein the first SL Rx-Tx time difference measurement type is based on a first time difference between: (i) a UE receive timing associated with a first subframe including a first positioning reference signal (PRS) from another device, and (ii) a first UE transmit timing of a second subframe including a second PRS transmitted by the UE, and wherein the second SL Rx-Tx time difference measurement type is based on a second time difference between: (i) the UE receive timing associated with the first subframe including the first PRS from the other device, and (iii) a second UE transmit timing of a third subframe following the first subframe and being temporally closest to the first subframe; and receive one or more SLs performed for the UE. The process includes: a measurement request for Rx-Tx time difference measurement; determining whether to perform the one or more SL Rx-Tx time difference measurements based on the first SL Rx-Tx time difference measurement type or the second SL Rx-Tx time difference measurement type, wherein the determination is based on an explicit network-specified SL Rx-Tx time difference measurement type associated with the measurement request, or wherein the determination includes an autonomous selection at the UE based on one or more rules associated with one or more criteria; performing the one or more SL Rx-Tx time difference measurements according to the determined SL Rx-Tx time difference measurement type; and sending a measurement report to a positioning estimation entity, the measurement report including measurement information based on the one or more SL Rx-Tx time difference measurements.

[0212] Clause 30. The UE as described in Clause 29, wherein the determination is based on the explicit network-specified SL Rx-Tx time difference measurement type associated with the measurement request.

[0213] Clause 31. A UE pursuant to any one of Clauses 29 to 30, wherein one or more of the rules include: selecting the default SL Rx-Tx time difference measurement type when the measurement request is not associated with the explicit network-specified SL Rx-Tx time difference measurement type.

[0214] Clause 32. The UE pursuant to any one of Clauses 29 to 31, wherein the one or more criteria include the time difference between the first subframe and the second subframe.

[0215] Clause 33. The UE as described in Clause 32, wherein one or more of the rules include: selecting the first SL Rx-Tx time difference measurement type when the time difference exceeds a time difference threshold, and selecting the second SL Rx-Tx time difference measurement type when the time difference does not exceed the time difference threshold.

[0216] Clause 34. The UE pursuant to any one of Clauses 29 to 33, wherein one or more of the criteria include UE mobility.

[0217] Clause 35. The UE as described in Clause 34, wherein one or more of the rules include: selecting the first SL Rx-Tx time difference measurement type when the UE mobility exceeds the UE mobility threshold, and selecting the second SL Rx-Tx time difference measurement type when the UE mobility does not exceed the UE mobility threshold.

[0218] Clause 36. The UE pursuant to any one of Clauses 29 to 35, wherein one or more of the criteria include a variation in the Reference Signal Received Power (RSRP).

[0219] Clause 37. The UE as described in Clause 36, wherein one or more of the rules include: selecting the first SL Rx-Tx time difference measurement type when the RSRP change exceeds an RSRP change threshold, and selecting the second SL Rx-Tx time difference measurement type when the RSRP change does not exceed the RSRP change threshold.

[0220] Clause 38. The UE pursuant to any one of Clauses 29 to 37, wherein one or more of the criteria include timing variation parameters.

[0221] Clause 39. The UE as described in Clause 38, wherein one or more rules include: selecting the first SL Rx-Tx time difference measurement type when a timing change is performed, and selecting the second SL Rx-Tx time difference measurement type when the timing change is not performed.

[0222] Clause 40. The UE according to any one of Clauses 38 to 39, wherein the timing change parameter is associated with a timing change in response to a timing advance (TA) command, an autonomous adjustment made by the UE, or a combination thereof.

[0223] Clause 41. A UE pursuant to any one of Clauses 29 to 40, wherein the one or more criteria comprise a difference in measurements between: (i) the UE reception timing associated with the first subframe including the first PRS from the other device, and (iii) the second UE transmission timing of the third subframe.

[0224] Clause 42. The UE as described in Clause 41, wherein one or more rules include: selecting the first SL Rx-Tx time difference measurement type when the measurement difference exceeds a measurement difference threshold, and selecting the second SL Rx-Tx time difference measurement type when the measurement difference does not exceed the measurement difference threshold.

[0225] Clause 43. A UE pursuant to any one of Clauses 29 to 42, wherein the one or more criteria, the one or more rules, or both comprise at least one criterion, at least one rule, or both, and the at least one criterion, the at least one rule, or both are: defined, configured prior to initiating a location session for the UE, or configured by the location estimation entity, network component, or another UE for the location session, or any combination thereof.

[0226] Clause 44. A UE pursuant to any one of Clauses 29 to 43, wherein the determined SL Rx-Tx time difference measurement type is associated with a resource pool, or wherein the determined SL Rx-Tx time difference measurement type is associated with an SL-PRS resource or an SL-PRS resource set.

[0227] Clause 45. The UE pursuant to any one of Clauses 29 to 44, wherein the determination is performed autonomously at the UE based on the one or more rules associated with the one or more criteria, and wherein the measurement report includes an indication of the determined SL Rx-Tx time difference measurement type.

[0228] Clause 46. The UE as described in Clause 45, wherein the indication of the determined SL Rx-Tx time difference measurement type is based on whether the measurement information includes a timestamp associated with the UE transmission timing.

[0229] Clause 47. The UE as described in Clause 46, wherein if the measurement information includes the timestamp, the indication indicates the first SL Rx-Tx time difference measurement type, and wherein if the measurement information does not include the timestamp, the indication indicates the second SL Rx-Tx time difference measurement type.

[0230] Clause 48. A UE pursuant to any one of Clauses 29 to 47, wherein all measurement information in the measurement report is associated with a determined SL Rx-Tx time difference measurement type, or wherein the measurement report further includes additional measurement information based on at least one SL Rx-Tx time difference measurement of a corresponding SL Rx-Tx time difference measurement type other than the determined SL Rx-Tx time difference measurement type.

[0231] Clause 49. The UE according to any one of Clauses 29 to 48, wherein the determined SL Rx-Tx time difference measurement type is the first SL Rx-Tx time difference measurement type.

[0232] Clause 50. The UE as described in Clause 49, wherein for each of the one or more SL Rx-Tx time difference measurements according to the first SL Rx-Tx time difference measurement type: the first PRS and the second PRS are SL-PRS, or the first PRS is a downlink PRS (DL-PRS) and the second PRS is SL-PRS, or the first PRS is SL-PRS and the second PRS is uplink (UL-PRS).

[0233] Clause 51. The UE pursuant to any one of Clauses 29 to 50, wherein the determined SL Rx-Tx time difference measurement type is the second SL Rx-Tx time difference measurement type.

[0234] Clause 52. A UE pursuant to any one of Clauses 49 to 51, wherein, for each of the one or more SL Rx-Tx time difference measurements according to the second SL Rx-Tx time difference measurement type: the first PRS is an SL-PRS and the third subframe is configured for SL, or the first PRS is a downlink PRS (DL-PRS) and the third subframe is configured for SL, or the first PRS is an SL-PRS and the third subframe is configured for uplink (UL).

[0235] Clause 53. A location estimation entity, the location estimation entity comprising: a memory; and at least one processor communicatively coupled to the memory, the at least one processor being configured to: a receive capability indication indicating that a user equipment (UE) is capable of performing a first side-link (SL) receive-transmit (Rx-Tx) time difference measurement type and a second SL Rx-Tx time difference measurement type on the location estimation entity, wherein the first SL Rx-Tx time difference measurement type is based on a first time difference between: (i) a UE receive timing associated with a first subframe including a first location reference signal (PRS) from another device, and (ii) a first UE transmit timing of a second subframe including a second PRS transmitted by the UE, and wherein the second SL Rx-Tx time difference measurement type is based on a second time difference between: (i) the UE receive timing associated with the first subframe including the first PRS from the other device, and (iii) a second UE transmit timing of a third subframe following the first subframe and being temporally closest to the first subframe; and transmitting one or more SLs performed on the UE. The measurement request for Rx-Tx time difference measurement; receiving a measurement report, the measurement report including measurement information based on one or more SL Rx-Tx time difference measurements; and determining whether the measurement information is based on the first SL Rx-Tx time difference measurement type or the second SL Rx-Tx time difference measurement type.

[0236] Clause 54. The location estimation entity as described in Clause 53, wherein the determination is based on which of the first SL Rx-Tx time difference measurement type or the second SL Rx-Tx time difference measurement type is explicitly specified to the UE by the location estimation entity, or wherein the determination is based on an indication in the measurement report.

[0237] Clause 55. The positioning estimation entity according to any one of Clauses 53 to 54, wherein the at least one processor is further configured to: pre-configure one or more rules for the UE, the one or more rules being associated with one or more criteria for autonomous SL Rx-Tx time difference measurement type selection at the UE.

[0238] Clause 56. A positioning estimation entity according to any one of Clauses 53 to 55, wherein the determined SL Rx-Tx time difference measurement type is the first SL Rx-Tx time difference measurement type, and for each of the one or more SL Rx-Tx time difference measurements according to the first SL Rx-Tx time difference measurement type: the first PRS and the second PRS are SL-PRS, or the first PRS is a downlink PRS (DL-PRS) and the second PRS is an SL-PRS, or the first PRS is an SL-PRS and the second PRS is an uplink PRS (UL-PRS), or wherein the determined SL Rx-Tx time difference measurement type is the second SL Rx-Tx time difference measurement type, and for each of the one or more SL Rx-Tx time difference measurements according to the second SL Rx-Tx time difference measurement type: the first PRS and the second PRS are ... the first PRS is an SL-PRS and the second PRS is an uplink Each SLRx-Tx time difference measurement in Rx-Tx time difference measurement: the first PRS is SL-PRS and the third subframe is configured for SL, or the first PRS is DL-PRS and the third subframe is configured for SL, or the first PRS is SL-PRS and the third subframe is configured for UL.

[0239] Clause 57. A user equipment (UE) comprising: components for transmitting a capability indication indicating that the UE is capable of performing a first side-link (SL) receive-transmit (Rx-Tx) time difference measurement type and a second SL Rx-Tx time difference measurement type to a positioning estimation entity, wherein the first SL Rx-Tx time difference measurement type is based on a first time difference between: (i) a UE receive timing associated with a first subframe including a first positioning reference signal (PRS) from another device, and (ii) a first UE transmit timing including a second subframe including a second PRS transmitted by the UE, and wherein the second SL Rx-Tx time difference measurement type is based on a second time difference between: (i) the UE receive timing associated with the first subframe including the first PRS from the other device, and (iii) a second UE transmit timing following the first subframe and being temporally closest to the first subframe; components for receiving a measurement request for performing one or more SL Rx-Tx time difference measurements for the UE; and components for determining whether the measurement is based on the first SL Rx-Tx time difference measurement type or the second SL Rx-Tx time difference measurement type. The components include: a component for performing the one or more SL Rx-Tx time difference measurements based on an explicit network-specified SL Rx-Tx time difference measurement type associated with the measurement request, or a component for performing the one or more SL Rx-Tx time difference measurements based on an Rx-Tx time difference measurement type associated with the measurement request, wherein the determination includes an autonomous selection at the UE based on one or more rules associated with one or more criteria; a component for performing the one or more SL Rx-Tx time difference measurements according to the determined SL Rx-Tx time difference measurement type; and a component for sending a measurement report to a positioning estimation entity, the measurement report including measurement information based on the one or more SL Rx-Tx time difference measurements.

[0240] Clause 58. The UE as described in Clause 57, wherein the determination is based on the explicit network-specified SL Rx-Tx time difference measurement type associated with the measurement request.

[0241] Clause 59. The UE pursuant to any one of Clauses 57 to 58, wherein one or more of the rules include: a component for selecting a default SL Rx-Tx time difference measurement type when the measurement request is not associated with the explicitly network-specified SL Rx-Tx time difference measurement type.

[0242] Clause 60. The UE pursuant to any one of Clauses 57 to 59, wherein the one or more criteria include the time difference between the first subframe and the second subframe.

[0243] Clause 61. The UE as described in Clause 60, wherein one or more rules include: a component for selecting the first SL Rx-Tx time difference measurement type when the time difference exceeds a time difference threshold, and a component for selecting the second SL Rx-Tx time difference measurement type when the time difference does not exceed the time difference threshold.

[0244] Clause 62. The UE pursuant to any one of Clauses 57 to 61, wherein one or more of the criteria include UE mobility.

[0245] Clause 63. The UE as described in Clause 62, wherein one or more rules include: a component for selecting the first SL Rx-Tx time difference measurement type when the UE mobility exceeds a UE mobility threshold, and a component for selecting the second SL Rx-Tx time difference measurement type when the UE mobility does not exceed the UE mobility threshold.

[0246] Clause 64. The UE pursuant to any one of Clauses 57 to 63, wherein one or more of the criteria include a variation in the Reference Signal Received Power (RSRP).

[0247] Clause 65. The UE as described in Clause 64, wherein one or more rules include: a component for selecting the first SL Rx-Tx time difference measurement type when the RSRP change exceeds an RSRP change threshold, and a component for selecting the second SL Rx-Tx time difference measurement type when the RSRP change does not exceed the RSRP change threshold.

[0248] Clause 66. The UE pursuant to any one of Clauses 57 to 65, wherein one or more of the criteria include timing variation parameters.

[0249] Clause 67. The UE as described in Clause 66, wherein one or more rules include: components for selecting the first SL Rx-Tx time difference measurement type when a timing change is performed, and components for selecting the second SL Rx-Tx time difference measurement type when the timing change is not performed.

[0250] Clause 68. The UE according to any one of Clauses 66 to 67, wherein the timing change parameter is associated with a timing change in response to a timing advance (TA) command, an autonomous adjustment made by the UE, or a combination thereof.

[0251] Clause 69. A UE pursuant to any one of Clauses 57 to 68, wherein the one or more criteria comprise a difference in measurements between: (i) the UE reception timing associated with the first subframe including the first PRS from the other device, and (iii) the second UE transmission timing of the third subframe.

[0252] Clause 70. The UE as described in Clause 69, wherein one or more rules include: a component for selecting the first SL Rx-Tx time difference measurement type when the measurement difference exceeds a measurement difference threshold, and a component for selecting the second SL Rx-Tx time difference measurement type when the measurement difference does not exceed the measurement difference threshold.

[0253] Clause 71. A UE pursuant to any one of Clauses 57 to 70, wherein the one or more criteria, the one or more rules, or both comprise at least one criterion, at least one rule, or both, and the at least one criterion, the at least one rule, or both are: components for definition, or components for configuration prior to initiating a location session for the UE, or any combination thereof configured by the location estimation entity, network component, or another UE for the location session.

[0254] Clause 72. A UE pursuant to any one of Clauses 57 to 71, wherein the determined SL Rx-Tx time difference measurement type is associated with a resource pool, or wherein the determined SL Rx-Tx time difference measurement type is associated with an SL-PRS resource or an SL-PRS resource set.

[0255] Clause 73. The UE pursuant to any one of Clauses 57 to 72, wherein the determination is performed autonomously at the UE based on the one or more rules associated with the one or more criteria, and wherein the measurement report includes an indication of the determined SL Rx-Tx time difference measurement type.

[0256] Clause 74. The UE as described in Clause 73, wherein the indication of the determined SL Rx-Tx time difference measurement type is based on whether the measurement information includes a timestamp associated with the UE transmission timing.

[0257] Clause 75. The UE as described in Clause 74, wherein if the measurement information includes the timestamp, the indication indicates the first SL Rx-Tx time difference measurement type, and wherein if the measurement information does not include the timestamp, the indication indicates the second SL Rx-Tx time difference measurement type.

[0258] Clause 76. The UE pursuant to any one of Clauses 57 to 75, wherein all measurement information in the measurement report is associated with the determined SL Rx-Tx time difference measurement type, or wherein the measurement report further includes additional measurement information based on at least one SL Rx-Tx time difference measurement of a corresponding SL Rx-Tx time difference measurement type other than the determined SL Rx-Tx time difference measurement type.

[0259] Clause 77. The UE pursuant to any one of Clauses 57 to 76, wherein the determined SL Rx-Tx time difference measurement type is the first SL Rx-Tx time difference measurement type.

[0260] Clause 78. The UE as described in Clause 77, wherein for each of the one or more SL Rx-Tx time difference measurements according to the first SL Rx-Tx time difference measurement type: the first PRS and the second PRS are SL-PRS, or the first PRS is a downlink PRS (DL-PRS) and the second PRS is an SL-PRS, or the first PRS is an SL-PRS and the second PRS is an uplink (UL-PRS).

[0261] Clause 79. The UE pursuant to any one of Clauses 57 to 78, wherein the determined SL Rx-Tx time difference measurement type is the second SL Rx-Tx time difference measurement type.

[0262] Clause 80. A UE pursuant to any one of Clauses 77 to 79, wherein, for each of the one or more SL Rx-Tx time difference measurements according to the second SL Rx-Tx time difference measurement type: the first PRS is an SL-PRS and the third subframe is configured for SL, or the first PRS is a downlink PRS (DL-PRS) and the third subframe is configured for SL, or the first PRS is an SL-PRS and the third subframe is configured for uplink (UL).

[0263] Clause 81. A positioning estimation entity, the positioning estimation entity comprising: components for receiving a capability indication indicating that a user equipment (UE) is capable of performing a first side-link (SL) receive-transmit (Rx-Tx) time difference measurement type and a second SL Rx-Tx time difference measurement type to the positioning estimation entity, wherein the first SL Rx-Tx time difference measurement type is based on a first time difference between: (i) a UE receive timing associated with a first subframe including a first positioning reference signal (PRS) from another device, and (ii) a first UE transmit timing of a second subframe including a second PRS transmitted by the UE, and wherein the second SL Rx-Tx time difference measurement type is based on a second time difference between: (i) the UE receive timing associated with the first subframe including the first PRS from the other device, and (iii) a second UE transmit timing of a third subframe following the first subframe and being temporally closest to the first subframe; components for transmitting a measurement request for performing one or more SL Rx-Tx time difference measurements for the UE; and components for receiving a measurement report, the measurement report including measurements based on one or more SL Rx-Tx time difference measurements. Measurement information for Rx-Tx time difference measurement; and a component for determining whether the measurement information is based on the first SL Rx-Tx time difference measurement type or the second SL Rx-Tx time difference measurement type.

[0264] Clause 82. The location estimation entity as described in Clause 81, wherein the determination is based on which of the first SL Rx-Tx time difference measurement type or the second SL Rx-Tx time difference measurement type is explicitly specified to the UE by the location estimation entity, or wherein the determination is based on an indication in the measurement report.

[0265] Clause 83. The location estimation entity according to any one of Clauses 81 to 82, the location estimation entity further comprising: a component for presetting one or more rules for the UE, the one or more rules being associated with one or more criteria for autonomous SL Rx-Tx time difference measurement type selection at the UE.

[0266] Clause 84. A positioning estimation entity according to any one of Clauses 81 to 83, wherein the determined SL Rx-Tx time difference measurement type is the first SL Rx-Tx time difference measurement type, and for each of the one or more SL Rx-Tx time difference measurements according to the first SL Rx-Tx time difference measurement type: the first PRS and the second PRS are SL-PRS, or the first PRS is a downlink PRS (DL-PRS) and the second PRS is an SL-PRS, or the first PRS is an SL-PRS and the second PRS is an uplink PRS (UL-PRS), or wherein the determined SL Rx-Tx time difference measurement type is the second SL Rx-Tx time difference measurement type, and for each of the one or more SL Rx-Tx time difference measurements according to the second SL Rx-Tx time difference measurement type: Each SLRx-Tx time difference measurement in Rx-Tx time difference measurement: the first PRS is SL-PRS and the third subframe is configured for SL, or the first PRS is DL-PRS and the third subframe is configured for SL, or the first PRS is SL-PRS and the third subframe is configured for UL.

[0267] Clause 85. A non-transitory computer-readable medium storing computer-executable instructions, which, when executed by a user equipment (UE), cause the UE to: transmit a capability indication indicating that the UE is capable of performing a first side-link (SL) receive-transmit (Rx-Tx) time difference measurement type and a second SL Rx-Tx time difference measurement type to a positioning estimation entity, wherein the first SL Rx-Tx time difference measurement type is based on a first time difference between: (i) a UE receive timing associated with a first subframe including a first positioning reference signal (PRS) from another device, and (ii) a first UE transmit timing including a second subframe including a second PRS transmitted by the UE, and wherein the second SL Rx-Tx time difference measurement type is based on a second time difference between: (i) the UE receive timing associated with the first subframe including the first PRS from the other device, and (iii) a second UE transmit timing following the first subframe and being temporally closest to the first subframe; receive a measurement request for performing one or more SL Rx-Tx time difference measurements for the UE; and determine whether the measurement is based on the first SL Rx-Tx time difference measurement type. The one or more SL Rx-Tx time difference measurements are performed using either the Rx-Tx time difference measurement type or the second SL Rx-Tx time difference measurement type, wherein the determination is based on an explicit network-specified SL Rx-Tx time difference measurement type associated with the measurement request, or wherein the determination includes an autonomous selection at the UE based on one or more rules associated with one or more criteria; the one or more SL Rx-Tx time difference measurements are performed according to the determined SL Rx-Tx time difference measurement type; and a measurement report is sent to a positioning estimation entity, the measurement report including measurement information based on the one or more SL Rx-Tx time difference measurements.

[0268] Clause 86. The non-transitory computer-readable medium as described in Clause 85, wherein the determination is based on the explicit network-specified SL Rx-Tx time difference measurement type associated with the measurement request.

[0269] Clause 87. A non-transitory computer-readable medium pursuant to any one of Clauses 85 to 86, wherein one or more of the rules include: selecting the default SL Rx-Tx time difference measurement type when the measurement request is not associated with the explicit network-specified SL Rx-Tx time difference measurement type.

[0270] Clause 88. A non-transitory computer-readable medium pursuant to any one of Clauses 85 to 87, wherein the one or more criteria include the time difference between the first subframe and the second subframe.

[0271] Clause 89. The non-transitory computer-readable medium as described in Clause 88, wherein one or more rules include: selecting the first SL Rx-Tx time difference measurement type when the time difference exceeds a time difference threshold, and selecting the second SL Rx-Tx time difference measurement type when the time difference does not exceed the time difference threshold.

[0272] Clause 90. A non-transitory computer-readable medium pursuant to any one of Clauses 85 to 89, wherein one or more of the criteria include UE mobility.

[0273] Clause 91. The non-transitory computer-readable medium as described in Clause 90, wherein one or more rules include: selecting the first SL Rx-Tx time difference measurement type when the UE mobility exceeds the UE mobility threshold, and selecting the second SL Rx-Tx time difference measurement type when the UE mobility does not exceed the UE mobility threshold.

[0274] Clause 92. A non-transitory computer-readable medium pursuant to any one of Clauses 85 to 91, wherein one or more of the criteria include variations in the reference signal received power (RSRP).

[0275] Clause 93. The non-transitory computer-readable medium as described in Clause 92, wherein one or more of the rules include: selecting the first SL Rx-Tx time difference measurement type when the RSRP change exceeds an RSRP change threshold, and selecting the second SL Rx-Tx time difference measurement type when the RSRP change does not exceed the RSRP change threshold.

[0276] Clause 94. A non-transitory computer-readable medium pursuant to any one of Clauses 85 to 93, wherein one or more of the criteria include timing variation parameters.

[0277] Clause 95. The non-transitory computer-readable medium as described in Clause 94, wherein one or more rules include: selecting the first SL Rx-Tx time difference measurement type when a timing change is performed, and selecting the second SL Rx-Tx time difference measurement type when the timing change is not performed.

[0278] Clause 96. A non-transitory computer-readable medium according to any one of Clauses 94 to 95, wherein the timing change parameter is associated with a timing change in response to a timing advance (TA) command, an autonomous adjustment made by the UE, or a combination thereof.

[0279] Clause 97. A non-transitory computer-readable medium pursuant to any one of Clauses 85 to 96, wherein the one or more criteria comprise a difference in measurements between: (i) the UE reception timing associated with the first subframe including the first PRS from the other device, and (iii) the second UE transmission timing of the third subframe.

[0280] Clause 98. The non-transitory computer-readable medium as described in Clause 97, wherein one or more of the rules include: selecting the first SL Rx-Tx time difference measurement type when the measurement difference exceeds a measurement difference threshold, and selecting the second SL Rx-Tx time difference measurement type when the measurement difference does not exceed the measurement difference threshold.

[0281] Clause 99. A nontransitory computer-readable medium pursuant to any one of Clauses 85 to 98, wherein the one or more criteria, the one or more rules, or both comprise at least one criterion, at least one rule, or both, and the at least one criterion, the at least one rule, or both are: defined, or configured prior to initiating a location session of the UE, or configured by the location estimation entity, network component, or another UE for the location session, or any combination thereof.

[0282] Clause 100. A nontransitory computer-readable medium pursuant to any one of Clauses 85 to 99, wherein the determined SL Rx-Tx time difference measurement type is associated with a resource pool, or wherein the determined SL Rx-Tx time difference measurement type is associated with an SL-PRS resource or an SL-PRS resource set.

[0283] Clause 101. A non-transitory computer-readable medium pursuant to any one of Clauses 85 to 100, wherein the determination is performed autonomously at the UE based on the one or more rules associated with the one or more criteria, and wherein the measurement report includes an indication of the determined SL Rx-Tx time difference measurement type.

[0284] Clause 102. The non-transitory computer-readable medium as described in Clause 101, wherein the indication of the determined SL Rx-Tx time difference measurement type is based on whether the measurement information includes a timestamp associated with the UE transmission timing.

[0285] Clause 103. The non-transitory computer-readable medium as described in Clause 102, wherein if the measurement information includes the timestamp, the indication indicates the first SL Rx-Tx time difference measurement type, and wherein if the measurement information does not include the timestamp, the indication indicates the second SL Rx-Tx time difference measurement type.

[0286] Clause 104. A non-transitory computer-readable medium pursuant to any one of Clauses 85 to 103, wherein all measurement information in the measurement report is associated with a determined SL Rx-Tx time difference measurement type, or wherein the measurement report further includes additional measurement information based on at least one SL Rx-Tx time difference measurement of a corresponding SL Rx-Tx time difference measurement type other than the determined SL Rx-Tx time difference measurement type.

[0287] Clause 105. A non-transitory computer-readable medium pursuant to any one of Clauses 85 to 104, wherein the determined SL Rx-Tx time difference measurement type is the first SL Rx-Tx time difference measurement type.

[0288] Clause 106. The non-transitory computer-readable medium as described in Clause 105, wherein for each of the one or more SL Rx-Tx time difference measurements according to the first SLRx-Tx time difference measurement type: the first PRS and the second PRS are SL-PRS, or the first PRS is a downlink PRS (DL-PRS) and the second PRS is an SL-PRS, or the first PRS is an SL-PRS and the second PRS is an uplink (UL-PRS).

[0289] Clause 107. A non-transitory computer-readable medium pursuant to any one of Clauses 85 to 106, wherein the determined SL Rx-Tx time difference measurement type is the second SL Rx-Tx time difference measurement type.

[0290] Clause 108. A non-transitory computer-readable medium according to any one of Clauses 105 to 107, wherein, for each of the one or more SL Rx-Tx time difference measurements according to the second SL Rx-Tx time difference measurement type: the first PRS is an SL-PRS and the third subframe is configured for SL, or the first PRS is a downlink PRS (DL-PRS) and the third subframe is configured for SL, or the first PRS is an SL-PRS and the third subframe is configured for uplink (UL).

[0291] Clause 109. A non-transitory computer-readable medium storing computer-executable instructions, which, when executed by a positioning estimation entity, cause the positioning estimation entity to: indicate a receiving capability, the capability indication instructing a user equipment (UE) to perform a first side-link (SL) receive-transmit (Rx-Tx) time difference measurement type and a second SL Rx-Tx time difference measurement type to the positioning estimation entity, wherein the first SL Rx-Tx time difference measurement type is based on a first time difference between: (i) a UE receiving timing associated with a first subframe including a first positioning reference signal (PRS) from another device, and (ii) a first UE transmitting timing including a second subframe including a second PRS transmitted by the UE, and wherein the second SL Rx-Tx time difference measurement type is based on a second time difference between: (i) the UE receiving timing associated with the first subframe including the first PRS from the other device, and (iii) a second UE transmitting timing following the first subframe and being temporally closest to the first subframe; and transmit one or more SLs for the UE. The measurement request for Rx-Tx time difference measurement; receiving a measurement report, the measurement report including measurement information based on one or more SL Rx-Tx time difference measurements; and determining whether the measurement information is based on the first SL Rx-Tx time difference measurement type or the second SL Rx-Tx time difference measurement type.

[0292] Clause 110. The non-transitory computer-readable medium as described in Clause 109, wherein the determination is based on which of the first SL Rx-Tx time difference measurement type or the second SL Rx-Tx time difference measurement type is explicitly specified to the UE by the positioning estimation entity, or wherein the determination is based on an indication in the measurement report.

[0293] Clause 111. The non-transitory computer-readable medium according to any one of Clauses 109 to 110 further includes computer-executable instructions that, when executed by the positioning estimation entity, cause the positioning estimation entity to: preset one or more rules for the UE, the one or more rules being associated with one or more criteria for autonomous SL Rx-Tx time difference measurement type selection at the UE.

[0294] Clause 112. A non-transitory computer-readable medium according to any one of Clauses 109 to 111, wherein the determined SL Rx-Tx time difference measurement type is the first SL Rx-Tx time difference measurement type, and for each of the one or more SL Rx-Tx time difference measurements according to the first SL Rx-Tx time difference measurement type: the first PRS and the second PRS are SL-PRS, or the first PRS is a downlink PRS (DL-PRS) and the second PRS is an SL-PRS, or the first PRS is an SL-PRS and the second PRS is an uplink PRS (UL-PRS), or wherein the determined SL Rx-Tx time difference measurement type is the second SL Rx-Tx time difference measurement type, and for each of the one or more SL Rx-Tx time difference measurements according to the second SL Rx-Tx time difference measurement type: Rx-Tx time difference measurement: The first PRS is SL-PRS and the third subframe is configured for SL, or the first PRS is DL-PRS and the third subframe is configured for SL, or the first PRS is SL-PRS and the third subframe is configured for UL.

[0295] Those skilled in the art will understand that information and signals can be represented using any of a variety of different techniques and methods. For example, data, instructions, commands, information, signals, bits, symbols, and chips that may be mentioned throughout the above description can be represented by voltage, current, electromagnetic waves, magnetic fields or magnetic particles, light fields or optical particles, or any combination thereof.

[0296] Furthermore, those skilled in the art will understand that the various exemplary logic blocks, modules, circuits, and algorithm steps described in connection with the aspects disclosed herein can be implemented as electronic hardware, computer software, or a combination of both. To clearly illustrate this interchangeability between hardware and software, various exemplary components, blocks, modules, circuits, and steps have been described above in general terms of their functionality. Whether such functionality is implemented as hardware or software depends on the specific application and the design constraints imposed on the overall system. Those skilled in the art may implement the described functionality in different ways for each specific application, but such specific implementation decisions should not be construed as departing from the scope of this disclosure.

[0297] The various exemplary logic blocks, modules, and circuits described in conjunction with the aspects disclosed herein may be implemented or performed using a general-purpose processor, a digital signal processor (DSP), an ASIC, a field-programmable gate array (FPGA) or other programmable logic device, discrete gate or transistor logic components, discrete hardware components, or any combination thereof designed to perform the functions described herein. The general-purpose processor may be a microprocessor, but in alternative embodiments, the processor may be any conventional processor, controller, microcontroller, or state machine. The processor may also be implemented as a combination of computing devices, such as a combination of a DSP and a microprocessor, multiple microprocessors, one or more microprocessors combined with a DSP core, or any other such configuration.

[0298] The methods, sequences, and / or algorithms described in conjunction with the aspects disclosed herein may be embodied directly in hardware, in a software module executed by a processor, or a combination of both. The software module may reside in random access memory (RAM), flash memory, read-only memory (ROM), erasable programmable ROM (EPROM), electrically erasable programmable ROM (EEPROM), registers, hard disks, removable disks, CD-ROMs, or any other form of storage medium known in the art. Example storage media are coupled to a processor such that the processor can read information from and write information to the storage medium. Alternatively, the storage medium may be integral with the processor. The processor and storage medium may reside in an ASIC. The ASIC may reside in a user terminal (e.g., a UE). Alternatively, the processor and storage medium may reside as discrete components in the user terminal.

[0299] In one or more examples, the described functionality may be implemented in hardware, software, firmware, or any combination thereof. If implemented in software, the functionality may be stored as one or more instructions or code on or transmitted via a computer-readable medium. A computer-readable medium includes both computer storage media and communication media, which includes any medium that facilitates the transfer of a computer program from one place to another. A storage medium may be any available medium accessible to a computer. By way of example and not limitation, such computer-readable media may include RAM, ROM, EEPROM, CD-ROM or other optical disc storage, disk storage or other magnetic storage devices, or any other medium that can be used to carry or store the desired program code in the form of instructions or data structures and is accessible to a computer. Furthermore, any connection is appropriately referred to as a computer-readable medium. For example, if the software is transmitted from a website, server, or other remote source using coaxial cable, fiber optic cable, twisted pair, digital subscriber line (DSL), or wireless technologies such as infrared, radio, and microwave, then coaxial cable, fiber optic cable, twisted pair, DSL, or wireless technologies such as infrared, radio, and microwave are included within the definition of a medium. As used herein, disks and optical discs include: compact optical discs (CDs), laser discs, optical discs, digital versatile discs (DVDs), floppy disks, and Blu-ray discs. Disks typically reproduce data magnetically, while optical discs reproduce data optically using lasers. Combinations of these should also be included within the scope of computer-readable media.

[0300] While the foregoing disclosure illustrates exemplary aspects of this disclosure, it should be noted that various changes and modifications may be made herein without departing from the scope of this disclosure as defined by the appended claims. Furthermore, the functions, steps, and / or actions of the method claims according to the aspects of this disclosure described herein need not be performed in any particular order. Moreover, although elements of this disclosure may be described or claimed in the singular, the plural form may also be considered unless expressly stated as limited to the singular.

Claims

1. A method for operating user equipment (UE), the method comprising: The capability indication indicates that the UE is capable of performing a first side-link (SL) receive-transmit (Rx-Tx) time difference measurement type and a second SL Rx-Tx time difference measurement type to the positioning estimation entity. The first SL Rx-Tx time difference measurement type is based on a first time difference between the following two items: (i) the UE reception timing associated with a first subframe including a first positioning reference signal (PRS) from another device, and (ii) the first UE transmission timing of a second subframe including a second PRS transmitted by the UE. The second SL Rx-Tx time difference measurement type is based on a second time difference between the following two items: (i) the UE reception timing associated with the first subframe including the first PRS from the other device, and (iii) the second UE transmission timing of the third subframe that is after the first subframe and is closest in time to the first subframe. Receive a measurement request to perform one or more SL Rx-Tx time difference measurements for the UE; and Determine whether to perform the one or more SL Rx-Tx time difference measurements based on either the first SL Rx-Tx time difference measurement type or the second SL Rx-Tx time difference measurement type. The determination is based on an explicit network specification of the SL Rx-Tx time difference measurement type associated with the measurement request, or... The determination includes an autonomous selection at the UE based on one or more rules associated with one or more criteria; Perform one or more SL Rx-Tx time difference measurements according to the determined SL Rx-Tx time difference measurement type; as well as A measurement report is sent to the positioning estimation entity, the measurement report including measurement information based on the one or more SL Rx-Tx time difference measurements.

2. The method of claim 1, wherein the determination is based on the explicit network-specified SL Rx-Tx time difference measurement type associated with the measurement request.

3. The method of claim 1, wherein the one or more rules comprise: If the measurement request is not associated with the explicitly specified network-specified SL Rx-Tx time difference measurement type, the default SL Rx-Tx time difference measurement type is selected.

4. The method of claim 1, wherein the one or more criteria include the time difference between the first subframe and the second subframe.

5. The method of claim 4, wherein the one or more rules comprise: If the time difference exceeds the time difference threshold, select the first SL Rx-Tx time difference measurement type, and If the time difference does not exceed the time difference threshold, select the second SL Rx-Tx time difference measurement type.

6. The method of claim 1, wherein the one or more criteria include UE mobility.

7. The method of claim 6, wherein the one or more rules comprise: If the UE mobility exceeds the UE mobility threshold, select the first SL Rx-Tx time difference measurement type, and If the UE mobility does not exceed the UE mobility threshold, select the second SL Rx-Tx time difference measurement type.

8. The method of claim 1, wherein the one or more criteria include a reference signal received power (RSRP) variation.

9. The method of claim 8, wherein the one or more rules comprise: If the RSRP change exceeds the RSRP change threshold, select the first SL Rx-Tx time difference measurement type, and If the RSRP change does not exceed the RSRP change threshold, select the second SL Rx-Tx time difference measurement type.

10. The method of claim 1, wherein the one or more criteria include a timed variation parameter.

11. The method of claim 10, wherein the one or more rules comprise: When performing timing variations, select the first SL Rx-Tx time difference measurement type, and Without performing the timing change, select the second SL Rx-Tx time difference measurement type.

12. The method of claim 10, wherein the timing change parameter is associated with a timing change in response to a timing advance (TA) command, an autonomous adjustment performed by the UE, or a combination thereof.

13. The method of claim 1, wherein the one or more criteria include the difference between the following two measurements: (i) the UE reception timing associated with the first subframe including the first PRS from the other device, and (iii) the second UE transmission timing of the third subframe.

14. The method of claim 13, wherein the one or more rules comprise: If the measured difference exceeds the measured difference threshold, select the first SL Rx-Tx time difference measurement type, and If the difference in the measured values ​​does not exceed the threshold value for the difference in the measured values, the second SL Rx-Tx time difference measurement type is selected.

15. The method of claim 1, wherein the one or more criteria, the one or more rules, or both comprise at least one criterion, at least one rule, or both, and the at least one criterion, the at least one rule, or both are: Predefined, or Pre-configured before initiating the location session for the UE, or The location estimation entity, network component, or another UE is configured for the location session, or Any combination of them.

16. The method according to claim 1, The determined SL Rx-Tx time difference measurement type is associated with the resource pool, or The identified SL Rx-Tx time difference measurement type is associated with SL-PRS resources or SL-PRS resource sets.

17. The method according to claim 1, The determination mentioned above is performed autonomously at the UE based on the one or more rules associated with the one or more criteria, and The measurement report includes an indication of the determined SL Rx-Tx time difference measurement type.

18. The method of claim 17, wherein the indication of the determined SL Rx-Tx time difference measurement type is based on whether the measurement information includes a timestamp associated with the UE transmission timing.

19. The method according to claim 18, If the measurement information includes the timestamp, then the indication indicates the first SL Rx-Tx time difference measurement type, and If the measurement information does not include the timestamp, then the indication indicates the second SL Rx-Tx time difference measurement type.

20. The method according to claim 1, All measurement information in the measurement report is associated with the determined SL Rx-Tx time difference measurement type, or The measurement report also includes additional measurement information based on at least one SL Rx-Tx time difference measurement of a corresponding SL Rx-Tx time difference measurement type other than the determined SL Rx-Tx time difference measurement type.

21. The method of claim 1, wherein the determined SL Rx-Tx time difference measurement type is the first SL Rx-Tx time difference measurement type.

22. The method of claim 21, wherein, For each of the one or more SL Rx-Tx time difference measurements according to the first SL Rx-Tx time difference measurement type: The first PRS and the second PRS are SL-PRS, or The first PRS is a downlink PRS (DL-PRS) and the second PRS is an SL-PRS, or The first PRS is an SL-PRS and the second PRS is an uplink (UL-PRS).

23. The method of claim 1, wherein the determined SL Rx-Tx time difference measurement type is the second SL Rx-Tx time difference measurement type.

24. The method of claim 21, wherein, For each of the one or more SL Rx-Tx time difference measurements according to the second SL Rx-Tx time difference measurement type: The first PRS is an SL-PRS and the third subframe is configured for SL, or The first PRS is a downlink PRS (DL-PRS) and the third subframe is configured for SL, or The first PRS is an SL-PRS and the third subframe is configured for uplink (UL).

25. A method for locating and estimating an entity, the method comprising: The capability indication indicates that the user equipment (UE) is capable of performing a first side-link (SL) receive-transmit (Rx-Tx) time difference measurement type and a second SL Rx-Tx time difference measurement type to the positioning estimation entity. The first SL Rx-Tx time difference measurement type is based on a first time difference between the following two items: (i) the UE reception timing associated with a first subframe including a first positioning reference signal (PRS) from another device, and (ii) the first UE transmission timing of a second subframe including a second PRS transmitted by the UE. The second SL Rx-Tx time difference measurement type is based on a second time difference between the following two items: (i) the UE reception timing associated with the first subframe including the first PRS from the other device, and (iii) the second UE transmission timing of the third subframe that is after the first subframe and is closest in time to the first subframe. Send a measurement request to perform one or more SL Rx-Tx time difference measurements for the UE; Receive a measurement report, the measurement report including measurement information based on one or more SL Rx-Tx time difference measurements; and Determine whether the measurement information is based on the first SL Rx-Tx time difference measurement type or the second SL Rx-Tx time difference measurement type.

26. The method according to claim 25, The determination is based on whether the positioning estimation entity explicitly specifies to the UE either the first SL Rx-Tx time difference measurement type or the second SL Rx-Tx time difference measurement type, or The determination is based on the indications in the measurement report.

27. The method of claim 25, further comprising: One or more rules are pre-configured for the UE, and the one or more rules are associated with one or more criteria for autonomous SL Rx-Tx time difference measurement type selection at the UE.

28. The method according to claim 25, in, The determined SL Rx-Tx time difference measurement type is the first SL Rx-Tx time difference measurement type, and for each SL Rx-Tx time difference measurement in the one or more SL Rx-Tx time difference measurements according to the first SL Rx-Tx time difference measurement type: the first PRS and the second PRS are SL-PRS, or the first PRS is a downlink PRS (DL-PRS) and the second PRS is an SL-PRS, or the first PRS is an SL-PRS and the second PRS is an uplink (UL-PRS), or Wherein, the determined SL Rx-Tx time difference measurement type is the second SL Rx-Tx time difference measurement type, and for each SL Rx-Tx time difference measurement in the one or more SL Rx-Tx time difference measurements according to the second SL Rx-Tx time difference measurement type: the first PRS is SL-PRS and the third subframe is configured for SL, or the first PRS is DL-PRS and the third subframe is configured for SL, or the first PRS is SL-PRS and the third subframe is configured for UL.

29. A user equipment (UE), the user equipment (UE) comprising: Memory; and At least one processor, communicatively coupled to the memory, the at least one processor being configured to: The capability indication indicates that the UE is capable of performing a first side-link (SL) receive-transmit (Rx-Tx) time difference measurement type and a second SL Rx-Tx time difference measurement type to the positioning estimation entity. The first SL Rx-Tx time difference measurement type is based on a first time difference between the following two items: (i) the UE reception timing associated with a first subframe including a first positioning reference signal (PRS) from another device, and (ii) the first UE transmission timing of a second subframe including a second PRS transmitted by the UE. The second SL Rx-Tx time difference measurement type is based on a second time difference between the following two items: (i) the UE reception timing associated with the first subframe including the first PRS from the other device, and (iii) the second UE transmission timing of the third subframe that is after the first subframe and is closest in time to the first subframe. Receive a measurement request to perform one or more SL Rx-Tx time difference measurements for the UE; and Determine whether to perform the one or more SL Rx-Tx time difference measurements based on either the first SL Rx-Tx time difference measurement type or the second SL Rx-Tx time difference measurement type. The determination is based on an explicit network specification of the SL Rx-Tx time difference measurement type associated with the measurement request, or... The determination includes an autonomous selection at the UE based on one or more rules associated with one or more criteria; Perform one or more SL Rx-Tx time difference measurements according to the determined SL Rx-Tx time difference measurement type; as well as A measurement report is sent to the positioning estimation entity, the measurement report including measurement information based on the one or more SL Rx-Tx time difference measurements.

30. A location estimation entity, the location estimation entity comprising: Memory; and At least one processor, communicatively coupled to the memory, the at least one processor being configured to: The capability indication indicates that the user equipment (UE) is capable of performing a first side-link (SL) receive-transmit (Rx-Tx) time difference measurement type and a second SL Rx-Tx time difference measurement type to the positioning estimation entity. The first SL Rx-Tx time difference measurement type is based on a first time difference between the following two items: (i) the UE reception timing associated with a first subframe including a first positioning reference signal (PRS) from another device, and (ii) the first UE transmission timing of a second subframe including a second PRS transmitted by the UE. The second SL Rx-Tx time difference measurement type is based on a second time difference between the following two items: (i) the UE reception timing associated with the first subframe including the first PRS from the other device, and (iii) the second UE transmission timing of the third subframe that is after the first subframe and is closest in time to the first subframe. Send a measurement request to perform one or more SL Rx-Tx time difference measurements for the UE; Receive a measurement report, the measurement report including measurement information based on one or more SL Rx-Tx time difference measurements; and Determine whether the measurement information is based on the first SL Rx-Tx time difference measurement type or the second SL Rx-Tx time difference measurement type.

Images