Timing information exchange for enhanced sidelink positioning

Abstract

Timing information exchange for enhanced sidelink positioning is described. An apparatus is configured to identify a synchronization reference type of a synchronization reference source based on synchronization of the UE with the synchronization reference source. The apparatus is configured to provide a first indication of the synchronization reference type to at least one of the LMF or another UE, the quality metric or the time of change therefrom as a basis for communication. Another apparatus is configured to receive, from at least one of the LMF or another UE, at least one of a first indication of a synchronization reference type of a synchronization reference source associated with synchronization of the UE, a quality metric, or a time of change. The apparatus is configured to communicate based on the first indication of the synchronization reference type, the quality metric, or the change time.

Description

Cross-reference to related applications

[0001] This application claims the benefit and priority of Greek patent application No. 20230100671, filed on August 10, 2023, entitled “TIMING INFORMATION EXCHANGE FORENHANCED SIDELINK POSITIONING”, the entire contents of which are expressly incorporated herein by reference. Technical Field

[0002] This disclosure relates generally to communication systems, and more specifically to wireless communication utilizing location. Background Technology

[0003] Wireless communication systems are widely deployed to provide a variety of telecommunications services, such as telephone, video, data, messaging, and broadcasting. Typical wireless communication systems may employ multiple access technologies capable of supporting communication with multiple users by sharing available system resources. Examples of such multiple access technologies include Code Division Multiple Access (CDMA) systems, Time Division Multiple Access (TDMA) systems, Frequency Division Multiple Access (FDMA) systems, Orthogonal Frequency Division Multiple Access (OFDMA) systems, Single Carrier Frequency Division Multiple Access (SC-FDMA) systems, and Time Division Synchronous Code Division Multiple Access (TD-SCDMA) systems.

[0004] These multiple access technologies have been adopted in various telecommunications standards to provide a common protocol that enables different wireless devices to communicate at the city, national, regional, and even global levels. An example telecommunications standard is 5G New Radio (NR). 5G NR is part of the Continuous Evolution of Mobile Broadband (CEM) program issued by the 3rd Generation Partnership Project (3GPP) to meet new requirements associated with latency, reliability, security, scalability (e.g., with the Internet of Things (IoT),) and other requirements. 5G NR includes services associated with enhanced mobile broadband (eMBB), massive machine-type communications (mMTC), and ultra-reliable low-latency communications (URLLC). Some aspects of 5G NR can be based on the 4G Long Term Evolution (LTE) standard. Further improvements to 5G NR technology are needed. Furthermore, these improvements can also be applied to other multiple access technologies and telecommunications standards that adopt these technologies. Summary of the Invention

[0005] The following presents a simplified summary of one or more aspects of the invention to provide a basic understanding of these aspects. This overview is not a comprehensive review of all conceived aspects. It neither identifies key or essential elements of all aspects nor describes the scope of any or all aspects. Its sole purpose is to present some concepts of one or more aspects in a simplified form as a prelude to the more detailed descriptions that follow.

[0006] In one aspect of this disclosure, a method, a computer-readable medium, and an apparatus are provided. The apparatus may include user equipment (UE), and the method may be performed at the UE. The apparatus is configured to identify a synchronization reference type of a synchronization reference source based on synchronization between the first UE and the synchronization reference source, wherein the synchronization reference type is one or more of the following: Global Navigation Satellite System (GNSS), network node, or synchronization reference UE. The apparatus is further configured to detect a change in time associated with an anchor entity, wherein the change in time includes at least one of the following: a first time since the last synchronization update, a second time of the last synchronization update, or a correction amount corrected in one or more last synchronization updates. The apparatus is further configured to provide at least one of the following to a location management function (LMF) or a second UE: a first indication of the synchronization reference type of the synchronization reference source, a quality metric, or the change in time.

[0007] In this respect, the method includes identifying the synchronization reference type of the synchronization reference source based on the synchronization between the first UE and the synchronization reference source, wherein the synchronization reference type is one or more of the following: GNSS, network node, or synchronization reference UE. The method also includes detecting a change time associated with an anchor entity, wherein the change time includes at least one of the following: a first time since the last synchronization update, a second time of the last synchronization update, or a correction amount corrected in one or more last synchronization updates. The method further includes providing at least one of the following to the LMF or the second UE: a first indication of the synchronization reference type of the synchronization reference source, a quality metric, or the change time.

[0008] In another aspect of this disclosure, a method, computer-readable medium, and apparatus are provided. The apparatus may include a UE, and the method may be performed at the UE. The apparatus is configured to receive from at least one of an LMF or a second UE at a synchronization reference source at a first indication, a quality metric, or a change time, wherein the synchronization reference type is associated with the synchronization of the first UE with the synchronization reference source and is one or more of the following: GNSS, a network node, or a synchronization reference UE, wherein the change time is associated with an anchor entity and includes at least one of the following: a first time since the last synchronization update, a second time of the last synchronization update, or a correction amount corrected in one or more last synchronization updates. The apparatus is also configured to communicate based on at least one of the first indication, the quality metric, or the change time of the synchronization reference type for the synchronization reference source.

[0009] In this respect, the method includes receiving from at least one of an indication of a synchronization reference type, a quality metric, or a change time for a synchronization reference source, a synchronization reference type associated with the synchronization of the first UE with the synchronization reference source, and being one or more of the following: GNSS, a network node, or a synchronization reference UE, wherein the change time is associated with an anchor entity and includes at least one of the following: a first time since the last synchronization update, a second time of the last synchronization update, or a correction amount corrected in one or more last synchronization updates. The method also includes communicating based on at least one of the first indication, the quality metric, or the change time for the synchronization reference source.

[0010] To achieve the foregoing and related objectives, one or more aspects may include the features fully described below and specifically pointed out in the claims. The following description and drawings set forth some exemplary features of one or more aspects in detail. However, these features indicate only a few of the various ways in which the principles of the various aspects may be employed. Attached Figure Description

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

[0012] Figure 2A This is an illustration of an example of the first frame according to various aspects of this disclosure.

[0013] Figure 2B This is a diagram illustrating examples of downlink (DL) channels within a subframe according to various aspects of this disclosure.

[0014] Figure 2C This is an illustration of an example of a second frame according to various aspects of this disclosure.

[0015] Figure 2D This is a diagram illustrating examples of uplink (UL) channels within a subframe according to various aspects of this disclosure.

[0016] Figure 3 This is a diagram illustrating examples of base stations and user equipment (UEs) in an access network.

[0017] Figure 4 This is a diagram illustrating an example of UE positioning based on reference signal measurements.

[0018] Figure 5 This is a diagram illustrating an example of UE positioning based on reference signal measurements and quality metrics.

[0019] Figure 6 This is a call flow diagram for wireless communication based on various aspects of this disclosure.

[0020] Figure 7 This is a diagram illustrating examples of timing information exchange for enhanced sidelink positioning according to various aspects of this disclosure.

[0021] Figure 8 This is a call flow diagram for wireless communication based on various aspects of this disclosure.

[0022] Figure 9 This is a flowchart of a wireless communication method according to various aspects of this disclosure.

[0023] Figure 10 This is a flowchart of a wireless communication method according to various aspects of this disclosure.

[0024] Figure 11 This is a flowchart of a wireless communication method according to various aspects of this disclosure.

[0025] Figure 12 This is a flowchart of a wireless communication method according to various aspects of this disclosure.

[0026] Figure 13 These are illustrations illustrating specific hardware implementations used for example devices and / or network entities.

[0027] Figure 14 This is a diagram illustrating an example of a hardware implementation used for an example network entity.

[0028] Figure 15 This is a diagram illustrating an example of a hardware implementation used for an example network entity. Detailed Implementation

[0029] Wireless communication networks (such as LTE networks and / or 5G NR networks, and other examples of wireless communication networks) can be designed to support the location of wireless devices. For example, based on reference signal communication between an anchor entity (e.g., a network node, base station, eNB, gNB, Transmit / Receive Point (TRP), etc.) and a wireless device, the UE can use the Time Difference of Arrival (TDoA) associated with that reference signal communication to determine the location / positioning of the wireless device. As an example of TDoA, a wireless device can locate itself or another wireless device based on the time difference of arrival of a positioning reference signal. In an uplink-like TDoA, the wireless device can transmit a Positioning Reference Signal (PRS), and the anchor entities can report the time they receive the PRS back to the wireless device, and the location of the wireless device can be calculated based on the difference between the arrival times and the anchor entity's location. In a downlink-like TDoA, multiple anchor entities can transmit PRS, the wireless device can receive those PRS transmissions, and the location of the wireless device can be calculated based on the time difference of arrival and the anchor entity's location. In UE-to-Universal Mobile Telecommunications System (UMTS) Terrestrial Radio Access Network (UTRAN) (Uu) interface localization, anchor entities can report a quality metric for the relative time difference between themselves and a synchronization reference source. This quality metric can be associated with a relative time difference (RTD), for example, the rtd-Quality field in the RTD-InfoElement, which can be used for anchor entity selection.

[0030] However, if the anchor entity is not fully synchronized with its synchronization reference source (e.g., a Global Navigation Satellite System (GNSS), network node, and / or independent synchronization reference UE, etc.), uncertainties may be introduced into arrival time and time difference measurements, which in turn may introduce uncertainties into the calculated position. For example, the anchor entity may be synchronized with the synchronization reference source, and this synchronization may shift by a certain amount of time over a period of time, within which corrections should be applied to avoid synchronization errors. However, the examples used for synchronization error management do not provide mitigation of the effects caused by synchronization errors between anchor UEs in side-link (SL) TDoA measurements.

[0031] Various aspects are generally related to wireless network positioning. Some aspects more specifically relate to the exchange of timing information for enhanced sidelink positioning. In some examples, synchronization information is exchanged according to aspects used to mitigate the impact of synchronization errors between anchor UEs in, for example, SL-based TDoA measurements. In some examples, methods and apparatus are provided to exchange synchronization information of anchor UEs between a UE and an LMF or another UE, and this synchronization information may be associated with a synchronization reference source, RTD, synchronization quality information, synchronization reference type, and / or change time, etc. In one example, a first UE may be configured to identify the synchronization reference type of the synchronization reference source based on the synchronization of the first UE with the synchronization reference source, wherein the synchronization reference type is one or more of the following: GNSS, network node, or independent synchronization reference UE. The first UE may also be configured to detect change time associated with the anchor entity, wherein the change time includes at least one of the following: a first time since the last synchronization update, a second time of the last synchronization update, or a correction amount corrected in one or more last synchronization updates. The first UE may also be configured to provide at least one of the LMF or the second UE with a first indication of the synchronization reference type for the synchronization reference source or at least one of the change time. In another example, the first UE may be configured to receive from at least one of the LMF or the second UE a first indication of the synchronization reference type for the synchronization reference source or at least one of the change time, wherein the synchronization reference source is associated with the synchronization of the first UE with the synchronization reference source and is one or more of the following: GNSS, network node, or independent synchronization reference UE, wherein the change time is associated with an anchor entity and includes at least one of the following: a first time since the last synchronization update, a second time of the last synchronization update, or a correction amount corrected in one or more last synchronization updates. The first UE may also be configured to communicate based on the first indication of the synchronization reference type for the synchronization reference source and the change time.

[0032] Specific aspects of the subject matter described in this disclosure can be implemented to achieve one or more of the following potential advantages. In one example, by providing the synchronization reference type and change time for the synchronization reference source for both the LMF and SL UE, the described technique can be used to correct synchronization errors between anchor UEs in SL positioning measurements. In another example, by correcting such synchronization errors, the described technique can be used to improve the positioning accuracy of wireless devices in a wireless communication network.

[0033] The detailed descriptions following, illustrated with reference to the accompanying drawings, describe various configurations and do not represent the only configurations in which the concepts described herein can be practiced. To provide a thorough understanding of the various concepts, the detailed descriptions include specific details. However, these concepts can be practiced without these specific details. In some instances, well-known structures and components are shown in block diagram form to avoid obscuring such concepts.

[0034] Various apparatuses and methods are presented with reference to several aspects of a telecommunications system. These apparatuses and methods are described in detail below and illustrated in the accompanying drawings by various blocks, components, circuits, processes, algorithms, etc. (collectively, “elements”). These elements can be implemented using electronic hardware, computer software, or any combination thereof. Whether such elements are implemented as hardware or software depends on the specific application and the design constraints imposed on the system as a whole.

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

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

[0037] While aspects, implementations, and / or use cases are described herein by way of example, additional or different aspects, implementations, and / or use cases may arise in many different arrangements and scenarios. The aspects, implementations, and / or use cases described herein can be implemented across many different platform types, devices, systems, shapes, sizes, and package arrangements. For example, aspects, implementations, and / or use cases may arise via integrated chip implementations and other devices based on non-modular components (e.g., end-user devices, vehicles, communication devices, computing devices, industrial equipment, retail / purchasing devices, medical devices, AI-enabled devices, etc.). While some examples may or may not be specific to a use case or application, the described examples may exhibit broad applicability. Aspects, implementations, and / or use cases can range from chip-level or modular components to non-modular, non-chip-level implementations, and further to aggregated, distributed, or original equipment manufacturer (OEM) devices or systems incorporating one or more of the technologies described herein. In some practical settings, devices incorporating the described aspects and features may also include additional components and features for implementing and practicing the claimed and described aspects. For example, the transmission and reception of wireless signals necessarily involve multiple components for analog and digital purposes (e.g., hardware components including antennas, RF chains, power amplifiers, modulators, buffers, processors, interleavers, adders / summers, etc.). The techniques described herein can be practiced in a wide variety of devices, chip-level components, systems, distributed arrangements, aggregated or decomposed components, end-user equipment, etc., of various sizes, shapes, and configurations.

[0038] 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, radio access network (RAN) nodes, core network nodes, network elements or network equipment (such as base stations (BS)), or one or more units (or components) performing base station functionality can be implemented in aggregated or decomposed architectures. For example, BSs (such as Node B (NB), evolved NB (eNB), NR BS, 5G NB, access point (AP), transmit / receive point (TRP), or cell, etc.) can be implemented as aggregated base stations (also known as standalone BS or monolithic BS) or decomposed base stations.

[0039] 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 respects, the CU may be implemented within a RAN node, and one or more DUs may co-located with the CU, or alternatively, may be geographically or virtually distributed across one or more other RAN nodes. DUs may be implemented to communicate with one or more RUs. Each of the CUs, DUs, and RUs may be implemented as a virtual unit, namely a virtual central unit (VCU), a virtual distributed unit (VDU), or a virtual radio unit (VRU).

[0040] Base station operation or network design can take into account the aggregation characteristics of base station functionality. For example, decomposed base stations can be utilized in Integrated Access Backhaul (IAB) networks, Open Radio Access Networks (O-RAN (such as network configurations initiated by the O-RAN Alliance)), 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 enables flexibility in network design. The various units of a decomposed base station or decomposed RAN architecture can be configured to communicate wirelessly with at least one other unit.

[0041] Figure 1Figure 100 illustrates an example of a wireless communication system and access network. The illustrated wireless communication system includes a decomposed base station architecture. The decomposed base station architecture may include one or more CUs 110, which may communicate directly with the core network 120 via a backhaul link, or indirectly with the core network 120 via one or more decomposed base station units, such as a near real-time (near-RT) RAN Intelligent Controller (RIC) 125 via an E2 link, or a non-real-time (non-RT) RIC 115 associated with a Service Management and Orchestration (SMO) framework 105, or both. CUs 110 may communicate with one or more DUs 130 via a corresponding midhaul link (such as an F1 interface). DUs 130 may communicate with one or more RUs 140 via a corresponding fronthaul link. RUs 140 may communicate with a corresponding UE 104 via one or more radio frequency (RF) access links. In some implementations, a UE 104 may be served simultaneously by multiple RUs 140.

[0042] Each unit in the cells (i.e., CU 110, DU 130, RU 140, and near-RT RIC 125, non-RT RIC 115, and SMO frame 105) 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 unit in the cells, 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 via wired transmission media or transmit signals to one or more other units. Additionally, these units may include wireless interfaces that may include receivers, transmitters, or transceivers (such as RF transceivers) configured to receive signals via wireless transmission media or transmit signals to one or more other units, or both.

[0043] In some aspects, the CU 110 can host one or more higher-level control functions. Such control functions may include Radio Resource Control (RRC), Packet Data Convergence Protocol (PDCP), Serving Data Adaptation Protocol (SDAP), etc. Each control function can be implemented using an interface configured to signal to other control functions hosted by the CU 110. The CU 110 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 110 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 110 can be implemented to communicate with the DU 130 for network control and signaling, as needed.

[0044] DU 130 may correspond to a logic unit that includes one or more base station functions for controlling the operation of one or more RU 140s. In some aspects, DU 130 may at least partially host one or more of the Radio Link Control (RLC) layer, Media Access Control (MAC) layer, and one or more high physical (PHY) layers (such as modules for forward error correction (FEC) encoding and decoding, scrambling, modulation, demodulation, etc.) according to functional splits (such as those defined by 3GPP). In some aspects, DU 130 may further host one or more low PHY layers. Each layer (or module) may be implemented using an interface configured to communicate signaling with other layers (and modules) hosted by DU 130 or with control functions hosted by CU 110.

