Real-time GNSS spacecraft broadcast data quality monitoring using crowdsourced data from roadside units

Abstract

Aspects presented herein may enable a network entity to determine whether there is any error in broadcast data from one or more spacecrafts (SVs) based on crowdsourcing information from a set of roadside units (RSUs). In one aspect, a network entity obtains at least one measurement of a satellite associated with a set of RSUs. The network entity estimates a location of the satellite based on the at least one measurement and a location of the set of RSUs. The network entity identifies whether the estimated location of the satellite is associated with an error based on a comparison of the estimated location of the satellite to ephemeris or almanac data of the satellite.

Description

[0001] Cross - Reference to Related Applications

[0002] This application claims the benefit of U.S. Non - Provisional Patent Application Serial No. 18 / 061,790, filed on December 5, 2022, entitled "REAL TIME GNSS SPACE VEHICLE BROADCAST DATA QUALITY MONITORING USING CROWD - SOURCED DATA FROM ROAD SIDE UNITS", which is hereby incorporated by reference in its entirety. Technical Field

[0003] The present disclosure generally relates to communication systems and, more particularly, to wireless communication regarding positioning. Background Art

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

[0005] These multiple access technologies have been adopted in various telecommunication standards to provide a common protocol that enables different wireless devices to communicate at the urban, national, regional, or even global level. An example telecommunication standard is 5G New Radio (NR). 5G NR is part of the ongoing evolution of mobile broadband promulgated by the Third Generation Partnership Project (3GPP) to meet new requirements associated with latency, reliability, security, scalability (e.g., with respect to the Internet of Things (IoT)), and other requirements. 5G NR includes services associated with Enhanced Mobile Broadband (eMBB), Massive Machine - Type Communication (mMTC), and Ultra - Reliable Low - Latency Communication (URLLC). Some aspects of 5G NR may be based on the 4G Long - Term Evolution (LTE) standard. Further improvements to 5G NR technology are needed. Additionally, these improvements may also be applicable to other multiple access technologies and telecommunication standards that employ 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 such aspects. This summary is not an extensive overview of all contemplated aspects. The summary neither identifies key or critical elements of all aspects nor describes the scope of any or all aspects. Its sole purpose is to present some concepts of one or more aspects in a simplified form as a prelude to the more detailed description that is presented later.

[0007] In one aspect of the present disclosure, a method, a computer-readable medium, and an apparatus are provided. The apparatus obtains at least one measurement of a satellite associated with a set of roadside units (RSUs). The apparatus estimates a positioning of the satellite based on the at least one measurement and a position of the set of RSUs. The apparatus identifies whether the estimated positioning of the satellite is associated with an error based on a comparison of the estimated positioning of the satellite with almanac (ALM) data or ephemeris (EPH) data of the satellite.

[0008] In one aspect of the present disclosure, a method, a computer-readable medium, and an apparatus are provided. The apparatus performs at least one of the following: measuring a pseudorange (PR) between an RSU and a satellite, estimating a positioning of the satellite based on EPH data or ALM data of the satellite, or estimating a clock offset associated with the satellite based on EPH data or ALM data of the satellite. The apparatus sends at least one of the measurement of the PR, the estimate of the positioning of the satellite, or the estimate of the clock offset of the satellite to a network entity. The apparatus receives information associated with the satellite from the network entity based on the measurement of the PR, the estimate of the positioning of the satellite, or the estimate of the clock offset.

[0009] To achieve the foregoing and related purposes, one or more aspects include the features described comprehensively hereinafter and particularly pointed out in the claims. The following description and the drawings set forth in detail some illustrative features of one or more aspects. However, these features indicate 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] Figure 2A is a diagram illustrating an example of a first frame according to various aspects of the present disclosure.

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

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

[0014] Figure 2DIs a diagram illustrating an example of an uplink (UL) channel 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 measurements.

[0017] Figure 5 Is a diagram illustrating an example of global navigation satellite system (GNSS) positioning according to various aspects of the present disclosure.

[0018] Figure 6 Is a diagram illustrating an example of using a roadside unit (RSU) network to estimate the positioning and clock offset of a space vehicle (SV) according to various aspects of the present disclosure.

[0019] Figure 7 Is a communication flow diagram illustrating an example of a network entity providing GNSS broadcast data quality monitoring for a set of SVs based on crowdsourced data from an RSU network according to various aspects of the present disclosure.

[0020] Figure 8 Is a flowchart of a method for wireless communication.

[0021] Figure 9 Is a flowchart of a method for wireless communication.

[0022] Figure 10 Is a diagram illustrating an example of a hardware implementation for a network entity.

[0023] Figure 11 Is a flowchart of a method for wireless communication.

[0024] Figure 12 Is a diagram illustrating an example of a hardware implementation for a device. Detailed Description

[0025] Aspects presented herein may enable a GNSS device (e.g., a UE, GNSS receiver, etc.) or a positioning entity (e.g., a location server, a location management function (LMF), a network node, a base station, etc.) to determine whether there are any errors in data broadcast from one or more SVs to ensure continuity and availability of accurate positioning and / or timing information received by the GNSS device or the positioning entity, which may be suitable for vehicle-to-everything (V2X) and cellular V2X (C-V2X) applications. For example, in one aspect of the present disclosure, an RSU network may be used to estimate the positioning and / or clock offset of an SV. Since the positions of RSUs are generally known (e.g., an RSU may be similar to a beacon with known positioning and clock), the distances between a particular SV and the RSU network can be measured and used to estimate the positioning of the SV. Then, the estimated positioning of the SV can be compared with the ephemeris information and / or almanac information broadcast from the SV (or received from another entity) to determine whether there are any errors associated with the SV. If it is determined that the SV has broadcast incorrect information, the SV can be isolated / excluded from the positioning. This process can be repeated for multiple SVs (e.g., all SVs participating in a positioning session), thereby improving the positioning accuracy of the GNSS device.

[0026] The detailed description set forth below in connection 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. To provide a thorough understanding of the various concepts, the detailed description includes specific details. However, the concepts may be practiced without these specific details. In some instances, well-known structures and components are shown in block diagram form to avoid obscuring the concepts.

[0027] Certain aspects of a telecommunications system are presented with reference to various apparatuses and methods. These apparatuses and methods are described in the following detailed description and illustrated in the 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 an element is implemented as hardware or software depends upon the particular application and design constraints imposed on the overall system.

[0028] 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. 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, gate logic, discrete hardware circuits, and other suitable hardware configured to perform the various functions described throughout this disclosure. One or more processors in the processing system can execute software. Software should be broadly construed to mean instructions, instruction sets, code, code segments, program code, programs, subprograms, software components, applications, software applications, software packages, routines, subroutines, objects, executable files, threads of execution, procedures, functions, or any combination thereof, regardless of whether it is referred to as software, firmware, middleware, microcode, hardware description language, or other terms.

[0029] Thus, in one or more example aspects, embodiments, and / or use cases, the described functionality can be implemented in hardware, software, or any combination thereof. If implemented in software, the functionality can be stored or encoded on a computer-readable medium as one or more instructions or code. Computer-readable media includes computer storage media. Storage media can be any available media that can be accessed by a computer. As an example, such computer-readable media can 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 capable of storing computer-executable code in the form of instructions or data structures that can be accessed by a computer.

[0030] Although aspects, embodiments, and / or use cases are described by way of illustration with some examples in this application, additional or different aspects, embodiments, and use cases may arise in many different arrangements and scenarios. The aspects, embodiments, 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, embodiments, and / or use cases may be embodied via integrated chips and other non-module-component-based devices (e.g., end-user devices, vehicles, communication devices, computing devices, industrial equipment, retail / purchase devices, medical devices, artificial intelligence (AI)-enabled devices, etc.). Although some examples may or may not be specifically targeted at use cases or applications, the described examples may have wide applicability. The aspects, embodiments, and / or use cases may range from chip-level or modular components to non-modular, non-chip-level embodiments, and further to aggregated, distributed, or original equipment manufacturer (OEM) devices or systems incorporating one or more of the technologies 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 includes multiple components for analog and digital purposes (e.g., hardware components including antennas, RF chains, power amplifiers, modulators, buffers, processors, interleavers, adders / summers, etc.). The technologies described herein may be practiced in a wide variety of devices, chip-level components, systems, distributed arrangements, aggregated components, or disaggregated components, end-user devices, etc., of various sizes, shapes, and configurations.

[0031] The deployment of a communication system (such as a 5G NR system) can be arranged with various components or constituent parts in a variety of ways. In a 5G NR system or network, network nodes, network entities, mobility elements of the network, radio access network (RAN) nodes, core network nodes, network elements, or network equipment (such as a base station (BS)), or one or more units (or one or more components) performing base station functionality can be implemented in an aggregated or disaggregated architecture. For example, a BS (such as a Node B (NB), evolved NB (eNB), NR BS, 5G NB, access point (AP), transmit receive point (TRP), or cell, etc.) can be implemented as an aggregated base station (also referred to as a stand-alone BS or monolithic BS) or a disaggregated base station.

[0032] 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 split base station may be configured to utilize a protocol stack that is physically or logically distributed between two or more units, such as one or more central or centralized units (CUs), one or more distributed units (DUs), or one or more radio units (RUs). In some aspects, a CU may be implemented within a RAN node, and one or more DUs may be co-located with the CU, or alternatively, may be geographically or virtually distributed among 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, i.e., a virtual central unit (VCU), a virtual distributed unit (VDU), or a virtual radio unit (VRU).

[0033] Base station operation or network design may consider the converged characteristics of base station functionality. For example, a split base station may be utilized in an integrated access backhaul (IAB) network, an open radio access network (O-RAN, such as a 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)). Splitting may include distributing functions across two or more units at various physical locations, as well as virtually distributing the functions of at least one unit, which may enable flexibility in network design. The various units of a split base station or a split RAN architecture may be configured for wired or wireless communication with at least one other unit.

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

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

[0036] In some aspects, CU 110 may host one or more higher layer control functions. Such control functions may include Radio Resource Control (RRC), Packet Data Convergence Protocol (PDCP), Service Data Adaptation Protocol (SDAP), etc. Each control function may utilize an interface that is configured to communicate signals with other control functions hosted by CU 110. CU 110 may be configured to handle user plane functionality (i.e., Central Unit - User Plane (CU-UP)), control plane functionality (i.e., Central Unit - Control Plane (CU-CP)), or a combination thereof. In some embodiments, 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-RA configuration, the CU-UP units may communicate bidirectionally with the CU-CP units via an interface (such as an E1 interface). As needed, CU 110 may be implemented to communicate with DU 130 for network control and signaling.

[0037] DU 130 may correspond to a logical unit that includes one or more base station functions for controlling the operation of one or more RUs 140. In some aspects, DU 130 may host one or more of the Radio Link Control (RLC) layer, Medium Access Control (MAC) layer, and one or more high Physical (PHY) layers (such as modules for forward error correction (FEC) encoding and decoding, scrambling, modulation, and demodulation, etc.) at least partially according to a functional split (such as those defined by 3GPP). In some aspects, DU 130 may also host one or more low PHY layers. Each layer (or module) may utilize an interface that is configured to communicate signals with other layers (and modules) hosted by DU 130 or with control functions hosted by CU 110.

[0038] The lower layer functionality may be implemented by one or more RUs 140. In some deployments, the RU 140 controlled by the DU 130 may correspond to a logical node that hosts RF processing functions or low PHY layer functions (such as performing Fast Fourier Transform (FFT), Inverse FFT (iFFT), digital beamforming, Physical Random Access Channel (PRACH) extraction and filtering, etc.) or both, at least in part based on functional splitting (such as lower layer functional splitting). In such an architecture, the RU 140 may be implemented to handle over-the-air (OTA) communication with one or more UEs 104. In some embodiments, the real-time and non-real-time aspects of the control plane and user plane communication 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).

