Ue GNSS assistance through sidelink-based communications

Abstract

A method and related apparatus for wireless communication at a first user equipment (UE) are provided. In the method, the first UE obtains global navigation satellite system (GNSS) assistance data for a sidelink positioning session with one or more second UEs via a sidelink message, and calculates a positioning of at least one of the first UE or the one or more second UEs based on the GNSS assistance data for the sidelink positioning session. The first UE also outputs an indication indicating the calculated location of at least one of the first UE or the one or more second UEs. The method provides a signaling mechanism that supports communication of positioning data over a sidelink connection of the UE. This enhances the positioning accuracy of the UE operating on the sidelink connection, and improves the efficiency of wireless communications.

Description

[0001] CROSS-REFERENCE TO RELATED APPLICATIONS

[0002] This application claims the benefit of and priority to U.S. Provisional Application No. 63 / 484,719, filed on February 13, 2023, entitled “UE GNSS ASSISTANCE OVERSIDELINK-BASED COMMUNICATION,” and U.S. Non-Provisional Patent Application Serial No. 18 / 327,645, filed on June 1, 2023, entitled “UE GNSS ASSISTANCE OVERSIDELINK-BASED COMMUNICATION,” which are expressly incorporated herein by reference in their entireties. Technical Field

[0003] The present disclosure relates generally to communication systems, and more particularly to Global Navigation Satellite System (GNSS) assistance provided through sidelink-based communication for user equipment (UE) in wireless communications. Background Art

[0004] Wireless communication systems are widely deployed to provide a variety of telecommunication services, such as telephony, video, data, messaging, and broadcasts. Typical wireless communication systems 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), time division multiple access (TDMA), frequency division multiple access (FDMA), orthogonal frequency division multiple access (OFDMA), single-carrier frequency division multiple access (SC-FDMA), and time division synchronous code division multiple access (TD-SCDMA).

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

[0006] The following presents a simplified summary of one or more aspects in order to provide a basic understanding of these aspects. This summary is not an extensive overview of all contemplated aspects. This summary does not identify key or critical elements of all aspects, nor does it delineate 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 description that will be presented later.

[0007] In one aspect of the present disclosure, a method, computer-readable medium, and apparatus for wireless communication at a user equipment (UE) are provided. The apparatus may include at least one memory and at least one processor coupled to the at least one memory. Based at least in part on information stored in the at least one memory, the at least one processor may be configured to: obtain, via a sidelink message, Global Navigation Satellite System (GNSS) assistance data for a sidelink positioning session with one or more second UEs; calculate a position of at least one of the first UE or the one or more second UEs based on the GNSS assistance data for the sidelink positioning session; and output an indication of the calculated position to the first UE or at least one of the one or more second UEs.

[0008] In one aspect of the present disclosure, a method, computer-readable medium, and apparatus for wireless communication at a network node are provided. The apparatus may include at least one memory and at least one processor coupled to the at least one memory. Based at least in part on information stored in the at least one memory, the at least one processor may be configured to: configure GNSS assistance data for a sidelink positioning session between a first UE and one or more second UEs; and send, to the first UE, the GNSS assistance data for the sidelink positioning session between the first UE and the one or more second UEs.

[0009] To achieve the foregoing and related ends, one or more aspects may include the features fully described below and particularly pointed out in the claims. The following description and the accompanying drawings set forth in detail some illustrative features of one or more aspects. However, these features are indicative of only some of the various ways in which the principles of the various aspects may be employed. BRIEF DESCRIPTION OF THE DRAWINGS

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

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

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

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

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

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

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

[0017] Figure 5 is a diagram illustrating an example of common signaling and dedicated signaling of GNSS assistance data implemented through a UE-UTRAN (Uu) connection.

[0018] Figure 6 is a diagram illustrating example GNSS data types and example GNSS data elements associated with the GNSS data types.

[0019] Figure 7 is a diagram illustrating an example of GNSS assistance data in SLPP positioning assistance data exchange in case of SLPP on PC5-U SL DRB according to various aspects of the present disclosure.

[0020] Figure 8 is a diagram illustrating an example of GNSS assistance data in SLPP positioning assistance data exchange in case of SLPP over PDCP on SL SRB according to various aspects of the present disclosure.

[0021] Figure 9 is a diagram illustrating an example of GNSS assistance data in SLPP positioning assistance data exchange in case of SLPP over PC5-RRC over SL SRB according to various aspects of the present disclosure.

[0022] Figure 10 is a diagram illustrating an example of GNSS assistance data in SLPP positioning assistance data exchange in case of SLPP on PC5-S on SL SRB according to various aspects of the present disclosure.

[0023] Figure 11 is a call flow diagram illustrating a method of wireless communication according to various aspects of the present disclosure.

[0024] Figure 12 is a flowchart illustrating a method of wireless communication at a UE according to various aspects of the present disclosure.

[0025] Figure 13 is a flowchart illustrating a method of wireless communication at a UE according to various aspects of the present disclosure.

[0026] Figure 14 is a flow chart illustrating a method of wireless communication at a network node according to various aspects of the present disclosure.

[0027] Figure 15 is a flow chart illustrating a method of wireless communication at a network node according to various aspects of the present disclosure.

[0028] Figure 16 are diagrams illustrating examples of hardware implementations for example apparatuses and / or network entities.

[0029] Figure 17 is a diagram illustrating an example of a hardware implementation for an example network entity. DETAILED DESCRIPTION

[0030] UEs operating over cellular connections can receive or request GNSS assistance data, thereby enhancing positioning accuracy. However, UEs operating over sidelink connections do not have this capability due to the lack of a defined signaling mechanism to deliver this data. Enabling GNSS assistance data delivery over sidelink connections will fill this technology gap and will provide UEs on sidelink connections with the same positioning accuracy benefits as those on cellular connections.

[0031] Various aspects generally relate to communication systems. Some aspects more specifically relate to providing GNSS assistance data via sidelink-based communication for UEs in wireless communication. In some examples, a first UE may be configured to: obtain Global Navigation Satellite System (GNSS) assistance data for a sidelink positioning session with one or more second UEs via a sidelink message; calculate a position of at least one of the first UE or the one or more second UEs based on the assistance data for the sidelink positioning session; and output an indication indicating the position of at least one of the first UE or the one or more second UEs.

[0032] Certain aspects of the subject matter described in this disclosure can be implemented to achieve one or more of the following potential advantages. In some examples, the described techniques can be used to provide a signaling mechanism that supports communicating positioning data over a UE's sidelink connection by obtaining GNSS assistance data for a sidelink positioning session with one or more second UEs via a sidelink message, and calculating a position of at least one of the first UE or the one or more second UEs based on the assistance data for the sidelink positioning session. This enhances positioning accuracy for UEs operating on the sidelink connection and improves the efficiency of wireless communications.

[0033] The detailed description set forth below in conjunction with the accompanying drawings is a description of various configurations and does not represent the only configurations in which the concepts described herein may be practiced. The detailed description includes specific details to provide a thorough understanding of the various concepts. However, these concepts may be practiced without these specific details. In some cases, well-known structures and components are shown in block diagram form to avoid obscuring such concepts.

[0034] Several aspects of telecommunications systems are presented with reference to various apparatus and methods. These apparatus and methods are described in the following detailed description and illustrated in the accompanying drawings by various blocks, components, circuits, processes, algorithms, etc. (collectively referred to as "elements"). These elements 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 overall system.

[0035] As an example, an element, or any part of an element, or any combination of elements, can be implemented as a "processing system" that includes one or more processors. When multiple processors are implemented, the multiple processors can 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, systems on a chip (SoCs), baseband processors, field programmable gate arrays (FPGAs), programmable logic devices (PLDs), state machines, gating logic, discrete hardware circuits, and other suitable hardware configured to perform the various functionalities described throughout this disclosure. One or more processors in a processing system can execute software. Whether referred to as software, firmware, middleware, microcode, hardware description language, or other terms, software should be broadly interpreted to mean instructions, instruction sets, codes, code segments, program codes, programs, subroutines, software components, applications, software applications, software packages, routines, subroutines, objects, executables, threads of execution, processes, functions, or any combination thereof.

[0036] Thus, in one or more example aspects, implementations, and / or use cases, the functionality described 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. A storage medium can be any available medium that can be accessed by a computer. By way of example, such computer-readable media may include random access memory (RAM), read-only memory (ROM), electrically erasable programmable ROM (EEPROM), optical disk storage, magnetic disk storage, other magnetic storage devices, combinations of these types of computer-readable media, or any other 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 through the lens of a few examples, 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 may be implemented across many different platform types, devices, systems, shapes, sizes, and packaging arrangements. For example, the aspects, implementations, and / or use cases may arise via integrated chip implementations and other non-module component-based devices (e.g., end-user devices, vehicles, communications equipment, computing devices, industrial equipment, retail / purchase equipment, medical devices, artificial intelligence (AI)-enabled devices, etc.). While some examples may or may not be specifically targeted at use cases or applications, the examples described may have broad applicability. The aspects, implementations, and / or use cases may 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 techniques 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 both analog and digital purposes (e.g., hardware components including antennas, RF chains, power amplifiers, modulators, buffers, processors, interleavers, adders / summers, etc.). The techniques described herein can be practiced in a wide variety of devices of various sizes, shapes, and configurations, including chip-level components, systems, distributed arrangements, aggregated or disaggregated components, end-user devices, and the like.

[0038] The deployment of a communication system, such as a 5G NR system, can be arranged in a variety of ways using various components or parts. In a 5G NR system or network, a network node, a network entity, a mobility element of the network, a radio access network (RAN) node, a core network node, a network element, or network equipment (such as a base station (BS)), or one or more units (or one or more components) performing base station functions can be implemented in a converged or disaggregated architecture. For example, a base station (such as a node B (NB), an evolved NB (eNB), a NR base station, a 5G NB, an access point (AP), a transmit / receive point (TRP), or a cell) can be implemented as a converged base station (also known as a standalone base station or a monolithic base station) or a disaggregated base station.

[0039] A converged base station may be configured to utilize a radio protocol stack that is physically or logically integrated within a single RAN node. A disaggregated base station may be configured to utilize a protocol stack that is physically or logically distributed across two or more units, such as one or more central or centralized units (CUs), one or more distributed units (DUs), or one or more radio units (RUs). In some aspects, a CU may be implemented within a RAN node, and one or more DUs may be co-located with the CU, or alternatively, may be geographically or virtually distributed across one or more other RAN nodes. A DU may be implemented to communicate with one or more RUs. Each of the CU, DU, and RU 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 may take into account the aggregated nature of base station functionality. For example, a disaggregated base station may be utilized in an integrated access backhaul (IAB) network, an open radio access network (O-RAN (such as the network configuration initiated by the O-RAN Alliance)), or a virtualized radio access network (vRAN, also known as a cloud radio access network (C-RAN)). Disaggregation may include distributing functionality across two or more units at various physical locations, as well as virtually distributing the functionality of at least one unit, which enables flexibility in network design. The various units of a disaggregated base station or disaggregated RAN architecture may be configured for wired or wireless communication with at least one other unit.

[0041] Figure 1Figure 100 illustrates an example of a wireless communication system and access network. The illustrated wireless communication system includes a disaggregated base station architecture. The disaggregated base station architecture may include one or more CUs 110, which may communicate directly with a core network 120 via a backhaul link or indirectly with the core network 120 through one or more disaggregated base station elements, such as a near real-time (near-RT) RAN intelligent controller (RIC) 125 via an E2 link, 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 corresponding midhaul links, such as an F1 interface. DUs 130 may communicate with one or more RUs 140 via corresponding fronthaul links. RUs 140 may communicate with corresponding UEs 104 via one or more radio frequency (RF) access links. In some implementations, a UE 104 may be served simultaneously by multiple RUs 140.

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

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

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

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