[0045] Lower-layer functionality can be implemented by one or more RU 140s. In some deployments, an RU140 controlled by a DU 130 may correspond to a logical node that hosts RF processing functions or low-PHY layer functions (such as performing Fast Fourier Transform (FFT), Inverse FFT (iFFT), digital beamforming, 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 140 may be implemented to handle over-the-air (OTA) communications with one or more UE 104s. In some specific implementations, the real-time and non-real-time aspects of control plane and user plane communications with the RU 140 may be controlled by the corresponding DU 130. In some scenarios, this configuration enables the implementation of the DU 130 and CU 110 in cloud-based RAN architectures such as vRAN architectures.

[0046] SMO framework 105 can be configured to support RAN deployment and provisioning of both non-virtualized and virtualized network elements. For non-virtualized network elements, SMO framework 105 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 105 can be configured to interact with a cloud computing platform such as Open Cloud (O-Cloud) 190 to perform network element lifecycle management (such as instantiating virtualized network elements) via a cloud computing platform interface such as the O2 interface. Such virtualized network elements may include, but are not limited to, CU 110, DU 130, RU 140, and near-RT RIC 125. In some implementations, SMO framework 105 can communicate with the hardware aspects of the 4G RAN (such as Open eNB (O-eNB) 111) via the O1 interface. Additionally, in some implementations, SMO framework 105 can communicate directly with one or more RU 140s via the O1 interface. SMO framework 105 may also include a non-RT RIC 115 configured to support the functionality of SMO framework 105.

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

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

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

[0050] Some UEs 104 can communicate with each other using device-to-device (D2D) communication link 158. D2D communication link 158 can use DL / UL wireless wide area network (WWAN) spectrum. D2D communication link 158 can use one or more sidelink channels, such as Physical Sidelink Broadcast Channel (PSBCH), Physical Sidelink Discovery Channel (PSDCH), Physical Sidelink Shared Channel (PSSCH), and Physical Sidelink Control Channel (PSCCH). D2D communication can be performed through various wireless D2D communication systems, such as Bluetooth. ™ (Bluetooth is a trademark of the Bluetooth Special Interest Group (SIG), and is based on the IEEE 802.11 standard for Wi-Fi.) ™ (Wi-Fi is a trademark of the Wi-Fi Alliance), LTE, or NR.

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

[0052] The electromagnetic spectrum is typically subdivided into various categories, bands, channels, etc., based on frequency / wavelength. In 5G NR, two initial operating bands have been designated as frequency ranges FR1 (410MHz to 7.125GHz) and FR2 (24.25GHz to 52.6GHz). Although a portion of FR1 is greater than 6GHz, in various documents and articles, FR1 is often (interchangeably) referred to as the "sub-6GHz" band. Similar naming issues sometimes occur with FR2, which is often (interchangeably) referred to as the "millimeter wave" band in documents and articles, although this is distinct from the Extremely High Frequency (EHF) band (30GHz to 300GHz) designated as "millimeter wave" by the International Telecommunication Union (ITU).

[0053] The frequencies between FR1 and FR2 are generally referred to as mid-band frequencies. Recent 5G NR studies have identified the operating bands used for these mid-band frequencies as the frequency range designation FR3 (7.125 GHz to 24.25 GHz). Bands falling within FR3 can inherit FR1 and / or FR2 characteristics, thus effectively extending the features of FR1 and / or FR2 to mid-band frequencies. Furthermore, higher frequency bands are currently being explored to extend 5G NR operation beyond 52.6 GHz. For example, three higher operating bands have been identified as the frequency range designations FR2-2 (52.6 GHz - 71 GHz), FR4 (71 GHz - 114.25 GHz), and FR5 (114.25 GHz - 300 GHz). Each of these higher bands falls within the EHF band.

[0054] In view of the above, unless otherwise specifically stated, the term "below 6 GHz" as used herein can broadly refer to frequencies less than 6 GHz, within FR1, or including intermediate frequency band frequencies. Furthermore, unless otherwise specifically stated, the term "millimeter wave" as used herein can broadly refer to frequencies that can include intermediate frequency band frequencies, within FR2, FR4, FR2-2 and / or FR5, or within the EHF band.

[0055] Base station 102 and UE 104 may each include multiple antennas (such as antenna elements, antenna panels, and / or antenna arrays) to facilitate beamforming. Base station 102 may transmit beamformed signals 182 to UE 104 in one or more transmit directions. UE 104 may receive beamformed signals from base station 102 in one or more receive directions. UE 104 may also transmit beamformed signals 184 to base station 102 in one or more transmit directions. Base station 102 may receive beamformed signals from UE 104 in one or more receive directions. Base station 102 / UE 104 may perform beamforming training to determine the optimal receive and transmit directions for each of base station 102 / UE 104. The transmit and receive directions for base station 102 may be the same or different. The transmit and receive directions for UE 104 may be the same or different.

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

[0057] The core network 120 may include Access and Mobility Management Function (AMF) 161, Session Management Function (SMF) 162, User Plane Function (UPF) 163, Unified Data Management (UDM) 164, one or more location servers 168, and other functional entities. AMF 161 is the control node that processes signaling between UE 104 and the core network 120. AMF 161 supports registration management, connection management, mobility management, and other functions. SMF 162 supports session management and other functions. UPF 163 supports packet routing, packet forwarding, and other functions. UDM 164 supports authentication and key agreement (AKA) credential generation, user identity processing, access authorization, and subscription management. One or more location servers 168 are exemplified as including a Gateway Mobile Location Center (GMLC) 165 and a Location Management Function (LMF) 166. However, generally, one or more location servers 168 may include one or more location / positioning servers, which may include one or more of GMLC 165, LMF 166, Position Determination Entity (PDE), Serving Mobile Location Center (SMLC), Mobile Location Center (MPC), etc. GMLC 165 and LMF 166 support UE location services. GMLC 165 provides an interface for clients / applications (e.g., emergency services) to access UE location information. LMF 166 receives measurement and auxiliary information from NG-RAN and UE 104 via AMF 161 to calculate the location of UE 104. NG-RAN may use one or more positioning methods to determine the location of UE 104. Positioning UE 104 may involve signal measurement, location estimation, and optional speed calculation based on these measurements. Signal measurement may be performed by UE 104 and / or base station 102 serving UE 104. The measured signals may be based on one or more of the following: Satellite Positioning System (SPS) 170 (e.g., one or more of Global Navigation Satellite System (GNSS), Global Positioning System (GPS), Non-Terrestrial Network (NTN) or other satellite positioning / location systems), LTE signals, Wireless Local Area Network (WLAN) signals, Bluetooth signals, Terrestrial Beacon System (TBS), sensor-based information (e.g., barometric pressure sensor, motion sensor), NR Enhanced Cell ID (NR E-CID) method, NR signals (e.g., multiple round-trip time (multiple RTT), DL departure angle (DL-AoD), DL time difference of arrival (DL-TDOA), UL time difference of arrival (UL-TDOA), and UL angle of arrival (UL-AoA) positioning) and / or other systems / signals / sensors.

[0058] Examples of UE 104 include cellular phones, smartphones, Session Initiation Protocol (SIP) phones, laptops, personal digital assistants (PDAs), satellite radios, GPS devices, multimedia devices, video devices, digital audio players (e.g., MP3 players), cameras, game consoles, tablet devices, smart devices, wearable devices, vehicles, electricity meters, air pumps, large or small kitchen appliances, healthcare devices, implants, sensors / actuators, displays, or any other similarly functional device. Some UEs in UE 104 may be referred to as IoT devices (e.g., parking meters, air pumps, toasters, vehicles, heart monitors, etc.). UE 104 may also be referred to as a station, mobile station, subscriber station, mobile unit, subscriber unit, wireless unit, remote unit, mobile device, wireless device, wireless communication device, remote device, mobile subscriber station, access terminal, mobile terminal, wireless terminal, remote terminal, mobile phone, user agent, mobile client, client, or some other suitable terminology. In some scenarios, the term UE may also be applied to one or more companion devices, such as in a device constellation arrangement. One or more of these devices may access the network together and / or individually.

[0059] Refer again Figure 1In some respects, UE 104 may have an SL timing information exchange component 198 (“Component 198”), which may be configured to identify the synchronization reference type of a synchronization reference source based on the synchronization between the first UE and the synchronization reference source, wherein the synchronization reference type is one or more of the following: GNSS, network node, or synchronization reference UE. Component 198 may also be configured to detect time changes associated with an anchor entity, wherein the time changes include at least one of the following: a first time since the last synchronization update, a second time of the last synchronization update, or a correction amount corrected in one or more last synchronization updates. Component 198 may also be configured to provide at least one of the synchronization reference type, quality metric, or time change for the synchronization reference source to at least one of the LMF or the second UE. Component 198 may also be configured to identify the satellite constellation associated with the GNSS. Component 198 may also be configured to report a second indication of the satellite constellation to the LMF or the second UE. Component 198 may also be configured to identify cell information associated with the network node. Component 198 may also be configured to report a marker of the cell information to the LMF or the second UE in the first indication. Component 198 may also be configured to identify the S-SSB reception time and the frequency location associated with synchronization with the synchronization reference UE. Component 198 may also be configured to report the reception time and the frequency location to the LMF or the second UE. Component 198 may also be configured to identify cell information associated with the quality metric. Component 198 may also be configured to report a second indication of the cell information to the LMF or the second UE in at least one of the first indication or signaling separate from the first indication. In some aspects, component 198 may be configured to receive from at least one of an LMF or a second UE a first indication of a synchronization reference type, a quality metric, and a change time for a synchronization reference source, wherein the synchronization reference type is associated with the synchronization of the first UE with the synchronization reference source and is one or more of the following: GNSS, a network node, or a synchronization reference UE, wherein the change time is associated with an anchor entity and includes at least one of the following: a first time since the last synchronization update, a second time of the last synchronization update, or a correction amount corrected in one or more last synchronization updates. Component 198 may also be configured to communicate based on at least one of the first indication, the quality metric, or the change time for the synchronization reference source. Component 198 may also be configured to receive from the LMF or the second UE a second indication of a satellite constellation, wherein the satellite constellation is associated with the GNSS. Component 198 may also be configured to receive a marker of cell information from the LMF or the second UE in the first indication, wherein the cell information is associated with the network node.Component 198 may also be configured to receive the S-SSB reception time from the LMF or the second UE and the frequency position associated with synchronization with the synchronization reference UE. Component 198 may also be configured to generate adjusted timing parameters for communication based on at least one of the synchronization reference type or the change time. Component 198 may also be configured to receive a marker of cell information from the LMF or the second UE in at least one of the first indication or signaling separate from the first indication. Component 198 may also be configured to perform positioning calculations based on at least one of the communication or the adjusted timing parameters. In some aspects, base station 102 may have an SL timing information exchange component 199 (“Component 199”) that may be configured to operate in a manner proportionate to component 198. Component 199 may be configured to provide synchronization information to the UE. Component 199 may also be configured to communicate with the UE or at least one of the other UEs based on at least one of the first indication, the quality metric, or the change time of the synchronization reference source. Therefore, various aspects provide methods and apparatus for exchanging synchronization information between anchor UEs to mitigate the impact of synchronization errors in, for example, SL-based TDoA measurements. These aspects provide methods and apparatus for exchanging synchronization information between a UE and an LMF or another UE, and this synchronization information may be associated with a synchronization reference source, RTD, synchronization quality information, synchronization reference type, and / or change time, etc.

[0060] Figure 2A Figure 200 illustrates an example of the first subframe within a 5G NR frame structure. Figure 2B Figure 230 illustrates an example of a DL channel within a 5G NR subframe. Figure 2C Figure 250 is an example of a second subframe within a 5G NR frame structure. Figure 2D Figure 280 illustrates an example of a UL channel within a 5G NR subframe. The 5G NR frame structure can be Frequency Division Duplex (FDD) (where subframes within a specific set of subcarriers (carrier system bandwidth) are dedicated to either DL or UL) or Time Division Duplex (TDD) (where subframes within a specific set of subcarriers (carrier system bandwidth) are dedicated to both DL and UL). Figure 2A , Figure 2CIn the provided example, the 5G NR frame structure is assumed to be TDD, where subframe 4 is configured with slot format 28 (most of which are DL), where D is DL, U is UL, and F is flexible and can be used between DL / UL, and subframe 3 is configured using slot format 1 (all of which are UL). Although subframes 3 and 4 are shown as having slot formats 1 and 28 respectively, any particular subframe can be configured using any of the various available slot formats 0-61. Slot formats 0 and 1 are both DL and UL, respectively. Other slot formats 2-61 include a mixture of DL, UL, and flexible symbols. The slot format is configured for the UE via the received Slot Format Indicator (SFI) (dynamically configured via DL Control Information (DCI) or semi-statically / statically configured via Radio Resource Control (RRC) signaling). Note that the following description also applies to the 5G NR frame structure as TDD.

[0061] Figures 2A to 2D The frame structure is illustrated, and aspects of this disclosure are applicable to other wireless communication technologies that may have different frame structures and / or different channels. A frame (10 ms) can be divided into 10 equal-sized subframes (1 ms). Each subframe may include one or more time slots. Subframes may also include micro-time slots, which may include 7, 4, or 2 symbols. Each time slot may include 14 or 12 symbols, depending on whether the cyclic prefix (CP) is normal or extended. For normal CP, each time slot may include 14 symbols, and for extended CP, each time slot may include 12 symbols. Symbols on the DL may be CP Orthogonal Frequency Division Multiplexing (OFDM) (CP-OFDM) symbols. Symbols on the UL may be CP-OFDM symbols (for high-throughput scenarios) or Discrete Fourier Transform (DFT) Extended OFDM (DFT-s-OFDM) symbols (for power-constrained scenarios; limited to single-stream transmission). The number of time slots within a subframe is based on the CP and a parameter set. The parameter set defines the subcarrier spacing (SCS) (see Table 1). The symbol length / duration can be scaled by 1 / SCS.

[0062]

[0063] Table 1: Parameter Set, SCS, and CP

[0064] For a normal CP (14 symbols / slot), different parameter sets µ 0 through 4 allow 1, 2, 4, 8, and 16 slots per subframe, respectively. For an extended CP, parameter set 2 allows 4 slots per subframe. Therefore, for a normal CP and parameter set µ, there are 14 symbols / slot and 2... µ One time slot / subframe. Subcarrier spacing can be equal to ,in The parameter sets are 0 to 4. Therefore, the subcarrier spacing is 15 kHz for parameter set µ=0 and 240 kHz for parameter set µ=4. The symbol length / duration is negatively correlated with the subcarrier spacing. Figures 2A to 2D Examples of a normal frequency division multiplexing (CP) with 14 symbols per time slot and a parameter set of µ=2 with 4 time slots per subframe are provided. The time slot duration is 0.25 ms, the subcarrier spacing is 60 kHz, and the symbol duration is approximately 16.67 μs. Within the frame set, there may be one or more distinct bandwidth portions (BWPs) of frequency division multiplexing (see [link to relevant documentation]). Figure 2B Each BWP can have a specific set of parameters and CP (normal or extended).

[0065] A resource grid can be used to represent the frame structure. Each time slot consists of a resource block (RB) extending for 12 consecutive subcarriers (also known as a physical RB (PRB)). The resource grid is divided into multiple resource elements (REs). The number of bits carried by each RE depends on the modulation scheme.

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

[0067] Figure 2BExamples of various DL channels within a subframe of a frame are illustrated. The Physical Downlink Control Channel (PDCCH) carries the DCI within one or more Control Channel Elements (CCEs) (e.g., 1, 2, 4, 8, or 16 CCEs), each CCE comprising six RE Groups (REGs), each REG comprising 12 coherent REs in the OFDM symbol of the RB. A PDCCH within a BWP can be referred to as a Control Resource Set (CORESET). The UE is configured to monitor PDCCH candidates in the PDCCH search space (e.g., the common search space, the UE-specific search space) during PDCCH monitoring timing on the CORESET, where the PDCCH candidates have different DCI formats and different aggregation levels. Additional BWPs may be located at higher and / or lower frequencies on the channel bandwidth. The Primary Synchronization Signal (PSS) may be located within symbol 2 of a specific subframe of the frame. The PSS is used by the UE 104 to determine subframe / symbol timing and physical layer identification. The Secondary Synchronization Signal (SSS) may be located within symbol 4 of a specific subframe of the frame. The SSS is used by the UE to determine the Physical Layer Cell Identifier Group Number and radio frame timing. Based on the Physical Layer Identifier and the Physical Layer Cell Identifier Group Number, the UE can determine the Physical Cell Identifier (PCI). Based on the PCI, the UE can determine the location of the DM-RS. The Physical Broadcast Channel (PBCH), carrying the Master Information Block (MIB), can be logically grouped with the PSS and SSS to form a Synchronization Signal (SS) / PBCH block (also known as an SS block (SSB)). The MIB provides the number of RBs in the system bandwidth and the System Frame Number (SFN). The Physical Downlink Shared Channel (PDSCH) carries user data, broadcast system information not transmitted via the PBCH (such as System Information Block (SIB)), and paging messages.

[0068] like Figure 2C As illustrated, some REs in the REs carry DM-RS (indicated as R for one particular configuration, but other DM-RS configurations are possible) for channel estimation at the base station. The UE can transmit DM-RS for the Physical Uplink Control Channel (PUCCH) and DM-RS for the Physical Uplink Shared Channel (PUSCH). The PUSCH DM-RS can be transmitted in the first or first two symbols of the PUSCH. Depending on whether a short or long PUCCH is transmitted and depending on the specific PUCCH format used, the PUCCH DM-RS can be transmitted in different configurations. The UE can transmit a Sounding Reference Signal (SRS). The SRS can be transmitted in the last symbol of a subframe. The SRS can have a comb structure, and the UE can transmit the SRS on one of the comb teeth. The SRS can be used by the base station for channel quality estimation to enable frequency-dependent scheduling of the UL.

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

[0070] Figure 3 This is a block diagram illustrating communication between base station 310 and UE 350 in the access network. In the DL, Internet Protocol (IP) packets can be provided to controller / processor 375. Controller / processor 375 implements Layer 3 and Layer 2 functionality. Layer 3 includes the Radio Resource Control (RRC) layer, and Layer 2 includes the Service Data Adaptation Protocol (SDAP) layer, Packet Data Convergence Protocol (PDCP) layer, Radio Link Control (RLC) layer, and Media Access Control (MAC) layer. The controller / processor 375 provides RRC layer functionality associated with broadcasting system information (e.g., MIB, SIB), RRC connection control (e.g., RRC connection paging, RRC connection establishment, RRC connection modification, and RRC connection release), inter-Radio Access Technology (RAT) mobility, and measurement configuration for UE measurement reporting; PDCP layer functionality associated with header compression / decompression, security (encryption, decryption, integrity protection, integrity verification), and handover support functions; RLC layer functionality associated with the delivery of upper-layer packet data units (PDUs), error correction via 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, multiplexing of MAC SDUs onto transport blocks (TBs), demultiplexing of MAC SDUs from TBs, scheduling information reporting, error correction via HARQ, priority handling, and logical channel priority ordering.

[0071] Transmit (TX) processor 316 and receive (RX) processor 370 implement Layer 1 functionality associated with various signal processing functions. Layer 1 (which includes the physical (PHY) layer) may include error detection on the transport channel, forward error correction (FEC) decoding / decoding of the transport channel, interleaving, rate matching, mapping to the physical channel, modulation / demodulation of the physical channel, and MIMO antenna processing. TX processor 316 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-order phase shift keying (M-PSK), M-order quadrature amplitude modulation (M-QAM)). The decoded and modulated symbols can then be split into parallel streams. Each stream can then be mapped to OFDM subcarriers, multiplexed with a reference signal (e.g., a pilot) in the time and / or frequency domains, and subsequently combined using inverse fast Fourier transform (IFFT) to produce a physical channel carrying a stream of time-domain OFDM symbols. The OFDM stream is spatially pre-decoded to generate multiple spatial streams. A channel estimate from channel estimator 374 is used to determine the decoding and modulation scheme and for spatial processing. This channel estimate can be derived from a reference signal and / or channel condition feedback transmitted by UE 350. Each spatial stream can then be provided to a different antenna 320 via a separate transmitter 318Tx. Each transmitter 318Tx can use the corresponding spatial stream to modulate a radio frequency (RF) carrier for transmission.