[0039] The SMO framework 105 may be configured to support RAN deployment and orchestration of non-virtualized network elements and virtualized network elements. For non-virtualized network elements, the SMO framework 105 may be configured to support the deployment of dedicated physical resources for RAN coverage requirements, which may be managed via an operation and maintenance interface (such as the O1 interface). For virtualized network elements, the SMO framework 105 may be configured to interact with a cloud computing platform (such as the Open Cloud (O-Cloud) 190) to perform network element lifecycle management (such as instantiating virtualized network elements) via a cloud computing platform interface (such as the O2 interface). Such virtualized network elements may include, but are not limited to, the CU 110, DU 130, RU 140, and the near RT RIC 125. In some embodiments, the SMO framework 105 may communicate with the hardware aspects of the 4G RAN (such as the Open eNB (O-eNB) 111) via the O1 interface. Additionally, in some embodiments, the SMO framework 105 may communicate directly with one or more RUs 140 via the O1 interface. The SMO framework 105 may also include a non-RT RIC 115 configured to support the functionality of the SMO framework 105.

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

[0041] In some specific implementations, to generate an AI / ML model to be deployed in the near-RT RIC 125, the non-RT RIC 115 can receive parameters or external enrichment information from an external server. Such information can be utilized by the near-RT RIC 125 and can 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 can be configured to tune RAN behavior or performance. For example, the non-RT RIC 115 can monitor long-term trends and patterns of performance and employ an AI / ML model to perform corrective actions via the SMO framework 105 (such as via reconfiguration of O1) or via creation of RAN management policies (such as A1 policies).

[0042] At least one of CU 110, DU 130, and RU 140 may be referred to as 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 an access point to core network 120 for UE 104. Base station 102 may include macro cells (high-power cellular base stations) and / or small cells (low-power cellular base stations). Small cells include femto cells, pico cells, and micro cells. A network including both small cells and macro cells may be referred to as a heterogeneous network. A heterogeneous network may also include a home evolved Node B (eNB) (HeNB), which may provide services to a restricted group referred to as a closed subscriber group (CSG). The communication link between RU 140 and UE 104 may include an uplink (UL) (also referred to as a reverse link) transmission from UE 104 to RU 140 and / or a downlink (DL) (also referred to as a forward link) transmission from RU 140 to UE 104. The communication link may use multiple-input multiple-output (MIMO) antenna technology, including spatial multiplexing, beamforming, and / or transmit diversity. The communication link may be through one or more carriers. For each carrier allocated in carrier aggregation with a total of up to Yx MHz (x component carriers) for transmission in each direction, base station 102 / UE 104 may use a spectrum with a bandwidth of up to Y MHz (e.g., 5 MHz, 10 MHz, 15 MHz, 20 MHz, 100 MHz, 400 MHz, etc.). The carriers may or may not be adjacent to each other. The allocation of carriers may be asymmetric with respect to DL and UL (e.g., more or fewer carriers may be allocated for DL compared to UL). 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 carriers may be referred to as secondary cells (SCells).

[0043] Some UEs 104 may use a device-to-device (D2D) communication link 158 to communicate with each other. D2D communication link 158 may use DL / UL wireless wide area network (WWAN) spectrum. D2D communication link 158 may use one or more sidelink channels, such as a physical sidelink broadcast channel (PSBCH), a physical sidelink discovery channel (PSDCH), a physical sidelink shared channel (PSSCH), and a physical sidelink control channel (PSCCH). D2D communication may be through various wireless D2D communication systems, such as, for example, Bluetooth, Wi-Fi based on the Institute of Electrical and Electronics Engineers (IEEE) 802.11 standard, LTE, or NR.

[0044] The wireless communication system may further include a Wi-Fi AP 150 that communicates with the 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) before communication to determine whether the channel is available.

[0045] The electromagnetic spectrum is generally subdivided into various categories, bands, channels, etc. based on frequency / wavelength. In 5G NR, two initial operating bands have been identified as Frequency Range Designation FR1 (410 MHz - 7.125 GHz) and FR2 (24.25 GHz - 52.6 GHz). Although a part of FR1 is greater than 6 GHz, in various documents and articles, FR1 is generally (interchangeably) referred to as the "sub-6 GHz" band. Regarding FR2, a similar naming issue sometimes occurs, which is generally (interchangeably) referred to as the "millimeter wave" band in documents and articles, although it is different from the Extremely High Frequency (EHF) band (30 GHz - 300 GHz) identified by the International Telecommunication Union (ITU) as the "millimeter wave" band.

[0046] The frequencies between FR1 and FR2 are generally referred to as mid-band frequencies. Recent 5G NR research has identified the operating bands for these mid-band frequencies as Frequency Range Designation FR3 (7.125 GHz - 24.25 GHz). The bands falling within FR3 may inherit FR1 characteristics and / or FR2 characteristics, and thus can effectively extend the features of FR1 and / or FR2 to the mid-band frequencies. In addition, higher 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 Designation FR2-2 (52.6 GHz - 71 GHz), FR4 (71 GHz - 114.25 GHz), and FR5 (114.25 GHz - 300 GHz). Each of these higher bands falls within the EHF band.

[0047] Considering the above aspects, unless otherwise specifically stated, if the term "sub-6 GHz" etc. is used herein, it may broadly represent frequencies that can be less than 6 GHz, can be within FR1, or can include mid-band frequencies. In addition, unless otherwise specifically stated, if the term "millimeter wave" etc. is used herein, it may broadly represent frequencies that can include mid-band frequencies, can be within FR2, FR4, FR2-2, and / or FR5, or can be within the EHF band.

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

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

[0050] 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 processes 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. One or more Location Servers 168 are illustrated as including a Gateway Mobile Location Center (GMLC) 165 and a Location Management Function (LMF) 166. However, in general, one or more Location Servers 168 may include one or more location / locationing servers, which may include one or more of the GMLC 165, LMF 166, a Position Determination Entity (PDE), a Serving Mobile Location Center (SMLC), a 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 location information. The LMF 166 receives measurements and assistance information from the NG-RAN and the UE 104 via the AMF 161 to calculate the location of the UE 104. The NG-RAN may utilize one or more locationing methods to determine the location of the UE 104. Locating the UE 104 may involve signal measurements, location estimation, and optional speed calculation based on these measurements. The signal measurements may be performed by the UE 104 and / or the serving base station 102. The measured signals may be based on a Satellite Positioning System (SPS) 170 (e.g., a Global Navigation Satellite System (GNSS), Global Positioning System (GPS), Non-Terrestrial Network (NTN), or one or more of 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), an NR Enhanced Cell ID (NR E-CID) method, NR signals (e.g., multi-round-trip time (multi-RTT), DL Angle of Departure (DL-AoD), DL Time Difference of Arrival (DL-TDOA), UL Time Difference of Arrival (UL-TDOA), and UL Angle of Arrival (UL-AoA) locationing), and / or one or more of other systems / signals / sensors.

[0051] Examples of the UE 104 include cellular phones, smart phones, Session Initiation Protocol (SIP) phones, laptop computers, personal digital assistants (PDAs), satellite radios, global positioning systems, multimedia devices, video devices, digital audio players (e.g., MP3 players), cameras, game consoles, tablet devices, smart devices, wearable devices, vehicles, electric meters, gas pumps, large or small kitchen appliances, healthcare devices, implants, sensors / actuators, displays, or any other device with similar functionality. Some of the UEs in the UE 104 may be referred to as IoT devices (e.g., parking meters, gas pumps, toasters, vehicles, heart monitors, etc.). The UE 104 may also be referred to as a station, mobile station, subscriber station, mobile unit, subscriber unit, wireless unit, remote unit, mobile device, wireless device, wireless communication device, remote device, mobile subscriber station, access terminal, mobile terminal, wireless terminal, remote terminal, cell phone, user agent, mobile client, client, or some other suitable term. In some scenarios, the term UE may also be applied to one or more companion devices, such as in a device constellation arrangement. One or more of these devices may access the network jointly and / or separately access the network.

[0052] Refer again to Figure 1 , in some aspects, the core network 120 and / or the base station 102 may be configured to obtain at least one measurement of a satellite associated with a set of RSUs; estimate the positioning of the satellite based on the at least one measurement and the location of the set of RSUs; and identify whether the estimated positioning of the satellite is associated with an error based on a comparison of the estimated positioning of the satellite with the ALM data or EPH data of the satellite (e.g., via the SV broadcast data monitoring component 199).

[0053] In some aspects, the UE 104 and / or the RSU 604 / 706 may be configured to perform at least one of the following: measure the PR between the RSU and the satellite, estimate the positioning of the satellite based on the EPH data or ALM data of the satellite, or estimate the clock offset associated with the satellite based on the EPH data or ALM data of the satellite; send at least one of the measurement of the PR, the estimate of the positioning of the satellite, or the estimate of the clock offset of the satellite to a network entity; and receive information associated with the satellite from the network entity based on the measurement of the PR, the estimate of the positioning of the satellite, or the estimate of the clock offset (e.g., via the SV measurement component 198).

[0054] Figure 2A FIG. 200 is a diagram illustrating an example of a first subframe within the 5G NR frame structure. Figure 2B FIG. 230 is a diagram illustrating an example of a DL channel within a 5G NR subframe. Figure 2CFIG. 250 is an illustration of an example of a second subframe within a 5G NR frame structure. Figure 2D FIG. 280 is an illustration of an example of a UL channel within a 5G NR subframe. The 5G NR frame structure can be Frequency Division Duplexing (FDD) (wherein for a particular set of subcarriers (carrier system bandwidth), the subframes within that set of subcarriers are dedicated to DL or UL), or can be Time Division Duplexing (TDD) (wherein for a particular set of subcarriers (carrier system bandwidth), the subframes within that set of subcarriers are dedicated to both DL and UL). In Figure 2A 、 Figure 2C the example provided, the 5G NR frame structure is assumed to be TDD, where subframe 4 is configured with slot format 28 (where most are DL), where D is DL, U is UL, and F is flexibly usable between DL / UL, and subframe 3 is configured with slot format 1 (where all are UL). Although subframes 3, 4 are shown as having slot formats 1, 28 respectively, any particular subframe can be configured with any one of the various available slot formats 0 - 61. Slot formats 0, 1 are all DL, UL respectively. The other slot formats 2 - 61 include a mixture of DL, UL, and flexible symbols. The slot format is configured for the UE via the received Slot Format Indicator (SFI) (configured dynamically via Downlink 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.

[0055] Figures 2A to 2D The frame structure is illustrated, and aspects of the present disclosure are applicable to other wireless communication technologies that may have different frame structures and / or different channels. One frame (10 ms) can be divided into 10 equal - sized subframes (1 ms). Each subframe can include one or more slots. A subframe can also include mini - slots, which can include 7, 4, or 2 symbols. Each slot can include 14 or 12 symbols, depending on whether the Cyclic Prefix (CP) is normal or extended. For normal CP, each slot can include 14 symbols, and for extended CP, each slot can include 12 symbols. The symbols on DL can be Cyclic Prefix Orthogonal Frequency Division Multiplexing (CP - OFDM) symbols. The symbols on UL can be CP - OFDM symbols (for high - throughput scenarios) or Discrete Fourier Transform (DFT) - spread OFDM (DFT - s - OFDM) symbols (also known as Single - Carrier Frequency Division Multiple Access (SC - FDMA) symbols) (for power - limited scenarios; limited to single - stream transmission). The number of slots within a subframe is based on CP and the parameter set. The parameter set defines the Subcarrier Spacing (SCS) (see Table 1). The symbol length / duration can be scaled with 1 / SCS.

[0056]

[0057] Table 1: Parameter Sets, SCS, and CP

[0058] For normal CP (14 symbols / slot), different parameter sets μ0 to 4 allow 1, 2, 4, 8, and 16 slots per subframe, respectively. For extended CP, parameter set 2 allows 4 slots per subframe. Thus, for normal CP and parameter set μ, there are 14 symbols / slot and 2 μ slots / subframe. The subcarrier spacing can be equal to 2μ * 15 kHz, where μ is parameter set 0 to 4. Thus, the subcarrier spacing for parameter set μ = 0 is 15 kHz, and the subcarrier spacing for parameter set μ = 4 is 240 kHz. The symbol length / duration is inversely related to the subcarrier spacing. Figures 2A to 2D An example of normal CP with 14 symbols per slot and parameter set μ = 2 with 4 slots per subframe is provided. 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) with frequency division multiplexing (see Figure 2B ). Each BWP can have a specific parameter set and CP (normal or extended).