[0046] The 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, the SMO framework 105 can be configured to support the deployment of dedicated physical resources for RAN coverage requirements, which can be managed via an operations and maintenance interface (such as the O1 interface). For virtualized network elements, the 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 cloud computing platform interfaces (such as the O2 interface). Such virtualized network elements may include, but are not limited to, the CU 110, DU 130, RU 140, and near-RT RIC 125. In some implementations, the SMO framework 105 can communicate with hardware aspects of the 4G RAN (such as the Open eNB (O-eNB) 111) via the O1 interface. Additionally, in some implementations, the SMO framework 105 can communicate directly with one or more RUs 140 via the O1 interface. The SMO framework 105 may also include a non-RT RIC 115 configured to support the functionality of the SMO framework 105 .

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

[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. Such information may be utilized by the near-RT RIC 125 and may be received from non-network data sources or from 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 execute corrective actions through the SMO framework 105 (such as via reconfiguration of O1) or by creating RAN management policies (such as A1 policies).

[0049] At least one of the CU 110, DU 130, and RU 140 may be referred to as a base station 102. Thus, 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 a UE 104 with access to core network 120. Base station 102 may include a macro cell (a high-power cellular base station) and / or a small cell (a low-power cellular base station). Small cells include femto cells, pico cells, and micro cells. A network that includes both small cells and macro cells may be referred to as a heterogeneous network. A heterogeneous network may also include a home evolved Node B (eNB) (HeNB), which may provide services to a restricted group known as a closed subscriber group (CSG). The communication link between RU 140 and UE 104 may include uplink (UL) (also known as reverse link) transmissions from UE 104 to RU 140 and / or downlink (DL) (also known as forward link) transmissions from RU 140 to UE 104. The communication link may utilize multiple-input, multiple-output (MIMO) antenna technology, including spatial multiplexing, beamforming, and / or transmit diversity. The communication link may be over one or more carriers. Base station 102 / UE 104 may utilize spectrum with a bandwidth of up to Y MHz (e.g., 5 MHz, 10 MHz, 15 MHz, 20 MHz, 100 MHz, 400 MHz, etc.) for each carrier allocated in a carrier aggregation for transmission in each direction, totaling up to Yx MHz (x component carriers). These carriers may 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 for DL ​​compared to UL). Component carriers may include a primary component carrier and one or more secondary component carriers. The primary component carrier may be referred to as a primary cell (PCell) and the secondary component carrier may be referred to as a secondary cell (SCell).