[0072] At UE 350, each receiver 354Rx receives signals via its corresponding antenna 352. Each receiver 354Rx recovers the information modulated onto the RF carrier and provides this information to the receive (RX) processor 356. The TX processor 368 and RX processor 356 implement Layer 1 functionality associated with various signal processing functions. The RX processor 356 can perform spatial processing on this information to recover any spatial streams destined for UE 350. If multiple spatial streams are destined for UE 350, these multiple spatial streams can be combined by the RX processor 356 into a single OFDM symbol stream. The RX processor 356 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 consists of a separate OFDM symbol stream for each subcarrier of the OFDM signal. The symbols on each subcarrier, along with a reference signal, are recovered and demodulated by determining the most probable signal constellation point transmitted by base station 310. These soft decisions can be based on a channel estimate calculated by channel estimator 358. The soft decision is then decoded and deinterleaved to recover the data and control signals originally transmitted by base station 310 on the physical channel. The data and control signals are then provided to controller / processor 359, which implements layer 3 and layer 2 functionality.

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

[0074] Similar to the functionality described in conjunction with DL transmission performed by base station 310, controller / processor 359 provides: 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 upper-layer PDU delivery, 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 TBs, demultiplexing of MAC SDUs from TBs, scheduling information reporting, error correction via HARQ, priority handling, and logical channel priority ordering.

[0075] The channel estimate derived by the channel estimator 358 from the reference signal or feedback transmitted by the base station 310 can be used by the TX processor 368 to select an appropriate decoding and modulation scheme and facilitate spatial processing. The spatial stream generated by the TX processor 368 can be provided to different antennas 352 via individual transmitters 354Tx. Each transmitter 354Tx can use the corresponding spatial stream to modulate an RF carrier for transmission.

[0076] UL transmission is processed at base station 310 in a manner similar to that described in conjunction with the receiver function at UE 350. Each receiver 318Rx receives signals via its corresponding antenna 320. Each receiver 318Rx recovers the information modulated onto the RF carrier and provides that information to RX processor 370.

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

[0078] At least one of the TX processor 368, RX processor 356, and controller / processor 359 can be configured to perform coupling. Figure 1 Various aspects of component 198. At least one of the TX processor 316, RX processor 370, and controller / processor 375 can be configured to perform combined Figure 1 The components of 199 in all aspects.

[0079] Figure 4 Figure 400 illustrates an example of UE positioning based on reference signal measurements. UE 404 can be positioned at time T. SRS_TX Send UL-SRS 412 and at time T PRS_RX Receives the DL positioning reference signal (PRS) (DL-PRS) 410. TRP 406 can be used at time T. SRS_RX Receive UL-SRS 412 and at time T PRS_TX Send DL-PRS 410. UE 404 may receive DL-PRS 410 before sending UL-SRS 412, or may send UL-SRS 412 before receiving DL-PRS 410. In both cases, the location server (e.g., location server 168) or UE 404 may base its response on ||T SRS_RX -T PRS_TX |-|T SRS_TX -T PRS_RX || to determine RTT 414. Therefore, multi-RTT positioning can utilize the UERx-Tx time difference measurement (i.e., |T) of downlink signals received from multiple TRPs 402, 406 and measured by UE 404. SRS_TX -T PRS_RX |) and DL-PRS reference signal received power (RSRP) (DL-PRS-RSRP), and the measured TRP Rx-Tx time difference (i.e., |T) of the uplink signal transmitted from UE 404 at multiple TRPs 402, 406. SRS_RX -T PRS_TX |) and UL-SRS-RSRP. UE 404 uses auxiliary data received from the positioning server to measure the UE Rx-Tx time difference (and optionally the DL-PRS-RSRP of the received signal), and TRPs 402, 406 use auxiliary data received from the positioning server to measure the gNB Rx-Tx time difference (and optionally the UL-SRS-RSRP of the received signal). These measurements can be used at the positioning server or at UE 404 to determine the RTT, which is used to estimate the location of UE 404. Other methods for determining the RTT are possible, such as, for example, using DL-TDOA and / or UL-TDOA measurements.

[0080] DL-AoD positioning utilizes the measured DL-PRS-RSRP of downlink signals received at UE 404 from multiple TRPs 402 and 406. UE 404 uses auxiliary data received from the positioning server to measure the DL-PRS-RSRP of the received signals, and the resulting measurement, along with the departure azimuth angle (A-AoD), departure zenith angle (Z-AoD), and other configuration information, is used to position UE 404 relative to adjacent TRPs 402 and 406.

[0081] DL-TDOA positioning utilizes the DL Reference Signal Time Difference (RSTD) (and optionally DL-PRS-RSRP) of downlink signals received at UE 404 from multiple TRPs 402, 406. UE 404 uses auxiliary data received from the positioning server to measure the DL RSTD (and optionally DL-PRS-RSRP) of the received signals, and the resulting measurement, along with other configuration information, is used to position UE 404 relative to adjacent TRPs 402, 406.

[0082] UL-TDOA positioning utilizes the UL relative time of arrival (RTOA) (and optionally UL-SRS-RSRP) of the uplink signal transmitted from UE 404 at multiple TRPs 402, 406. TRPs 402, 406 use auxiliary data received from the positioning server to measure the UL-RTOA (and optionally UL-SRS-RSRP) of the received signal, and the resulting measurements, along with other configuration information, are used to estimate the location of UE 404.

[0083] UL-AoA positioning utilizes the azimuth (A-AoA) and zenith (Z-AoA) of the uplink signal transmitted from UE 404 at multiple TRPs 402 and 406. TRPs 402 and 406 use auxiliary data received from the positioning server to measure the A-AoA and Z-AoA of the received signal, and the resulting measurements, along with other configuration information, are used to estimate the position of UE 404.

[0084] Additional positioning methods can be used to estimate the location of UE 404, such as, for example, UE-side UL-AoD and / or DL-AoA. It should be noted that data / measurements from various technologies can be combined in various ways to increase accuracy, determine and / or enhance certainty, supplement / improve measurements, and / or replace / provide missing information.

[0085] Wireless communication networks can support the location of wireless devices. For example, based on reference signal communication between an anchor entity (e.g., a network node, base station, eNB, gNB, Transmitter / Receiver Point, TRP, etc.) and a wireless device, the UE can use the Time-of-Arrival (TDoA) associated with that reference signal communication to determine the location / positioning of the wireless device. As an example of TDoA, a wireless device can locate itself or another wireless device based on the time difference of arrival of a positioning reference signal. In an uplink-like TDoA, the wireless device can send a PRS (Presentation Reference Signal), and the anchor entity can report the time when it received the PRS back to the wireless device. The location of the wireless device can be calculated based on the difference between the arrival times and the anchor entity's location. In a downlink-like TDoA, multiple anchor entities can send PRSs, the wireless device can receive those PRSs, and the location of the wireless device can be calculated based on the difference in arrival times and the anchor entity's location. In Uu interface positioning, the anchor entity can report a quality metric for the relative time difference between itself and a synchronization reference source. This quality metric can be the rtd-Quality field in the RTD-InfoElement, which can be used for anchor entity selection. However, if the anchor entity is not fully synchronized with its synchronization reference source (e.g., GNSS, network nodes, and / or independent synchronization reference UEs), uncertainties may be introduced into arrival time and time difference measurements, which in turn may introduce uncertainties into the calculated location. For example, the anchor entity may be synchronized with the synchronization reference source, and this synchronization may shift by a certain amount of time over a period of time, within which corrections should be applied to avoid synchronization errors. However, the examples used for synchronization error management do not provide mitigation of the effects caused by synchronization errors between anchor UEs in sidelink SL TDoA measurements.

[0086] Figure 5 Figure 500 illustrates an example of UE positioning based on reference signal measurements and quality metrics. Figure 500 shows configurations 550, 560, and 570, respectively, illustrating examples of TDoA positioning, in which a wireless device (e.g., UE 502) can locate itself or another device based on the time difference of arrival of a positioning signal associated with anchor entity 504.

[0087] In configuration 550, UE 502 is associated with a TDoA similar to an uplink. UE 502 may send a PRS 506 to anchor entity 504, which in turn provides a report 508 (e.g., indicating the time they received the PRS 506) back to UE 502. The location of UE 502 can be calculated based on the difference between the arrival times in the reports 508 and the location of anchor entity 504.

[0088] In configuration 560, UE 502 is associated with a TDoA similar to a downlink. UE 502 can receive PRS 510 transmitted from anchor entity 504. The location of UE 502 can be calculated based on the difference in arrival times of PRS 510 and the location of anchor entity 504.

[0089] In configuration 570, UE 502 may be associated with Uu interface positioning. Anchor entity 504' (e.g., in anchor entity 504) may report, for example, a quality metric 512 to UE 502 and / or to the LMF regarding the relative time difference (RTD) between anchor entity 504' and a synchronization reference source. Quality metric 512 may be, for example, an rtd-Quality field in an RTD-InfoElement as shown in reporting configuration 514, which can be used for anchor entity selection. In one example, a timing quality value may indicate the numerical value of quality metric 512, and a timing quality resolution may indicate the unit of the timing quality value, such as resolution, like 0.1m, 1m, 10m, 30m, etc.

[0090] This paper describes various aspects of timing information exchange for enhanced sidelink positioning, enabling synchronization information exchange to mitigate the impact of synchronization errors between anchor UEs in SL-based TDoA measurements. Exchanging anchor UE synchronization information (e.g., associated with synchronization reference source, RTD, synchronization quality information, synchronization reference type, and / or change time) between the UE and the LMF or another UE improves positioning. Providing the synchronization reference type and change time of the synchronization reference source to the LMF and SL UE makes it possible to correct synchronization errors between anchor UEs in SL positioning measurements. Additionally, correcting such synchronization errors improves the positioning accuracy of wireless devices in the wireless communication network.

[0091] Figure 6This is a call flowchart 600 for wireless communication in various aspects. Call flowchart 600 illustrates the exchange of timing information for enhanced sidelink positioning associated with a wireless device (e.g., UE 602), which may be configured to communicate with a synchronization reference source 604 and / or an LMF / UE 606. The synchronization reference source 604 may be of the type GNSS, a network node (e.g., as shown, for example, a base station, such as a gNB or another type of base station), an independent synchronization reference UE, and / or an independent synchronization reference, etc. In each aspect, LMF / UE 606 may be an LMF or a UE, or may represent both an LMF and a UE. The aspects described for the synchronization reference source 604 as a base station may be performed by the base station in an aggregated form and / or by one or more components of the base station in a decomposed form. Additionally or alternatively, as a supplement and / or alternative to the operation of the synchronization reference source 604 and / or LMF / UE 606, the aspects may be performed autonomously by the UE 602.