[0059] A resource grid can be used to represent the frame structure. Each slot includes a resource block (RB) (also referred to 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.

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

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

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

[0063] Figure 2DIllustrates examples of various UL channels within a subframe of a frame. The PUCCH can be located at the position indicated in one configuration. The PUCCH carries uplink control information (UCI), such as a scheduling request, a channel quality indicator (CQI), a precoding matrix indicator (PMI), a rank indicator (RI), and a 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 can additionally be used to carry a buffer status report (BSR), a power headroom report (PHR), and / or UCI.

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

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

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

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

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

[0069] The TX processor 368 may use channel estimates derived from reference signals or feedback transmitted by the base station 310 by the channel estimator 358 to select an appropriate decoding and modulation scheme and to facilitate spatial processing. The spatial streams generated by the TX processor 368 may be provided to different antennas 352 via a separate transmitter 354Tx. Each transmitter 354Tx may modulate an RF carrier with a corresponding spatial stream for transmission.

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

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

[0072] At least one of TX processor 368, RX processor 356, and controller / processor 359 may be configured to perform aspects associated with Figure 1 SV measurement component 198.

[0073] At least one of TX processor 316, RX processor 370, and controller / processor 375 may be configured to perform aspects in conjunction with Figure 1 SV broadcast data monitoring component 199.

[0074] Figure 4 FIG. 400 is an illustration of an example of UE positioning based on reference signal measurements (which may also be referred to as “network-based positioning”) in accordance with various aspects of the present disclosure. UE 404 may transmit UL-SRS 412 at time T SRS_TX and receive a downlink positioning reference signal (PRS) (DL-PRS) 410 at time T PRS_RX . TRP 406 may receive UL-SRS 412 at time T SRS_RX and transmit DL-PRS 410 at time T PRS_TX . UE 404 may receive DL-PRS 410 before transmitting UL-SRS 412, or may transmit UL-SRS 412 before receiving DL-PRS 410. In either case, a positioning server (e.g., location server 168) or UE 404 may determine RTT 414 based on ||T SRS_RX - T PRS_TX | - |T SRS_TX - T PRS_RX ||. Thus, multi-RTT positioning may utilize UE Rx-Tx time difference measurements of downlink signals received from multiple TRPs 402, 406 and measured by UE 404 (i.e., |T SRS_TX - T PRS_RX |) and DL-PRS reference signal received power (RSRP) (DL-PRS-RSRP), as well as measured TRP Rx-Tx time difference measurements of uplink signals transmitted from UE 404 at multiple TRPs 402, 406 (i.e., |T SRS_RX - T PRS_TX|) and UL-SRS-RSRP. The UE 404 uses the assistance data received from the positioning server to measure the UE Rx-Tx time difference measurement (and / or the DL-PRS-RSRP of the received signal), and the TRP 402, 406 use the assistance data received from the positioning server to measure the gNB Rx-Tx time difference measurement (and / or the UL-SRS-RSRP of the received signal). These measurements can be used at the positioning server or the UE 404 to determine the RTT, which is used to estimate the location of the UE 404. Other methods for determining the RTT are possible, such as using DL-TDOA and / or UL-TDOA measurements.

[0075] PRS can be defined for network-based positioning (e.g., NR positioning) such that the UE can detect and measure more adjacent transmit and receive points (TRP), where multiple configurations are supported to enable various deployments (e.g., indoor, outdoor, sub-6, mmW, etc.). To support PRS beam operation, beam scanning can also be configured for PRS. The UL positioning reference signal can be based on the sounding reference signal (SRS) with enhancements / modifications for positioning purposes. In some examples, UL-PRS can be referred to as "SRS for positioning", and new information elements (IE) can be configured for SRS for positioning in RRC signaling.

[0076] The DL PRS-RSRP can be defined as the linear average of the power contributions (in [W]) of the resource elements of the antenna port carrying the DL PRS reference signal configured for RSRP measurement within the considered measurement frequency bandwidth. In some examples, for FR1, the reference point of the DL PRS-RSRP can be the antenna connector of the UE. For FR2, the DL PRS-RSRP can be measured based on the combined signal from the antenna elements corresponding to a given receiver branch. For FR1 and FR2, if the UE uses receiver diversity, the reported DL PRS-RSRP value may not be lower than the corresponding DL PRS-RSRP of any individual receiver branch in the individual receiver branches. Similarly, the UL SRS-RSRP can be defined as the linear average of the power contributions (in [W]) of the resource elements carrying the sounding reference signal (SRS). The UL SRS-RSRP can be measured within the considered measurement frequency bandwidth, in the configured measurement occasion, by the configured resource elements. In some examples, for FR1, the reference point of the UL SRS-RSRP can be the antenna connector of the base station (e.g., gNB). For FR2, the UL SRS-RSRP can be measured based on the combined signal from the antenna elements corresponding to a given receiver branch. For FR1 and FR2, if the base station uses receiver diversity, the reported UL SRS-RSRP value may not be lower than the corresponding UL SRS-RSRP of any individual receiver branch in the individual receiver branches.

[0077] The PRS-path RSRP (PRS-RSRPP) can be defined as the power of the linear average of the channel response at the i-th path delay of the resource elements carrying the DL PRS signal configured for measurement, where the DL PRS-RSRPP of the first path delay is the power contribution corresponding to the path first detected in time. In some examples, the PRS path phase measurement can refer to the phase associated with the i-th path of the channel derived using the PRS resources.

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

[0079] DL-TDOA positioning can utilize the downlink reference signal time difference (RSTD) (and / or DL-PRS-RSRP) of the downlink signals received at the UE 404 from multiple TRPs 402, 406. The UE 404 uses the assistance data received from the positioning server to measure the DL RSTD (and / or DL-PRS-RSRP) of the received signals, and the resulting measurements, together with other configuration information, are used to position the UE 404 relative to the neighboring TRPs 402, 406.

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

[0081] UL-AoA positioning can utilize the measured azimuth of arrival (A-AoA) and zenith angle of arrival (Z-AoA) of the uplink signals transmitted from the UE 404 at multiple TRPs 402, 406. The TRPs 402, 406 use the assistance data received from the positioning server to measure the A-AoA and Z-AoA of the received signals, and the resulting measurements, together with other configuration information, are used to estimate the location of the UE 404. For the purposes of this disclosure, a positioning operation in which the UE provides measurements to a base station / location entity / server for use in calculating the UE location may be described as "UE-assisted", "UE-assisted positioning", and / or "UE-assisted location calculation", while a positioning operation in which the UE measures and calculates its own location may be described as "UE-based", "UE-based positioning", and / or "UE-based location calculation".

[0082] Additional positioning methods can be used to estimate the location of UE 404, such as, for example, UE-side UL-AoD and / or DL-AoA. It should be noted that data / measurements from various techniques can be combined in various ways to increase accuracy, determine and / or enhance certainty, supplement / complete measurements, and / or replace / provide missing information. For example, some UE positioning mechanisms can be radio access technology (RAT)-dependent (e.g., the positioning of the UE is RAT-based), such as downlink positioning (e.g., measurements of observed time difference of arrival (OTDOA)), uplink positioning (e.g., measurements of uplink time difference of arrival (UTDOA)), and / or combined positioning based on DL and UL (e.g., measurements of RTT with respect to neighboring cells), etc. Some wireless communication systems may also support enhanced cell ID (E-CID) positioning procedures based on radio resource management (RRM) measurements. On the other hand, some UE positioning mechanisms can be RAT-independent (e.g., the positioning of the UE does not depend on RAT), such as enhanced GNSS, and / or positioning techniques based on WLAN, Bluetooth, terrestrial beacon system (TBS), and / or positioning techniques based on sensors (e.g., barometric pressure sensors, motion sensors), etc. Some UE positioning mechanisms can be based on a hybrid model, where multiple positioning methods are used, which may include both RAT-dependent positioning techniques and RAT-independent positioning techniques (e.g., GNSS-OTDOA hybrid positioning).

[0083] Note that the terms "positioning reference signal" and "PRS" generally refer to specific reference signals used for positioning in NR and LTE systems. However, as used herein, the terms "positioning reference signal" and "PRS" may also refer to any type of reference signal that can be used for positioning, such as, but not limited to: PRS, TRS, PTRS, CRS, CSI-RS, DMRS, PSS, SSS, SSB, SRS, UL-PRS, etc., as defined in LTE and NR. In addition, the terms "positioning reference signal" and "PRS" may refer to downlink or uplink positioning reference signals, unless otherwise indicated by the context. To further distinguish the types of PRS, downlink positioning reference signals may be referred to as "DL PRS", and uplink positioning reference signals (e.g., SRS, PTRS used for positioning) may be referred to as "UL-PRS". In addition, for signals that can be transmitted in both uplink and downlink (e.g., DMRS, PTRS), these signals may be prefixed with "UL" or "DL" to distinguish the direction. For example, "UL-DMRS" can be distinguished from "DL-DMRS".

[0084] Devices (e.g., UEs) equipped with a Global Navigation Satellite System (GNSS) receiver (which may include a Global Positioning System (GPS) receiver) can determine their location based on GNSS positioning. GNSS is a satellite network that broadcasts timing and orbital information for navigation and positioning measurements. GNSS can include multiple groups of satellites called constellations, and the multiple groups of satellites broadcast signals (which may be referred to as GNSS signals) to the control stations and users of GNSS. Based on the broadcast signals, users may be able to determine their location (e.g., via a trilateration process). For the purposes of this disclosure, a device (e.g., UE) equipped with a GNSS receiver or capable of receiving GNSS signals may be referred to as a GNSS device, and a device capable of transmitting GNSS signals (such as a satellite) may be referred to as a Space Vehicle (SV).

[0085] Figure 5 FIG. 500 is a diagram illustrating an example of GNSS positioning in accordance with various aspects of the present disclosure. A GNSS device 506 can estimate its position and time based at least in part on data received from multiple Space Vehicles (SVs) 502 (e.g., GNSS signals 504), where each SV 502 can carry a record of its position and time and can send that data (e.g., the record) to the GNSS device 506. Each SV 502 may also include a clock that is synchronized with other clocks of the SV and with a ground clock. If the SV 502 detects a deviation from the time maintained on the ground, the SV 502 can correct it. The GNSS device 506 may also include a clock, but the clock of the GNSS device 506 may be less stable and accurate compared to the clocks of each SV 502.

[0086] Since the speed of radio waves can be constant and independent of the satellite speed, the time delay between the time when the SV 502 transmits the GNSS signal 504 and the time when the GNSS device 506 receives the GNSS signal 504 can be proportional to the distance from the SV 502 to the GNSS device 506. In some examples, the GNSS device 506 can use at least four SVs to calculate / estimate one or more unknowns associated with the position (e.g., three position coordinates and a clock deviation from satellite time, etc.).

[0087] Each SV 502 can continuously broadcast GNSS signals 504 (e.g., with a modulated carrier), which can include a pseudorandom code (e.g., a sequence of ones and zeros) known to the GNSS device 506, and can also include a message that includes the transmission time and the SV's location at that time. In other words, each GNSS signal 504 can carry two types of information: time and a carrier (e.g., a modulated waveform of an input signal to be transmitted electromagnetically). Based on the GNSS signals 504 received from each SV 502, the GNSS device 506 can measure the time of arrival (TOA) of the GNSS signal 504 and calculate the time of flight (TOF) of the GNSS signal 504. Then, based on the TOF, the GNSS device 506 can calculate its three-dimensional location and clock bias, and the GNSS device 506 can determine its location on the earth. For example, the location of the GNSS device 506 can be converted into latitude, longitude, and altitude relative to an ellipsoidal earth model. These coordinates can be displayed on, for example, a mobile map display, or recorded or used by some other system (such as a vehicle guidance system).

[0088] Although the distance between the GNSS device and the SV can be estimated based on the time it takes for the GNSS signal to reach the GNSS device, the signal sequence of the SV can be delayed relative to the sequence of the GNSS device. Thus, in some examples, a delay can be applied to the sequence of the GNSS device so that the two sequences are aligned. For example, to estimate the delay, the GNSS device can align the pseudorandom binary sequence included in the SV signal with an internally generated pseudorandom binary sequence. Since the GNSS signal of the SV takes time to reach the GNSS device, the sequence of the SV can be delayed relative to the sequence of the GNSS device. By gradually delaying the sequence of the GNSS device, the two sequences can eventually be aligned. The accuracy of GNSS-based positioning can depend on various factors, such as satellite geometry, signal blockage, atmospheric conditions, and / or receiver design features / quality, etc. For example, GNSS receivers used by smartphones or smartwatches can have lower accuracy compared to GNSS receivers used by vehicles and exploration equipment.

[0089] It may be important for some applications to be able to continuously receive GNSS signals or GNSS SV broadcast data without interruption. For example, vehicle-to-everything (V2X) and cellular V2X (C-V2X) applications are associated with communications between vehicles and any entity that may affect or be affected by a vehicle and / or is associated with an autonomous vehicle (which may also be referred to as a self-driving vehicle, driverless vehicle, and / or robotic vehicle), where one purpose / motivation of V2X / C-V2X applications is to improve road safety, traffic efficiency, energy conservation, and large-scale monitoring, etc. Thus, real-time GNSS satellite broadcast data may be important for ensuring the continuity and / or availability of positioning / time information for V2X / C-V2X applications.

[0090] In some scenarios, the data broadcast from GNSS SVs may contain errors (hereinafter referred to as "satellite errors" or "broadcast data errors"), which may affect the positioning accuracy of GNSS devices. For the purposes of this disclosure, errors associated with an SV (such as broadcast data errors) may refer to the reasons that result in a loss of accuracy in the calculation of the positioning of a GNSS device. This may include errors that affect the time signal broadcast from the SV and errors that affect the estimated positioning of the SV in space. For example, satellite errors or broadcast data errors may include satellite clock errors, ephemeris errors (e.g., each SV may broadcast ephemeris data describing its orbit), errors associated with hardware components, atmospheric errors, and / or multipath errors, etc.

[0091] Satellite errors and / or broadcast data errors can be detected via various error detection mechanisms (e.g., by a GNSS device or a positioning entity). For example, a GNSS SV can be configured to provide its ephemeris, almanac, and / or health status information, and a GNSS device or a positioning entity can decode this information via over-the-air (OTA) transmission and determine whether there are errors associated with the SV. The ephemeris information of the SV can be used to calculate the positioning of the SV in its orbit, and the almanac information can be used to determine the availability and status of the satellite constellation (e.g., the entire satellite constellation), etc. For example, both the GNSS almanac and ephemeris can form a navigation message sent by the satellite. The ephemeris may contain information about the week number, satellite accuracy and health status, data age, satellite clock correction factor, orbital parameters, etc. In some examples, the ephemeris may be valid for two hours before and two hours after the ephemeris reference time (toe). The toe can be understood as the time when the data is calculated and generated from the GNSS control segment. The ephemeris data can be used for real-time satellite coordinate calculation. On the other hand, the almanac may contain orbital information with lower accuracy than the ephemeris data. In some examples, the almanac can be valid for a period of up to ninety (90) days.

[0092] However, since GNSS SVs can be configured to update their ephemeris data, almanac, and / or health status information periodically (e.g., every X hours), their actual / current status may not be reflected for several hours.

[0093] In another example, a GNSS device or positioning entity may use integrity information of a satellite-based augmentation system (SBAS) to identify whether there are errors associated with an SV. SBAS is a highly accurate and reliable navigation satellite system capable of enhancing the GNSS system. For example, current GNSS systems can provide a positioning accuracy of 5 to 15 meters to users. However, SBAS and precise point positioning (PPP) systems can provide integrity and correction information to users to improve positioning accuracy (e.g., to meter-level and / or decimeter-level (e.g., 10 to 15 cm) accuracy). However, this integrity and correction information may be limited to GPS / GNSS SVs. Additionally, in challenging or dense urban environments, decoding of SBAS-based integrity and correction information may not be available.

[0094] In another example, a GNSS device or positioning entity may determine whether there are errors associated with an SV based on receiver autonomous integrity monitoring (RAIM). RAIM is a technology developed to evaluate the integrity of GPS signals in a GPS receiver system. For example, since GPS SVs may not include any internal information about the integrity of their signals, a GPS SV may broadcast incorrect information, resulting in incorrect navigation information, and the GPS device may not be aware of such incorrect information. RAIM uses redundant signals to generate several GPS positioning bearings and compares them, and statistical functions determine whether a fault is associated with any of the signals. However, using RAIM for error detection may specify greater computational complexity and combinatorial problems may occur. For example, if an SV is not available for the positioning of a GNSS device but is broadcasting incorrect information / data, RAIM may not be helpful.

[0095] In other examples, a GNSS device or positioning entity may determine whether there are errors associated with an SV based on integrity information provided by another entity. However, the GNSS device of the positioning entity may be designated to request an integrity file from another entity, and the download resolution of the integrity file can be 4h, 6h, 12h, and / or 24h, etc.

[0096] In this way, real-time (or near real-time) monitoring of SV broadcast data that can identify one or more errors associated with the information / data broadcast from the SVs can be of great benefit in preventing GNSS outages. A GNSS outage may refer to a situation where a GNSS device is unable to receive GNSS signals / information from one or more SVs, or is unable to perform positioning based on the received GNSS signals / information (e.g., due to errors or issues with the SV health status, etc.). Such real-time (or near real-time) monitoring of SV broadcast data can also be beneficial for applications that require continuous reception of GNSS signals and broadcast data without interruption, such as V2X / C-V2X applications.

[0097] Aspects presented herein can enable a GNSS device (e.g., a UE, a GNSS receiver, etc.) or a positioning entity (e.g., a location server, an LMF, a network node, a base station, etc.) to determine whether there are any errors in the data broadcast from one or more SVs, to ensure the continuity and availability of accurate positioning and / or time information received by the GNSS device or the positioning entity, which may be suitable for V2X / C-V2X applications. For example, in one aspect of the present disclosure, a network (e.g., a set) of roadside units (RSUs) can be used to estimate the positioning and / or clock offset of the SVs. The clock offset may refer to the difference between two clocks at any given moment, and the rate of clock drift may be referred to as clock drift. In some scenarios, the clock of a satellite may include a clock offset (which may also be referred to as a clock error), which may be caused by the satellite oscillator not being synchronized with GPS time, and it is one of the main errors that can affect positioning accuracy. Since the location of the RSU is usually known (e.g., the RSU can be similar to a beacon with a known location and clock), the distance between a particular SV and the RSU network can be measured and used to estimate the positioning of the SV. Then, the estimated positioning of the SV can be compared with the ephemeris information and / or almanac information broadcast from the SV (or received from another entity) to determine whether there are any errors associated with the SV. If it is determined that the SV has broadcast incorrect information, the SV can be isolated / excluded from the positioning. This process can be repeated for multiple SVs (e.g., all SVs participating in a positioning session), thereby improving the positioning accuracy of the GNSS device. A positioning session (or a UE positioning session) may refer to the occasion / instance in which the positioning of the UE is to be determined, such as based on one of the positioning mechanisms described in conjunction with Figure 4 one of the described positioning mechanisms.

[0098] For the purposes of this disclosure, an RSU may refer to a transceiver (e.g., a dedicated short-range communication (DSRC) transceiver) placed along a road or pedestrian path. An RSU may also include a GNSS receiver capable of receiving GNSS signals transmitted / broadcast from one or more SVs. In some examples, an RSU may also be placed on a vehicle or be handheld, but it may operate when the vehicle or handheld unit (e.g., a UE) is stationary. An RSU may broadcast data to a vehicle's on-board unit (OBU) and / or exchange data with an OBU within its communication area (e.g., within its transmission range). An RSU may also be configured to provide channel assignments (e.g., resource allocations) and operation instructions to OBUs within its communication area.

[0099] Figure 6 FIG. 600 is a diagram illustrating an example of using an RSU network to estimate the positioning and clock offset of an SV in accordance with various aspects of the present disclosure. In one example, the RSU network may include a first RSU 604 (RSU 1), a second RSU 606 (RSU 2), a third RSU 608 up to an Nth RSU 610 (RSU N), etc., where the positions of the RSU network may be known.

[0100] As shown at 612, each RSU in the RSU network may receive GNSS signals, ephemeris (EPH) information, and / or almanac (ALM) information (collectively referred to as EPH / ALM information or EPH / ALM data) transmitted from a first SV 602 (e.g., a GNSS SV). Based on the received GNSS signals, each RSU may calculate an estimate of its distance (e.g., PR) from the first SV 602, such as in conjunction with Figure 5 described. For example, the pseudorange (PR) (e.g., PR1) between the first RSU 604 and the first SV 602 may be calculated based on the following formula:

[0101]

[0102] where X, Y, Z RSU1 may indicate the Earth-centered, Earth-fixed (ECEF) positioning of the first RSU 604 (e.g., obtained based on the known position of the first RSU 604), X, Y, Z SV1 may indicate the ECEF positioning of the first SV 602 (e.g., derived based on the EPH / ALM information), and CB SVV may indicate the clock offset associated with the first SV 602 (the clock bias at the first RSU 604 may be fully compensated). PR may refer to the pseudorange between the SV and the GNSS receiver. For a GNSS receiver whose positioning is to be determined, as in conjunction with Figure 5As described, the GNSS receiver can determine its distances to four SVs and their positions at the time of transmission. Given the orbital parameters of the SVs, these positions can be estimated for any point in time. The PR for each SV can be obtained by multiplying the speed of light by the time it takes for the signal to travel from the SV to the GNSS receiver. Since there may be accuracy errors in the measurement time, the term "PR" is used to represent such distances. Similarly, the PR (e.g., PR2) between the second RSU 606 and the first SV 602 can be calculated based on the following formula:

[0103]

[0104] where X, Y, Z RSU can indicate the ECEF position of the second RSU 606 (e.g., obtained based on the known position of the second RSU 606), and the PR (e.g., PR N ) between the Nth RSU 610 and the first SV 602 can be calculated based on the following formula:

[0105]

[0106] where X, Y, Z RSUN can indicate the ECEF position of the Nth RSU 610 (e.g., obtained based on the known position of the Nth RSU 610), etc. This process can be repeated for multiple SVs, such as up to the Kth SV.

[0107] Based on the PR calculated / estimated at each RSU, the position of the first SV 602 can be determined. For example, the position of the first SV 602 can be determined based on a trilateration process using known distances from at least three points with known positions (e.g., using the PR calculated by at least four RSUs with their known positions). Therefore, at least four RSUs can be specified to determine the position of the first SV602. Additionally, if the RSU network is distributed over a wide geographical area and / or from multiple directions, the accuracy of the SV position estimation can also be improved.

[0108] In another aspect of the present disclosure, a network entity such as a cloud server can be configured to control and / or coordinate the RSU network (e.g., the first RSU 604, the second RSU 606,..., up to the Nth RSU 610, etc.), and the network entity can collect / sample data and measurements from the RSU network (this process can also be referred to as performing crowdsourcing on data and measurements from the RSU network). For example, the network entity can obtain at least one of the following from the RSU network: the ECEF position of the RSU (e.g., X RSU , Y RSU , Z RSU), the estimated PR of the RSU relative to one or more SVs (e.g., SV 602), the SV positioning and clock offset calculated from the EPH data associated with the SV (e.g., (X SV , Y SV , z SV )) EPH and ), and / or the SV positioning and clock offset calculated from the ALM data associated with the SV (e.g., (X SV , Y SV , Z SV )) ALM 、 ). Note that for some SVs, the EPH data and / or ALM data may not be available, or may be received from another entity other than the SV itself (e.g., the SV may not have the ability to broadcast this data).