[0050] Some UEs 104 may communicate with each other using device-to-device (D2D) communication links 158. The D2D communication links 158 may use DL / UL wireless wide area network (WWAN) spectrum. The D2D communication links 158 may use one or more sidelink channels, such as a physical sidelink broadcast channel (PSBCH), a physical sidelink discovery channel (PSDCH), a physical sidelink shared channel (PSSCH), and a physical sidelink control channel (PSCCH). D2D communication may be performed via various wireless D2D communication systems, such as, for example, Bluetooth. ™ (Bluetooth is a trademark of the Bluetooth Special Interest Group (SIG)), Wi-Fi based on the Institute of Electrical and Electronics Engineers (IEEE) 802.11 standard ™ (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 that communicates with a UE 104 (also referred to as a Wi-Fi station (STA)) via a communication link 154, for example, in the 5 GHz unlicensed spectrum. When communicating in the unlicensed spectrum, the UE 104 / AP 150 may perform a clear channel assessment (CCA) to determine whether the channel is available before communicating.

[0052] The electromagnetic spectrum is typically subdivided into various categories, bands, channels, and so on, based on frequency / wavelength. In 5G NR, two initial operating bands have been identified as frequency ranges designated FR1 (410 MHz-7.125 GHz) and FR2 (24.25 GHz-52.6 GHz). Although a portion of FR1 extends beyond 6 GHz, FR1 is often (interchangeably) referred to as the "sub-6 GHz" band in various documents and articles. A similar naming issue sometimes arises with FR2, which is often (interchangeably) referred to as the "millimeter wave" band in documents and articles, despite being distinct from the extremely high frequency (EHF) band (30 GHz to 300 GHz), which is designated as a "millimeter wave" band by the International Telecommunication Union (ITU).

[0053] Frequencies between FR1 and FR2 are often referred to as mid-band frequencies. Recent 5G NR research has identified an operating band for these mid-band frequencies as frequency range designation FR3 (7.125 GHz to 24.25 GHz). Frequency bands falling within FR3 may inherit FR1 characteristics and / or FR2 characteristics, 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 frequency range designations FR2-2 (52.6 GHz-71 GHz), FR4 (71 GHz-114.25 GHz), and FR5 (114.25 GHz-300 GHz). Each of these higher frequency bands falls within the EHF band.

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

[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 beam training to determine the optimal receive and transmit directions for each of base station 102 / UE 104. The transmit and receive directions of base station 102 may or may not be the same. The transmit and receive directions of UE 104 may or may not be the same.

[0056] The base station 102 may include and / or be referred to as a gNB, Node B, eNB, access point, base transceiver station, 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. The base station 102 may be implemented as an integrated access and backhaul (IAB) node, a relay node, a sidelink node, a converged (monolithic) base station having a baseband unit (BBU) (including a CU and a DU) and a RU, or as a disaggregated base station including one or more of a CU, a DU, and / or a RU. A collection of base stations that may include disaggregated base stations and / or converged base stations may be referred to as a next generation (NG) RAN (NG-RAN).

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

[0058] Examples of UE 104 include a cellular phone, a smartphone, a Session Initiation Protocol (SIP) phone, a laptop, a personal digital assistant (PDA), a satellite radio, a global positioning system, a multimedia device, a video device, a digital audio player (e.g., an MP3 player), a camera, a game console, a tablet, a smart device, a wearable device, a vehicle, an electric meter, a gas pump, a large or small kitchen appliance, a healthcare device, an implant, a sensor / actuator, a display, or any other similarly functional device. Some of UE 104 may be referred to as IoT devices (e.g., a parking meter, a gas pump, a toaster, a vehicle, a heart rate monitor, etc.). UE 104 may also be referred to as a station, a mobile station, a subscriber station, a mobile unit, a subscriber unit, a wireless unit, a remote unit, a mobile device, a wireless device, a wireless communication device, a remote device, a mobile subscriber station, an access terminal, a mobile terminal, a wireless terminal, a remote terminal, a handset, a user agent, a mobile client, a client, or some other suitable terminology. In some scenarios, the term UE may also apply to one or more companion devices, such as in a device constellation arrangement. One or more of these devices may access the network collectively and / or individually.

[0059] Reference again Figure 1 In certain aspects, the UE 104 may include an SLPP positioning assistance component 198. As used herein, SLPP may refer to a sidelink positioning protocol, which is a UE-to-UE protocol sent over a PC5 sidelink for the purpose of coordinating and performing sidelink positioning and ranging measurements. SLPP may be transacted between mobile UEs and between mobile UEs and fixed UEs (e.g., roadside units (RSUs)). The SLPP positioning assistance component 198 may be configured to: obtain GNSS assistance data for a sidelink positioning session with one or more second UEs via a sidelink message; calculate a position of at least one of the first UE or the one or more second UEs based on the GNSS assistance data for the sidelink positioning session; and output an indication indicating the position of at least one of the first UE or the one or more second UEs. In certain aspects, the base station 102 may include an SLPP positioning assistance component 199. The SLPP positioning assistance component 199 may be configured to: configure GNSS assistance data for a sidelink positioning session between a first UE and one or more second UEs; and send, to the first UE, the GNSS assistance data for the sidelink positioning session between the first UE and the one or more second UEs. Although the following description may focus on 5G NR, the concepts described herein may be applicable to other similar fields, such as LTE, LTE-A, CDMA, GSM, and other wireless technologies.

[0060] Figure 2A is a diagram 200 illustrating an example of a first subframe within a 5G NR frame structure. Figure 2B is a diagram 230 illustrating an example of a DL channel within a 5G NR subframe. Figure 2C is a diagram 250 illustrating an example of a second subframe within a 5G NR frame structure. Figure 2D is a diagram 280 illustrating an example of a UL channel within a 5G NR subframe. The 5G NR frame structure can be frequency division duplex (FDD) (wherein, for a particular set of subcarriers (carrier system bandwidth), subframes within that subcarrier set are dedicated to either DL or UL), or time division duplex (TDD) (wherein, for a particular set of subcarriers (carrier system bandwidth), subframes within that subcarrier set are dedicated to both DL and UL). In the examples provided in Figures 2A and 2C, the 5G NR frame structure is assumed to be TDD, where subframe 4 is configured with slot format 28 (mostly DL), where D stands for DL, U stands for UL, and F stands for flexible use between DL / UL, and subframe 3 is configured with slot format 1 (wherein all are UL). While subframes 3 and 4 are shown as having slot formats 1 and 28, respectively, any particular subframe can be configured with any of the various available slot formats 0-61. Slot formats 0 and 1 are all DL and all UL, respectively. The other slot formats 2-61 include a mix of DL, UL, and flexible symbols. The UE is configured with the slot format via a received slot format indicator (SFI), either dynamically via DL control information (DCI) or semi-statically / statically via radio resource control (RRC) signaling. Note that the following description also applies to the 5G NR frame structure as TDD.

[0061] Figures 2A through 2D illustrate a frame structure, and aspects of the present 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 equally sized subframes (1 ms). Each subframe may include one or more slots. A subframe may also include mini-slots, which may include 7, 4, or 2 symbols. Each slot may include 14 or 12 symbols, depending on whether the cyclic prefix (CP) is normal or extended. For a normal CP, each slot may include 14 symbols, and for an extended CP, each slot may include 12 symbols. Symbols on the DL may be CP-orthogonal frequency division multiplexing (OFDM) symbols. Symbols on the UL may be CP-OFDM symbols (for high-throughput scenarios) or discrete Fourier transform (DFT)-spread OFDM (DFT-s-OFDM) symbols (for power-limited scenarios; limited to single-stream transmission). The number of slots within a subframe depends on the CP and the numerology set. The numerology defines the subcarrier spacing (SCS) (see Table 1). The symbol length / duration is scalable with 1 / SCS.

[0062]

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

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

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

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

[0067] Figure 2B illustrates examples of various downlink channels within a subframe of a frame. The physical downlink control channel (PDCCH) carries DCI within one or more control channel elements (CCEs) (e.g., 1, 2, 4, 8, or 16 CCEs). Each CCE consists of six resource element groups (REGs), with each REG comprising 12 contiguous REs within an OFDM symbol of a RB. The PDCCH within a BWP is referred to as a control resource set (CORESET). During PDCCH monitoring opportunities within a CORESET, a UE is configured to monitor PDCCH search spaces (e.g., common search space, UE-specific search space) for PDCCH candidates with different DCI formats and aggregation levels. Additional BWPs may be located at higher and / or lower frequencies across the channel bandwidth. The primary synchronization signal (PSS) may be within symbol 2 of specific subframes of a frame. The PSS is used by UE 104 to determine subframe / symbol timing and physical layer identification. The secondary synchronization signal (SSS) may be within symbol 4 of specific subframes of a frame. The SSS is used by the UE to determine the physical layer cell identity group number and radio frame timing. Based on the physical layer identity and the physical layer cell identity group number, the UE can determine the physical cell identifier (PCI). Based on the PCI, the UE can determine the location of the DM-RS. The physical broadcast channel (PBCH), which carries 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 system frame number (SFN) and the number of RBs in the system bandwidth. The physical downlink shared channel (PDSCH) carries user data, broadcast system information not sent via the PBCH (such as the system information block (SIB)), and paging messages.

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

[0069] FIG2D illustrates an example of various UL channels within a subframe of a frame. 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), precoding matrix indicators (PMI), rank indicators (RI), and hybrid automatic repeat request (HARQ) acknowledgement (ACK) (HARQ-ACK) feedback (i.e., one or more HARQ ACK bits indicating one or more ACKs and / or negative ACKs (NACKs)). The PUSCH carries data and may additionally be used to carry buffer status reports (BSRs), power headroom reports (PHRs), and / or UCI.

[0070] Figure 3 Figure 3 is a block diagram of a base station 310 communicating with a UE 350 in an access network. In the DL, Internet Protocol (IP) packets may be provided to a controller / processor 375. The controller / processor 375 implements Layer 3 and Layer 2 functionality. Layer 3 includes the Radio Resource Control (RRC) layer, and Layer 2 includes the Service Data Adaptation Protocol (SDAP) layer, the Packet Data Convergence Protocol (PDCP) layer, the Radio Link Control (RLC) layer, and the Medium Access Control (MAC) layer. The controller / processor 375 provides RRC layer functionality associated with broadcasting of system information (e.g., MIB, SIB), RRC connection control (e.g., RRC connection paging, RRC connection establishment, RRC connection modification, and RRC connection release), inter-radio access technology (RAT) mobility, and measurement configuration for UE measurement reporting; PDCP layer functionality associated with header compression / decompression, security (ciphering, deciphering, integrity protection, integrity verification), and handover support functions; RLC layer functionality associated with delivery of upper layer packet data units (PDUs), error correction through ARQ, concatenation, segmentation and reassembly of RLC service data units (SDUs), 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 through HARQ, priority handling, and logical channel prioritization.

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

[0072] At the UE 350, each receiver 354Rx receives a signal via its corresponding antenna 352. Each receiver 354Rx recovers the information modulated onto the RF carrier and provides the information to a receive (RX) processor 356. The TX processor 368 and the RX processor 356 implement Layer 1 functionality associated with various signal processing functions. The RX processor 356 performs spatial processing on the information to recover any spatial streams destined for the UE 350. If multiple spatial streams are destined for the UE 350, they may be combined into a single OFDM symbol stream by the RX processor 356. The RX processor 356 then converts the OFDM symbol stream from the time domain to the frequency domain using a fast Fourier transform (FFT). The frequency-domain signal includes a separate OFDM symbol stream for each subcarrier of the OFDM signal. The symbols on each subcarrier, along with the reference signal, are recovered and demodulated by determining the most likely signal constellation point transmitted by the base station 310. These soft decisions may be based on channel estimates calculated by the channel estimator 358. The soft decisions are then decoded and deinterleaved to recover the data and control signals originally sent on the physical channel by base station 310. The data and control signals are then provided to a 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 that stores program codes 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 between transport and logical channels, packet reassembly, decryption, header decompression, and control signal processing to recover IP packets. The controller / processor 359 is also responsible for error detection using ACK and / or NACK protocols to support HARQ operations.

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

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

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

[0077] The controller / processor 375 may be associated with at least one memory 376 that stores program codes 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 between transport and logical channels, packet reassembly, decryption, header decompression, and control signal processing to recover IP packets. The controller / processor 375 is also responsible for error detection using ACK and / or NACK protocols to support HARQ operations.

[0078] At least one of the TX processor 368, the RX processor 356, and the controller / processor 359 may be configured to perform operations related to Figure 1 The SLPP positioning assist assembly 198 combines various aspects.

[0079] At least one of the TX processor 316, the RX processor 370, and the controller / processor 375 may be configured to perform operations related to Figure 1 The SLPP positioning auxiliary component 199 combines various aspects.

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

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

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

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

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

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

[0086] Cellular connections, such as UE-UTRAN (Uu) connections, can support the delivery of GNSS assistance data to UEs, enabling improved UE positioning accuracy. Over the Uu connection, GNSS assistance data can be delivered via public signaling or dedicated signaling. A new SLPP can be defined to enable positioning and inter-UE ranging over a sidelink (e.g., PC5) for UEs that are out of coverage (OOC) of the network or in coverage with sidelink-enabled infrastructure components (such as RSUs). SLPP can support sidelink positioning assistance data transfer between UEs. As used herein, "GNSS assistance data" refers to information that can facilitate a device in determining its position using GNSS. This information may include, for example, information related to the positions of satellites, the position of the device, and the current time.

[0087] UEs operating over a sidelink connection can benefit from GNSS assistance data to achieve positioning accuracy in the same manner as UEs operating over a cellular connection. However, there is currently no defined signaling mechanism for GNSS assistance data on the sidelink. Providing such a signaling mechanism on the sidelink, with the flexibility to support unicast, multicast, and broadcast connections via sidelink data radio bearers (DRBs) or sidelink signaling radio bearers (SRBs), would enhance the positioning accuracy achievable by UEs supporting sidelink.

[0088] The present disclosure provides methods and apparatus for providing GNSS assistance data via sidelink-based communications for UEs. These mechanisms define a signaling path to support GNSS assistance data over a sidelink connection, thereby enhancing the positioning capability of the UE. In one aspect, the signaling mechanism may include support for GNSS assistance data over sidelink unicast, sidelink multicast, or sidelink broadcast, as well as support for GNSS assistance data transmitted over a sidelink DRB or sidelink SRB. Participating UEs may be mobile or stationary (such as RSUs). In one aspect, the signaling mechanism may also include a mechanism for reducing signaling overhead when sharing GNSS assistance data over a sidelink.

[0089] The transmission of GNSS assistance data over the Uu connection can be accomplished through public signaling (e.g., via System Information (SI)) or dedicated signaling (e.g., via the RRC reconfiguration message RRCReconfiguration). For example, with public signaling, the GNSS assistance data in the SIBpos information element (IE) can be transmitted in the system information (e.g., via PosSystemInformation-r16 or PosSI-SchedulingInfo). With dedicated signaling, the GNSS assistance data can be transmitted via an uplink message (e.g., the DedicatedSIBRequest message) or a downlink message (e.g., the RRCReconfiguration message). In one example, the GNSS assistance data in the SIBpos IE can be transmitted in the RRCReconfiguration message (e.g., via dedicatedPosSysInfoDelivery-r16). In another example, the GNSS assistance data via the LTE Positioning Protocol (LPP) IE can be transmitted via the control plane (e.g., the Evolved Serving Mobile Location Center (E-SMLC)) or the usage plane (e.g., SUPL). Figure 5 is a diagram illustrating an example 500 of common signaling and dedicated signaling of GNSS assistance data implemented over a Uu connection. Figure 5 In the example, for public signaling, GNSS assistance data can be sent via the assistanceDataSIB-Element in the SIBposIE; for dedicated signaling, GNSS assistance data can be sent via a downlink message (such as an RRCReconfiguration message) or an LLP IE (such as GNSS-CommonAssistData or GNSS-GenericAssistData) via the CP or UP.

[0090] In some aspects, the GNSS assistance data may include a GNSS data type and GNSS data elements associated with the GNSS data type. The GNSS data type may include one or more of the following: GNSS common assistance data, observed time difference of arrival (OTDOA) assistance data, barometric assistance data, time difference of arrival based system (TBS) assistance data, or new radio (NR) downlink time difference of arrival / downlink angle of arrival (DL-TDOA / DL-AoD) assistance data. Figure 6 is a diagram 600 illustrating example GNSS data types and example GNSS data elements associated with the GNSS data types. Figure 6 In FIG, , GNSS assistance data types may include, for example, GNSS common assistance data 602, OTDOA assistance data 604, barometric assistance data 606, TBS assistance data 608, NR DL-TDOA / DL-AoD assistance data 610, and GNSS general assistance data 612. Each of these GNSS data types may have one or more associated GNSS data elements. For example, Figure 6 As shown, the GNSS common assistance data 602 may include GNSS data elements GNSS-ReferenceTime 622 , GNSS-ReferenceLocation 624 , GNSS-IonosphericModel 626 , and GNSS-EarthOrientationParameters 628 , among others, and the GNSS universal assistance data 612 may include GNSS data elements GNSS-DifferentialCorrections 632 and GNSS-Almanac 634 , among others.

[0091] In some aspects, GNSS assistance data may be communicated via a sidelink connection. For example, GNSS assistance data (e.g., PosSystemInformation) may be communicated via an SLPP positioning assistance data exchange (e.g., via a sidelink unicast message, a sidelink multicast message, or a sidelink broadcast message), and the GNSS assistance data (e.g., PosSystemInformation) may be communicated via a sidelink DRB or SRB, for example.

[0092] In some aspects, GNSS assistance data may be communicated via a unicast SLPP positioning assistance data exchange. For example, a sidelink device may obtain SLPP GNSS assistance data in at least one of the following: a vehicle-to-everything (V2X) layer payload on a sidelink DRB, a packet data convergence protocol (PDCP) service data unit (SDU) on a sidelink signaling radio bearer (SRB), a new PC5 radio resource control (RRC) (PC5-RRC) information element (IE) on a sidelink SRB, or a PC5 sidelink (PC5-S) IE on a sidelink SRB. In some examples, the sidelink device may be a first vehicle and may obtain SLPP GNSS assistance data via a sidelink unicast message from another sidelink device (which may be a second vehicle). The first vehicle may obtain GNSS assistance data from the second vehicle in a sidelink unicast message sent from the second vehicle in: a payload in the V2X layer on a sidelink DRB, a PDCP SDU on a sidelink SRB, a new PC5-RRC IE on a sidelink SRB, or a PC5-S IE on a sidelink SRB. In some examples, the sidelink device may be a stationary device, such as an RSU.

[0093] In some aspects, GNSS assistance data may be communicated via a multicast SLPP positioning assistance data exchange. For example, a sidelink device may obtain SLPP GNSS assistance data in at least one of the following: a V2X layer payload on a sidelink DRB, or a PDCP SDU on a sidelink SRB. For example, in an exemplary scenario where the sidelink devices are sidelink-connected vehicles (e.g., a first vehicle and a second vehicle), the first vehicle may obtain SLPP GNSS assistance data via a sidelink multicast message from the second vehicle. The first vehicle may obtain GNSS assistance data from the second vehicle in a sidelink multicast message as a payload in the V2X layer on the sidelink DRB, or a PDCP SDU on the sidelink SRB. In some examples, the sidelink device may be a stationary device of the sidelink connection, such as a sidelink-connected RSU. In some examples, one sidelink device may be a vehicle, and the other sidelink device may be a stationary device connected to the vehicle via a sidelink connection, such as a sidelink-connected RSU.

[0094] In some aspects, GNSS assistance data may be communicated via a broadcast SLPP positioning assistance data exchange. For example, a sidelink device may obtain SLPP GNSS assistance data in at least one of the following: a V2X layer payload on a sidelink DRB, or a PDCP SDU on a sidelink SRB. For example, in an exemplary scenario where the sidelink devices are sidelink-connected vehicles (e.g., a first vehicle and a second vehicle), the first vehicle may obtain SLPP GNSS assistance data via a sidelink broadcast message from the second vehicle. The first vehicle may obtain GNSS assistance data from the second vehicle in the sidelink broadcast message as a payload in the V2X layer on a sidelink DRB, or a PDCP SDU on a sidelink SRB.

[0095] In some examples, the GNSS assistance data received by the sidelink device from the sidelink message may include GNSS assistance data that the sidelink device may receive via a Uu connection with a network entity. Figure 6 GNSS assistance data that a sidelink device may receive from a sidelink message may include one or more of the following: GNSS common assistance data 602, OTDOA assistance data 604, barometric assistance data 606, TBS assistance data 608, NR DL-TDOA / DL-AoD assistance data 610, and GNSS general assistance data 612. In some examples, the GNSS assistance data may include the relative positioning between the transmitting sidelink device and the receiving sidelink device. The relative positioning may include, for example, the relative distance and relative orientation of one sidelink device relative to the other sidelink device.

[0096] In some examples, the transmission of sidelink messages including GNSS assistance data between sidelink devices may be based on one or more pre-configured conditions that can be pre-configured for the sidelink devices. These pre-configured conditions can be set, for example, to reduce signaling overhead between the transmitting sidelink device and the receiving sidelink device when communicating GNSS assistance data. In one example, a sidelink message may be transmitted if the transmitting sidelink device is within a specific range of the receiving sidelink device. In another example, a sidelink message including GNSS assistance data may be transmitted between a transmitting sidelink device and a receiving sidelink device that have an established sidelink session to reduce signaling overhead.

[0097] In some aspects, the sidelink GNSS assistance data may mirror the Uu GNSS assistance data (e.g., PosSystemInformation). In some examples, for GNSS assistance data communicated via a unicast SLPP positioning assistance data exchange, the PC5-RRC IE may be a new IE defined in the sidelink unicast message (e.g., sl-dedicatedPosSysInfoDelivery-r16 carried in the RRCReconfigurationSidelink message), and the PC5-S IE may be a new PC5-S IE defined for GNSS assistance data based on PosSystemInformation. In some examples, for SLPP carried as a V2X payload via a unicast, multicast, or broadcast SLPP positioning assistance data exchange, the SLPP positioning assistance data exchange message may include GNSS assistance data based on PosSystemInformation. In some examples, the GNSS assistance data communicated via the sidelink may include all or a portion of the GNSS assistance data communicated via the Uu connection. For example, referring to Figure 6 The GNSS assistance data conveyed via a sidelink unicast message, a sidelink multicast message, or a sidelink broadcast message may include one or more of the following: GNSS common assistance data 602, OTDOA assistance data 604, barometric assistance data 606, TBS assistance data 608, NR DL-TDOA / DL-AoD assistance data 610, or GNSS general assistance data 612.

[0098] Figure 7 FIG700 is a diagram illustrating an example of GNSS assistance data in SLPP positioning assistance data exchange in the case of SLPP over PC5-U SL DRB according to various aspects of the present disclosure. Figure 7 In the embodiment, GNSS assistance data 702 can be exchanged between sidelink devices via the sidelink DRB, and the sidelink message carrying the GNSS assistance data 702 can be a unicast message, a multicast message, or a broadcast message. The unicast message, the multicast message, or the broadcast message can be, for example, a payload in the V2X layer 704 on the sidelink DRB, or an SDU on the PDCP 706 on the sidelink DRB. Figure 6 , the GNSS assistance data 702 may include one or more of the following: GNSS common assistance data 602 , OTDOA assistance data 604 , barometric assistance data 606 , TBS assistance data 608 , NR DL-TDOA / DL-AoD assistance data 610 , or GNSS general assistance data 612 .

[0099] Figure 8FIG800 is a diagram illustrating an example of GNSS assistance data in SLPP positioning assistance data exchange in case of SLPP over PDCP over SL SRB according to various aspects of the present disclosure. Figure 8 In the embodiment, GNSS assistance data 802 can be exchanged between sidelink devices via the sidelink SRB, and the sidelink message carrying the GNSS assistance data 802 can be a unicast message, a multicast message, or a broadcast message. The unicast message, the multicast message, or the broadcast message can be in an SDU on the PDCP 804 on the sidelink SRB, for example. Figure 6 In one example, the GNSS assistance data 802 may include one or more of the following: GNSS common assistance data 602 , OTDOA assistance data 604 , barometric assistance data 606 , TBS assistance data 608 , NR DL-TDOA / DL-AoD assistance data 610 , or GNSS general assistance data 612 .

[0100] Figure 9 FIG900 is a diagram illustrating an example of GNSS assistance data in SLPP positioning assistance data exchange in the case of SLPP over PC5-RRC over SL SRB according to various aspects of the present disclosure. Figure 9 In the embodiment, GNSS assistance data 902 may be exchanged between sidelink devices via the sidelink SRB, and the message carrying the GNSS assistance data 902 may be a unicast message. The unicast message may be in, for example, a PC5-RRC 904 IE on the sidelink SRB or an SDU on the PDCP 906 on the sidelink SRB. Figure 6 In one example, the GNSS assistance data 902 may include one or more of the following: GNSS common assistance data 602 , OTDOA assistance data 604 , barometric assistance data 606 , TBS assistance data 608 , NR DL-TDOA / DL-AoD assistance data 610 , or GNSS general assistance data 612 .

[0101] Figure 10 FIG1000 is a diagram illustrating an example of GNSS assistance data in SLPP positioning assistance data exchange in the case of SLPP on PC5-S on SL SRB according to various aspects of the present disclosure. Figure 10 In the embodiment, GNSS assistance data 1002 may be exchanged between sidelink devices via the sidelink SRB, and the message carrying the GNSS assistance data 1002 may be a unicast message. The unicast message may be in, for example, a PC5-S 1004 IE on the sidelink SRB or an SDU on the PDCP 1006 on the sidelink SRB. Figure 6In one example, the GNSS assistance data 1002 may include one or more of the following: GNSS common assistance data 602 , OTDOA assistance data 604 , barometric assistance data 606 , TBS assistance data 608 , NR DL-TDOA / DL-AoD assistance data 610 , or GNSS general assistance data 612 .

[0102] In some examples, the sidelink device may be a vehicle connected to the sidelink. For example, a transmitting sidelink device (e.g., a transmitting vehicle) may send a sidelink message including GNSS assistance data to one or more receiving sidelink devices (e.g., a receiving vehicle) to facilitate these receiving sidelink devices to determine their positioning using GNSS. The GNSS assistance data may be transmitted via Figure 7 、 Figure 8 、 Figure 9 and Figure 10 One of the mechanisms described in is included in a sidelink message. In some examples, the GNSS assistance data may be included in a payload of the V2X layer 704 on a sidelink DRB or a PDCP 706 SDU in a unicast sidelink message, a multicast sidelink message, or a broadcast sidelink message from a transmitting sidelink device (e.g., a transmitting vehicle) to a receiving sidelink device (e.g., a receiving vehicle). In some examples, the GNSS assistance data may be included in a PDCP 804 SDU on a sidelink SRB in a unicast sidelink message, a multicast sidelink message, or a broadcast sidelink message from a transmitting sidelink device (e.g., a transmitting vehicle) to a receiving sidelink device (e.g., a receiving vehicle). In some examples, the GNSS assistance data may be included in a PC5-RRC 904 IE or a PDCP 906 SDU on a sidelink SRB in a unicast sidelink message from a transmitting sidelink device (e.g., a transmitting vehicle) to a receiving sidelink device (e.g., a receiving vehicle). In some examples, the GNSS assistance data may be included in a PC5-S 1004 IE or a PDCP 1006 SDU on a sidelink SRB in a unicast sidelink message from a transmitting sidelink device (e.g., a transmitting vehicle) to a receiving sidelink device (e.g., a receiving vehicle). In some examples, the sidelink device may be a stationary device of a sidelink connection, such as an RSU of a sidelink connection. In some examples, one of the transmitting sidelink device and the receiving sidelink device may be a vehicle, and the other of the transmitting sidelink device and the receiving sidelink device may be a stationary device, such as an RSU of a sidelink connection.

[0103] In some examples, a side link message may be sent from a sending side link device (eg, a sending vehicle) when a certain preset condition is met (eg, when the sending side link device and the receiving side link device are within a certain range).

[0104] In some aspects, sidelink implementation can be implemented via SLPP. SLPP can be defined for the configuration and execution of sidelink positioning and ranging measurements. SLPP can be carried on the PC5 user plane (PC5-U) as V2X or Proximity Services (ProSe).

[0105] Example aspects of the present disclosure utilize SLPP as the signaling mechanism for sidelink positioning, thereby leveraging the protocol to carry GNSS assistance information. This allows existing IEs (e.g., IEs for GNSS assistance information over Uu connections) to be carried as payload within SLPP. For example, the IEPosSystemInformation-r16-IE transmitted over a Uu connection can be used as the IE sl-PosSystemInformation-r16-IE over SLPP. Similarly, the IEPosSIB-Type-r16 sent over a Uu connection can be used as the IE sl-PosSIB-Type-r16 over SLPP, and the DedicatedSIBRequest sent over a Uu connection can be used as the sl-DedicatedSIBRequest over SLPP.

[0106] In some aspects, sidelink implementation may be achieved by utilizing unicast PC5-RRC or PC5-U protocols. To utilize the unicast PC5-RRC protocol, a new PC5-RRC message, such as sl-PosSystemInformation-r16, may be introduced for GNSS assistance delivery. The content of this message may include Uu-based GNSS assistance within PosSystemInformation-IEs-r16. The new PC5-RRC IE sl-PosSystemInformation-IEs-r16 may be included within the PC5-RRCRCReconfigurationSidelink message. For GNSS assistance requests, a new PC5-RRC message for GNSS assistance requests, such as sl-DedicatedSIBRequest-r16, may be introduced. The content of this new message may include the Uu-based GNSS assistance request present in, for example, DedicatedSIBRequest-r16.

[0107] To utilize unicast PC5 signaling (eg, PC5-S), new PC5-S messages for GNSS assistance delivery (eg, sl-PosSystemInformation-r16) and new PC5-S messages for GNSS assistance request (eg, sl-DedicatedSIBRequest-r16) may be introduced.

[0108] Figure 11 is a call flow diagram 1100 illustrating a method of wireless communication according to various aspects of the present disclosure. Various aspects are described in conjunction with a first UE 1102, a network node 1104, and a second UE 1106. These aspects may be performed by the first UE 1102, the network node 1104, or the second UE 1106.

[0109] exist Figure 11 In the example, at 1108, the first UE 1102 may receive a request message requesting an indication of the calculated position. In some examples, the first UE 1102 may receive the request message from the second UE 1106.

[0110] At 1110 , the network node 1104 may configure GNSS assistance data for a sidelink positioning session between the first UE 1102 and the second UE 1106 .

[0111] At 1112 , the first UE 1102 may establish a sidelink positioning session with the second UE 1106 .

[0112] The first UE 1102 may obtain GNSS assistance data via a sidelink message for a sidelink positioning session with the second UE 1106. In some examples, at 1114, the first UE 1102 may obtain the GNSS assistance data from the network node 1104. In some examples, at 1116, the first UE 1102 may obtain the GNSS assistance data from a storage medium, which may be a memory (e.g., memory 1130) or a cache.

[0113] At 1118, the first UE 1102 may calculate a position of at least one of the first UE 1102 or the second UE 1106 based on the GNSS assistance data for the sidelink positioning session.

[0114] The first UE 1102 may output an indication of the calculated position of at least one of the first UE 1102 or the second UE 1106. In some examples, at 1120, the first UE 1102 may output the indication to the second UE 1106. In some examples, at 1122, the first UE 1102 may output the indication to the network node 1104. For example, referring to Figure 7 , the first UE may output an indication of the calculated positioning (eg, GNSS assistance data 702) to the second UE via a sidelink DRB. Figure 8, the first UE may output an indication of the calculated position (e.g., GNSS assistance data 802) to the second UE via a sidelink SRB. In some examples, at 1124, the first UE 1102 may store the indication of the calculated position in at least one memory or cache.

[0115] Figure 12 1200 is a flowchart illustrating a method for wireless communication at a first UE according to various aspects of the present disclosure. The method may be performed by the first UE. The first UE may be UE 104, 350, 1102, or Figure 16 The method provides a signaling mechanism that supports the communication of positioning data via the sidelink connection of the UE. This enhances the positioning accuracy of the UE operating on the sidelink connection and improves the efficiency of wireless communication.

[0116] like Figure 12 As shown, at 1202, a first UE may obtain GNSS assistance data for a sidelink positioning session with one or more second UEs via a sidelink message. Figure 7 、 Figure 8 、 Figure 9 、 Figure 10 and Figure 11 Various aspects of the steps associated with flowchart 1200 are illustrated. For example, referring to Figure 11 At 1114, the first UE 1102 can obtain GNSS assistance data for a sidelink positioning session via a sidelink message, and the sidelink positioning session can be conducted with one or more second UEs (e.g., the second UE 1106). In some aspects, 1202 can be performed by the SLPP positioning assistance component 198.

[0117] At 1204, the first UE may calculate a position of at least one of the first UE or the one or more second UEs based on the GNSS assistance data for the sidelink positioning session. Figure 11 At 1118, first UE 1102 may calculate a position of at least one of first UE 1102 or one or more second UEs (eg, second UE 1106) based on the GNSS assistance data for the sidelink positioning session. In some aspects, 1204 may be performed by SLPP positioning assistance component 198.

[0118] At 1206, the first UE may output an indication of the calculated position of the first UE or at least one of the one or more second UEs. In some aspects, the first UE may output the indication to the network node. In some aspects, the network node may Figure 1A base station or a component of a base station in an access network, or a core network component (e.g., base station 102, 310; or Figure 16 In some aspects, the network node may be a roadside unit (RSU), a third UE, a side link device, or a wireless device. For example, referring to Figure 11 In some examples, at 1122, the first UE 1102 may output the indication to the network node 1104. In some examples, at 1120, the first UE 1102 may output the indication to the second UE (eg, the second UE 1106). In some aspects, 1206 may be performed by the SLPP positioning assistance component 198.

[0119] Figure 13 1300 is a flowchart illustrating a method for wireless communication at a first UE according to various aspects of the present disclosure. The method may be performed by the first UE. The first UE may be UE 104, 350, 1102, or Figure 16 The method provides a signaling mechanism that supports the communication of positioning data via the sidelink connection of the UE. This enhances the positioning accuracy of the UE operating on the sidelink connection and improves the efficiency of wireless communication.

[0120] like Figure 13 As shown, at 1308, the first UE may obtain GNSS assistance data for a sidelink positioning session with one or more second UEs via a sidelink message. Figure 7 、 Figure 8 、 Figure 9 、 Figure 10 and Figure 11 Various aspects of the steps associated with flowchart 1300 are illustrated. For example, referring to Figure 11 At 1114, the first UE 1102 can obtain GNSS assistance data for a sidelink positioning session via a sidelink message, and the sidelink positioning session can be conducted with one or more second UEs (e.g., the second UE 1106). In some aspects, 1308 can be performed by the SLPP positioning assistance component 198.

[0121] At 1310, the first UE may calculate a position of at least one of the first UE or the one or more second UEs based on the GNSS assistance data for the sidelink positioning session. Figure 11 At 1118, first UE 1102 may calculate a position of at least one of first UE 1102 or one or more second UEs (eg, second UE 1106) based on the GNSS assistance data for the sidelink positioning session. In some aspects, 1310 may be performed by SLPP positioning assistance component 198.

[0122] At 1312, the first UE may output an indication of the calculated position of the first UE or at least one of the one or more second UEs. In some aspects, the first UE may output the indication to the network node. In some aspects, the network node may Figure 1 A base station or a component of a base station in an access network, or a core network component (e.g., base station 102, 310; or Figure 16 In some aspects, the network node may be a roadside unit (RSU), a third UE, a side link device, or a wireless device. For example, referring to Figure 11 In some examples, at 1122, the first UE 1102 may output the indication to the network node 1104; in some examples, at 1120, the first UE 1102 may output the indication to the second UE (e.g., the second UE 1106). In some aspects, 1312 may be performed by the SLPP positioning assistance component 198.

[0123] In some aspects, at 1306, the first UE may establish a sidelink positioning session with the one or more second UEs. To obtain GNSS assistance data at 1308, the first UE may obtain GNSS assistance data for the established sidelink positioning session. For example, referring to Figure 11 At 1112 , the first UE 1102 can establish a sidelink positioning session with the one or more second UEs (eg, the second UE 1106 ). In some aspects, 1306 can be performed by the SLPP positioning assistance component 198 .

[0124] In some aspects, to obtain GNSS assistance data at 1308, the first UE may obtain GNSS assistance data for the established sidelink positioning session via one of public signaling or dedicated signaling for the sidelink positioning session. Figure 11 In order to obtain the GNSS assistance data, the first UE 1102 may obtain the GNSS assistance data for the established sidelink positioning session via one of public signaling or dedicated signaling for the sidelink positioning session.

[0125] In some aspects, the GNSS assistance data may include a GNSS data type and GNSS data elements associated with the GNSS data type. Figure 11 , the GNSS assistance data (obtained by the first UE 1102 at 1114 ) may include a GNSS data type and GNSS data elements associated with the GNSS data type.

[0126] In some aspects, the GNSS data type may include one or more of the following: GNSS common assistance data, observed time difference of arrival (OTDOA) assistance data, barometric assistance data, time difference of arrival based system (TBS) assistance data, or new radio (NR) downlink time difference of arrival / downlink angle of arrival (DL-TDOA / DL-AoD) assistance data. For example, referring to Figure 11 , the GNSS assistance data (at 1114) may include GNSS data types, and these GNSS data types may include one or more of the following: GNSS common assistance data, OTDOA assistance data, barometric assistance data, TBS assistance data, or NR DL-TDOA / DL-AoD assistance data. For example, referring to Figure 6 , the GNSS assistance data (at 1114 ) may include GNSS data types, and these GNSS data types may include one or more of the following: GNSS common assistance data 602 , OTDOA assistance data 604 , barometric assistance data 606 , TBS assistance data 608 , or NR DL-TDOA / DL-AoD assistance data 610 .

[0127] In some aspects, at 1302, the first UE may receive a request message via PC5-S requesting an indication of the calculated position. To output the indication of the calculated position at 1312, the first UE may output the indication of the calculated position in response to the request message. For example, referring to Figure 11 At 1108, the first UE 1102 may receive a request message requesting an indication of the calculated position via the PC5-S. To output the indication of the calculated position, the first UE 1102 may output the indication of the calculated position in response to the request message at 1120. In some aspects, 1302 may be performed by the SLPP positioning assistance component 198.

[0128] In some aspects, at 1304, the first UE may establish sidelink communications with the one or more second UEs. To obtain GNSS assistance data at 1308, the first UE may obtain GNSS assistance data for the established sidelink communications. For example, referring to Figure 11 , the first UE 1102 may establish sidelink communications with the one or more second UEs (e.g., the second UE 1106), and the first UE may obtain GNSS assistance data for the sidelink communications established with the one or more second UEs (e.g., the second UE 1106). In some aspects, 1304 may be performed by the SLPP positioning assistance component 198.

[0129] In some aspects, to obtain GNSS assistance data at 1308, the first UE may receive GNSS assistance data for a sidelink positioning session from the network node. In some aspects, the network node may be Figure 1 A base station or a component of a base station in an access network, or a core network component (e.g., base station 102, 310; or Figure 16 In some aspects, the network node may be a roadside unit (RSU), a third UE, a side link device, or a wireless device. For example, referring to Figure 11 At 1114 , the first UE 1102 may receive GNSS assistance data from the network node 1104 for the sidelink positioning session.

[0130] In some aspects, to obtain GNSS assistance data at 1308, the first UE may retrieve GNSS assistance data for the sidelink positioning session from at least one memory or cache. The at least one memory or cache may be associated with a positioning application. For example, referring to Figure 11 At 1116, the first UE 1102 may retrieve GNSS assistance data for the sidelink positioning session from the memory 1130. The memory 1130 may be associated with a positioning application.

[0131] In some aspects, to obtain GNSS assistance data via the sidelink message at 1308, the first UE may obtain GNSS assistance data via one of a sidelink unicast message, a sidelink multicast message, or a sidelink broadcast message. Figure 7 , the first UE may obtain GNSS assistance data (eg, GNSS common assistance data 602 ) via one of a sidelink unicast message, a sidelink multicast message, or a sidelink broadcast message.

[0132] In some aspects, the GNSS assistance data obtained via the sidelink unicast message, the sidelink multicast message, or the sidelink broadcast message may mirror the second assistance data in the access link with the network node. The second assistance data may be, for example, the GNSS assistance data in the access link. For example, referring to Figure 11 , the first UE 1102 may obtain GNSS assistance data via a side link (eg, via a side link unicast message, a side link multicast message, or a side link broadcast message), and the GNSS assistance data may be mirrored with the second assistance data in the access link.

[0133] In some aspects, to obtain GNSS assistance data at 1308, the first UE may obtain GNSS assistance data via a sidelink unicast message. The sidelink unicast message may be in at least one of: a V2X layer payload on a sidelink DRB, a PDCP SDU on a sidelink SRB, a PC5-RRC IE on a sidelink SRB, or a PC5-S IE on a sidelink SRB. For example, referring to Figure 7 、 Figure 8 、 Figure 9 and Figure 10 The first UE may obtain GNSS assistance data via a sidelink unicast message. The sidelink unicast message may be in the following: a payload of the V2X layer 704 on the sidelink DRB, an SDU on the PDCP 804 on the sidelink SRB, a PC5-RRC 904 IE on the sidelink SRB, or a PC5-S 1004 IE on the sidelink SRB.

[0134] In some aspects, the PC5-RRC IE may be a first new IE defined in a sidelink unicast message, and the PC5-S IE may be a second new IE defined in a sidelink unicast message for GNSS assistance data based on second assistance data in an access link with a network node. The V2X layer payload may include GNSS assistance data based on second assistance data in an access link with a network node. For example, referring to Figure 7 、 Figure 9 and Figure 10 The PC5-RRC 904 IE may be the first new IE defined in a sidelink unicast message, and the PC5-S 1004 IE may be the second new IE defined in a sidelink unicast message for GNSS assistance data based on second assistance data in an access link with a network node. The payload on the V2X layer 704 may include GNSS assistance data based on the second assistance data in the access link.

[0135] In some aspects, to obtain GNSS assistance data at 1308, the first UE may obtain GNSS assistance data via a sidelink multicast message. The sidelink multicast message may be in at least one of the following: a V2X layer payload on a sidelink DRB, or a PDCP SDU on a sidelink SRB. For example, referring to Figure 7 and Figure 8 , the sidelink multicast message can be in the payload of the V2X layer 704 on the sidelink DRB or the SDU of the PDCP 804 on the sidelink SRB.

[0136] In some aspects, the V2X layer payload may include GNSS assistance data based on secondary assistance data in an access link with a network node. For example, referring to Figure 7, the payload of the V2X layer 704 may include GNSS assistance data based on the second assistance data in the access link.

[0137] In some aspects, to obtain GNSS assistance data at 1308, the first UE may obtain GNSS assistance data via a sidelink broadcast message. The sidelink broadcast message may be in at least one of the following: a V2X layer payload on a sidelink DRB, or a PDCP SDU on a sidelink SRB. For example, referring to Figure 7 and Figure 8 , the sidelink broadcast message may be in the payload of the V2X layer 704 on the sidelink DRB or in the SDU of the PDCP 804 on the sidelink SRB.

[0138] In some aspects, the V2X layer payload may include GNSS assistance data based on secondary assistance data in an access link with a network node. For example, referring to Figure 7 , the payload of the V2X layer 704 may include GNSS assistance data based on the second assistance data in the access link.

[0139] In some aspects, a sidelink positioning session may be associated with an SLPP. For example, Figure 11 , the sidelink positioning session (established by the first UE 1102 at 1112) may be associated with the SLPP.

[0140] In some aspects, to output the indication of the location of the first UE or at least one of the one or more second UEs at 1312, the first UE may send the indication of the location of the first UE or at least one of the one or more second UEs to the one or more second UEs, or store the indication of the location of the first UE or at least one of the one or more second UEs in the at least one memory or cache. For example, referring to Figure 11 At 1120, the first UE 1102 may send an indication of the positioning to the second UE 1106, or at 1124, the first UE may store the indication of the positioning in the at least one memory or cache.

[0141] Figure 14 1400 is a flowchart illustrating a method for wireless communication at a network node according to various aspects of the present disclosure. The method may be performed by the network node. In some aspects, the network node may be Figure 1 A base station or a component of a base station in an access network, or a core network component (e.g., base station 102, 310; or Figure 16In some aspects, the network node may be another device, such as an RSU, a third UE, a sidelink device, or a wireless device. The method provides a signaling mechanism that supports communicating positioning data via a UE's sidelink connection. This enhances positioning accuracy for UEs operating on the sidelink connection and improves the efficiency of wireless communications.

[0142] like Figure 14 As shown, at 1402, the network node may configure GNSS assistance data for a sidelink positioning session between a first UE and one or more second UEs. The first UE may be UE 104, 350, 1102, or Figure 16 The second UE may be, for example, UE 1106. Figure 7 、 Figure 8 、 Figure 9 、 Figure 10 and Figure 11 Various aspects of the steps associated with flowchart 1400 are illustrated. For example, referring to Figure 11 At 1110 , the network node 1104 can configure GNSS assistance data for a sidelink positioning session between the first UE 1102 and the second UE 1106 . In some aspects, 1402 can be performed by the SLPP positioning assistance component 199 .

[0143] At 1404, the network node may send the GNSS assistance data for the sidelink positioning session between the first UE and the one or more second UEs to the first UE. Figure 11 At 1114 , the network node 1104 may send GNSS assistance data for the first UE 1102 for a sidelink positioning session between the first UE 1102 and the second UE 1106 . In some aspects, 1404 may be performed by the SLPP positioning assistance component 199 .

[0144] Figure 15 1500 is a flowchart illustrating a method for wireless communication at a network node according to various aspects of the present disclosure. The method may be performed by the network node. In some aspects, the network node may be Figure 1 A base station or a component of a base station in an access network, or a core network component (e.g., base station 102, 310; or Figure 16 In some aspects, the network node may be another device, such as an RSU, a third UE, a sidelink device, or a wireless device. The method provides a signaling mechanism that supports communicating positioning data via a UE's sidelink connection. This enhances positioning accuracy for UEs operating on the sidelink connection and improves the efficiency of wireless communications.

[0145] like Figure 15 As shown, at 1502, the network node may configure GNSS assistance data for a sidelink positioning session between a first UE and one or more second UEs. The first UE may be UE 104, 350, 1102, or Figure 16 The second UE may be, for example, UE 1106. Figure 7 、 Figure 8 、 Figure 9 、 Figure 10 and Figure 11 Various aspects of the steps associated with flowchart 1500 are illustrated. For example, referring to Figure 11 At 1110 , the network node 1104 can configure GNSS assistance data for a sidelink positioning session between the first UE 1102 and the second UE 1106 . In some aspects, 1502 can be performed by the SLPP positioning assistance component 199 .

[0146] At 1504, the network node may send the GNSS assistance data for the sidelink positioning session between the first UE and the one or more second UEs to the first UE. Figure 11 At 1114 , the network node 1104 may send GNSS assistance data for the first UE 1102 for a sidelink positioning session between the first UE 1102 and the second UE 1106 . In some aspects, 1504 may be performed by the SLPP positioning assistance component 199 .

[0147] In some aspects, the network node may be at least one of the following: an RSU, a base station, a third UE, a sidelink device, or a wireless device. Figure 11 , the network node 1104 may be at least one of the following: an RSU, a base station, a third UE, a sidelink device, or a wireless device.

[0148] In some aspects, to send the GNSS assistance data at 1504, the network node may send the GNSS assistance data via one of a sidelink unicast message, a sidelink multicast message, or a sidelink broadcast message at 1508. The GNSS assistance data may mirror the second assistance data in the access link with the network node. For example, referring to Figure 11 To send the GNSS assistance data at 1114 , the network node 1104 may send the GNSS assistance data via one of a sidelink unicast message, a sidelink multicast message, or a sidelink broadcast message.

[0149] In some aspects, to send the GNSS assistance data at 1504, the network node may send the GNSS assistance data via a sidelink unicast message at 1510. The sidelink unicast message may be in at least one of: a V2X layer payload on a sidelink DRB, a PDCP SDU on a sidelink SRB, a PC5-RRC IE on a sidelink SRB, or a PC5-S IE on a sidelink SRB. For example, referring to Figure 7 、 Figure 8 、 Figure 9 and Figure 10 , the sidelink unicast message may be in: a payload of the V2X layer 704 on the sidelink DRB, an SDU on the PDCP 804 on the sidelink SRB, a PC5-RRC 904 IE on the sidelink SRB, or a PC5-S 1004 IE on the sidelink SRB.

[0150] In some aspects, the PC5-RRC IE may be a first new IE defined in a sidelink unicast message, and the PC5-S IE may be a second new IE defined in a sidelink unicast message for GNSS assistance data based on second assistance data in an access link with a network node. The V2X layer payload may include GNSS assistance data based on second assistance data in an access link with a network node. For example, referring to Figure 7 、 Figure 9 and Figure 10 The PC5-RRC 904 IE may be the first new IE defined in a sidelink unicast message, and the PC5-S 1004 IE may be the second new IE defined in a sidelink unicast message for GNSS assistance data based on second assistance data in an access link with a network node. The payload on the V2X layer 704 may include GNSS assistance data based on the second assistance data in an access link with a network node.

[0151] In some aspects, to transmit the GNSS assistance data at 1504, the network node may transmit the GNSS assistance data via a sidelink multicast message at 1512. The sidelink multicast message may be in at least one of: a V2X layer payload on a sidelink DRB, wherein the V2X layer payload may include GNSS assistance data based on second assistance data in an access link with the network node; or a PDCP SDU on a sidelink SRB. For example, referring to Figure 7 and Figure 8 The sidelink multicast message may be in the payload of the V2X layer 704 on the sidelink DRB or in the SDU of the PDCP 804 on the sidelink SRB. The payload of the V2X layer 704 may include GNSS assistance data based on the second assistance data in the access link with the network node.

[0152] In some aspects, to transmit the GNSS assistance data at 1504, the network node may transmit the GNSS assistance data via a sidelink broadcast message at 1514. The sidelink broadcast message may be in at least one of: a V2X layer payload on a sidelink DRB, wherein the V2X layer payload may include GNSS assistance data based on second assistance data in an access link with the network node; or a PDCP SDU on a sidelink SRB. For example, referring to Figure 7 and Figure 8 The sidelink broadcast message may be in the payload of the V2X layer 704 on the sidelink DRB or in the SDU of the PDCP 804 on the sidelink SRB. The payload of the V2X layer 704 may include GNSS assistance data based on the second assistance data in the access link with the network node.

[0153] In some aspects, the sidelink positioning session may be associated with an SLPP, and at 1506, the network node may receive from the first UE an indication of the location of at least one of the first UE or the one or more second UEs based on the GNSS assistance data for the sidelink positioning session. Figure 11 The sidelink positioning session (established by the first UE 1102 at 1112) may be associated with the SLPP. At 1120, the network node 1104 may receive, from the first UE 1102, an indication of the location of at least one of the first UE 1102 or the second UE 1106 based on the GNSS assistance data for the sidelink positioning session. In some aspects, 1506 may be performed by the SLPP positioning assistance component 199.

[0154] Figure 1616 is a diagram illustrating an example of a hardware implementation for an apparatus 1604. Apparatus 1604 may be a UE, a component of a UE, or may implement UE functionality. In some aspects, apparatus 1604 may include at least one cellular baseband processor 1624 (also referred to as a modem) coupled to one or more transceivers 1622 (e.g., a cellular RF transceiver). Cellular baseband processor 1624 may include at least one on-chip memory 1624′. In some aspects, apparatus 1604 may also include one or more subscriber identity module (SIM) cards 1620 and at least one application processor 1606 coupled to a secure digital (SD) card 1608 and a screen 1610. Application processor 1606 may include on-chip memory 1606′. In some aspects, device 1604 may also include a Bluetooth module 1612, a WLAN module 1614, an SPS module 1616 (e.g., a GNSS module), one or more sensor modules 1618 (e.g., a barometric pressure sensor / altimeter; a motion sensor such as an inertial measurement unit (IMU), a gyroscope, and / or an accelerometer; light detection and ranging (LIDAR), radio-aided detection and ranging (RADAR), sound navigation and ranging (SONAR), a magnetometer, audio, and / or other technologies for positioning), an additional memory module 1626, a power source 1630, and / or a camera 1632. The Bluetooth module 1612, the WLAN module 1614, and the SPS module 1616 may include an on-chip transceiver (TRX) (or, in some cases, only a receiver (RX)). The Bluetooth module 1612, the WLAN module 1614, and the SPS module 1616 may include their own dedicated antennas and / or utilize antenna 1680 for communication. The cellular baseband processor 1624 communicates with the UE 104 and / or RUs associated with the network entity 1602 via the transceiver 1622 via one or more antennas 1680. The cellular baseband processor 1624 and the application processor 1606 may each include computer-readable media / memory 1624′, 1606′, respectively. The additional memory module 1626 may also be considered computer-readable media / memory. Each computer-readable medium / memory 1624′, 1606′, 1626 may be non-transitory. The cellular baseband processor 1624 and the application processor 1606 are each responsible for general processing, including the execution of software stored on the computer-readable media / memory. When executed by the cellular baseband processor 1624 / application processor 1606, the software enables the cellular baseband processor 1624 / application processor 1606 to perform the various functions described above. The computer-readable media / memory may also be used to store data manipulated by the cellular baseband processor 1624 / application processor 1606 when executing the software.The cellular baseband processor 1624 / application processor 1606 may be a component of the UE 350 and may include at least one memory 360 and / or at least one of the TX processor 368, the RX processor 356, and the controller / processor 359. In one configuration, the device 1604 may be at least one processor chip (modem and / or applications) and include only the cellular baseband processor 1624 and / or the application processor 1606, while in another configuration, the device 1604 may be the entire UE (e.g., see. Figure 3 UE350 ) and includes additional modules of device 1604.

[0155] As discussed above, component 198 may be configured to obtain GNSS assistance data for a sidelink positioning session with one or more second UEs via a sidelink message; calculate a position of at least one of the first UE or the one or more second UEs based on the GNSS assistance data for the sidelink positioning session; and output an indication of the calculated position of the first UE or at least one of the one or more second UEs. Component 198 may be further configured to perform in conjunction with Figure 12 or Figure 13 Any of the aspects described in the flowcharts of, and / or by Figure 11 1604. Component 198 may be within the cellular baseband processor 1624, the application processor 1606, or both. Component 198 may be one or more hardware components specifically configured to perform the recited processes / algorithms, implemented by one or more processors configured to perform the recited processes / algorithms, stored on a computer-readable medium for implementation by one or more processors, or some combination thereof. When multiple processors are implemented, the multiple processors may perform the recited processes / algorithms individually or in combination. As shown, device 1604 may include a variety of components configured for various functions. In one configuration, the apparatus 1604, and specifically the cellular baseband processor 1624 and / or the application processor 1606, includes: means for obtaining GNSS assistance data for a sidelink positioning session with one or more second UEs via a sidelink message; means for calculating a position of at least one of the first UE or the one or more second UEs based on the GNSS assistance data for the sidelink positioning session; and means for outputting an indication of the calculated position of the first UE or at least one of the one or more second UEs. The apparatus 1604 may also include means for performing a combined Figure 12 and Figure 13 Aspects of the flowcharts described and / or by Figure 111604 is a component of any of the aspects performed by the UE 1102 in the apparatus 1604. A component may be a component 198 of the apparatus 1604 configured to perform the functions recited by the component. As described above, the apparatus 1604 may include the TX processor 368, the RX processor 356, and the controller / processor 359. Thus, 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 recited by the component.

[0156] Figure 17 Diagram 1700 illustrates an example hardware implementation for a network entity 1702. Network entity 1702 may be a base station (BS), a component of a BS, or may implement BS functionality. Network entity 1702 may include at least one of a CU 1710, a DU 1730, or a RU 1740. For example, depending on the layer functionality handled by component 199, network entity 1702 may include: a CU 1710; both the CU 1710 and the DU 1730; each of the CU 1710, the DU 1730, and the RU 1740; the DU 1730; both the DU 1730 and the RU 1740; or the RU 1740. CU 1710 may include at least one CU processor 1712. CU processor 1712 may include on-chip memory 1712′. In some aspects, CU 1710 may also include an additional memory module 1714 and a communication interface 1718. The CU 1710 communicates with the DU 1730 via a midhaul link, such as an F1 interface. The DU 1730 may include at least one DU processor 1732. The DU processor 1732 may include on-chip memory 1732′. In some aspects, the DU 1730 may also include additional memory modules 1734 and a communication interface 1738. The DU 1730 communicates with the RU 1740 via a fronthaul link. The RU 1740 may include at least one RU processor 1742. The RU processor 1742 may include on-chip memory 1742′. In some aspects, the RU 1740 may also include additional memory modules 1744, one or more transceivers 1746, an antenna 1780, and a communication interface 1748. The RU 1740 communicates with the UE 104. On-chip memories 1712', 1732', 1742' and additional memory modules 1714, 1734, 1744 can each be considered a computer-readable medium / memory. Each computer-readable medium / memory can be non-transitory. Each of processors 1712, 1732, 1742 is responsible for general processing, including executing software stored on the computer-readable medium / memory. When executed by the corresponding processor, the software causes the processor to perform the various functions described above. The computer-readable medium / memory can also be used to store data manipulated by the processor when executing the software.

[0157] As discussed above, component 199 may be configured to: configure GNSS assistance data for a sidelink positioning session between a first UE and one or more second UEs; and send, to the first UE, the GNSS assistance data for the sidelink positioning session between the first UE and the one or more second UEs. Component 199 may be further configured to perform a combined Figure 14 and Figure 15 Any of the aspects described in the flowcharts of, and / or by Figure 11 Any of the aspects performed by the network node 1104 in . Component 199 may be within one or more processors of one or more of the CU 1710, DU 1730, and RU 1740. Component 199 may be one or more hardware components that are 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. The network entity 1702 may include multiple components configured for various functions. In one configuration, the network entity 1702 includes: a component for configuring GNSS assistance data for a sidelink positioning session between a first UE and one or more second UEs; and a component for sending the GNSS assistance data for the sidelink positioning session between the first UE and the one or more second UEs to the first UE. The network entity 1702 may also include a component for performing a combined Figure 14 and Figure 15 The various aspects described in the flowcharts and / or by Figure 11 A means for any of the aspects performed by the network node 1104 in the embodiment of the present invention. A means may be a component 199 of the network entity 1702 configured to perform the functions recited by the means. As described above, the network entity 1702 may include the TX processor 316, the RX processor 370, and the controller / processor 375. Thus, in one configuration, a means may be the TX processor 316, the RX processor 370, and / or the controller / processor 375 configured to perform the functions recited by the means.

[0158] The present disclosure provides a method for wireless communication at a first UE. The method may include: obtaining GNSS assistance data for a sidelink positioning session with one or more second UEs via a sidelink message; calculating a position of at least one of the first UE or the one or more second UEs based on the GNSS assistance data for the sidelink positioning session; and outputting an indication of the calculated position of the first UE or at least one of the one or more second UEs. The method provides a signaling mechanism that supports the communication of positioning data via the UE's sidelink connection. This enhances the positioning accuracy of the UE operating on the sidelink connection and improves the efficiency of wireless communication.

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

[0160] 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 claims. Unless otherwise specified, references to elements in the singular do not mean "one and only one", but rather "one or more". Terms such as "if", "when" and "while" do not imply a direct temporal relationship or reaction. That is, these phrases, such as "when...", do not imply immediate action in response to the occurrence of an action or during the occurrence of an action, but simply imply that if the conditions are met, the action will occur, but no specific or immediate time limit is required for the action to occur. 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 interpreted as preferred or having advantages over other aspects. Unless otherwise specified, the term "some" refers to one or more. Combinations such as “at least one of A, B, or C,” “one or more of A, B, or C,” “at least one of A, B, and C,” “one or more of A, B, and C,” and “A, B, C, or any combination thereof” include any combination of A, B, and / or C, which may include multiple As, multiple Bs, or multiple Cs. 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, B, and C, where any such combination may include one or more members of A, B, or C. A set should be interpreted as a set of elements, where the number of elements is one or more. Thus, for a set of X, X will include one or more elements. When at least one processor is configured to perform a set of functions, the at least one processor is configured to perform the set of functions individually or in any combination. Thus, each of the at least one processor can be configured to perform a specific subset of the set of functions, where the subset is the complete set, a suitable subset of the set, or an empty subset of the set. If a first device receives data from or sends data to a second device, the data may 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 a transmission, signal, or message) may, for example, transmit the data using a transceiver, or may transfer the data to the device that sent the data.A device configured to "obtain" data (such as a transmission, signal, or message) may, for example, receive the data using a transceiver, or may obtain the data from a device that receives the data. Information stored in a memory includes instructions and / or data. All structural and functional equivalents to the elements of the various aspects described throughout this disclosure that are or later become known to those of ordinary skill in the art are expressly incorporated herein by reference and are covered by the claims. In addition, nothing disclosed herein is intended to be dedicated to the public, regardless of whether such disclosure is expressly recited in the claims. Words such as "module," "mechanism," "element," and "device" are not intended to be substituted for the word "component." Therefore, no claim element will be construed as part-plus-function unless the element is expressly recited using the phrase "component for..."

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

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

[0163] Aspect 1 is a method of wireless communication at a first user equipment (UE). The method may include: obtaining, via a sidelink message, global navigation satellite system (GNSS) assistance data for a sidelink positioning session with one or more second UEs; calculating a position of at least one of the first UE or the one or more second UEs based on the GNSS assistance data for the sidelink positioning session; and outputting an indication of the calculated position of the first UE or at least one of the one or more second UEs.

[0164] Aspect 2 is a method according to Aspect 1, wherein the method may further include: establishing the side link positioning session with the one or more second UEs before obtaining the GNSS assistance data, wherein in order to obtain the GNSS assistance data, the first UE may be configured to: obtain the GNSS assistance data for the established side link positioning session.

[0165] Aspect 3 is a method according to aspect 2, wherein obtaining the GNSS assistance data may include: obtaining the GNSS assistance data for the established sidelink positioning session via one of public signaling or dedicated signaling for the sidelink positioning session.

[0166] Aspect 4 is a method according to aspect 3, wherein the GNSS assistance data may include a GNSS data type and a GNSS data element associated with the GNSS data type.

[0167] Aspect 5 is a method according to aspect 4, wherein the GNSS data type may include one or more of the following: GNSS common assistance data, observed time difference of arrival (OTDOA) assistance data, barometric assistance data, time difference of arrival based system (TBS) assistance data, or new radio (NR) downlink time difference of arrival / downlink angle of arrival (DL-TDOA / DL-AoD) assistance data.

[0168] Aspect 6 is a method according to any one of Aspects 1 to 5, wherein the method may further include: receiving a request message requesting the indication of the calculated positioning via a PC5 side link (PC5-S), and wherein outputting the indication of the calculated positioning may include outputting the indication of the calculated positioning in response to the request message.

[0169] Aspect 7 is a method according to any one of Aspects 1 to 6, wherein the method may further include: establishing side link communication with the one or more second UEs before obtaining the GNSS assistance data, wherein obtaining the GNSS assistance data may include: obtaining the GNSS assistance data for the established side link communication.

[0170] Aspect 8 is a method according to any one of aspects 1 to 6, wherein obtaining the GNSS assistance data may include: receiving the GNSS assistance data for the sidelink positioning session from a network node.

[0171] Aspect 9 is the method according to aspect 8, wherein the network node may be at least one of the following: a road side unit (RSU), a base station, a third UE, a side link device, or a wireless device.

[0172] Aspect 10 is a method according to any one of Aspects 1 to 6, wherein obtaining the GNSS assistance data may include: retrieving the GNSS assistance data for the sidelink positioning session from at least one memory or cache, wherein the at least one memory or the cache is associated with a positioning application.

[0173] Aspect 11 is a method according to any one of aspects 1 to 6, wherein obtaining the GNSS assistance data via the sidelink message may include: obtaining the GNSS assistance data via one of a sidelink unicast message, a sidelink multicast message, or a sidelink broadcast message.

[0174] Aspect 12 is a method according to aspect 11, wherein the GNSS assistance data obtained via the sidelink unicast message, the sidelink multicast message or the sidelink broadcast message can mirror the second assistance data in the access link with the network node.

[0175] Aspect 13 is a method according to aspect 11, wherein obtaining the GNSS assistance data may include: obtaining the GNSS assistance data via the sidelink unicast message in at least one of the following: a vehicle-to-everything (V2X) layer payload on a sidelink data radio bearer (DRB), a packet data convergence protocol (PDCP) service data unit (SDU) on a sidelink signaling radio bearer (SRB), a PC5 radio resource control (RRC) (PC5-RRC) information element (IE) on the sidelink SRB, or a PC5 sidelink (PC5-S) IE on the sidelink SRB.

[0176] Aspect 14 is a method according to aspect 13, wherein the PC5-RRC IE may be a first new IE defined in the sidelink unicast message, the PC5-S IE may be a second new IE defined in the sidelink unicast message, the second new IE is used for the GNSS assistance data based on the second assistance data in the access link with the network node, and wherein the V2X layer payload may include the GNSS assistance data based on the second assistance data in the access link with the network node.

[0177] Aspect 15 is a method according to aspect 11, wherein obtaining the GNSS assistance data may include: obtaining the GNSS assistance data via the sidelink multicast message in at least one of the following: a vehicle-to-everything (V2X) layer payload on a sidelink data radio bearer (DRB), or a packet data convergence protocol (PDCP) service data unit (SDU) on a sidelink signaling radio bearer (SRB).

[0178] Aspect 16 is a method according to aspect 15, wherein the V2X layer payload may include the GNSS assistance data based on second assistance data in an access link with a network node.

[0179] Aspect 17 is a method according to aspect 11, wherein obtaining the GNSS assistance data may include: obtaining the GNSS assistance data via the sidelink broadcast message in at least one of the following: a vehicle-to-everything (V2X) layer payload on a sidelink data radio bearer (DRB), or a packet data convergence protocol (PDCP) service data unit (SDU) on a sidelink signaling radio bearer (SRB).

[0180] Aspect 18 is a method according to aspect 17, wherein the V2X layer payload may include the GNSS assistance data based on second assistance data in an access link with a network node.

[0181] Aspect 19 is a method according to any one of aspects 1 to 18, wherein the sidelink positioning session may be associated with a Sidelink Positioning Protocol (SLPP).

[0182] Aspect 20 is a method according to any one of aspects 1 to 19, wherein outputting the indication of the positioning of the first UE or at least one of the one or more second UEs may include: sending the indication of the positioning of the first UE or at least one of the one or more second UEs to the one or more second UEs, or storing the indication of the positioning of the first UE or at least one of the one or more second UEs in the at least one memory or the cache.

[0183] Aspect 21 is an apparatus for performing wireless communications at a UE, the apparatus comprising: at least one memory; and at least one processor, the at least one processor being coupled to the at least one memory and, based at least in part on information stored in the at least one memory, the at least one processor being configured, alone or in any combination, to perform the method according to any one of Aspects 1 to 20.

[0184] Aspect 22 is an apparatus according to aspect 21, further comprising at least one of a transceiver or an antenna, the at least one of the transceiver or the antenna being coupled to the at least one processor and configured to obtain the GNSS assistance data.

[0185] Aspect 23 is an apparatus for wireless communication, the apparatus comprising means for implementing the method according to any one of aspects 1 to 20.

[0186] Aspect 24 is a computer-readable medium (eg, non-transitory computer-readable medium) storing computer-executable code, wherein the code, when executed by at least one processor, causes the at least one processor to implement the method according to any one of aspects 1 to 20.

[0187] Aspect 25 is a method of wireless communication at a network node. The method may include: configuring global navigation satellite system (GNSS) assistance data for a sidelink positioning session between a first user equipment (UE) and one or more second UEs; and sending, to the first UE, the GNSS assistance data for the sidelink positioning session between the first UE and the one or more second UEs.

[0188] Aspect 26 is a method according to aspect 25, wherein the network node may be at least one of the following: a road side unit (RSU), a base station, a third UE, a side link device, or a wireless device.

[0189] Aspect 27 is a method according to any one of Aspects 25 to 26, wherein sending the GNSS assistance data may include: sending the GNSS assistance data via one of a sidelink unicast message, a sidelink multicast message, or a sidelink broadcast message, wherein the GNSS assistance data may mirror the second assistance data in the access link with the network node.

[0190] Aspect 28 is a method according to aspect 27, wherein sending the GNSS assistance data may include: sending the GNSS assistance data via the sidelink unicast message in at least one of the following: a vehicle-to-everything (V2X) layer payload on a sidelink data radio bearer (DRB), a packet data convergence protocol (PDCP) service data unit (SDU) on a sidelink signaling radio bearer (SRB), a PC5 radio resource control (RRC) (PC5-RRC) information element (IE) on the sidelink SRB, or a PC5 sidelink (PC5-S) IE on the sidelink SRB.

[0191] Aspect 29 is a method according to aspect 28, wherein the PC5-RRC IE may be a first new IE defined in the sidelink unicast message, the PC5-S IE may be a second new IE defined in the sidelink unicast message, the second new IE is used for the GNSS assistance data based on the second assistance data in the access link with the network node, and wherein the V2X layer payload may include the GNSS assistance data based on the second assistance data in the access link with the network node.

[0192] Aspect 30 is a method according to aspect 27, wherein sending the GNSS assistance data may include: sending the GNSS assistance data via the sidelink multicast message in at least one of the following: a vehicle-to-everything (V2X) layer payload on a sidelink data radio bearer (DRB), wherein the V2X layer payload may include the GNSS assistance data based on the second assistance data in the access link with the network node; or a packet data convergence protocol (PDCP) service data unit (SDU) on a sidelink signaling radio bearer (SRB).

[0193] Aspect 31 is a method according to aspect 27, wherein sending the GNSS assistance data may include: sending the GNSS assistance data via the sidelink broadcast message in at least one of the following: a vehicle-to-everything (V2X) layer payload on a sidelink data radio bearer (DRB), wherein the V2X layer payload may include the GNSS assistance data based on the second assistance data in the access link with the network node; or a packet data convergence protocol (PDCP) service data unit (SDU) on a sidelink signaling radio bearer (SRB).

[0194] Aspect 32 is a method according to any one of Aspects 25 to 31, wherein the sidelink positioning session may be associated with a Sidelink Positioning Protocol (SLPP), and wherein the method may further include: receiving an indication of the positioning of the first UE or at least one of the one or more second UEs from the first UE based on the GNSS assistance data used for the sidelink positioning session.

[0195] Aspect 33 is an apparatus for wireless communication at a network node, the apparatus comprising: at least one memory; and at least one processor, the at least one processor being coupled to the at least one memory and, based at least in part on information stored in the at least one memory, the at least one processor being configured, alone or in any combination, to perform the method according to any one of aspects 25 to 32.

[0196] Aspect 34 is an apparatus according to aspect 33, the apparatus further comprising at least one of a transceiver or an antenna, the at least one of the transceiver or the antenna being coupled to the at least one processor and configured to transmit the GNSS assistance data.

[0197] Aspect 35 is an apparatus for wireless communication, the apparatus comprising means for implementing the method according to any one of aspects 25 to 32.

[0198] Aspect 36 is a computer-readable medium (eg, non-transitory computer-readable medium) storing computer-executable code, wherein the code, when executed by at least one processor, causes the at least one processor to implement the method according to any one of aspects 25 to 32.

Claims

1. An apparatus for 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, based at least in part on information stored in the at least one memory, configured, alone or in any combination, to: obtaining, via a sidelink message, Global Navigation Satellite System (GNSS) assistance data for a sidelink positioning session with one or more second UEs; calculating a position of at least one of the first UE or the one or more second UEs based on the GNSS assistance data for the sidelink positioning session; as well as An indication of the calculated position of at least one of the first UE or the one or more second UEs is output.

2. The apparatus according to claim 1, further comprising: a transceiver coupled to the at least one processor, wherein to obtain the GNSS assistance data, the at least one processor is configured, alone or in any combination, to receive the GNSS assistance data via the transceiver, and wherein the at least one processor is further configured, alone or in any combination, to: Prior to obtaining the GNSS assistance data, establishing the sidelink positioning session with the one or more second UEs, wherein to obtain the GNSS assistance data, the at least one processor is configured, alone or in any combination, to obtain the GNSS assistance data for the established sidelink positioning session.

3. An apparatus according to claim 2, wherein, in order to obtain the GNSS assistance data, the at least one processor is configured, alone or in any combination, to: obtain the GNSS assistance data for the established sidelink positioning session via one of public signaling or dedicated signaling for the sidelink positioning session. The apparatus of claim 3 , wherein the GNSS assistance data comprises a GNSS data type and a GNSS data element associated with the GNSS data type.

5. The apparatus of claim 4 , wherein the GNSS data type comprises one or more of: GNSS public assistance data, Observed Time Difference of Arrival (OTDOA) assistance data, Air pressure assist data, Time Difference of Arrival Based System (TBS) assistance data, or New Radio (NR) downlink time difference of arrival / downlink angle of arrival (DL-TDOA / DL-AoD) assistance data.

6. The apparatus of claim 1 , wherein the at least one processor, alone or in any combination, is further configured to: receiving, via a PC5 side link (PC5-S), a request message requesting said indication of the calculated position fix, and wherein, in order to output said indication of the calculated position fix, said at least one processor is configured, alone or in any combination, to: The indication of the calculated position position is output in response to the request message.

7. The apparatus of claim 1 , wherein the at least one processor, alone or in any combination, is further configured to: Prior to obtaining the GNSS assistance data, sidelink communication is established with the one or more second UEs, wherein to obtain the GNSS assistance data, the at least one processor is configured, alone or in any combination, to obtain the GNSS assistance data for the established sidelink communication.

8. The apparatus of claim 1 , wherein to obtain the GNSS assistance data, the at least one processor is configured, alone or in any combination, to: The GNSS assistance data for the sidelink positioning session is received from a network node.

9. The apparatus of claim 8, wherein the network node is at least one of: Roadside Unit (RSU), base stations, The third UE, Sidelink device, or Wireless devices.

10. The apparatus of claim 1 , wherein to obtain the GNSS assistance data, the at least one processor is configured, alone or in any combination, to: The GNSS assistance data for the sidelink positioning session is retrieved from the at least one memory or cache, wherein the at least one memory or the cache is associated with a positioning application.

11. The apparatus of claim 1 , wherein to obtain the GNSS assistance data via the sidelink message, the at least one processor is configured, alone or in any combination, to: The GNSS assistance data is obtained via one of a sidelink unicast message, a sidelink multicast message, or a sidelink broadcast message.

12. The apparatus of claim 11, wherein the GNSS assistance data obtained via the sidelink unicast message, the sidelink multicast message, or the sidelink broadcast message mirrors second assistance data in an access link with a network node.

13. The apparatus of claim 11 , wherein to obtain the GNSS assistance data, the at least one processor is further configured, alone or in any combination, to: obtain the GNSS assistance data via the sidelink unicast message in at least one of the following: Vehicle-to-everything (V2X) layer payload on the sidelink Data Radio Bearer (DRB), Packet Data Convergence Protocol (PDCP) Service Data Unit (SDU) on a Sidelink Signalling Radio Bearer (SRB), PC5 Radio Resource Control (RRC) (PC5-RRC) Information Element (IE) on the sidelink SRB, or PC5 Sidelink (PC5-S) IE on the sidelink SRB.

14. The apparatus of claim 13 , wherein the PC5-RRC IE is a first new IE defined in the sidelink unicast message, the PC5-S IE is a second new IE defined in the sidelink unicast message, the second new IE is used for the GNSS assistance data based on second assistance data in an access link with a network node, and wherein the V2X layer payload includes the GNSS assistance data based on the second assistance data in the access link with the network node.

15. The apparatus of claim 11 , wherein to obtain the GNSS assistance data, the at least one processor is configured, alone or in any combination, to: obtain the GNSS assistance data via the sidelink multicast message in at least one of the following: Vehicle-to-everything (V2X) layer payload on a sidelink Data Radio Bearer (DRB), or Packet Data Convergence Protocol (PDCP) Service Data Unit (SDU) on a sidelink signaling radio bearer (SRB).

16. The apparatus of claim 15, wherein the V2X layer payload includes the GNSS assistance data based on second assistance data in an access link with a network node.

17. The apparatus of claim 11 , wherein to obtain the GNSS assistance data, the at least one processor is configured, alone or in any combination, to: obtain the GNSS assistance data via the sidelink broadcast message in at least one of the following: Vehicle-to-everything (V2X) layer payload on a sidelink Data Radio Bearer (DRB), or Packet Data Convergence Protocol (PDCP) Service Data Unit (SDU) on a sidelink signaling radio bearer (SRB).

18. The apparatus of claim 17, wherein the V2X layer payload includes the GNSS assistance data based on second assistance data in an access link with a network node.

19. The apparatus of claim 1, wherein the sidelink positioning session is associated with a Sidelink Positioning Protocol (SLPP).

20. The apparatus of claim 1 , wherein to output the indication of the location of at least one of the first UE or the one or more second UEs, the at least one processor is configured, alone or in any combination, to: sending said indication of said positioning of at least one of said first UE or said one or more second UEs to said one or more second UEs, or The indication of the location of at least one of the first UE or the one or more second UEs is stored in the at least one memory or cache.

21. An apparatus for wireless communication at a network node, 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, configured, alone or in any combination, to: configuring global navigation satellite system (GNSS) assistance data for a sidelink positioning session between a first user equipment (UE) and one or more second UEs; as well as The GNSS assistance data is sent for the first UE for the sidelink positioning session between the first UE and the one or more second UEs.

22. The apparatus according to claim 21, further comprising: a transceiver coupled to the at least one processor, wherein to transmit the GNSS assistance data, the at least one processor, alone or in any combination, is configured to transmit the GNSS assistance data via the transceiver, and wherein the network node is at least one of: Roadside Unit (RSU), base stations, The third UE, Sidelink device, or Wireless devices.

23. The apparatus of claim 21 , wherein to transmit the GNSS assistance data, the at least one processor is configured, alone or in any combination, to: The GNSS assistance data is sent via one of a sidelink unicast message, a sidelink multicast message, or a sidelink broadcast message, wherein the GNSS assistance data mirrors second assistance data in an access link of the network node.

24. The apparatus of claim 23, wherein to send the GNSS assistance data, the at least one processor is configured, alone or in any combination, to: send the GNSS assistance data via the sidelink unicast message in at least one of the following: Vehicle-to-everything (V2X) layer payload on the sidelink Data Radio Bearer (DRB), Packet Data Convergence Protocol (PDCP) Service Data Unit (SDU) on a Sidelink Signalling Radio Bearer (SRB), PC5 Radio Resource Control (RRC) (PC5-RRC) Information Element (IE) on the sidelink SRB, or PC5 Sidelink (PC5-S) IE on the sidelink SRB.

25. The apparatus of claim 24 , wherein the PC5-RRC IE is a first new IE defined in the sidelink unicast message, the PC5-S IE is a second new IE defined in the sidelink unicast message, the second new IE being used for the GNSS assistance data based on the second assistance data in the access link with the network node, and wherein the V2X layer payload includes the GNSS assistance data based on the second assistance data in the access link with the network node.

26. The apparatus of claim 23, wherein to transmit the GNSS assistance data, the at least one processor is configured, alone or in any combination, to: transmit the GNSS assistance data via the sidelink multicast message in at least one of the following: a vehicle-to-everything (V2X) layer payload on a sidelink data radio bearer (DRB), wherein the V2X layer payload includes the GNSS assistance data based on the second assistance data in the access link with the network node, or Packet Data Convergence Protocol (PDCP) Service Data Unit (SDU) on a sidelink signaling radio bearer (SRB).

27. The apparatus of claim 23, wherein to transmit the GNSS assistance data, the at least one processor is configured, alone or in any combination, to: transmit the GNSS assistance data via the sidelink broadcast message in at least one of the following: a vehicle-to-everything (V2X) layer payload on a sidelink data radio bearer (DRB), wherein the V2X layer payload includes the GNSS assistance data based on the second assistance data in the access link with the network node, or Packet Data Convergence Protocol (PDCP) Service Data Unit (SDU) on a sidelink signaling radio bearer (SRB).

28. The apparatus of claim 21 , wherein the sidelink positioning session is associated with a Sidelink Positioning Protocol (SLPP), and wherein the at least one processor is further configured, alone or in any combination, to: An indication of a location of at least one of the first UE or the one or more second UEs is received from the first UE based on the GNSS assistance data for the sidelink positioning session.

29. A method of wireless communication at a first user equipment (UE), the method comprising: obtaining, via a sidelink message, Global Navigation Satellite System (GNSS) assistance data for a sidelink positioning session with one or more second UEs; calculating a position of at least one of the first UE or the one or more second UEs based on the GNSS assistance data for the sidelink positioning session; as well as An indication of the calculated position of at least one of the first UE or the one or more second UEs is output.

30. A method of wireless communication at a network node, the method comprising: configuring global navigation satellite system (GNSS) assistance data for a sidelink positioning session between a first user equipment (UE) and one or more second UEs; as well as The GNSS assistance data is sent for the first UE for the sidelink positioning session between the first UE and the one or more second UEs.

Images