[0092] In the illustrated aspect, UE 602 may be configured to receive synchronization information 608, and synchronization reference source 604 and / or LMF / UE 606 may be configured to provide / transmit the synchronization information. Synchronization information 608 may include one or more of the following: synchronization reference type, UE identifier, cell information, and / or time associated with synchronization reference source 604. The synchronization reference source may be a device and / or system configured to provide a synchronization reference (such as time, frame number, counter, etc.) through which the radio device synchronizes itself relative to the synchronization reference. The synchronization reference source may also be a device and / or system configured to transmit a synchronization reference signal (e.g., S-SSB). The synchronization reference type may be GNSS, a network (e.g., gNB / eNB), an independent synchronization reference UE, or another device as described herein, and in various aspects, the synchronization reference type may be associated with a configuration or implementation through which the radio device communicates with the synchronization reference source. In various respects, time can be the time since the last synchronization update (e.g., indicated / represented as a subframe, microsecond, millisecond, second, etc.), or a qualitative time period measured relative to a threshold (e.g., a threshold that can be configured to identify updates relative to a relative time (such as very recent, recent, not recent, long ago, etc.). In other respects, the time can be the time since the last synchronization update (e.g., absolute time (such as, but not limited to, Coordinated Universal Time (UTC)), a time period associated with a system frame number (SFN), and / or a time period associated with a direct frame number (DFN), etc.).

[0093] In some respects, the synchronization reference source 604 may be associated with at least one of the following: the specific implementation of the anchor entity, the communication layer message of the LMF or another UE in LMF / UE 606, the configuration at UE 602 and / or the request from UE 602.

[0094] UE 602 can be configured to identify the synchronization reference type of the synchronization reference source (e.g., synchronization reference source 604) based on synchronization and / or synchronization information 608 between UE 602 and synchronization reference source 604 (at 610). In various aspects, the synchronization reference source can be one or more of the following: GNSS, network node, independent synchronization reference UE (e.g., synchronized with itself) and / or independent synchronization reference (e.g., unsynchronized), etc. The synchronization reference type can be GNSS, UE directly synchronized with GNSS, UE indirectly synchronized with GNSS, base station (e.g., gNB, eNB, etc.), UE directly synchronized with gNB / eNB, UE indirectly synchronized with gNB / eNB, and / or UE synchronized with a synchronization reference UE (e.g., an independent synchronization reference UE, where the anchor entity itself is an independent synchronization reference), etc.

[0095] In some aspects, where the synchronization reference type is based on synchronization with a GNSS, UE 602 may be configured (at 610) to identify the satellite constellation associated with that GNSS (e.g., which satellite constellation is used for synchronization reference source 604). In some aspects, where the synchronization reference type is based on synchronization with a network node, UE 602 may be configured (at 610) to identify cell information associated with that network node (e.g., cell identification information for synchronization reference source 604). In some aspects, where the synchronization reference type is based on synchronization with a synchronization reference UE, UE 602 may be configured (e.g., as part of 610) to identify (e.g., as part of 610) the reception time of the SL SSB (S-SSB) (e.g., absolute time, SFN, DFN, etc.) and the frequency position associated with synchronization with that synchronization reference UE (e.g., absolute radio frequency channel number (ARFCN)).

[0096] UE 602 may be configured (at 612) to detect a change in time associated with an anchor entity, wherein the change in time includes at least one of the following: a first time since the last synchronization update, a second time of the last synchronization update, or a correction amount corrected in the last one or more synchronization updates. In various aspects, the change in time may be based on the average of at least two or more synchronization updates in the last one or more synchronization updates, and in some aspects, the change in time may represent a time offset. In various aspects, UE 606 may be configured (at 612) to detect a change in time associated with an anchor entity based on a PRS signal received from the anchor entity and / or based on a report of the reception time of the PRS signal provided / transmitted by UE 602 to the anchor entity (received from the anchor entity), as described herein. In some aspects, UE 602 may not detect a change in time or may skip one or more detections of the change in time.

[0097] UE 602 may be configured to provide at least one of the LMF or a second UE (e.g., LMF / UE 606) with a first indication 614 of the synchronization reference type, a quality metric, and / or a change time to the synchronization reference source 604. In various aspects, the second UE or the UE in LMF / UE 606 may be an SL UE associated with UE 602. In some aspects, the change time may be an RTD between a first ToA associated with a first reference signal from the anchor entity and a second ToA associated with a second reference signal from the second UE (e.g., the UE in LMF / UE 606, etc.), wherein the second UE may be configured as an SL UE associated with UE 602. The first indication 614 may be provided to LMF / UE 606 thereby serving as the basis for communication, for example, as the communication basis for LMF / UE 606.

[0098] In some aspects, when the synchronization reference type is based on synchronization with GNSS, UE 602 may be configured to report a second indication of the satellite constellation to the LMF or a second UE (e.g., LMF / UE 606). In some aspects, when the synchronization reference type is based on synchronization with a network node, UE 602 may be configured to report a second indication of cell information to the LMF or a second UE (e.g., LMF / UE 606). In some aspects, when the synchronization reference type is based on synchronization with an independent synchronization UE / reference, UE 602 may be configured to report the received S-SSB reception time and the frequency location associated with synchronization with that independent synchronization UE / reference to the LMF or a second UE (e.g., LMF / UE 606). In some aspects, UE 602 may report the satellite constellation, cell information, and / or reception time and frequency location together with the first indication 614, quality metric, and / or change time, or report them within the first indication.

[0099] Therefore, aspects of this paper address the synchronization error between anchor UEs in SL positioning measurements by providing the synchronization reference type and change time for the synchronization reference source for LMF and SL UE. This allows, for example, the wireless device positioning accuracy of wireless communication networks to be improved by correcting such synchronization errors.

[0100] Figure 7 Figure 700 illustrates examples of timing information exchange for enhanced sidelink positioning in various aspects. Figure 700 may be... Figure 6 One aspect of the call flow diagram 600. Figure 700 illustrates a UE 702 according to various aspects of this document, which can be synchronized with one or more synchronization reference sources 706 and can be configured to perform SL communication 718 with SL UE 704.

[0101] As illustrated, UE 702 can be configured to receive synchronization information 716, and one or more synchronization reference sources among synchronization reference sources 706 can be configured to provide / transmit the synchronization information. Synchronization information 716 can be... Figure 6 One aspect of the synchronization information 608 is that the synchronization information 716 may include one or more of the following: synchronization reference type, UE identifier, cell information, and / or time associated with the synchronization reference source 706, as described herein. The synchronization reference source 706 may include GNSS 708, network node 710 (e.g., TRP and / or base station (eNB, gNB, etc.)), UE 712 (e.g., synchronization reference UE, independent synchronization reference UE that can synchronize with itself, etc.), and / or UE 714 (e.g., may be an asynchronous independent synchronization reference), etc.

[0102] In various respects, UE 702 may be configured to receive PRS information 724, which may include PRS from an anchor entity and / or may be based on a report (received from the anchor entity) of the reception time of a PRS signal provided / transmitted by UE 702 to the anchor entity, as described herein. UE 702 may be configured to identify (e.g., as described above for synchronization reference sources 702 and / or synchronization information 716) based on synchronization and / or synchronization information 716 between UE 702 and one or more synchronization reference sources 706. Figure 6 The synchronization reference type of the synchronization reference source (e.g., synchronization reference source 706) described in section 610. UE 702 can also be configured to detect (e.g., based at least in part on synchronization information 716 and / or PRS information 724) the synchronization reference type. Figure 6(as described in 612) the change time associated with the anchor entity, wherein the change time includes at least one of the following: a first time since the last synchronization update, a second time since the last synchronization update, or a correction amount corrected in one or more previous synchronization updates.

[0103] UE 702 can be configured to provide / transmit a first indication of the synchronization reference type of one of the synchronization reference sources utilized in synchronization reference source 706 and / or the change time (e.g., as for LMF 722, using core network (CN) communication 720 via NG-RAN) and / or a second UE (e.g., SL UE 704 using SL communication 718) to LMF 722 and / or a second UE (e.g., SL UE 704 using SL communication 718). Figure 6 (As described similarly to the first indication 614). In all respects, when UE 702 provides / transmits a first indication of the synchronization reference type and the change time to LMF 722 (e.g., using core network (CN) communication 720), LMF 722 may subsequently provide a first indication of the synchronization reference type and the change time to a second UE (e.g., SL UE 704 using, for example, CN communication 726 via NG-RAN). Thus, SL UE 704 may receive the indication of the synchronization reference type and the change time, which enables SL UE 704 to perform communication and / or correction of synchronization errors.

[0104] Figure 8 This is a call flowchart 800 for various aspects of wireless communication. Call flowchart 800 can be... Figure 6 Call flowchart 600 and / or Figure 7 This is one aspect of Figure 700. Call flowchart 800 illustrates the exchange of timing information for enhanced sidelink positioning associated with a wireless device (e.g., UE 802), which may be configured to communicate with anchor entity 804 and / or LMF / UE 806. For example, anchor entity 804 may be one or more TRPs, network nodes, base stations, gNBs, eNBs, and / or UEs. In each aspect, LMF / UE 806 may be an LMF or a UE, or may represent both an LMF and a UE. The aspects described for anchor entity 804, which is a base station, may be performed by the base station in an aggregated form and / or by one or more components of the base station in a decomposed form. Additionally or alternatively, as a supplement and / or alternative to the operation of anchor entity 804 and / or LMF / UE 806, aspects may be performed autonomously by UE 802. Call flowchart 800 may be Figure 6 Call flowchart 600 and / or Figure 7 This is one aspect of Figure 700. In various respects, UE 802 can represent... Figure 7 SL UE 704 in the middle.

[0105] In the illustrated aspect, UE 802 may be configured to receive at least one of the following from at least one of an LMF or a second UE (e.g., LMF / UE 806): a first indication 808 of the synchronization reference type for the synchronization reference source, a quality metric, and / or a change time. The synchronization reference type may be associated with the synchronization of UE 802 with the synchronization reference source and may be one or more of the following: GNSS, a network node, a synchronization reference UE (e.g., synchronized with itself), and / or an independent synchronization reference (e.g., unsynchronized), etc. The synchronization reference type may be GNSS, a UE directly synchronized with GNSS, a UE indirectly synchronized with GNSS, a base station (e.g., gNB, eNB, etc.), a UE directly synchronized with gNB / eNB, a UE indirectly synchronized with gNB / eNB, and / or a UE synchronized with an independent synchronization reference UE (where anchor entity 804 itself is an independent synchronization reference), etc. The change time may be associated with anchor entity 804 and may include at least one of the following: a first time since the last synchronization update, a second time since the last synchronization update, or a correction amount corrected in one or more previous synchronization updates.

[0106] In various aspects, the change time may be based on the average of at least two or more synchronization updates from the last one or more synchronization updates, and in some aspects, the change time may represent a time offset. In various aspects, the UE in LMF / UE806 may be configured to identify the synchronization reference type and / or detect the change time associated with anchor entity 804 based on a report of the reception time of a PRS signal received from anchor entity 804 and / or based on a report of the reception time of a PRS signal provided / transmitted by such UE 802 to anchor entity 804 (received from anchor entity 804). In some aspects, the change time may be the RTD between a first ToA associated with a first reference signal from anchor entity 804 and a second ToA associated with a second reference signal from UE 802.

[0107] In some aspects, when the synchronization reference type is based on synchronization with GNSS, UE 802 may be configured to receive a second indication of the satellite constellation from the LMF or a second UE (e.g., LMF / UE 806). In some aspects, when the synchronization reference type is based on synchronization with a network node, UE 802 may be configured to receive a second indication of cell information from the LMF or a second UE (e.g., LMF / UE 806). In some aspects, when the synchronization reference type is based on synchronization with an independent synchronization UE / reference, UE 802 may be configured to receive the reception time of the received S-SSB and the frequency position associated with the synchronization with that independent synchronization UE / reference from the LMF or a second UE (e.g., LMF / UE 806). In some aspects, UE 802 may receive the satellite constellation, cell information, and / or reception time and frequency position together with or within a first indication 808.

[0108] UE 802 may be configured to provide / transmit and / or receive communication 810 based on at least one of a first indication 808 of the synchronization reference type of the synchronization reference source, the quality metric, and / or the change time. In various aspects, UE 802 may provide / transmit communication 810 for positioning UE 802 and / or another radio device. As an example, UE 802 may be configured to use communication 810 to receive and / or transmit PRS information. That is, communication 810 may include PRS from anchor entity 804 and / or may be a report based on the reception time of the PRS signal provided / transmitted by UE 802 to anchor entity 804 using communication 810 (received from anchor entity 804 using communication 810), as described herein.

[0109] UE 802 can be configured to generate adjusted timing parameters for communication 810 based on at least one of the synchronization reference type indicated by the first indication 808 or the change time (at 812). For example, the change time may include at least one of the following: a first time since the last synchronization update, a second time of the last synchronization update, or a correction amount corrected in one or more previous synchronization updates. In various aspects, the change time may be based on the average of at least two or more of the last one or more synchronization updates, and in some aspects, the change time may represent a time offset. Based on the change time, UE 802 can generate adjusted timing parameters to compensate for the change time and correct for synchronization errors represented by the change time.

[0110] UE 802 can be configured to perform positioning calculations (at 814) based on either communication 810 or the adjusted timing parameters. For example, UE 802 can be configured (at 814) to perform positioning calculations for itself. In all respects, where communication 810 includes PRS information that can be used for positioning, UE 802 can apply (at 812) the generated adjusted timing parameters to account for synchronization errors and calculate its position.

[0111] Figure 9 This is a flowchart 900 of a method for wireless communication in various aspects. The method can be performed by a UE (e.g., UE 104, 502, 602, 702, 704; device 1304). In some aspects, the method may include combining... Figure 6 The communication process described in the document and / or Figure 7 , Figure 8 The described aspects. This method may involve timing information exchange for enhanced sidelink positioning, and can correct synchronization errors between anchor UEs in SL positioning measurements and improve the positioning accuracy of wireless devices in wireless communication networks by providing synchronization reference types and change times for synchronization reference sources to LMF and SL UEs.

[0112] At 902, the UE identifies the synchronization reference type of the synchronization reference source based on the synchronization between the first UE and the synchronization reference source, wherein the synchronization reference type is one or more of the following: GNSS, network node, or synchronization reference UE. For example, this identification could be provided by... Figure 13 It is performed by one or more of the components 198, transceiver 1322 and / or antenna 1380. Figure 6 , Figure 7 Example: UE 602 identifies the synchronization reference source (e.g., synchronization reference source 604 (e.g., Figure 7 Examples of such synchronous reference types are 706, 708, 710, 712, and 714.

[0113] UE 602 can be configured to receive synchronization information 608 (e.g., Figure 7 716 in the middle), synchronized reference source 604 (e.g., Figure 7 706, 708, 710, 712, 714) and / or LMF / UE 606 (e.g., Figure 7 726 and 704 in the code can be configured to provide / send this synchronization information. Synchronization information 608 (e.g., Figure 7 716 in the table may include synchronization reference type, UE identifier, cell information and / or synchronization reference source 604 (e.g., Figure 7The time can be one or more of the times associated with 706, 708, 710, 712, 714, etc. In each respect, the time can be the time since the last synchronization update (e.g., indicated / represented as a subframe, microsecond, millisecond, second, etc.), or a qualitative time period measured relative to a threshold (e.g., a threshold that can be configured to identify updates relative to a relative time (such as very recent, recent, not recent, long ago, etc.). In other respects, the time can be the time since the last synchronization update (e.g., absolute time (such as, but not limited to, Coordinated Universal Time (UTC)), a time period associated with a System Frame Number (SFN), and / or a time period associated with a Direct Frame Number (DFN), etc.).

[0114] In some respects, synchronizing the reference source 604 (e.g., Figure 7 706, 708, 710, 712, and 714 in the table can be related to the specific implementation of the anchor entity, LMF / UE 606 (e.g., Figure 7 It is associated with at least one of the following: LMF in 726, 704 (or another UE's communication layer message), configuration at UE 602, and / or requests from UE 602.

[0115] UE 602 can be configured to be based on UE 602 and synchronization reference source 604 (e.g., Figure 7 Synchronization and / or synchronization information 608 (e.g., 706, 708, 710, 712, 714) in the above (e.g., Figure 7 (716 in the middle) to identify the synchronization reference source (e.g., synchronization reference source 604 (e.g., Figure 7 The synchronization reference type is 706, 708, 710, 712, 714. In each respect, the synchronization reference source can be one or more of the following: GNSS (e.g., Figure 7 706, 708), network nodes (e.g., Figure 7 706, 710), and synchronization reference UE (e.g., synchronized with itself) (e.g., Figure 7 706, 712) and / or independent synchronous references (e.g., unsynchronized) (e.g., Figure 7 (e.g., 706, 714, etc.). This synchronization reference type can be GNSS (e.g., ...). Figure 7 706, 708), and GNSS (e.g., Figure 7 UEs directly synchronized with GNSS (e.g., 706, 708) and GNSS (e.g., Figure 7 Indirect synchronization of UEs and base stations (e.g., gNB, eNB, etc.) (e.g., 706, 708) Figure 7 706, 710 in the middle), and gNB / eNB (e.g., Figure 7UEs directly synchronized with gNB / eNB (e.g., 706, 710) and gNB / eNB (e.g., Figure 7 UEs indirectly synchronized (e.g., 706, 710) and / or with a synchronization reference UE (e.g., independent synchronization reference UE (e.g., Figure 7 (706, 712 in the text), where the anchor entity itself is an independent synchronization reference (e.g., Figure 7 UEs that are synchronized, such as 706 and 714.

[0116] In some respects, the synchronization reference type is based on GNSS (e.g., Figure 7 In the case of synchronization with GNSS (706, 708), UE 602 can be configured (at 610) to identify with that GNSS (e.g., Figure 7 The satellite constellations associated with 706 and 708 (e.g., which satellite constellation is used to synchronize reference source 604 (e.g., ...) Figure 7 (706, 708, 710, 712, 714 in the original text). In some aspects, the synchronization reference type is based on the network node (e.g., ...). Figure 7 In the case of synchronization with network nodes (706, 710), UE 602 can be configured (at 610) to identify itself with that network node (e.g., Figure 7 Cell information associated with 706, 710 (e.g., for synchronization reference source 604 (e.g., Figure 7 Cell identifier information (706, 708, 710, 712, 714 in the original text). In some aspects, the synchronization reference type is based on the independent synchronization UE / reference (e.g., Figure 7 In the case of synchronization with 706, 712, 714 in the above, UE602 can be configured to identify (e.g., as part of 610) the reception time (e.g., absolute time, SFN, DFN, etc.) of the SL SSB (S-SSB) and associate it with the independently synchronized UE / reference (e.g., Figure 7 The synchronous frequency position (e.g., absolute radio frequency channel number (ARFCN)) of 706, 712, 714 in the series.

[0117] In some aspects, the UE detects the change time associated with the anchor entity, wherein the change time includes at least one of the following: a first time since the last synchronization update, a second time since the last synchronization update, or a correction amount corrected in one or more previous synchronization updates. For example, this detection may be performed by... Figure 13 It is performed by one or more of the components 198, transceiver 1322 and / or antenna 1380. Figure 6 , Figure 7 An example of UE 602 detecting such time changes is shown.

[0118] UE 602 can be configured (at 612) to detect a change in time associated with an anchor entity, wherein the change in time includes at least one of the following: a first time since the last synchronization update, a second time since the last synchronization update, or a correction amount corrected in the last one or more synchronization updates. In various aspects, the change in time may be based on the average of at least two or more synchronization updates in the last one or more synchronization updates, and in some aspects, the change in time may represent a time offset. In various aspects, UE 602 can be configured to base its detection on a PRS signal received from the anchor entity and / or on a PRS signal provided / transmitted by UE 602 to the anchor entity (e.g., Figure 7 The report of the receiving time (at 724) (received from the anchor entity) is used (at 612) to detect the change time associated with the anchor entity, as described herein.

[0119] At 904, the UE provides at least one of the following to the LMF or a second UE: a first indication of the synchronization reference type, a quality metric, or a change time for the synchronization reference source, thereby serving as the basis for communication. The change time includes at least one of the following: a first time since the last synchronization update, a second time since the last synchronization update, or a correction amount corrected in one or more previous synchronization updates. For example, this provision may be provided by... Figure 13 It is performed by one or more of the components 198, transceiver 1322 and / or antenna 1380. Figure 6 , Figure 7 An example is given of UE 602 providing such indications / quality metrics / time of change for LMF and / or UE (e.g., LMF / UE 606).

[0120] UE 602 can be configured to send to an LMF or a second UE (e.g., LMF / UE 606). Figure 7 At least one of 726 and 704 in the above provides a reference source 604 (e.g., Figure 7 The first instruction 614 of the synchronization reference type (e.g., 706, 708, 710, 712, 714) in the series 706, 708, 710, 712, 714) Figure 7 718, 720), quality metrics and / or time of change. In all aspects, the second UE or LMF / UE 606 (e.g., Figure 7 The UE in 726, 704) can be an SL UE associated with UE 602. In some aspects, the change time can be a first ToA associated with a first reference signal from the anchor entity and with a signal from a second UE (e.g., LMF / UE 606). Figure 7The RTD between the second reference signal associated with the second ToA of the UE (e.g., 726, 704) in the UE, wherein the second UE can be configured as an SL UE associated with UE 602.

[0121] In some respects, the synchronization reference type is based on GNSS (e.g., Figure 7 In the case of synchronization with 706 and 708 in the above, UE 602 can be configured to send to LMF or a second UE (e.g., LMF / UE 606). Figure 7 The reports 726 and 704 in the document provide a second indication of the satellite constellation. In some respects, the synchronization reference type is based on the network nodes (e.g., Figure 7 In the case of synchronization with 706 and 710 in the above, UE 602 can be configured to send to LMF or a second UE (e.g., LMF / UE 606). Figure 7 The 726 and 704 reports provide a second indication of cell information. In some aspects, the synchronization reference type is based on the independent UE / reference (e.g., ...). Figure 7 In the case of synchronization with 706, 712, 714 in the above, UE 602 can be configured to send a signal to the LMF or a second UE (e.g., LMF / UE 606). Figure 7 The 726 and 704 reports indicate that the received S-SSB time is associated with the independent UE / reference (e.g., ...). Figure 7 The frequency position synchronized with the first indication 614 (e.g., 706, 712, 714). In some aspects, UE 602 can synchronize the satellite constellation, cell information, and / or reception time and frequency position with the first indication 614 (e.g., Figure 7 Report the quality measures and / or change times together with 718, 720, or in the first instruction.

[0122] Therefore, aspects of this paper address the synchronization error between anchor UEs in SL positioning measurements by providing the synchronization reference type and change time for the synchronization reference source for LMF and SL UE. This allows, for example, the wireless device positioning accuracy of wireless communication networks to be improved by correcting such synchronization errors.

[0123] Figure 10 This is a flowchart 1000 of a method for wireless communication in various aspects. The method can be performed by a UE (e.g., UE 104, 502, 602, 702, 704; device 1304). In some aspects, the method may include combining... Figure 6 The communication process described in the document and / or Figure 7 , Figure 8The described aspects. This method may involve timing information exchange for enhanced sidelink positioning, and can correct synchronization errors between anchor UEs in SL positioning measurements and improve the positioning accuracy of wireless devices in wireless communication networks by providing synchronization reference types and change times for synchronization reference sources to LMF and SL UEs.

[0124] At point 1002, the UE identifies the synchronization reference type of the synchronization reference source based on the synchronization between the first UE and the synchronization reference source, wherein the synchronization reference type is one or more of the following: GNSS, network node, or synchronization reference UE. For example, this identification could be provided by... Figure 13 It is performed by one or more of the components 198, transceiver 1322 and / or antenna 1380. Figure 6 , Figure 7 An example of this type of synchronization reference is shown where UE 602 identifies a synchronization reference source (e.g., synchronization reference source 604).

[0125] UE 602 can be configured to receive synchronization information 608 (e.g., Figure 7 716 in the middle), synchronized reference source 604 (e.g., Figure 7 706, 708, 710, 712, 714) and / or LMF / UE 606 (e.g., Figure 7 726 and 704 in the code can be configured to provide / send this synchronization information. Synchronization information 608 (e.g., Figure 7 716 in the table may include synchronization reference type, UE identifier, cell information and / or synchronization reference source 604 (e.g., Figure 7 The time can be one or more of the times associated with 706, 708, 710, 712, 714, etc. In each respect, the time can be the time since the last synchronization update (e.g., indicated / represented as a subframe, microsecond, millisecond, second, etc.), or a qualitative time period measured relative to a threshold (e.g., a threshold that can be configured to identify updates relative to a relative time (such as very recent, recent, not recent, long ago, etc.). In other respects, the time can be the time since the last synchronization update (e.g., absolute time (such as, but not limited to, Coordinated Universal Time (UTC)), a time period associated with a System Frame Number (SFN), and / or a time period associated with a Direct Frame Number (DFN), etc.).

[0126] In some respects, synchronizing the reference source 604 (e.g., Figure 7 706, 708, 710, 712, and 714 in the table can be related to the specific implementation of the anchor entity, LMF / UE 606 (e.g., Figure 7It is associated with at least one of the following: LMF in 726, 704 (or another UE's communication layer message), configuration at UE 602, and / or requests from UE 602.

[0127] UE 602 can be configured to be based on UE 602 and synchronization reference source 604 (e.g., Figure 7 Synchronization and / or synchronization information 608 (e.g., 706, 708, 710, 712, 714) in the above (e.g., Figure 7 (716 in the middle) to identify the synchronization reference source (e.g., synchronization reference source 604 (e.g., Figure 7 The synchronization reference type is 706, 708, 710, 712, 714. In each respect, the synchronization reference source can be one or more of the following: GNSS (e.g., Figure 7 706, 708), network nodes (e.g., Figure 7 706, 710), and synchronization reference UE (e.g., synchronized with itself) (e.g., Figure 7 706, 712) and / or independent synchronous references (e.g., unsynchronized) (e.g., Figure 7 (e.g., 706, 714, etc.). This synchronization reference type can be GNSS (e.g., ...). Figure 7 706, 708), and GNSS (e.g., Figure 7 UEs directly synchronized with GNSS (e.g., 706, 708) and GNSS (e.g., Figure 7 Indirect synchronization of UEs and base stations (e.g., gNB, eNB, etc.) (e.g., 706, 708) Figure 7 706, 710 in the middle), and gNB / eNB (e.g., Figure 7 UEs directly synchronized with gNB / eNB (e.g., 706, 710) and gNB / eNB (e.g., Figure 7 UEs indirectly synchronized (e.g., 706, 710) and / or with a synchronization reference UE (e.g., independent synchronization reference UE (e.g., Figure 7 (706, 712 in the text), where the anchor entity itself is an independent synchronization reference (e.g., Figure 7 UEs that are synchronized, such as 706 and 714.

[0128] At 1004, the UE determines whether the synchronization reference source is GNSS. If yes, flowchart 1000 continues to 1006; if no, flowchart 1000 continues to 1016. For example, this determination can be made by… Figure 13 It is performed by one or more of the components 198, transceiver 1322 and / or antenna 1380.

[0129] At position 1006, the UE identifies the satellite constellation associated with the GNSS. For example, this identifier could be... Figure 13 It is performed by one or more of the components 198, transceiver 1322 and / or antenna 1380. Figure 6 , Figure 7 An example of UE 602 identifying such a satellite constellation is shown.

[0130] In some respects, the synchronization reference type is based on GNSS (e.g., Figure 7 In the case of synchronization with GNSS (706, 708), UE 602 can be configured (at 610) to identify with that GNSS (e.g., Figure 7 The satellite constellations associated with 706 and 708 (e.g., which satellite constellation is used to synchronize reference source 604 (e.g., ...) Figure 7 (706, 708, 710, 712, 714 in the text).

[0131] At 1008, the UE determines whether the synchronization reference source is a network node. If yes, flowchart 1000 continues to 1010; if no, flowchart 1000 continues to 1016. For example, this determination can be made by... Figure 13 It is performed by one or more of the components 198, transceiver 1322 and / or antenna 1380.

[0132] At position 1010, the UE identifier is associated with the cell information of the network node. For example, this identifier may be provided by... Figure 13 It is performed by one or more of the components 198, transceiver 1322 and / or antenna 1380. Figure 6 , Figure 7 An example of UE 602 identifying this type of cell information is shown.

[0133] In some respects, the synchronization reference type is based on the network node (e.g., Figure 7 In the case of synchronization with network nodes (706, 710), UE 602 can be configured (at 610) to identify itself with that network node (e.g., Figure 7 Cell information associated with 706, 710 (e.g., for synchronization reference source 604 (e.g., Figure 7 (The information on the community identifiers of 706, 708, 710, 712, and 714).

[0134] At 1012, the UE determines whether the synchronization reference source is an independent UE or an independent synchronization reference. If yes, flowchart 1000 continues to 1014; if no, flowchart 1000 continues to 1016. For example, this determination can be made by... Figure 13 It is performed by one or more of the components 198, transceiver 1322 and / or antenna 1380.

[0135] At position 1014, the UE identifies the S-SSB reception time and the frequency position associated with the synchronization reference UE. For example, this identifier could be... Figure 13 It is performed by one or more of the components 198, transceiver 1322 and / or antenna 1380. Figure 6 , Figure 7 An example of UE 602 identifying such a receive time and frequency location is shown.

[0136] In some respects, the synchronization reference type is based on the independent synchronization UE / reference (e.g., Figure 7 In the case of synchronization with 706, 712, 714 in the above, UE 602 can be configured to identify (e.g., as part of 610) the reception time (e.g., absolute time, SFN, DFN, etc.) of the SL SSB (S-SSB) and associate it with the independently synchronized UE / reference (e.g., Figure 7 The synchronous frequency position (e.g., absolute radio frequency channel number (ARFCN)) of 706, 712, 714 in the series.

[0137] At position 1016, the UE detects a change in time associated with the anchor entity, wherein the change in time includes at least one of the following: a first time since the last synchronization update, a second time since the last synchronization update, or a correction amount corrected in one or more previous synchronization updates. For example, this detection may be performed by... Figure 13 It is performed by one or more of the components 198, transceiver 1322 and / or antenna 1380. Figure 6 , Figure 7 An example of UE 602 detecting such time changes is shown.

[0138] UE 602 can be configured (at 612) to detect a change in time associated with an anchor entity, wherein the change in time includes at least one of the following: a first time since the last synchronization update, a second time since the last synchronization update, or a correction amount corrected in the last one or more synchronization updates. In various aspects, the change in time may be based on the average of at least two or more synchronization updates in the last one or more synchronization updates, and in some aspects, the change in time may represent a time offset. In various aspects, UE 602 can be configured to base its detection on a PRS signal received from the anchor entity and / or on a PRS signal provided / transmitted by UE 602 to the anchor entity (e.g., Figure 7 The report of the receiving time (at 724) (received from the anchor entity) is used (at 612) to detect the change time associated with the anchor entity, as described herein.

[0139] At point 1018, the UE provides at least one of the following to the LMF or the second UE: a first indication of the synchronization reference type, a quality metric, or the change time for the synchronization reference source. For example, this provision may be made by... Figure 13 It is performed by one or more of the components 198, transceiver 1322 and / or antenna 1380. Figure 6 , Figure 7 An example is given of UE 602 providing such indications / quality metrics / time of change for LMF and / or UE (e.g., LMF / UE 606).

[0140] UE 602 can be configured to send to an LMF or a second UE (e.g., LMF / UE 606). Figure 7 At least one of 726 and 704 in the above provides a reference source 604 (e.g., Figure 7 The first instruction 614 of the synchronization reference type (e.g., 706, 708, 710, 712, 714) in the series 706, 708, 710, 712, 714) Figure 7 718, 720), quality metrics and / or time of change. In all aspects, the second UE or LMF / UE 606 (e.g., Figure 7 The UE in 726, 704) can be an SL UE associated with UE 602. In some aspects, the change time can be a first ToA associated with a first reference signal from the anchor entity and with a signal from a second UE (e.g., LMF / UE 606). Figure 7 The RTD between the second reference signal associated with the second ToA of the UE (e.g., 726, 704) in the UE, wherein the second UE can be configured as an SL UE associated with UE 602.

[0141] At 1020, the UE determines whether the synchronization reference source is GNSS. If yes, flowchart 1000 continues to 1008; if no, flowchart 1000 can return to 1002, and further perform the next synchronization error monitoring iteration and / or correction. For example, this determination can be made by... Figure 13 It is performed by one or more of the components 198, transceiver 1322 and / or antenna 1380.

[0142] At position 1022, the UE reports a second instruction regarding the satellite constellation to the LMF or the second UE. For example, this report could be made by... Figure 13 It is performed by one or more of the components 198, transceiver 1322 and / or antenna 1380. Figure 6 , Figure 7 An example of UE 602 reporting such an instruction is shown.

[0143] In some respects, the synchronization reference type is based on GNSS (e.g., Figure 7 In the case of synchronization with 706 and 708 in the above, UE 602 can be configured to send to LMF or a second UE (e.g., LMF / UE 606). Figure 7 The 726 and 704 reports provide the second instruction for the satellite constellation.

[0144] At 1024, the UE determines whether the synchronization reference source is a network node. If yes, flowchart 1000 continues to 1012; if no, flowchart 1000 can return to 1002, and further perform the next synchronization error monitoring iteration and / or correction. For example, this determination can be made by... Figure 13 It is performed by one or more of the components 198, transceiver 1322 and / or antenna 1380.

[0145] At position 1026, the UE reports a second indication of the cell information to the LMF or the second UE. For example, this report could be generated by... Figure 13 It is performed by one or more of the components 198, transceiver 1322 and / or antenna 1380. Figure 6 , Figure 7 An example of UE 602 reporting such an instruction is shown.

[0146] In some respects, the synchronization reference type is based on the network node (e.g., Figure 7 In the case of synchronization with 706 and 710 in the above, UE 602 can be configured to send to LMF or a second UE (e.g., LMF / UE 606). Figure 7 The 726 and 704 reports provide the second instruction on community information.

[0147] At 1028, the UE determines whether the synchronization reference source is an independent UE or an independent synchronization reference. If yes, flowchart 1000 continues to 1016; if no, flowchart 1000 can return to 1002 and further perform the next synchronization error monitoring iteration and / or correction. For example, this determination can be made by... Figure 13 It is performed by one or more of the components 198, transceiver 1322 and / or antenna 1380.

[0148] At position 1030, the UE reports the reception time and frequency location to the LMF or the second UE. For example, this report could be generated by... Figure 13 It is performed by one or more of the components 198, transceiver 1322 and / or antenna 1380. Figure 6 , Figure 7 An example of UE602 reporting such receive time and frequency locations is shown.

[0149] In some respects, the synchronization reference type is based on the independent synchronization UE / reference (e.g., Figure 7 In the case of synchronization with 706, 712, 714 in the above, UE 602 can be configured to send a signal to the LMF or a second UE (e.g., LMF / UE 606). Figure 7 The 726 and 704 reports indicate that the received S-SSB time is associated with the independent UE / reference (e.g., ...). Figure 7 The synchronization frequency positions of 706, 712, and 714 in the series.

[0150] In some respects, UE 602 can correlate satellite constellation, cell information, and / or reception time and frequency location with the first indication 614 at 1018 (e.g., Figure 7 Report the quality measures and / or change times together with 718, 720, or in the first instruction.

[0151] From 1030, flowchart 1000 can return to 1002 and further perform the next synchronization error monitoring iteration and / or correction.

[0152] Figure 11 This is a flowchart 1100 of a method for wireless communication in various aspects. The method can be performed by a UE (e.g., UE 104, 502, 602, 702, 704; device 1304). In some aspects, the method may include combining... Figure 8 The communication process described in the document and / or Figure 6 , Figure 7 The described aspects. This method may involve timing information exchange for enhanced sidelink positioning, and can correct synchronization errors between anchor UEs in SL positioning measurements and improve the positioning accuracy of wireless devices in wireless communication networks by providing synchronization reference types and change times for synchronization reference sources to LMF and SL UEs.

[0153] At 1102, the UE receives from at least one of the following: a first indication, a quality metric, or a change time for a synchronization reference type of the synchronization reference source, from either the LMF or a second UE. The synchronization reference type is associated with the synchronization of the first UE with the synchronization reference source and is one or more of the following: GNSS, a network node, or a synchronization reference UE. The change time is associated with an anchor entity and includes at least one of the following: a first time since the last synchronization update, a second time of the last synchronization update, or a correction amount corrected in one or more last synchronization updates. As an example, this reception may be provided by... Figure 13 It is performed by one or more of the components 198, transceiver 1322 and / or antenna 1380. Figure 6 , Figure 7 , Figure 8An example is shown where UE 802 receives such a first indication, quality metric, and / or change time for a synchronization reference type from an LMF or UE (e.g., LMF / UE 806).

[0154] UE 802 can be configured to receive signals from an LMF or a second UE (e.g., LMF / UE 806). Figure 7 At least one of 722, 704) in the above structures receives a first indication 808 of the synchronization reference type of the synchronization reference source (e.g., Figure 6 614 in the middle; Figure 7 (718, 726 in the original text) and the change time. Synchronization reference source (e.g., Figure 6 604 in the middle; Figure 7 706, 708, 710, 712, and 714 in the table can be associated with UE 802 and the synchronization reference source (e.g., Figure 6 604 in the middle; Figure 7 Synchronization of GNSS (706, 708, 710, 712, 714) can be one or more of the following: GNSS (e.g., Figure 7 706, 708), network nodes (e.g., Figure 7 706, 710), independent synchronization reference UE (e.g., synchronized with itself) (e.g., Figure 7 706, 712) and / or independent synchronous references (e.g., unsynchronized) (e.g., Figure 7 (e.g., 706, 714, etc.). This synchronization reference type can be GNSS (e.g., ...). Figure 7 706, 708), and GNSS (e.g., Figure 7 UEs directly synchronized with GNSS (e.g., 706, 708) and GNSS (e.g., Figure 7 Indirect synchronization of UEs and base stations (e.g., gNB, eNB, etc.) (e.g., 706, 708) Figure 7 706, 710 in the middle), and gNB / eNB (e.g., Figure 7 UEs directly synchronized with gNB / eNB (e.g., 706, 710) and gNB / eNB (e.g., Figure 7 UEs indirectly synchronized (e.g., 706, 710) and / or with independent synchronization reference UEs (e.g., Figure 7 (706, 712), where anchor entity 804 itself is an independent synchronization reference (e.g., Figure 7 The UE synchronized in 706, 714, etc. The change time may be associated with anchor entity 804 and may include at least one of the following: a first time since the last synchronization update, a second time of the last synchronization update, or a correction amount corrected in one or more last synchronization updates.

[0155] In all aspects (for example, Figure 6 The change time detected (at 610) may be based on the average of at least two or more of the previous one or more synchronization updates, and in some respects, the change time may represent a temporal offset. In various respects, LMF / UE 806 (e.g., Figure 7 The UE in 722, 704 can be configured to identify the synchronization reference type and / or based on the PRS signal received from anchor entity 804 (e.g., Figure 7 (724 in the text) and / or based on the PRS signal provided / transmitted by such UE 802 to anchor entity 804 (e.g., Figure 7 The report of the reception time (received from anchor entity 804) in 724 is used to detect the change time associated with anchor entity 804, as described herein. In some aspects, this change time may be the RTD between a first ToA associated with a first reference signal from anchor entity 804 and a second ToA associated with a second reference signal from UE 802.

[0156] At 1104, the UE communicates based on the first indication of the synchronization reference type of the synchronization reference source and the change time. As an example, this communication could be... Figure 13 It is performed by one or more of the components 198, transceiver 1322 and / or antenna 1380. Figure 6 , Figure 7 , Figure 8 An example is given of UE 802 communicating with LMF or UE and / or anchor entity (e.g., LMF / UE 806 and / or anchor entity 804) based on a first indication of the synchronization reference type and the change time.

[0157] UE 802 can be configured to be based on this synchronization reference source (e.g., Figure 6 604 in the middle; Figure 7 The first indication 808 of this synchronization reference type (e.g., 706, 708, 710, 712, 714) is... Figure 7 The UE 802 may provide / transmit communication 810 using at least one of the following: 718, 726; the quality metric; and / or the change time. In various aspects, the UE 802 may provide / transmit communication 810 for locating the UE 802 and / or another radio device. As an example, the UE 802 may be configured to use communication 810 to receive and / or transmit PRS information (e.g., ...). Figure 7 (724 in the text). That is, communication 810 may include PRS (e.g., from anchor entity 804) Figure 7 (724 in the original text) and / or may be based on the PRS signal provided / sent by UE 802 to anchor entity 804 using communication 810 (e.g., Figure 7 The report of the reception time of (724 in the document) (received from anchor entity 804 using communication 810), as described herein.

[0158] UE 802 can be configured to be based on a first indication 808 (e.g., Figure 7 The adjusted timing parameters for communication 810 are generated (at 812) based on at least one of the synchronization reference type or the change time indicated by 718, 726 in the above. For example, the change time may include at least one of the following: a first time since the last synchronization update, a second time of the last synchronization update, or a correction amount corrected in the last one or more synchronization updates. In various aspects, the change time may be based on the average of at least two or more synchronization updates in the last one or more synchronization updates, and in some aspects, the change time may represent a time offset. Based on the change time, UE 802 may (at 812) generate adjusted timing parameters to compensate for the change time and correct the synchronization error represented by the change time. UE 802 may be configured to perform positioning calculations (at 814) based on communication 810 or at least one of the adjusted timing parameters. For example, UE 802 may be configured (at 814) to perform positioning calculations for itself. In various aspects, communication 810 includes PRS information (e.g., PRS information that can be used for positioning) Figure 7 In the case of 724), UE 802 can apply (at 812) the adjusted timing parameters generated to account for synchronization errors and calculate their position.

[0159] Figure 12 This is a flowchart 1200 of a method for wireless communication in various aspects. The method can be performed by a UE (e.g., UE 104, 502, 602, 702, 704; device 1304). In some aspects, the method may include combining... Figure 8 The communication process described in the document and / or Figure 6 , Figure 7 The described aspects. This method may involve timing information exchange for enhanced sidelink positioning, and can correct synchronization errors between anchor UEs in SL positioning measurements and improve the positioning accuracy of wireless devices in wireless communication networks by providing synchronization reference types and change times for synchronization reference sources to LMF and SL UEs.

[0160] At 1202, the UE receives from at least one of the LMF or the second UE a first indication of the synchronization reference type or a change time for the synchronization reference source, wherein the synchronization reference type is associated with the synchronization of the first UE with the synchronization reference source and is one or more of the following: GNSS, network node, or synchronization reference UE, wherein the change time is associated with an anchor entity and includes at least one of the following: a first time since the last synchronization update, a second time of the last synchronization update, or a correction amount corrected in one or more last synchronization updates. As an example, this reception may be provided by... Figure 13 It is performed by one or more of the components 198, transceiver 1322 and / or antenna 1380. Figure 6 , Figure 7 , Figure 8 An example is shown where UE 802 receives such a first indication, quality metric, and / or change time for a synchronization reference type from an LMF or UE (e.g., LMF / UE 806).

[0161] UE 802 can be configured to receive signals from an LMF or a second UE (e.g., LMF / UE 806). Figure 7 At least one of 722, 704) in the above structures receives a first indication 808 of the synchronization reference type of the synchronization reference source (e.g., Figure 6 614 in the middle; Figure 7 At least one of 718, 726), quality metric, and / or change time. Synchronous reference source (e.g., ...). Figure 6 604 in the middle; Figure 7 706, 708, 710, 712, and 714 in the table can be associated with UE 802 and the synchronization reference source (e.g., Figure 6 604 in the middle; Figure 7 Synchronization of GNSS (706, 708, 710, 712, 714) can be one or more of the following: GNSS (e.g., Figure 7 706, 708), network nodes (e.g., Figure 7 706, 710), and synchronization reference UE (e.g., synchronized with itself) (e.g., Figure 7 706, 712) and / or independent synchronous references (e.g., unsynchronized) (e.g., Figure 7 (e.g., 706, 714, etc.). This synchronization reference type can be GNSS (e.g., ...). Figure 7 706, 708), and GNSS (e.g., Figure 7 UEs directly synchronized with GNSS (e.g., 706, 708) and GNSS (e.g., Figure 7 Indirect synchronization of UEs and base stations (e.g., gNB, eNB, etc.) (e.g., 706, 708) Figure 7706, 710 in the middle), and gNB / eNB (e.g., Figure 7 UEs directly synchronized with gNB / eNB (e.g., 706, 710) and gNB / eNB (e.g., Figure 7 UEs indirectly synchronized (e.g., 706, 710) and / or with independent synchronization reference UEs (e.g., Figure 7 (706, 712), where anchor entity 804 itself is an independent synchronization reference (e.g., Figure 7 The UE synchronized in 706, 714, etc. The change time may be associated with anchor entity 804 and may include at least one of the following: a first time since the last synchronization update, a second time of the last synchronization update, or a correction amount corrected in one or more last synchronization updates.

[0162] In all aspects (for example, Figure 6 The change time detected (at 610) may be based on the average of at least two or more of the previous one or more synchronization updates, and in some respects, the change time may represent a temporal offset. In various respects, LMF / UE 806 (e.g., Figure 7 The UE in 722, 704 can be configured to identify the synchronization reference type and / or based on the PRS signal received from anchor entity 804 (e.g., Figure 7 (724 in the text) and / or based on the PRS signal provided / transmitted by such UE 802 to anchor entity 804 (e.g., Figure 7 The report of the reception time (received from anchor entity 804) in 724 is used to detect the change time associated with anchor entity 804, as described herein. In some aspects, this change time may be the RTD between a first ToA associated with a first reference signal from anchor entity 804 and a second ToA associated with a second reference signal from UE 802.

[0163] At 1202, the UE may perform one or more additional receive operations.

[0164] As an example, at 1204, the UE receives a second indication of a satellite constellation from the LMF or the second UE, wherein the satellite constellation is associated with a GNSS, and the synchronization reference type is based on synchronization with the GNSS. As an example, this reception may be provided by... Figure 13 It is performed by one or more of the components 198, transceiver 1322 and / or antenna 1380. Figure 6 , Figure 7 , Figure 8 An example of UE 802 receiving such a second instruction from LMF or UE (e.g., LMF / UE 806) is illustrated.

[0165] In some respects, the synchronization reference type is based on GNSS (e.g., Figure 7 In the case of synchronization with 706, 708, UE 802 can be configured to receive data from the LMF or a second UE (e.g., LMF / UE 806). Figure 6 606 in the middle; Figure 7 The 726 and 704 satellites in the constellation receive the second instruction to the satellite constellation.

[0166] As an example, at 1206, the UE receives a second indication of cell information from the LMF or the second UE, wherein the cell information is associated with a network node, and the synchronization reference type is based on synchronization with the network node. As an example, this reception may be provided by... Figure 13 It is performed by one or more of the components 198, transceiver 1322 and / or antenna 1380. Figure 6 , Figure 7 , Figure 8 An example of UE 802 receiving such a second instruction from LMF or UE (e.g., LMF / UE 806) is illustrated.

[0167] In some respects, the synchronization reference type is based on the network node (e.g., Figure 7 In the case of synchronization with 706, 710 in the above, UE 802 can be configured to receive data from LMF or a second UE (e.g., LMF / UE 806). Figure 6 606 in the middle; Figure 7 The 726 and 704 in the middle receive the second instruction on cell information.

[0168] As an example, at 1208, the UE receives the S-SSB from the LMF or the second UE at a time associated with a frequency position synchronized with a synchronization reference UE, wherein the synchronization reference type is based on synchronization with the synchronization reference UE. As an example, this reception may be provided by... Figure 13 It is performed by one or more of the components 198, transceiver 1322 and / or antenna 1380. Figure 6 , Figure 7 , Figure 8 An example is given of UE 802 receiving such a reception time and frequency location from an LMF or UE (e.g., LMF / UE 806).

[0169] In some respects, the synchronization reference type is based on the independent synchronization UE / reference (e.g., Figure 7 In the case of synchronization with 706, 712, 714 in the above, UE 802 can be configured to receive data from the LMF or a second UE (e.g., LMF / UE 806). Figure 6 606 in the middle; Figure 7The reception time of the S-SSB received in 726 and 704 is associated with the independent synchronization UE / reference (e.g., Figure 7 The synchronization frequency positions of 706, 712, and 714 in the series.

[0170] In some respects, at 1202, UE 802 may correlate satellite constellation, cell information, and / or reception time and frequency location with the first indication 808 (e.g., Figure 6 614 in the middle; Figure 7 (718 and 720 in the middle) are received separately.

[0171] At 1210, the UE communicates based on at least one of the first indication of the synchronization reference type of the synchronization reference source, the quality metric, or the change time. As an example, this communication may be provided by... Figure 13 It is performed by one or more of the components 198, transceiver 1322 and / or antenna 1380. Figure 6 , Figure 7 , Figure 8 An example is given of UE 802 communicating with LMF or UE and / or anchor entity (e.g., LMF / UE 806 and / or anchor entity 804) based on a first indication of the synchronization reference type and the change time.

[0172] UE 802 can be configured to be based on this synchronization reference source (e.g., Figure 6 604 in the middle; Figure 7 The first indication 808 of this synchronization reference type (e.g., 706, 708, 710, 712, 714) is... Figure 7 The UE 802 may provide / transmit communication 810 using at least one of the following: 718, 726; the quality metric; and / or the change time. In various aspects, the UE 802 may provide / transmit communication 810 for locating the UE 802 and / or another radio device. As an example, the UE 802 may be configured to use communication 810 to receive and / or transmit PRS information (e.g., ...). Figure 7 (724 in the text). That is, communication 810 may include PRS (e.g., from anchor entity 804) Figure 7 (724 in the original text) and / or may be based on the PRS signal provided / sent by UE 802 to anchor entity 804 using communication 810 (e.g., Figure 7 The report of the reception time of (724 in the document) (received from anchor entity 804 using communication 810), as described herein.

[0173] Based on the time variation, UE 802 can (at 812) generate adjusted timing parameters to compensate for the time variation and correct for synchronization errors represented by the time variation. UE 802 can be configured to perform positioning calculations (at 814) based on at least one of communication 810 or the adjusted timing parameters. For example, UE 802 can be configured (at 814) to perform positioning calculations for itself. In various aspects, communication 810 includes PRS information that can be used for positioning (e.g., Figure 7 In the case of 724), UE 802 can apply (at 812) the adjusted timing parameters generated to account for synchronization errors and calculate their position.

[0174] Figure 13Figure 1300 illustrates an example of a hardware implementation for device 1304. Device 1304 may be a UE, a component of a UE, or implement UE functionality. In some aspects, device 1304 may include at least one cellular baseband processor 1324 (also referred to as a modem) coupled to one or more transceivers 1322 (e.g., cellular RF transceivers). Cellular baseband processor 1324 may include at least one on-chip memory 1324'. In some aspects, device 1304 may also include one or more Subscriber Identity Module (SIM) cards 1320 and at least one application processor 1306 coupled to a Secure Digital Card (SD) card 1308 and a screen 1310. Application processor 1306 may include on-chip memory 1306'. In some aspects, device 1304 may also include a Bluetooth module 1312, a WLAN module 1314, an SPS module 1316 (e.g., a GNSS module), one or more sensor modules 1318 (e.g., an atmospheric pressure sensor / altimeter; motion sensors such as an inertial measurement unit (IMU), gyroscope and / or accelerometer, magnetometer, audio and / or other technologies for positioning), an additional memory module 1326, a power source 1330, and / or a camera 1332. Bluetooth module 1312, WLAN module 1314, and SPS module 1316 may include an on-chip transceiver (TRX) (or in some cases, only a receiver (RX)). Bluetooth module 1312, WLAN module 1314, and SPS module 1316 may include their own dedicated antennas and / or communicate using antenna 1380. Cellular baseband processor 1324 communicates with the UE via transceiver 1322 through one or more antennas 1380. 104 communicates with and / or with the RU associated with network entity 1302. Cellular baseband processor 1324 and application processor 1306 may each include computer-readable media / memory 1324', 1306' respectively. Additional memory module 1326 may also be considered a computer-readable media / memory. Each computer-readable media / memory 1324', 1306', 1326 may be non-transitory. Cellular baseband processor 1324 and application processor 1306 are each responsible for general processing, including the execution of software stored on the computer-readable media / memory. This software is processed by the cellular baseband processor... When executed, the cellular baseband processor 1324 / application processor 1306 causes the cellular baseband processor 1324 / application processor 1306 to perform the various functions described above. The cellular baseband processor 1324 and application processor 1306 are configured to perform the various functions described above based at least in part on information stored in memory. That is, the cellular baseband processor 1324 and application processor 1306 can be configured to perform a first subset of the various functions described above without information stored in memory, and can be configured to perform a second subset of the various functions described above based on information stored in memory.The computer-readable medium / memory can also be used to store data manipulated by the cellular baseband processor 1324 / application processor 1306 during software execution. The cellular baseband processor 1324 / application processor 1306 can be a component of the UE 350 and may include at least one memory 360 and / or at least one of a TX processor 368, an RX processor 356, and a controller / processor 359. In one configuration, the device 1304 may be at least one processor chip (modem and / or application) and includes only the cellular baseband processor 1324 and / or the application processor 1306; in another configuration, the device 1304 may be the entire UE (e.g., see below). Figure 3 The UE 350 includes an additional module of the device 1304.

[0175] As discussed above, component 198 can be configured to identify the synchronization reference type of the synchronization reference source based on the synchronization between the first UE and the synchronization reference source, wherein the synchronization reference type is one or more of the following: GNSS, network node, or synchronization reference UE. Component 198 can also be configured to detect a change in time associated with an anchor entity, wherein the change in time includes at least one of the following: a first time since the last synchronization update, a second time of the last synchronization update, or a correction amount corrected in one or more last synchronization updates. Component 198 can also be configured to provide at least one of the following to the LMF or the second UE: a first indication of the synchronization reference type of the synchronization reference source, a quality metric, or the change in time. Component 198 can also be configured to identify the satellite constellation associated with the GNSS. Component 198 can also be configured to report a second indication of the satellite constellation to the LMF or the second UE. Component 198 can also be configured to identify cell information associated with the network node. Component 198 can also be configured to report a marker of the cell information to the LMF or the second UE in the first indication. Component 198 may also be configured to identify the reception time of the S-SSB and the frequency location associated with synchronization with the synchronization reference UE. Component 198 may also be configured to report the reception time and the frequency location to the LMF or the second UE. Component 198 may also be configured to identify cell information associated with the quality metric. Component 198 may also be configured to report a second indication of the cell information to the LMF or the second UE in at least one of the first indication or signaling separate from the first indication. In some aspects, component 198 may be configured to receive from at least one of the LMF or the second UE a first indication of a synchronization reference type for a synchronization reference source, a quality metric, and a change time, wherein the synchronization reference type is associated with synchronization between the first UE and the synchronization reference source and is one or more of the following: GNSS, a network node, or a synchronization reference UE, wherein the change time is associated with an anchor entity and includes at least one of the following: a first time since the last synchronization update, a second time of the last synchronization update, or a correction amount corrected in one or more last synchronization updates. Component 198 may also be configured to communicate based on at least one of the first indication of the synchronization reference type of the synchronization reference source, the quality metric, or the change time. Component 198 may also be configured to receive a second indication of a satellite constellation from the LMF or the second UE, wherein the satellite constellation is associated with the GNSS. Component 198 may also be configured to receive a marker of cell information from the LMF or the second UE in the first indication, wherein the cell information is associated with the network node. Component 198 may also be configured to receive the reception time of the S-SSB and the frequency position associated with synchronization with the synchronization reference UE from the LMF or the second UE.Component 198 may also be configured to generate adjusted timing parameters for communication based on at least one of the synchronization reference type or the change time. Component 198 may also be configured to receive a marker for cell information from the LMF or the second UE in at least one of the first indication or signaling separate from the first indication. Component 198 may also be configured to perform location calculations based on at least one of the communication or the adjusted timing parameters. Component 198 may be further configured to perform a combination. Figure 9 , Figure 10 , Figure 11 , Figure 12 Any aspect described in the flowchart of any of the above and / or by the UE for any aspect Figure 5 , Figure 6 , Figure 7 , Figure 8Any aspect of the process / algorithm performed by any of the components. Component 198 may be within cellular baseband processor 1324, application processor 1306, or both cellular baseband processor 1324 and application processor 1306. Component 198 may be one or more hardware components specifically configured to perform the stated process / algorithm, implemented by one or more processors configured to execute the stated process / algorithm, stored in a computer-readable medium for implementation by one or more processors, or some combination thereof. When multiple processors are implemented, the multiple processors may execute the stated process / algorithm individually or in combination. As shown, device 1304 may include various components configured for various functions. In one configuration, device 1304 (and specifically cellular baseband processor 1324 and / or application processor 1306) may include components for identifying a synchronization reference type of the synchronization reference source based on synchronization between the first UE and the synchronization reference source, wherein the synchronization reference type is one or more of the following: GNSS, network node, or synchronization reference UE. In this configuration, device 1304 (and specifically cellular baseband processor 1324 and / or application processor 1306) may include components for detecting changes in time associated with the anchor entity, wherein the changes in time include at least one of the following: a first time since the last synchronization update, a second time since the last synchronization update, or a correction amount corrected in one or more last synchronization updates. In this configuration, device 1304 (and specifically cellular baseband processor 1324 and / or application processor 1306) may include components for providing at least one of the following to the LMF or the second UE: a first indication of the synchronization reference type, a quality metric, or the changes in time for the synchronization reference source. In one configuration, device 1304 (and specifically cellular baseband processor 1324 and / or application processor 1306) may include components for identifying the satellite constellation associated with the GNSS. In one configuration, device 1304 (and specifically cellular baseband processor 1324 and / or application processor 1306) may include components for reporting a second indication of the satellite constellation to the LMF or the second UE. In one configuration, device 1304 (and specifically cellular baseband processor 1324 and / or application processor 1306) may include components for identifying cell information associated with the network node. In one configuration, device 1304 (and specifically cellular baseband processor 1324 and / or application processor 1306) may include components for reporting a marker of the cell information to the LMF or the second UE in the first indication. In one configuration, device 1304 (and specifically cellular baseband processor 1324 and / or application processor 1306) may include components for identifying the reception time of the S-SSB and the frequency location associated with synchronization with the synchronization reference UE.In one configuration, device 1304 (and specifically cellular baseband processor 1324 and / or application processor 1306) may include components for reporting the reception time and frequency location to the LMF or the second UE. In one configuration, device 1304 (and specifically cellular baseband processor 1324 and / or application processor 1306) may include components for identifying cell information associated with the quality metric. In one configuration, device 1304 (and specifically cellular baseband processor 1324 and / or application processor 1306) may include components for reporting a second indication of the cell information to the LMF or the second UE in at least one of the first indication or signaling separate from the first indication. In another configuration, device 1304 (and specifically cellular baseband processor 1324 and / or application processor 1306) may include components for receiving from at least one of an LMF or a second UE a synchronization reference type, a quality metric, or a change time for a synchronization reference source, wherein the synchronization reference type is associated with the synchronization of the first UE with the synchronization reference source and is one or more of the following: GNSS, a network node, or a synchronization reference UE, wherein the change time is associated with an anchor entity and includes at least one of the following: a first time since the last synchronization update, a second time since the last synchronization update, or a correction amount corrected in one or more last synchronization updates. In this configuration, device 1304 (and specifically cellular baseband processor 1324 and / or application processor 1306) may include components for communicating based on at least one of the first indication of the synchronization reference type, the quality metric, or the change time for the synchronization reference source. In one configuration, device 1304 (and specifically cellular baseband processor 1324 and / or application processor 1306) may include components for receiving a second indication of a satellite constellation from the LMF or the second UE, wherein the satellite constellation is associated with the GNSS. In one configuration, device 1304 (and specifically cellular baseband processor 1324 and / or application processor 1306) may include components for receiving a tag of cell information from the LMF or the second UE in the first notification, wherein the cell information is associated with the network node. In one configuration, device 1304 (and specifically cellular baseband processor 1324 and / or application processor 1306) may include components for receiving the reception time of the S-SSB from the LMF or the second UE and the frequency position associated with synchronization with the synchronization reference UE. In one configuration, device 1304 (and specifically cellular baseband processor 1324 and / or application processor 1306) may include components for receiving cell information from the LMF or the second UE in at least one of the first indication or signaling separate from the first indication.In one configuration, device 1304 (and specifically cellular baseband processor 1324 and / or application processor 1306) may include components for generating adjusted timing parameters for communication based on at least one of the synchronization reference type or the change time. In another configuration, device 1304 (and specifically cellular baseband processor 1324 and / or application processor 1306) may include components for performing location calculations based on at least one of the communication or the adjusted timing parameters. This component may be component 198 of device 1304 configured to perform the functions described therein. As described above, device 1304 may include a TX processor 368, an RX processor 356, and a controller / processor 359. Therefore, in one configuration, the component may be the TX processor 368, the RX processor 356, and / or the controller / processor 359 configured to perform the functions described therein.

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

[0177] As discussed above, component 199 can be configured to operate in a manner consistent with component 198. Component 199 can be configured to provide synchronization information to the UE. Component 199 can also be configured to communicate with the UE or at least one of the other UEs based on the first indication of the synchronization reference type of the synchronization reference source, the quality metric, and / or the time of change. Component 199 can be further configured to perform a combination. Figure 9 , Figure 10 , Figure 11 , Figure 12Any aspect described in the flowchart of any of the above and / or by network nodes / entities Figure 5 , Figure 6 , Figure 7 , Figure 8 Component 199 may be any aspect of any of the aspects executed by any of the components. Component 199 may be within one or more processors of one or more of CU 1410, DU 1430, and RU 1440. Component 199 may be one or more hardware components specifically configured to perform the stated process / algorithm, implemented by one or more processors configured to execute the stated process / algorithm, stored in a computer-readable medium for implementation by one or more processors, or some combination thereof. When multiple processors are implemented, the multiple processors may execute the stated process / algorithm individually or in combination. Network entity 1402 may include a variety of components configured for various functions. In one configuration, network entity 1402 may include components for operating in a manner commensurate with component 198. In one configuration, network entity 1402 may include components for providing synchronization information to the UE. In one configuration, network entity 1402 may include components for communicating with the UE or at least one of another UEs based on the first indication of the synchronization reference type of the synchronization reference source, the quality metric, and / or the time of change. The component may be a component 199 of network entity 1402 configured to perform the functions described therein. As described above, network entity 1402 may include a TX processor 316, an RX processor 370, and a controller / processor 375. Therefore, in one configuration, the component may be the TX processor 316, the RX processor 370, and / or the controller / processor 375 configured to perform the functions described therein.

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

[0179] As discussed above, component 199 can be configured to operate in a manner consistent with component 198. Component 199 can be configured to provide synchronization information to the UE. Component 199 can also be configured to communicate with the UE or at least one of the other UEs based on the first indication of the synchronization reference type of the synchronization reference source, the quality metric, and / or the time of change. Component 199 can be further configured to perform a combination. Figure 9 , Figure 10 , Figure 11 , Figure 12 Any aspect described in the flowchart of any of the above and / or by network nodes / entities Figure 5 , Figure 6 , Figure 7 , Figure 8Any aspect of the process / algorithm performed by any of the components. Component 199 may be within network processor 1512. Component 199 may be one or more hardware components specifically configured to perform the stated process / algorithm, implemented by one or more processors configured to perform the stated process / algorithm, stored in a computer-readable medium for implementation by one or more processors, or some combination thereof. When multiple processors are implemented, the multiple processors may execute the stated process / algorithm individually or in combination. Network entity 1560 may include a variety of components configured for various functions. In one configuration, network entity 1560 may include components for operating in a manner commensurate with component 198. In one configuration, network entity 1560 may include components for providing synchronization information to the UE. In one configuration, network entity 1560 may include components for communicating with the UE or at least one of another UEs based on the first indication of the synchronization reference type of the synchronization reference source, the quality metric, and / or the time of change. This component may be component 199 of network entity 1560 configured to perform the functions described therein.

[0180] Wireless communication networks can support the location of wireless devices. For example, based on reference signal communication between an anchor entity (e.g., a network node, base station, eNB, gNB, TRP, etc.) and the wireless device, the UE can use the Time-of-Arrival (TDoA) associated with that reference signal communication to determine the location / positioning of the wireless device. As an example of TDoA, a wireless device can locate itself or another wireless device based on the time difference of arrival of a positioning reference signal. In an uplink-like TDoA, the wireless device can send a PRS (Presentation Reference Signal), and the anchor entity can report the time when it received the PRS back to the wireless device. The location of the wireless device can be calculated based on the difference between the arrival times and the anchor entity's location. In a downlink-like TDoA, multiple anchor entities can send PRSs, the wireless device can receive those PRSs, and the location of the wireless device can be calculated based on the difference in arrival times and the anchor entity's location. In Uu interface positioning, the anchor entity can report a quality metric for the relative time difference between itself and a synchronization reference source. This quality metric can be the rtd-Quality field in the RTD-InfoElement, which can be used for anchor entity selection. However, if the anchor entity is not fully synchronized with its synchronization reference source (e.g., GNSS, network nodes, and / or independent synchronization reference UEs), uncertainties may be introduced into arrival time and time difference measurements, which in turn may introduce uncertainties into the calculated location. For example, the anchor entity may be synchronized with the synchronization reference source, and this synchronization may shift by a certain amount of time over a period of time, within which corrections should be applied to avoid synchronization errors. However, the examples used for synchronization error management do not provide mitigation for the effects caused by synchronization errors between anchor UEs in SL TDoA measurements.

[0181] This paper describes various aspects of timing information exchange for enhanced sidelink positioning, enabling synchronization information exchange to mitigate the impact of synchronization errors between anchor UEs in SL-based TDoA measurements. Exchanging anchor UE synchronization information (e.g., associated with synchronization reference source, RTD, synchronization quality information, synchronization reference type, and / or change time) between the UE and the LMF or another UE improves positioning. Providing the synchronization reference type and change time of the synchronization reference source to the LMF and SL UE makes it possible to correct synchronization errors between anchor UEs in SL positioning measurements. Additionally, correcting such synchronization errors improves the positioning accuracy of wireless devices in the wireless communication network.

[0182] It should be understood that the specific order or hierarchy of the boxes in the disclosed process / flowcharts is merely an example of the exemplary method. It should be understood that the specific order or hierarchy of the boxes in the process / flowcharts may be rearranged based on design preferences. Furthermore, some boxes may be combined or omitted. The appended method claims present the elements of various boxes in a sample order, but are not limited to the given specific order or hierarchy.

[0183] The foregoing description is provided to enable any person skilled in the art to practice the various aspects described herein. Various modifications to these aspects will be apparent to those skilled in the art, and the general principles defined herein may be applied to other aspects. Therefore, the claims are not limited to the aspects described herein but should be given the full scope consistent with the language of the claims. Unless specifically stated otherwise, references to elements in the singular form do not mean “one and only one” but rather “one or more.” Terms such as “if,” “when,” and “simultaneously” do not imply a direct temporal relationship or reaction. That is, these phrases, such as “when,” do not imply an immediate action in response to the occurrence of an action or during the occurrence of an action, but simply suggest that an action will occur if the condition is met, without requiring a specific or immediate time limit for the occurrence of the action. The word “exemplary” is used herein to mean “serving as an example, instance, or illustration.” Any aspect described herein as “exemplary” is not necessarily to be construed as preferred or superior to other aspects. Unless otherwise specifically stated, the term “some” refers to one or more. Combinations such as "at least one of A, B, or C", "one or more of A, B, or C", "at least one of A, B, and C", "one or more of A, B, and C", and "A, B, C, or any combination thereof" include any combination of A, B, and / or C, and may include multiple A, multiple B, or multiple C. Specifically, combinations such as "at least one of A, B, or C", "one or more of A, B, or C", "at least one of A, B, and C", "one or more of A, B, and C", and "A, B, C, or any combination thereof" may be only A, only B, only C, A and B, A and C, B and C, or A and B and C, wherein any such combination may contain one or more members of A, B, or C. A set should be interpreted as a collection of elements in which the number of elements is one or more. Therefore, for a set of X, X will include one or more elements. When at least one processor is configured to execute a set of functions, the at least one processor is configured to execute the set of functions individually or in any combination. Therefore, each of the at least one processor can be configured to perform a specific subset of the set of functions, wherein the subset is the complete set, a suitable subset of the set, or an empty subset of the set. If the first device receives data from or sends data to the second device, data can be received / sent directly between the first and second devices, or indirectly between the first and second devices via a set of devices. A device configured to “output” data (such as transmission, signaling, or messaging) can, for example, transmit the data using a transceiver, or can transmit the data to the device that sent the data. A device configured to “receive” data (such as transmission, signaling, or messaging) can, for example, receive the data using a transceiver, or can obtain the data from the device that received the data.Information stored in memory includes instructions and / or data. All structural and functional equivalents of the elements throughout the various aspects described herein that are known to or will later be known to a person skilled in the art are expressly incorporated herein by reference and are covered by the claims. Furthermore, nothing disclosed herein is intended to be offered to the public, whether or not such disclosure is expressly recited in the claims. The terms “module,” “mechanism,” “element,” “device,” etc., cannot replace the word “component.” Therefore, no claim element will be construed as a functional component unless the element is expressly recited using the phrase “component for…”.

[0184] As used in this article, the phrase “based on” should not be interpreted as referring to a closed set of information, one or more conditions, one or more factors, etc. In other words, the phrase “based on A” (where “A” can be information, conditions, factors, etc.) should be interpreted as “based on at least A”, unless otherwise stated otherwise.

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

[0186] Aspect 1 is a method for wireless communication at a first user equipment (UE), the method comprising: identifying a synchronization reference type of the synchronization reference source based on synchronization between the first UE and the synchronization reference source, wherein the synchronization reference type is one or more of the following: a Global Navigation Satellite System (GNSS), a network node, or a synchronization reference UE; and providing at least one of a first indication, a quality metric, or a change time of the synchronization reference source to a location management function (LMF) or a second UE as the basis for communication, wherein the change time includes at least one of the following: a first time since the last synchronization update, a second time since the last synchronization update, or a correction amount corrected in one or more last synchronization updates.

[0187] Aspect 2 is the method according to aspect 1, wherein the change time includes the first time since the last synchronization update, wherein the first time is based on at least one of the number of symbols, absolute time, or relative time associated with a duration threshold.

[0188] Aspect 3 is the method according to any one of Aspects 1 and 2, wherein the change time includes the second time of the last synchronization update, wherein the second time is at least one of absolute time, a time period associated with a system frame number (SFN), or a time period associated with a direct frame number (DFN).

[0189] Aspect 4 is the method according to any one of Aspects 1 to 3, wherein the change time includes the correction amount corrected in the last one or more synchronous updates.

[0190] Aspect 5 is the method according to aspect 4, wherein the change time is based on the average of at least two or more of the previous one or more synchronous updates.

[0191] Aspect 6 is a method according to any one of Aspects 1 to 5, wherein the synchronization reference type is based on synchronization with the GNSS, wherein the method further includes: identifying a satellite constellation associated with the GNSS; and reporting a second indication of the satellite constellation to the LMF or the second UE.

[0192] Aspect 7 is the method according to aspect 6, wherein reporting the second instruction to the satellite constellation includes reporting the second instruction in the first instruction.

[0193] Aspect 8 is a method according to any one of Aspects 1 to 5, wherein the synchronization reference type is based on synchronization with the network node, wherein the method further includes: identifying cell information associated with the network node; and reporting the cell information to the LMF or the second UE in the first indication.

[0194] Aspect 9 is a method according to any one of Aspects 1 to 5, wherein the synchronization reference type is based on synchronization with the synchronization reference UE, wherein the method further comprises: identifying the reception time of a side link (SL) synchronization signal block (S-SSB) and the frequency position associated with the synchronization with the synchronization reference UE; and reporting the reception time and the frequency position to the LMF or the second UE.

[0195] Aspect 10 is the method according to aspect 9, wherein the reception time is at least one of absolute time, a time period associated with a system frame number (SFN), or a time period associated with a direct frame number (DFN).

[0196] Aspect 11 is a method according to any one of Aspects 1 to 10, wherein the quality metric is associated with at least one of the following: a specific implementation of the anchor entity; a communication layer message of the LMF or another UE; a configuration at the first UE; or a request from the first UE; or cell information associated with the quality metric.

[0197] Aspect 12 is a method according to any one of aspects 1 to 11, the method further comprising: identifying cell information associated with the quality metric; and reporting a second indication of the cell information to the LMF or the second UE in at least one of the first indication or signaling separate from the first indication.

[0198] Aspect 13 is a method according to any one of Aspects 1 to 12, wherein the quality metric is a relative time difference (RTD) between a first arrival time (ToA) associated with a first reference signal from the anchor entity and a second ToA associated with a second reference signal from the second UE, wherein the second UE is configured as a side link (SL) UE with the first UE.

[0199] Aspect 14 is a method of wireless communication at a first user equipment (UE), the method comprising: receiving from at least one of a location management function (LMF) or a second UE a first indication of a synchronization reference type, a quality metric, or a change time for a synchronization reference source, wherein the synchronization reference type is associated with the synchronization of the first UE with the synchronization reference source and is one or more of the following: a Global Navigation Satellite System (GNSS), a network node, or a synchronization reference UE, wherein the change time is associated with an anchor entity and includes at least one of the following: a first time since the last synchronization update, a second time of the last synchronization update, or a correction amount corrected in one or more last synchronization updates; and communicating based on at least one of the first indication of the synchronization reference type for the synchronization reference source, the quality metric, or the change time.

[0200] Aspect 15 is the method according to aspect 14, wherein the change time includes the first time since the last synchronization update, wherein the first time is based on at least one of the number of symbols, absolute time, or relative time associated with a duration threshold.

[0201] Aspect 16 is the method according to any one of Aspects 14 and 15, wherein the change time includes the second time of the last synchronization update, wherein the second time is at least one of absolute time, a time period associated with a system frame number (SFN), or a time period associated with a direct frame number (DFN).

[0202] Aspect 17 is the method according to any one of aspects 14 to 16, wherein the change time includes the correction amount corrected in the last one or more synchronous updates.

[0203] Aspect 18 is the method according to aspect 17, wherein the change time is based on the average of at least two or more of the previous one or more synchronous updates.

[0204] Aspect 19 is a method according to any one of Aspects 14 to 18, wherein the synchronization reference type is based on synchronization with the GNSS, wherein the method further comprises: receiving a second indication of a satellite constellation from the LMF or the second UE, wherein the satellite constellation is associated with the GNSS.

[0205] Aspect 20 is the method according to aspect 19, wherein receiving the second instruction to the satellite constellation includes receiving the second instruction in the first instruction.

[0206] Aspect 21 is a method according to any one of Aspects 14 to 18, wherein the synchronization reference type is based on synchronization with the network node, wherein the method further comprises: receiving a tag of cell information in the first indication from the LMF or the second UE, wherein the cell information is associated with the network node.

[0207] Aspect 22 is a method according to any one of Aspects 14 to 18, wherein the synchronization reference type is based on synchronization with the synchronization reference UE, wherein the method further comprises: receiving the reception time of a side link (SL) synchronization signal block (S-SSB) from the LMF or the second UE and the frequency position associated with the synchronization with the synchronization reference UE.

[0208] Aspect 23 is the method according to aspect 22, wherein the reception time is at least one of absolute time, a time period associated with a system frame number (SFN), or a time period associated with a direct frame number (DFN).

[0209] Aspect 24 is a method according to any one of aspects 14 to 23, wherein the quality metric is associated with at least one of: a specific implementation of the anchor entity; a communication layer message of the LMF or another UE; a configuration at the first UE; a request from the first UE; or cell information associated with the quality metric.

[0210] Aspect 25 is the method according to aspect 24, the method further comprising: receiving a marker from the LMF or the second UE in at least one of the first indication or signaling separate from the first indication.

[0211] Aspect 26 is a method according to any one of Aspects 14 to 25, wherein the quality metric is a relative time difference (RTD) between a first time of arrival (ToA) associated with a first reference signal from the anchor entity and a second ToA associated with a second reference signal from the second UE, wherein the second UE is configured as a side link (SL) UE with the first UE.

[0212] Aspect 27 is an apparatus for wireless communication, the apparatus including components for implementing any one of aspects 1 to 13.

[0213] Aspect 28 is a computer-readable medium (e.g., a non-transitory computer-readable medium) storing computer-executable code that, when executed by at least one processor, causes the at least one processor to implement any one of aspects 1 to 13.

[0214] Aspect 29 is an apparatus for wireless communication at a network node. The apparatus includes: a memory; and at least one processor coupled to the memory and based at least in part on information stored in the memory, the at least one processor being configured to implement any one of aspects 1 to 13.

[0215] Aspect 30 is the apparatus according to aspect 29, the apparatus further comprising at least one of a transceiver or an antenna coupled to the at least one processor.

[0216] Aspect 31 is an apparatus for wireless communication, the apparatus including components for implementing any one of aspects 14 to 26.

[0217] Aspect 32 is a computer-readable medium (e.g., a non-transitory computer-readable medium) storing computer-executable code that, when executed by at least one processor, causes the at least one processor to implement any one of aspects 14 to 26.

[0218] Aspect 33 is an apparatus for wireless communication at a network node. The apparatus includes: a memory; and at least one processor coupled to the memory and based at least in part on information stored in the memory, the at least one processor being configured to implement any one of aspects 14 to 26.

[0219] Aspect 34 is the apparatus according to aspect 33, the apparatus further comprising at least one of a transceiver or an antenna coupled to the at least one processor.

[0220] Aspect 35 is an apparatus for wireless communication at a user equipment (UE), the apparatus comprising: at least one memory; and at least one processor coupled to the at least one memory and based at least in part on information stored in the at least one memory, the at least one processor being configured individually or in any combination to perform the method according to any one of aspects 1 to 13.

[0221] Aspect 36 is an apparatus for wireless communication at a user equipment (UE), the apparatus comprising components for performing each step of the method according to any one of aspects 1 to 13.

[0222] Aspect 37 is an apparatus according to any one of aspects 35 to 36, the apparatus further comprising a transceiver configured to receive or transmit in association with the method according to any one of aspects 1 to 13.

[0223] Aspect 38 is a computer-readable medium (e.g., a non-transitory computer-readable medium) that stores computer-executable code at a user equipment (UE), the code causing the at least one processor to perform the method according to any one of aspects 1 to 13 when executed by at least one processor.

[0224] Aspect 39 is an apparatus for wireless communication at a user equipment (UE), the apparatus comprising: at least one memory; and at least one processor coupled to the at least one memory and based at least in part on information stored in the at least one memory, the at least one processor being configured individually or in any combination to perform the method according to any one of aspects 14 to 26.

[0225] Aspect 40 is an apparatus for wireless communication at a user equipment (UE), the apparatus comprising components for performing each step of the method according to any one of aspects 14 to 26.

[0226] Aspect 41 is an apparatus according to any one of aspects 39 to 40, the apparatus further comprising a transceiver configured to receive or transmit in association with the method according to any one of aspects 14 to 26.

[0227] Aspect 42 is a computer-readable medium (e.g., a non-transitory computer-readable medium) storing computer-executable code at a user equipment (UE), the code causing the at least one processor to perform a method according to any one of aspects 14 to 26 when executed by at least one processor.

Claims

1. An apparatus for performing wireless communication at a first user equipment (UE), the apparatus comprising: At least one memory; and At least one processor, coupled to the at least one memory, and configured individually or in any combination, based at least in part on information stored in the at least one memory, to: Receives at least one of a first indication, a quality metric, or a change time for a synchronization reference source from at least one of a location management function (LMF) or a second UE, wherein the synchronization reference type is associated with the synchronization of the first UE with the synchronization reference source and is one or more of the following: a Global Navigation Satellite System (GNSS), a network node, or a synchronization reference UE, wherein the change time is associated with an anchor entity and includes at least one of the following: a first time since the last synchronization update, a second time of the last synchronization update, or a correction amount corrected in one or more last synchronization updates; and Communication is based on at least one of the first indication of the synchronization reference type of the synchronization reference source, the quality metric, or the change time.

2. The apparatus of claim 1, wherein the change time includes the first time since the last synchronization update, wherein the first time is based on at least one of the number of symbols, absolute time, or relative time associated with a duration threshold.

3. The apparatus of claim 1, wherein the change time includes the second time of the last synchronization update, wherein the second time is at least one of an absolute time, a time period associated with a system frame number (SFN), or a time period associated with a direct frame number (DFN).

4. The apparatus of claim 1, wherein the change time includes the correction amount corrected in the last one or more synchronization updates.

5. The apparatus of claim 4, wherein the change time is based on the average of at least two or more of the previous one or more synchronous updates.

6. The apparatus of claim 1, wherein the synchronization reference type is based on synchronization with the GNSS, wherein the at least one processor is further configured, individually or in any combination, to: Receive a second indication of a satellite constellation from the LMF or the second UE, wherein the satellite constellation is associated with the GNSS.

7. The apparatus of claim 6, wherein, in order to receive the second instruction for the satellite constellation, the at least one processor is configured individually or in any combination to receive the second instruction in the first instruction.

8. The apparatus of claim 1, wherein the synchronization reference type is based on synchronization with the network node, wherein the at least one processor is further configured individually or in any combination to: The LMF or the second UE receives a tag of the cell information in the first indication, wherein the cell information is associated with the network node.

9. The apparatus of claim 1, wherein the synchronization reference type is based on synchronization with the synchronization reference UE, wherein the at least one processor is further configured individually or in any combination to: The reception time of the side link (SL) synchronization signal block (S-SSB) received from the LMF or the second UE is associated with the frequency position of the synchronization with the synchronization reference UE.

10. The apparatus of claim 9, wherein the reception time is at least one of absolute time, a time period associated with a system frame number (SFN), or a time period associated with a direct frame number (DFN).

11. The apparatus of claim 1, wherein the mass metric is associated with at least one of the following: The specific implementation of the anchor entity; The LMF or another UE's communication layer message; Configuration at the first UE; A request from the first UE; or Cell information associated with the quality metric.

12. The apparatus of claim 1, wherein the at least one processor is further configured, alone or in any combination, to: A marker indicating that cell information is received from the LMF or the second UE in at least one of the first indication or a signaling separate from the first indication.

13. The apparatus of claim 1, wherein the quality metric is a relative time difference (RTD) between a first arrival time (ToA) associated with a first reference signal from the anchor entity and a second ToA associated with a second reference signal from the second UE, wherein the second UE is configured as a side link (SL) UE with the first UE.

14. The apparatus of claim 1, further comprising a transceiver coupled to the at least one processor, wherein, in order to communicate based on the first indication of the synchronization reference type of the synchronization reference source and the change time, the at least one processor is configured individually or in any combination to communicate via the transceiver based on the first indication of the synchronization reference type of the synchronization reference source and the change time.

15. An apparatus for performing wireless communication at a first user equipment (UE), the apparatus comprising: At least one memory; and At least one processor, coupled to the at least one memory, and configured individually or in any combination, based at least in part on information stored in the at least one memory, to: The synchronization reference type of the synchronization reference source is identified based on the synchronization between the first UE and the synchronization reference source, wherein the synchronization reference type is one or more of the following: Global Navigation Satellite System (GNSS), network node, or synchronization reference UE. as well as The location management function (LMF) or the second UE provides at least one of the following as the basis for communication: a first indication of the synchronization reference type of the synchronization reference source, a quality metric, or a change time, wherein the change time includes at least one of the following: a first time since the last synchronization update, a second time of the last synchronization update, or a correction amount corrected in one or more last synchronization updates.

16. The apparatus of claim 15, wherein the change time includes the first time since the last synchronization update, wherein the first time is based on at least one of the number of symbols, absolute time, or relative time associated with a duration threshold.

17. The apparatus of claim 15, wherein the change time includes the second time of the last synchronization update, wherein the second time is at least one of an absolute time, a time period associated with a system frame number (SFN), or a time period associated with a direct frame number (DFN).

18. The apparatus of claim 15, wherein the change time includes the correction amount corrected in the last one or more synchronization updates.

19. The apparatus of claim 18, wherein the change time is based on the average of at least two or more of the previous one or more synchronous updates.

20. The apparatus of claim 15, wherein the synchronization reference type is based on synchronization with the GNSS, wherein the at least one processor is further configured, individually or in any combination, to: Identify the satellite constellation associated with the GNSS; and Report a second instruction on the satellite constellation to the LMF or the second UE.

21. The apparatus of claim 20, wherein, in order to report the second instruction to the satellite constellation, the at least one processor is configured, individually or in any combination, to report the second instruction in the first instruction.

22. The apparatus of claim 15, wherein the synchronization reference type is based on synchronization with the network node, wherein the at least one processor is further configured individually or in any combination to: Cell information associated with the network node; and The first instruction includes a flag that reports the cell information to the LMF or the second UE.

23. The apparatus of claim 15, wherein the synchronization reference type is based on synchronization with the synchronization reference UE, wherein the at least one processor is further configured individually or in any combination to: The reception time of the identification side link (SL) synchronization signal block (S-SSB) and the frequency position associated with the synchronization with the synchronization reference UE; and The receiving time and the frequency position are reported to the LMF or the second UE.

24. The apparatus of claim 23, wherein the reception time is at least one of absolute time, a time period associated with a system frame number (SFN), or a time period associated with a direct frame number (DFN).

25. The apparatus of claim 15, wherein the mass metric is associated with at least one of the following: The specific implementation of the anchor entity; The LMF or another UE's communication layer message; Configuration at the first UE; or A request from the first UE; or Cell information associated with the quality metric.

26. The apparatus of claim 25, wherein the at least one processor is further configured, alone or in any combination, to: Identify cell information associated with the quality metric; and In at least one of the first instruction or signaling separate from the first instruction, a second instruction regarding the cell information is reported to the LMF or the second UE.

27. The apparatus of claim 15, wherein the quality metric is a relative time difference (RTD) between a first arrival time (ToA) associated with a first reference signal from the anchor entity and a second ToA associated with a second reference signal from the second UE, wherein the second UE is configured as a side link (SL) UE with the first UE.

28. The apparatus of claim 15, further comprising a transceiver coupled to the at least one processor, wherein, in order to provide the first indication of the synchronization reference type of the synchronization reference source and the change time, the at least one processor is configured individually or in any combination to provide, via the transceiver, the first indication of the synchronization reference type of the synchronization reference source and the change time to at least one of the LMF or the second UE.

29. A method for wireless communication for a first user equipment (UE), the method comprising: Receives at least one of a first indication, a quality metric, or a change time for a synchronization reference source from at least one of a location management function (LMF) or a second UE, wherein the synchronization reference type is associated with the synchronization of the first UE with the synchronization reference source and is one or more of the following: a Global Navigation Satellite System (GNSS), a network node, or a synchronization reference UE, wherein the change time is associated with an anchor entity and includes at least one of the following: a first time since the last synchronization update, a second time of the last synchronization update, or a correction amount corrected in one or more last synchronization updates; and Communication is based on at least one of the first indication of the synchronization reference type of the synchronization reference source, the quality metric, or the change time.

30. A method for wireless communication for a first user equipment (UE), the method comprising: The synchronization reference type of the synchronization reference source is identified based on the synchronization between the first UE and the synchronization reference source, wherein the synchronization reference type is one or more of the following: Global Navigation Satellite System (GNSS), network node, or synchronization reference UE. The location management function (LMF) or the second UE provides at least one of the following as the basis for communication: a first indication of the synchronization reference type of the synchronization reference source, a quality metric, or a change time, wherein the change time includes at least one of the following: a first time since the last synchronization update, a second time of the last synchronization update, or a correction amount corrected in one or more last synchronization updates.

Images