[0109] After the network entity collects these data and measurements from the RSU network, the network entity can process these data and measurements, and use these sampled data and measurements from different RSUs to estimate the positioning and clock offset of one or more SVs (e.g., estimated at a cloud server). Then, based on the data and measurements collected / sampled from each RSU, the network entity can be configured to find the difference between the SV positioning estimated by the network entity / cloud server and the SV positioning calculated by each RSU (e.g., based on the broadcast data / information of the SV, such as EPH / ALM information). In one example, since the network entity may know the positioning of the RSU, the network entity can also select RSUs based on the location of the RSU to determine the positioning of the SV. For example, if the RSUs used to estimate the positioning of the SV are distributed over a wide geographical area and / or from multiple directions, the accuracy of the SV positioning estimate can be improved, so the network entity can select RSUs that are at least a certain distance apart from each other, and / or RSUs from different directions / regions, etc.

[0110] The network entity can perform statistical analysis on the SV positioning calculated by the network entity and the RSU network, and the network entity can determine outliers and / or valid user equivalent range errors (UERE) (e.g., ranging errors between the SV and the RSU) for modeling broadcast data errors. Then, the network entity can share this data and information (e.g., the determined broadcast data errors) with the RSU and / or one or more end users (e.g., a UE or GNSS device performing GNSS-based positioning). For V2X / C-V2X applications, the RSU can also transmit this data and information to a set of users (e.g., the OBU of a vehicle) via the V2X / C-V2X protocol. The network entity can periodically perform crowdsourcing on the data and information from the RSU network to provide real-time (or near real-time) broadcast data health status monitoring for the set of SVs. In another example, the network entity can also perform crowdsourcing on the data and information from the RSU network on demand, where the network entity can send / initiate one or more requests to the RSU network, requesting the RSU network to provide data and information associated with the set of SVs. In response, the RSU network can provide data and information associated with the set of SVs based on the one or more requests. This on-demand configuration can reduce power consumption and signaling overhead between the network entity and the RSU network.

[0111] In one example, based on the broadcast data health status monitoring, the network entity can associate / assign a scale factor (e.g., a scale from 1 to 10), a weight factor (e.g., a percentage), or a quality indication (e.g., good, bad, acceptable, etc.) to each SV or the SVs used in a positioning session. For example, an SV with accurate broadcast data can be given a higher scale factor, a higher weight factor, and / or a good quality indication, while an SV with inaccurate broadcast data can be given a lower scale factor, a lower weight factor, and / or a bad quality indication. Then, this weight / scale factor and / or quality indication can be used by one or more positioning entities during the positioning session.

[0112] For example, the network entity can transmit the scale factor, weight factor, and / or quality indication associated with the set of SVs to end users, such as a UE and GNSS receiver performing GNSS-based positioning. In response, these UEs / GNSS receivers can determine whether to use a particular SV for positioning and / or the weight to give to a particular SV for positioning. For example, if a UE / GNSS receiver receives an indication that a particular satellite has a low scale factor, a low weight, or a bad quality indication, the UE / GNSS receiver can exclude that SV from its positioning (or exclude / ignore the measurements obtained based on that SV).

[0113] Figure 7Communication flow 700 is an example that illustrates a network entity (e.g., a cloud server) according to various aspects of the present disclosure to provide GNSS broadcast data quality monitoring for a set of SVs based on crowdsourced data from an RSU network. The numbers associated with communication flow 700 do not specify a particular time order and are only used as a reference to communication flow 700.

[0114] In one example, a network entity 710 (e.g., a cloud server, a location server, a base station, or an RSU among multiple RSUs, etc.) may control or coordinate multiple RSUs to obtain measurements of one or more SVs (which may also be referred to as satellites). For example, the network entity 710 may select an RSU network 704 including a first RSU 706 up to an Nth RSU 708 to perform measurements on the SV 702. The measurements may include measuring the PR between the RSU and the SV 702, estimating the positioning of the SV 702, and / or estimating the clock offset associated with the SV 702, etc. (collectively referred to as "SV measurements"). In some examples, the location of the RSU network 704 may be known to the network entity 710. For example, the RSU network 704 may indicate the ECEF location of the RSUs to the network entity 710, or the network entity 710 may access a database including the location of the RSU network 704, etc. In other examples, the location of the RSU network 704 may not be known to the network entity 710, and the RSUs in the RSU network 704 may be configured to indicate their locations to the network entity 710 (e.g., upon request). For example, the RSU network 704 may indicate the ECEF locations of these RSUs to the network entity 710, or the network entity 710 may access a database including the location of the RSU network 704, etc.

[0115] In some examples, to improve the accuracy of SV positioning, the network entity 710 may also select the RSU network 704 based on the location of the RSUs, based on the distance between two RSUs, and / or based on the direction of the RSUs relative to one or more SVs, etc. In some examples, the SV 702 may be a GNSS satellite, a low Earth orbit (LEO) satellite, a medium Earth orbit (MEO) satellite, a geostationary (GEO) satellite, or a high-altitude pseudolite (HAPS).

[0116] At 720, each RSU in the RSU network 704 may receive and measure GNSS signals and / or EPH / ALM data (if available) sent from the SV 702. Then, at 722, each RSU may measure the PR between itself and the SV 702, and / or estimate the positioning of the SV 702 and / or the clock offset associated with the SV 702 based on the EPH / ALM data of the SV 702. For example, the first RSU 706 may calculate the PR between the first RSU 706 and the SV 702, the positioning and clock offset of the SV 702 calculated from the EPH data of the SV 702 (e.g., (X SV ,Y SV ,Z SV ) EPH and ), and / or the positioning and clock offset of the SV 702 calculated from the ALM data (e.g., (X SV ,Y SV ,Z SV ) ALM and ), such as described in conjunction with Figure 6 .

[0117] At 724, the RSU network 704 may send its SV measurements of the SV 702 (e.g., the corresponding PR, positioning, and / or clock offset of the SV 702) to the network entity 710. In some examples, the network entity 710 may be configured to collect / sample these SV measurements based on a crowdsourcing mechanism (e.g., based on receiving the SV measurements from the RSU network 704 as crowdsourcing information). Crowdsourcing may refer to obtaining information or data from a group of entities that submit their data to a server. If the network entity 710 does not have the location of the RSU network 704, the RSU network 704 may also provide the locations of the RSUs (e.g., their ECEF locations) to the network entity 710.

[0118] At 726, based on the received / collected SV measurements of the SV 702, the network entity 710 may estimate the positioning and / or clock offset of the SV 702 based on these SV measurements and also based on the location of the RSU network, such as described in conjunction with Figure 6 .

[0119] At 728, the network entity 710 may identify whether the estimated positioning / clock offset of the SV 702 is associated with an error based on a comparison of the estimated positioning / clock offset with the ALM / EPH data of the SV 702.

[0120] In one example, as shown at 730, the network entity 710 may assign a scaling factor (e.g., a number), a weighting factor (e.g., a percentage), or a quality indication to the SV 702 based on whether the SV 702 is associated with an error. For example, if the SV 702 is not associated with an error, a higher scaling factor, a higher weighting factor, and / or a good quality indication may be assigned to the SV, while if the SV 702 is associated with an error, a lower scaling factor, a lower weighting factor, and / or a poor quality indication may be assigned to the SV. Additionally, the scaling factor, the weighting factor, and / or the quality indication may also vary based on the magnitude of the identified error. For example, a larger error may have a lower scaling / weighting factor or quality indication compared to a minor error.

[0121] Based on whether the SV 702 is associated with an error, or based on the scaling factor, the weighting factor, and / or the quality indication associated with the SV 702, if the network entity 710 is a positioning entity (e.g., a location server, an LMF, etc.), the network entity 710 may determine whether to include the SV 702 for the positioning of one or more GNSS devices. For example, if the SV 702 is not associated with an error (e.g., it is providing / broadcasting accurate SV information), the network entity 710 may include the SV 702 in the positioning session of the UE. On the other hand, as shown at 732, if the network entity 710 identifies that the SV 702 is associated with an error (or an error exceeding an error threshold), the network entity 710 may exclude the SV 702 from the UE positioning session or give the SV a lower weight in the UE positioning session. For example, the network entity 710 may remove at least some of the ALM data or EPH data of the SV 702 from the positioning session of the UE.

[0122] In some examples, as shown at 734, the network entity 710 may indicate to one or more RSUs in the RSU network 704 and / or one or more UEs 712 (e.g., end users, devices performing GNSS-based positioning, etc.) whether the SV 702 is associated with an error (e.g., via an error indication). In other examples, the network entity 710 may indicate to one or more RSUs in the RSU network 704 and / or one or more UEs 712 the scaling factor, the weighting factor, and / or the quality indication it has assigned to the SV 702.

[0123] In another example, as shown at 736, network entity 710 may indicate to one or more RSUs in RSU network 704 an error indication associated with SV 702 (e.g., an indication of whether SV 702 is associated with an error), a scaling factor, a weighting factor, and / or a quality indication. Then, the RSUs in RSU network 704 may forward the error indication, scaling factor, weighting factor, and / or quality indication associated with SV 702 to UEs within their transmission range, such as one or more UEs 712.

[0124] At 738, based on the error indication, scaling factor, weighting factor, and / or quality indication associated with SV 702, one or more UEs 712 may determine whether to include / exclude SV 702 in their positioning, and / or whether to give more / less weight to that SV in their positioning, etc.

[0125] Thus, the aspects presented herein may enable a network entity to use a set of RSUs to monitor the broadcast data quality from SVs and detect whether an SV is providing inaccurate information (e.g., information containing errors).

[0126] Figure 8 is a flowchart 800 of a method of wireless communication. The method may be performed by a network entity (e.g., base station 102; LMF 166; RSUs 604, 606, 608, 610, 706, 708; network entities 710, 1060). The method may enable a network entity to determine whether there are any errors in broadcast data from one or more SVs based on crowdsourced information from a set of RSUs.

[0127] At 802, the network entity may obtain at least one measurement of a satellite associated with the set of RSUs, such as described in conjunction with Figure 7 For example, at 724, network entity 710 may obtain PR, positioning, and / or clock offset measurements associated with SV 702 from RSU network 704. The components for obtaining the at least one measurement of the satellite may be performed by, for example, Figure 10 the SV broadcast data monitoring component 199, network processor 1012, and / or network interface 1080 of network entity 1060 in

[0128] In one example, to obtain at least one measurement of a satellite associated with the set of RSUs, the network entity may receive at least one measurement of the satellite from the set of RSUs. In such an example, the at least one measurement of the satellite is received from the set of RSUs periodically or on demand (e.g., based on one or more requests initiated by the network entity).

[0129] In another example, the at least one measurement includes at least one of the following: the PR between each RSU in the set of RSUs and the satellite, the estimated positioning of the satellite calculated at each RSU in the set of RSUs based on satellite-based ALM data or EPH data, or the clock offset associated with the satellite calculated at each RSU in the set of RSUs based on satellite-based ALM data or EPH data.

[0130] In another example, the network entity may receive the location of each RSU in the set of RSUs from the set of RSUs. In some embodiments, the location of the set of RSUs may correspond to the ECEF location of the set of RSUs.

[0131] In another example, the network entity may select the set of RSUs for obtaining at least one measurement of the satellite based on the location of each RSU in the set of RSUs.

[0132] In another example, the set of RSUs includes at least four RSUs.

[0133] In another example, the network entity is a base station, a component of a base station, a location server, or an RSU within the set of RSUs.

[0134] In another example, the satellite is an SV, a GNSS satellite, a LEO satellite, a MEO satellite, a GEO satellite, or a HAPS.

[0135] At 804, the network entity may estimate the positioning of the satellite based on the at least one measurement and the location of the set of RSUs, such as in combination with Figure 7 as described. For example, at 726, the network entity 710 may estimate the positioning and / or clock offset of the SV 702 based on the PR, positioning, and / or clock offset measured by the RSU network 704 and the location of the RSUs. The components for estimating the positioning of the satellite may be performed by, for example, Figure 10 the SV broadcast data monitoring component 199, the network processor 1012, and / or the network interface 1080 of the network entity 1060 in

[0136] At 806, the network entity may identify whether the estimated positioning of the satellite is associated with an error based on a comparison of the estimated positioning of the satellite with the ALM data or EPH data of the satellite, such as in combination with Figure 7 as described. For example, at 728, the network entity 710 may identify whether the estimated positioning and / or clock offset of the SV 702 is associated with an error by comparing the estimated positioning of the SV 702 with the ALM / EPH data. The components for identifying whether the estimated positioning of the satellite is associated with an error may be performed by, for example, Figure 10executed by the SV broadcast data monitoring component 199, network processor 1012, and / or network interface 1080 of the network entity 1060 in

[0137] In one example, to identify whether the estimated satellite positioning is associated with an error, a network entity may estimate a clock offset associated with the satellite, where the error associated with the estimated satellite positioning may be further based on the estimated clock offset, such as in conjunction with Figure 7 described. For example, at 726, the network entity 710 may estimate the positioning and / or clock offset of the SV 702 based on the PR, positioning, and / or clock offset measured by the RSU network 704 and the location of the RSU. The estimation of the satellite's clock offset may be performed by, for example Figure 10 the SV broadcast data monitoring component 199, network processor 1012, and / or network interface 1080 of the network entity 1060 in

[0138] At 808, the network entity may include the satellite in the UE's positioning session in response to the estimated satellite positioning being associated with an error, where the satellite is included in the positioning session together with a scale factor, weight factor, or quality indication, and / or the network entity may exclude the satellite from the UE's positioning session in response to the estimated satellite positioning being associated with an error, such as in conjunction with Figure 7 described. For example, at 730, the network entity 710 may assign a scale factor, weight factor, or quality indication to the SV 702 based on whether the SV 702 is associated with an error, where such scale factor, weight factor, and / or quality indication may be used for UE positioning. At 732, if the SV 702 is associated with an error, the network entity 710 may exclude the SV from the UE positioning session or give the SV a smaller weight in the UE positioning session. The component for including the satellite in the UE's positioning session or the component for excluding the satellite from the UE's positioning session may be executed by, for example, the SV broadcast data monitoring component 199, network processor 1012, and / or network interface 1080 of the network entity 1060 in the figure.

[0139] At 812, the network entity may exclude the satellite from the UE's positioning session in response to the estimated satellite positioning being associated with an error, such as in conjunction with Figure 7 described. For example, at 732, if the SV 702 is associated with an error, the network entity 710 may exclude the SV from the UE positioning session or give the SV a smaller weight in the UE positioning session. The exclusion of the satellite from the UE's positioning session may be executed by, for example Figure 10 the SV broadcast data monitoring component 199, network processor 1012, and / or network interface 1080 of the network entity 1060 in

[0140] In one example, to exclude the satellite from the UE's positioning session, the network entity may remove at least some of the satellite's ALM data or EPH data from the UE's positioning session.

[0141] At 810, the network entity may send an indication of the error to at least one RSU in the set of RSUs or to at least one UE, such as described in conjunction with Figure 7 For example, at 734, the network entity 710 may send an error indication to one or more RSUs in the RSU network 704 and / or to one or more UEs 712. The sending of the indication may be performed by, for example, Figure 10 the SV broadcast data monitoring component 199, the network processor 1012, and / or the network interface 1080 of the network entity 1060 in

[0142] Figure 9 is a flowchart 900 of a method of wireless communication. The method may be performed by a network entity (e.g., base station 102; LMF 166; RSUs 604, 606, 608, 610, 706, 708; network entities 710, 1060). The method may enable the network entity to determine whether there are any errors in the broadcast data from one or more SVs based on crowdsourced information from a set of RSUs.

[0143] At 902, the network entity may obtain at least one measurement of a satellite associated with the set of RSUs, such as described in conjunction with Figure 7 For example, at 724, the network entity 710 may obtain PR, positioning, and / or clock offset measurements associated with the SV 702 from the RSU network 704. The component for obtaining the at least one measurement of the satellite may be performed by, for example, Figure 10 the SV broadcast data monitoring component 199, the network processor 1012, and / or the network interface 1080 of the network entity 1060 in

[0144] In one example, to obtain at least one measurement of a satellite associated with the set of RSUs, the network entity may receive at least one measurement of the satellite from the set of RSUs. In such an example, the at least one measurement of the satellite is received from the set of RSUs periodically or on demand.

[0145] In another example, the at least one measurement includes at least one of the following: the PR between each RSU in the set of RSUs and the satellite, the estimated positioning of the satellite calculated at each RSU in the set of RSUs based on satellite-based ALM data or EPH data, or the clock offset associated with the satellite calculated at each RSU in the set of RSUs based on satellite-based ALM data or EPH data.

[0146] In another example, a network entity may receive the locations of each RSU in an RSU set from the RSU set. In some embodiments, the location of the RSU set may correspond to the ECEF location of the RSU set.

[0147] In another example, a network entity may select the RSU set for obtaining at least one measurement of a satellite based on the locations of each RSU in the RSU set.

[0148] In another example, the RSU set includes at least four RSUs.

[0149] In another example, the network entity is a base station, a component of a base station, a location server, or an RSU within the RSU set.

[0150] In another example, the satellite is an SV, a GNSS satellite, a LEO satellite, a MEO satellite, a GEO satellite, or a HAPS.

[0151] At 904, the network entity may estimate the positioning of the satellite based on the at least one measurement and the location of the RSU set, such as in combination with Figure 7 as described. For example, at 726, the network entity 710 may estimate the positioning and / or clock offset of the SV 702 based on the PR, positioning, and / or clock offset measured by the RSU network 704 and the location of the RSU. The components for estimating the positioning of the satellite may be performed by, for example, Figure 10 the SV broadcast data monitoring component 199, the network processor 1012, and / or the network interface 1080 of the network entity 1060 in

[0152] At 906, the network entity may identify whether the estimated positioning of the satellite is associated with an error based on a comparison of the estimated positioning of the satellite with the ALM data or EPH data of the satellite, such as in combination with Figure 7 as described. For example, at 728, the network entity 710 may identify whether the estimated positioning and / or clock offset of the SV 702 is associated with an error by comparing the estimated positioning of the SV 702 with the ALM / EPH data. The components for identifying whether the estimated positioning of the satellite is associated with an error may be performed by, for example, Figure 10 the SV broadcast data monitoring component 199, the network processor 1012, and / or the network interface 1080 of the network entity 1060 in

[0153] In one example, to identify whether the estimated positioning of the satellite is associated with an error, the network entity may estimate the clock offset associated with the satellite, wherein the error associated with the estimated positioning of the satellite is further based on the estimated clock offset, such as in combination with Figure 7As described. For example, at 726, the network entity 710 may estimate the positioning and / or clock offset of the SV 702 based on the PR, positioning, and / or clock offset measured by the RSU network 704 and the position of the RSU. The estimation of the clock offset of the satellite may be performed by, for example Figure 10 the SV broadcast data monitoring component 199, the network processor 1012, and / or the network interface 1080 of the network entity 1060 in

[0154] In another example, the network entity may include a satellite in the positioning session of the UE in response to the estimated positioning of the satellite being associated with an error, where the satellite is included in the positioning session together with a scaling factor, a weighting factor, or a quality indication, and / or the network entity may exclude the satellite from the positioning session of the UE in response to the estimated positioning of the satellite being associated with an error, such as in conjunction with Figure 7 As described. For example, at 730, the network entity 710 may assign a scaling factor, a weighting factor, or a quality indication to the SV 702 based on whether the SV 702 is associated with an error, where such a scaling factor, weighting factor, and / or quality indication may be used for UE positioning. At 732, if the SV 702 is associated with an error, the network entity 710 may exclude the SV from the UE positioning session or give the SV a lower weight in the UE positioning session. The component for including a satellite in the UE or for excluding a satellite from the UE may be performed by, for example Figure 10 the SV broadcast data monitoring component 199, the network processor 1012, and / or the network interface 1080 of the network entity 1060 in

[0155] In another example, the network entity may exclude the satellite from the positioning session of the UE in response to the estimated positioning of the satellite being associated with an error, such as in conjunction with Figure 7 As described. For example, at 732, if the SV 702 is associated with an error, the network entity 710 may exclude the SV from the UE positioning session or give the SV a lower weight in the UE positioning session. The exclusion of the satellite from the positioning session of the UE may be performed by, for example Figure 10 the SV broadcast data monitoring component 199, the network processor 1012, and / or the network interface 1080 of the network entity 1060 in

[0156] In another example, in order to exclude the satellite from the positioning session of the UE, the network entity may remove at least some of the ALM data or EPH data of the satellite from the positioning session of the UE.

[0157] In another example, the network entity may send an indication of the error to at least one RSU in the set of RSUs or to at least one UE, such as in conjunction with Figure 7As described. For example, at 734, network entity 710 may send an error indication to one or more RSUs in RSU network 704 and / or to one or more UEs 712. The sending of the indication may be performed by, for example Figure 10 the SV broadcast data monitoring component 199, network processor 1012, and / or network interface 1080 of network entity 1060 in

[0158] Figure 10 FIG. 1000 is a diagram illustrating an example of a hardware implementation for network entity 1060. In one example, network entity 1060 may be within core network 120. Network entity 1060 may include network processor 1012. Network processor 1012 may include on-chip memory 1012'. In some aspects, network entity 1060 may also include additional memory module 1014. Network entity 1060 communicates with CU 1002 directly (e.g., backhaul link) or indirectly (e.g., through RIC) via network interface 1080. On-chip memory 1012' and additional memory module 1014 may each be considered a computer-readable medium / memory. Each computer-readable medium / memory may be non-transitory. Processor 1012 is responsible for general processing, including executing software stored on the computer-readable medium / memory. The software, when executed by the corresponding processor, causes the processor to perform the various functions described above. The computer-readable medium / memory may also be used to store data manipulated by the processor when executing the software.

[0159] As discussed above, the SV broadcast data monitoring component 199 is configured to obtain at least one measurement of a satellite associated with a set of RSUs. The SV broadcast data monitoring component 199 may also be configured to estimate the positioning of the satellite based on the at least one measurement and the location of the set of RSUs. The SV broadcast data monitoring component 199 may also be configured to identify whether the estimated positioning of the satellite is associated with an error based on a comparison of the estimated positioning of the satellite with the ALM data or EPH data of the satellite. The SV broadcast data monitoring component 199 may be within the processor 1012. The SV broadcast data monitoring component 199 may be one or more hardware components specifically configured to perform the stated process / algorithm, implemented by one or more processors configured to perform the stated process / algorithm, stored in a computer-readable medium for implementation by one or more processors, or some combination of the above. The network entity 1060 may include various components configured for various functions. In one configuration, the network entity 1060 includes means for obtaining at least one measurement of a satellite associated with a set of RSUs. The network entity 1060 may also include means for estimating the positioning of the satellite based on the at least one measurement and the location of the set of RSUs. The network entity 1060 may also include means for: identifying whether the estimated positioning of the satellite is associated with an error based on a comparison of the estimated positioning of the satellite with the ALM data or EPH data of the satellite.

[0160] In one configuration, the means for obtaining at least one measurement of a satellite associated with a set of RSUs includes: configuring the network entity 1060 to receive at least one measurement of the satellite from the set of RSUs. In such a configuration, the at least one measurement of the satellite is received from the set of RSUs periodically or on demand.

[0161] In another configuration, the at least one measurement includes at least one of the following: the PR between each RSU in the set of RSUs and the satellite, the estimated positioning of the satellite calculated at each RSU in the set of RSUs based on the satellite's ALM data or EPH data, or the clock offset associated with the satellite calculated at each RSU in the set of RSUs based on the satellite's ALM data or EPH data.

[0162] In another configuration, the network entity 1060 may also include means for receiving the location of each RSU in the set of RSUs from the set of RSUs, where the locations correspond to the ECEF locations of the set of RSUs.

[0163] In another configuration, the network entity 1060 may also include means for selecting the set of RSUs for obtaining at least one measurement of the satellite based on the location of each RSU in the set of RSUs.

[0164] In another configuration, the set of RSU includes at least four RSUs.

[0165] In another configuration, the network entity is a base station, a component of a base station, a location server, or an RSU within the set of RSUs.

[0166] In another configuration, the satellite is an SV, a GNSS satellite, a LEO satellite, a MEO satellite, a GEO satellite, or a HAPS.

[0167] In another configuration, network entity 1060 may further include components for estimating a clock offset associated with a satellite, wherein an error associated with the positioning of the estimated satellite is further based on the estimated clock offset.

[0168] In another configuration, network entity 1060 may further include components for: in response to the positioning of the estimated satellite being associated with an error, including the satellite in a positioning session of a UE, wherein the satellite is included in the positioning session together with a scaling factor, a weighting factor, or a quality indication.

[0169] In another configuration, network entity 1060 may further include components for: in response to the positioning of the estimated satellite being associated with an error, excluding the satellite from a positioning session of a UE.

[0170] In another configuration, the components for excluding the satellite from a positioning session of a UE include configuring network entity 1060 to remove at least some of the ALM data or EPH data of the satellite from the positioning session of the UE.

[0171] In another configuration, network entity 1060 may further include components for transmitting an indication of the error to at least one RSU in the set of RSUs or to at least one UE.

[0172] The component may be an SV broadcast data monitoring component 199 of network entity 1060 configured to perform the functions recited by the component.

[0173] Figure 11 It is a flowchart 1100 of a method of wireless communication. The method may be performed by an RSU (e.g., RSU 604, 606, 608, 610, 706, 708; device 1204). The method may enable the RSU to estimate the PR, positioning, and / or clock offset of one or more SVs (e.g., based on their EPH / ALM data), and report these measurements to a network entity to assist the network entity in monitoring the quality of broadcast data from one or more SVs.

[0174] At 1102, the RSU may perform at least one of the following: measurement of the PR between the RSU and the satellite, estimation of the satellite's positioning based on the satellite's EPH data or ALM data, or estimation of the clock offset associated with the satellite based on the satellite's EPH data or ALM data, such as in conjunction with Figure 7 as described. For example, at 722, the first RSU 706 may estimate the PR, positioning, and / or clock offset of the SV 702, which may be based on the EPH / ALM data of the SV 702. The components for measuring the PR and / or the components for estimating the satellite's positioning may be performed by, for example, Figure 12 the SV measurement component 198, the application processor 1206, the cellular baseband processor 1224, and / or the transceiver 1222 of the device 1204 in

[0175] At 1104, the RSU may send at least one of the measurement of the PR, the estimation of the satellite's positioning, or the estimation of the satellite's clock offset to a network entity, such as in conjunction with Figure 7 as described. For example, at 724, the first RSU 706 may send the estimated PR, positioning, and / or clock offset of the SV702 to the network entity 710. The components for sending the measurement or estimation may be performed by, for example, Figure 12 the SV measurement component 198, the application processor 1206, the cellular baseband processor 1224, and / or the transceiver 1222 of the device 1204 in

[0176] At 1106, the RSU may receive information associated with the satellite from the network entity based on the measurement of the PR, the estimation of the satellite's positioning, or the estimation of the clock offset, such as in conjunction with Figure 7 as described. For example, at 736, the first RSU 706 may receive information associated with the SV 702 from the network entity 710 based on the measurement of the PR, the estimation of the satellite's positioning, or the estimation of the clock offset. The components for receiving the information associated with the satellite may be performed by, for example, Figure 12 the SV measurement component 198, the application processor 1206, the cellular baseband processor 1224, and / or the transceiver 1222 of the device 1204 in

[0177] In one example, the information is an indication of the error, and the RSU may forward the indication of the error to at least one UE.

[0178] In another example, the RSU may send at least one of a scaling factor, a weighting factor, or a quality indication associated with the satellite to at least one UE, where at least one of the scaling factor, the weighting factor, or the quality indication is based on the received information.

[0179] In another example, the RSU may send the location of the RSU to a network entity. In some aspects, the location of the RSU may correspond to the ECEF location of the RSU. In some examples, the RSU may receive from the network entity a request to perform at least one of a measurement of the PR, an estimation of the positioning of the satellite, or an estimation of the clock offset of the satellite based on the sent location of the RSU.

[0180] In another example, the satellite is a SV, GNSS satellite, LEO satellite, MEO satellite, GEO satellite, or HAPS.

[0181] In another example, the network entity is a base station, a component of the base station, a location server, or a second RSU.

[0182] Figure 12FIG. 1200 is a diagram illustrating an example of a hardware implementation for apparatus 1204. Apparatus 1204 may be an RSU, a component of an RSU, or may implement RSU functionality. In some aspects, apparatus 1204 may include a cellular baseband processor 1224 (also referred to as a modem) coupled to one or more transceivers 1222 (e.g., cellular RF transceivers). The cellular baseband processor 1224 may include on-chip memory 1224'. In some aspects, apparatus 1204 may also include one or more subscriber identity module (SIM) cards 1220 and an application processor 1206 coupled to a secure digital (SD) card 1208 and a screen 1210. The application processor 1206 may include on-chip memory 1206'. In some aspects, apparatus 1204 may further include a Bluetooth module 1212, a WLAN module 1214, an SPS module 1216 (e.g., a GNSS module), one or more sensor modules 1218 (e.g., an atmospheric pressure sensor / altimeter; motion sensors such as an inertial measurement unit (IMU), a gyroscope, and / or an accelerometer; light detection and ranging (LIDAR), radio assisted detection and ranging (RADAR), sound navigation and ranging (SONAR), a magnetometer, audio, and / or other technologies for positioning), additional memory modules 1226, a power source 1230, and / or a camera 1232. The Bluetooth module 1212, the WLAN module 1214, and the SPS module 1216 may include on-chip transceivers (TRX) (or in some cases, only a receiver (RX)). The Bluetooth module 1212, the WLAN module 1214, and the SPS module 1216 may include their own dedicated antennas and / or communicate using antenna 1280. The cellular baseband processor 1224 communicates with UE 104 and / or with an RU associated with network entity 1202 via transceiver 1222 through one or more antennas 1280. The cellular baseband processor 1224 and the application processor 1206 may each separately include computer-readable media / memory 1224', 1206'. The additional memory modules 1226 may also be considered computer-readable media / memory. Each computer-readable media / memory 1224', 1206', 1226 may be non-transitory. The cellular baseband processor 1224 and the application processor 1206 are each responsible for general processing, including executing software stored on the computer-readable media / memory. The software, when executed by the cellular baseband processor 1224 / application processor 1206, causes the cellular baseband processor 1224 / application processor 1206 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 1224 / application processor 1206 when executing the software.The cellular baseband processor 1224 / application processor 1206 may be a component of the UE 350 and may include the 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 1204 may be a processor chip (modem and / or application) and include only the cellular baseband processor 1224 and / or the application processor 1206, and in another configuration, the device 1204 may be the entire UE (e.g., see. Figure 3 of 350) and include additional modules of the device 1204.

[0183] As discussed above, the SV measurement component 198 is configured to perform at least one of the following: measurement of the PR between the RSU and the satellite, estimation of the location of the satellite based on the satellite's EPH data or ALM data, or estimation of the clock offset associated with the satellite based on the satellite's EPH data or ALM data. The SV measurement component 198 may also be configured to send at least one of the measurement of the PR, the estimation of the location of the satellite, or the estimation of the satellite's clock offset to a network entity. The SV measurement component 198 may also be configured to receive information associated with the satellite from the network entity based on the measurement of the PR, the estimation of the location of the satellite, or the estimation of the clock offset. The SV measurement component 198 may be within the cellular baseband processor 1224, the application processor 1206, or both within the cellular baseband processor 1224 and the application processor 1206. The SV measurement component 198 may be one or more hardware components specifically configured to perform the process / algorithm, implemented by one or more processors configured to perform the process / algorithm, stored in a computer-readable medium for implementation by one or more processors, or some combination thereof. As shown, the device 1204 may include various components configured for various functions. In one configuration, the device 1204, and specifically the cellular baseband processor 1224 and / or the application processor 1206, includes components for performing at least one of the following: measurement of the PR between the RSU and the satellite, estimation of the location of the satellite based on the satellite's EPH data or ALM data, or estimation of the clock offset associated with the satellite based on the satellite's EPH data or ALM data. The device 1204 may also include components for sending at least one of the measurement of the PR, the estimation of the location of the satellite, or the estimation of the satellite's clock offset to a network entity. The device 1204 may also include components for receiving information associated with the satellite from the network entity based on the measurement of the PR, the estimation of the location of the satellite, or the estimation of the clock offset.

[0184] In one configuration, the information is an indication of an error, and the device 1204 may also include components for forwarding the indication of the error to at least one UE.

[0185] In another configuration, the apparatus 1204 may further include components for sending to at least one UE at least one of a scaling factor, a weighting factor, or a quality indication associated with a satellite, where at least one of the scaling factor, the weighting factor, or the quality indication is based on the received information.

[0186] In another configuration, the apparatus 1204 may further include components for sending the location of the RSU to a network entity. In such a configuration, the apparatus 1204 may further include components for: receiving from the network entity a request to perform at least one of a measurement of the PR, an estimation of the location of the satellite, or an estimation of the clock offset of the satellite based on the sent location of the RSU.

[0187] In another configuration, the satellite is a SV, a GNSS satellite, a LEO satellite, a MEO satellite, a GEO satellite, or a HAPS.

[0188] In another configuration, the network entity is a base station, a component of the base station, a location server, or a second RSU.

[0189] The component may be the SV measurement component 198 of the apparatus 1204 configured to perform the functions recited by the component. As described above, the apparatus 1204 may include a TX processor 368, an RX processor 356, and a 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.

[0190] It should be understood that the specific order or hierarchy of the blocks in the disclosed process / flowchart is illustrative of example methods. It should be understood that based on design preferences, the specific order or hierarchy of the blocks in the process / flowchart may be rearranged. Further, some blocks may be combined or omitted. The appended method claims present the elements of the various blocks in a sample order, but are not limited to the specific order or hierarchy given.

[0191] 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 readily apparent to those skilled in the art, and the general principles defined herein may be applied to other aspects. Thus, the claims are not limited to the aspects described herein, but are to be accorded the full scope consistent with the language of the claims, and the singular forms of elements are not intended to mean "one and only one" but "one or more" unless specifically stated otherwise. Terms such as "if," "when," and "while" do not denote a direct temporal relationship or reaction. That is, these phrases, such as "when...," do not mean an immediate action in response to or during the occurrence of an action, but simply imply that the action will occur if the condition is met, without requiring a specific or immediate time limitation for the occurrence of the action. The word "exemplary" is used herein to mean "serving as an example, instance, or illustration." Any aspect described herein as "exemplary" is not necessarily to be construed as preferred or having an advantage over other aspects. Unless specifically stated otherwise, 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 "any combination of A, B, C, or any of them," including any combination of A, B, and / or C, may include multiple A's, multiple B's, or multiple C's. 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 "any combination of A, B, C, or any of them" can be only A, only B, only C, A and B, A and C, B and C, or A and B and C, where any such combination may contain one or more members of A, B, or C. A set should be construed as a collection of elements, where the number of elements is one or more. Thus, for a set of X, X will include one or more elements. If a first device receives data from or transmits data to a second device, the data may be received / transmitted directly between the first device and the second device, or indirectly between the first device and the second device through a collection of devices. All structural and functional equivalents of elements of the various aspects described throughout this disclosure that are known or later will be known to those of ordinary skill in the art are expressly incorporated herein by reference and are covered by the claims. Additionally, nothing disclosed herein is intended to be dedicated to the public, whether or not such disclosure is explicitly recited in the claims. The words "module," "mechanism," "element," "device," etc. do not substitute for the word "component." Thus, no claim element shall be construed as a functional component unless the element is expressly recited using the phrase "component for...".

[0192] As used herein, the phrase "based on" should not be construed to mean 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 construed as "at least based on A", unless specifically stated otherwise.

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

[0194] Aspect 1 is a method for wireless communication at a network entity, the method comprising: obtaining at least one measurement of a satellite associated with a set of RSUs; estimating a positioning of the satellite based on the at least one measurement and a location of the set of RSUs; and identifying whether the estimated positioning of the satellite is associated with an error based on a comparison of the estimated positioning of the satellite with ALM data or EPH data of the satellite.

[0195] Aspect 2 is the method according to aspect 1, wherein identifying whether the estimated positioning of the satellite is associated with an error comprises: estimating a clock offset associated with the satellite, wherein the error associated with the estimated positioning of the satellite is further based on the estimated clock offset.

[0196] Aspect 3 is the method according to aspect 1 or 2, wherein obtaining the at least one measurement of the satellite associated with the set of RSUs comprises: receiving the at least one measurement of the satellite from the set of RSUs.

[0197] Aspect 4 is the method according to aspect 3, wherein the at least one measurement of the satellite is received from the set of RSUs periodically or on demand.

[0198] Aspect 5 is the method according to any one of aspects 1 to 4, further comprising: including the satellite in a positioning session of a UE in response to the estimated positioning of the satellite being associated with the error, wherein the satellite is included in the positioning session together with a scaling factor, a weighting factor, or a quality indication.

[0199] Aspect 6 is the method according to any one of aspects 1 to 5, further comprising: excluding the satellite from the positioning session of the UE in response to the estimated positioning of the satellite being associated with the error.

[0200] Aspect 7 is the method according to aspect 6, wherein excluding the satellite from the positioning session of the UE comprises: removing at least some of the ALM data or the EPH data of the satellite from the positioning session of the UE.

[0201] Aspect 8 is the method according to any one of Aspects 1 to 7, further comprising: sending an indication of the error to at least one RSU in the set of RSUs or to at least one UE.

[0202] Aspect 9 is the method according to any one of Aspects 1 to 8, wherein the at least one measurement comprises at least one of the following: the PR between each RSU in the set of RSUs and the satellite, the estimated positioning of the satellite calculated at each RSU in the set of RSUs based on the ALM data or the EPH data of the satellite, or the clock offset associated with the satellite calculated at each RSU in the set of RSUs based on the ALM data or the EPH data of the satellite.

[0203] Aspect 10 is the method according to any one of Aspects 1 to 9, further comprising: receiving the position of each RSU in the set of RSUs from the set of RSUs.

[0204] Aspect 11 is the method according to any one of Aspects 1 to 10, further comprising: selecting the set of RSUs for obtaining the at least one measurement of the satellite based on the positions of each RSU in the set of RSUs.

[0205] Aspect 12 is the method according to any one of Aspects 1 to 11, wherein the set of RSUs comprises at least four RSUs.

[0206] Aspect 13 is the method according to any one of Aspects 1 to 12, wherein the network entity is a base station, a component of the base station, a location server, or an RSU within the set of RSUs.

[0207] Aspect 14 is the method according to any one of Aspects 1 to 13, wherein the satellite is an SV, a GNSS satellite, a LEO satellite, a MEO satellite, a GEO satellite, or a HAPS.

[0208] Aspect 15 is a device for wireless communication at a network entity, the device comprising: a memory; and at least one processor coupled to the memory, and at least partially based on information stored in the memory, the at least one processor being configured to implement any one of Aspects 1 to 14.

[0209] Aspect 16 is the device according to Aspect 15, the device further comprising: at least one of a transceiver or an antenna coupled to the at least one processor.

[0210] Aspect 17 is a device for wireless communication, the device comprising: components for implementing any one of Aspects 1 to 14.

[0211] Aspect 18 is a computer-readable medium (e.g., a non-transitory computer-readable medium) storing computer-executable code, where the code, when executed by a processor, causes the processor to implement any one of Aspects 1 to 14.

[0212] Aspect 19 is a method for wireless communication at an RSU, the method including: performing at least one of the following: measurement of the PR between the RSU and a satellite, estimation of the location of the satellite based on the EPH data or ALM data of the satellite, or estimation of the clock offset associated with the satellite based on the EPH data or the ALM data of the satellite; sending at least one of the measurement of the PR, the estimation of the location of the satellite, or the estimation of the clock offset of the satellite to a network entity; and receiving information associated with the satellite from the network entity based on the measurement of the PR, the estimation of the location of the satellite, or the estimation of the clock offset.

[0213] Aspect 20 is the method according to Aspect 19, where the information is an indication of an error, and the method further includes: forwarding the indication of the error to at least one UE.

[0214] Aspect 21 is the method according to Aspect 19 or Aspect 20, further including: sending at least one of a scale factor, a weight factor, or a quality indication associated with the satellite to at least one UE, where at least one of the scale factor, the weight factor, or the quality indication is based on the received information.

[0215] Aspect 22 is the method according to any one of Aspects 19 to 21, further including: sending the location of the RSU to the network entity.

[0216] Aspect 23 is the method according to Aspect 22, further including: receiving from the network entity a request to perform at least one of the measurement of the PR, the estimation of the location of the satellite, or the estimation of the clock offset of the satellite based on the sent location of the RSU.

[0217] Aspect 24 is the method according to any one of Aspects 19 to 23, where the satellite is an SV, a GNSS satellite, a LEO satellite, a MEO satellite, a GEO satellite, or a HAPS.

[0218] Aspect 25 is the method according to any one of Aspects 19 to 24, where the network entity is a base station, a component of the base station, a location server, or a second RSU.

[0219] Aspect 26 is a device for wireless communication at an RSU, the device comprising: a memory; and at least one processor coupled to the memory, and at least partially based on information stored in the memory, the at least one processor being configured to implement any one of aspects 19 to 25.

[0220] Aspect 27 is the device according to aspect 26, the device further comprising: at least one of a transceiver or an antenna coupled to the at least one processor.

[0221] Aspect 28 is a device for wireless communication, the device comprising: means for implementing any one of aspects 19 to 25.

[0222] Aspect 29 is a computer-readable medium (e.g., a non-transitory computer-readable medium) storing computer-executable code, wherein the code, when executed by a processor, causes the processor to implement any one of aspects 19 to 25.

Claims

1. An apparatus for wireless communication at a network entity, the apparatus comprising: a memory; and at least one processor coupled to the memory and configured, at least in part based on second information stored in the memory, to: obtain at least one measurement of a satellite associated with a set of roadside units (RSUs); estimate a positioning of the satellite based on the at least one measurement and positions of the set of RSUs; and identify whether the estimated positioning of the satellite is associated with an error based on a comparison of the estimated positioning of the satellite with almanac (ALM) data or ephemeris (EPH) data of the satellite.

2. The apparatus according to claim 1, wherein, in order to identify whether the estimated positioning of the satellite is associated with the error, the at least one processor is configured to: estimate a clock offset associated with the satellite, wherein the error associated with the estimated positioning of the satellite is further based on the estimated clock offset.

3. The apparatus according to claim 1, wherein, in order to obtain the at least one measurement of the satellite associated with the set of RSUs, the at least one processor is configured to: receive the at least one measurement of the satellite from the set of RSUs.

4. The apparatus according to claim 3, wherein, in order to receive the at least one measurement of the satellite, the at least one processor is configured to: receive the at least one measurement of the satellite from the set of RSUs periodically or on demand.

5. The apparatus according to claim 1, wherein the at least one processor is further configured to: include the satellite in a positioning session of a user equipment (UE) in response to the estimated positioning of the satellite being associated with the error, wherein the at least one processor is configured to include the satellite in the positioning session together with a scale factor, a weight factor, or a quality indication.

6. The apparatus according to claim 1, wherein the at least one processor is further configured to: exclude the satellite from a positioning session of a user equipment (UE) in response to the estimated positioning of the satellite being associated with the error.

7. The apparatus according to claim 6, wherein, in order to exclude the satellite from the positioning session of the UE, the at least one processor is configured to: remove at least some of the ALM data or the EPH data of the satellite from the positioning session of the UE.

8. The apparatus according to claim 1, wherein the at least one processor is further configured to: send an indication of the error to at least one RSU in the set of RSUs or to at least one user equipment (UE).

9. The apparatus according to claim 1, wherein the at least one measurement comprises at least one of the following: a pseudorange (PR) between each RSU in the set of RSUs and the satellite, an estimated positioning of the satellite calculated at each RSU in the set of RSUs based on the ALM data or the EPH data of the satellite, or The clock offset associated with the satellite calculated at each RSU in the set of RSUs based on the ALM data or the EPH data of the satellite.

10. The apparatus according to claim 1, wherein the at least one processor is further configured to: Receive the location of each RSU in the set of RSUs from the set of RSUs.

11. The apparatus according to claim 1, wherein the at least one processor is further configured to: Select, based on the locations of each RSU in the set of RSUs, the set of RSUs to be configured to obtain the at least one measurement of the satellite.

12. The apparatus according to claim 1, wherein the set of RSUs includes at least four RSUs.

13. The apparatus according to claim 1, wherein the network entity is a base station, a component of the base station, a location server, or an RSU within the set of RSUs.

14. The apparatus according to claim 1, wherein the satellite is a space vehicle (SV), a global navigation satellite system (GNSS) satellite, a low Earth orbit (LEO) satellite, a medium Earth orbit (MEO) satellite, a geostationary (GEO) satellite, or a high altitude pseudo satellite (HAPS).

15. A method for wireless communication at a network entity, the method comprising: Obtaining at least one measurement of a satellite associated with a set of roadside units (RSUs); Estimating the positioning of the satellite based on the at least one measurement and the location of the set of RSUs; And Identifying whether the estimated positioning of the satellite is associated with an error based on a comparison between the estimated positioning of the satellite and the almanac (ALM) data or ephemeris (EPH) data of the satellite.

16. The method according to claim 15, wherein identifying whether the estimated positioning of the satellite is associated with the error includes: Estimating a clock offset associated with the satellite, wherein the error associated with the estimated positioning of the satellite is further based on the estimated clock offset.

17. The method according to claim 15, the method further comprising: In response to the estimated positioning of the satellite being associated with the error, including the satellite in a positioning session of a user equipment (UE), wherein the satellite is included in the positioning session together with a scaling factor, a weighting factor, or a quality indication.

18. The method according to claim 15, the method further comprising: In response to the estimated positioning of the satellite being associated with the error, excluding the satellite from a positioning session of a user equipment (UE).

19. The method according to claim 15, the method further comprising: Sending an indication of the error to at least one RSU in the set of RSUs or to at least one user equipment (UE).

20. The method according to claim 15, wherein the at least one measurement includes at least one of the following: The pseudo range (PR) between each RSU in the set of RSUs and the satellite The estimated positioning of the satellite calculated at each RSU in the set of RSUs based on the ALM data or the EPH data of the satellite, or The clock offset associated with the satellite calculated at each RSU in the set of RSUs based on the ALM data or the EPH data of the satellite.

21. The method according to claim 15, the method further comprising: Receiving the position of each RSU in the set of RSUs from the set of RSUs.

22. The method according to claim 15, the method further comprising: Selecting the set of RSUs for obtaining the at least one measurement of the satellite based on the positions of each RSU in the set of RSUs.

23. The method according to claim 15, wherein the network entity is a base station, a component of the base station, a location server, or an RSU within the set of RSUs.

24. An apparatus for wireless communication at a roadside unit (RSU), the apparatus comprising: A memory; And At least one processor coupled to the memory and at least partially based on second information stored in the memory, the at least one processor being configured to: Perform at least one of the following: measuring the pseudorange (PR) between the RSU and the satellite, estimating the positioning of the satellite based on the ephemeris (EPH) data or almanac (ALM) data of the satellite, or estimating the clock offset associated with the satellite based on the EPH data or the ALM data of the satellite; Sending at least one of the measurement of the PR, the estimate of the positioning of the satellite, or the estimate of the clock offset of the satellite to a network entity; And Receiving information associated with the satellite from the network entity based on the measurement of the PR, the estimate of the positioning of the satellite, or the estimate of the clock offset.

25. The apparatus according to claim 24, wherein the information is an indication of an error, and the at least one processor is further configured to: Forward the indication of the error to at least one user equipment (UE).

26. The apparatus according to claim 24, wherein the at least one processor is further configured to: Send at least one of a scaling factor, a weighting factor, or a quality indication associated with the satellite to at least one user equipment (UE), wherein at least one of the scaling factor, the weighting factor, or the quality indication is based on the received information.

27. The apparatus according to claim 24, wherein the at least one processor is further configured to: Send the position of the RSU to the network entity.

28. The apparatus according to claim 27, wherein the at least one processor is further configured to: Receive from the network entity a request to perform at least one of the measurement of the PR, the estimate of the positioning of the satellite, or the estimate of the clock offset of the satellite based on the sent position of the RSU.

29. The apparatus according to claim 24, wherein the satellite is a space vehicle (SV), a global navigation satellite system (GNSS) satellite, a low Earth orbit (LEO) satellite, a medium Earth orbit (MEO) satellite, a geostationary (GEO) satellite, or a high-altitude pseudo satellite (HAPS).

30. The apparatus according to claim 24, wherein the network entity is a base station, a component of the base station, a location server, or a second RSU.

31. A method for wireless communication at a roadside unit (RSU), the method comprising: performing at least one of the following: measuring a pseudorange (PR) between the RSU and a satellite, estimating a position of the satellite based on ephemeris (EPH) data or almanac (ALM) data of the satellite, or estimating a clock offset associated with the satellite based on the EPH data or the ALM data of the satellite; sending at least one of the measurement of the PR, the estimate of the position of the satellite, or the estimate of the clock offset of the satellite to a network entity; and receiving information associated with the satellite from the network entity based on the measurement of the PR, the estimate of the position of the satellite, or the estimate of the clock offset.

32. The method according to claim 31, wherein the information is an indication of an error, and the method further comprises: forwarding the indication of the error to at least one user equipment (UE).

33. The method according to claim 31, the method further comprising: sending to at least one user equipment (UE) at least one of a scaling factor, a weighting factor, or a quality indication associated with the satellite, wherein at least one of the scaling factor, the weighting factor, or the quality indication is based on the received information.

34. The method according to claim 31, the method further comprising: sending the location of the RSU to the network entity.

35. The method according to claim 34, the method further comprising: receiving from the network entity a request to perform at least one of the measurement of the PR, the estimate of the position of the satellite, or the estimate of the clock offset of the satellite based on the sent location of the RSU.

Images