DETERMINING POSITION INFORMATION OF MOBILE DEVICES

BACKGROUND

Field of Invention

[0001] The present invention relates generally to the field of wireless communications, and more specifically to determining position information of mobile devices.

Description of Related Art

[0002] With the proliferation of mobile devices, identifying precise positioning information (e.g., to centimeter-level accuracy) has become increasingly desired. Various techniques, such as Precise Point Positioning (PPP) and Real Time Kinematics (RTK), may be used for identifying precise positioning information. However, these techniques may have various drawbacks. For example, conventional PPP techniques may take a long time to converge. As another example, RTK may use a relatively large amount of data.

BRIEF SUMMARY

[0003] An example mobile device for determining a PPP position, according to this disclosure comprises a GNSS receiver, a memory, and one or more processing units communicatively coupled with the GNSS receiver and the memory. The one or more processing units are configured to obtain, via the GNSS receiver, one or more Global Navigation Satellite System (GNSS) signals, obtain position information based on one or more position sources, wherein the position information is indicative of a location of the mobile device, determine one or more Precise Point Positioning (PPP) positions of the mobile device based on the position information and the one or more GNSS signals, wherein a position uncertainty of the position information meets or is below an uncertainty threshold, determine whether at least one PPP position meets or is below one or more convergence thresholds, and in response to determining that at least one PPP position meets or is below the one or more convergence thresholds, provide the at least one PPP position.

[0004] An example method of determining a Precise Point Positioning (PPP) position, according to this disclosure, comprises obtaining, by a mobile device, one or more Global Navigation Satellite System (GNSS) signals, obtaining, by the mobile device, position 2 information based on one or more position sources, wherein the position information is indicative of a location of the mobile device, determining one or more Precise Point Positioning (PPP) positions of the mobile device based on the position information and the one or more GNSS signals, wherein a position uncertainty of the position information meets or is below an uncertainty threshold, determining whether at least one PPP position meets or is below one or more convergence thresholds, and in response to determining that at least one PPP position meets or is below the one or more convergence thresholds, providing the at least one PPP position.

[0005] An example mobile device for determining a PPP position, according to this disclosure, comprises means for obtaining one or more Global Navigation Satellite System (GNSS) signals, means for obtaining position information based on one or more position sources, wherein the position information is indicative of a location of the mobile device, means for determining one or more Precise Point Positioning (PPP) positions of the mobile device based on the position information and the one or more GNSS signals, wherein a position uncertainty of the position information meets or is below an uncertainty threshold, means for determining whether at least one PPP position meets or is below one or more convergence thresholds, and means for providing the at least one PPP position in response to determining that at least one PPP position meets or is below the one or more convergence thresholds.

[0006] An example non-transitory computer-readable medium, according to this disclosure, stores instructions for determining a PPP position. The instructions comprise code for obtaining one or more Global Navigation Satellite System (GNSS) signals, obtaining position information based on one or more position sources, wherein the position information is indicative of a location of a mobile device, determining one or more Precise Point Positioning (PPP) positions of the mobile device based on the position information and the one or more GNSS signals, wherein a position uncertainty of the position information meets or is below an uncertainty threshold, and in response determining that at least one PPP position meets or is below the one or more convergence thresholds, providing the at least one PPP position.

BRIEF DESCRIPTION OF THE DRAWINGS [0007] FIG. l is a diagram of a positioning system, according to an embodiment. -3-

[0008] FIG. 2 is a block diagram of a positioning system, according to an embodiment.

[0009] FIG. 3 is a flow diagram for determining positioning information, according to an embodiment.

[0010] FIG. 4 is an information flow diagram for determining positioning information, according to an embodiment.

[0011] FIG. 5 is a flow diagram for determining positioning information based on camera data, according to an embodiment.

[0012] FIG. 6 is a flow diagram for determining positioning information, according to an embodiment.

[0013] FIG. 7 is a block diagram of an embodiment of a mobile device, which can be utilized in embodiments as described herein.

[0014] Like reference symbols in the various drawings indicate like elements, in accordance with certain example implementations.

DETAILED DESCRIPTION

[0015] The following description is directed to certain implementations for the purposes of describing the innovative aspects of this disclosure. However, a person having ordinary skill in the art will readily recognize that the teachings herein can be applied in a multitude of different ways. The described implementations may be implemented in any device, system, or network that is capable of transmitting and receiving radio frequency (RF) signals according to any communication standard, such as any of the Institute of Electrical and Electronics Engineers (IEEE) IEEE 802.11 standards (including those identified as WiFi® technologies), the Bluetooth® standard, code division multiple access (CDMA), frequency division multiple access (FDMA), time division multiple access (TDMA), Global System for Mobile communications (GSM), GSM/General Packet Radio Service (GPRS), Enhanced Data GSM Environment (EDGE), Terrestrial Trunked Radio (TETRA), Wideband-CDMA (W-CDMA), Evolution Data Optimized (EV-DO), lxEV-DO, EV-DO Rev A, EV-DO Rev B, High Rate Packet Data (HRPD), High Speed Packet Access (HSPA), High Speed Downlink Packet Access (HSDPA), High Speed Uplink Packet Access (HSUPA), Evolved High -4-

Speed Packet Access (HSPA+), Long Term Evolution (LTE), Advanced Mobile Phone System (AMPS), or other known signals that are used to communicate within a wireless, cellular or internet of things (IoT) network, such as a system utilizing Third Generation (3G), Fourth Generation (4G), Fifth Generation (5G), Sixth Generation (6G), or further implementations thereof, technology.

[0016] As used herein, an “RF signal” comprises an electromagnetic wave that transports information through the space between a transmitter (or transmitting device) and a receiver (or receiving device). As used herein, a transmitter may transmit a single “RF signal” or multiple “RF signals” to a receiver. However, the receiver may receive multiple “RF signals” corresponding to each transmitted RF signal due to the propagation characteristics of RF signals through multipath channels. The same transmitted RF signal on different paths between the transmitter and receiver may be referred to as a “multipath” RF signal.

[0017] As used herein, a “mobile device” may refer to various types of electronic or computing devices, such as mobile or cellular phones, wearable computers (e.g., a fitness tracker, a virtual reality or augmented reality headset, etc.), tablet computers, laptop computers, vehicle computing devices (e.g., computing devices of an autonomous or semi-autonomous vehicle, devices associated with vehicle entertainment or navigation systems, etc.), and the like. The techniques described herein relate to determining location data of a mobile device, that indicates, for example, a current location of the mobile device.

[0018] As used herein, a “position source device” may refer to a device that provides location information and/or position information to a mobile device. Examples of position source devices include: cellular base stations (e.g., LTE cells and/or base stations, 5G cells and/or base stations, and the like), wireless network base stations that provide RTK data, IoT devices (e.g., smart traffic cameras, smart security cameras, smart motion sensors, etc.), WiFi Access Points (APs), wireless beacon devices, RF sensing devices, Ultra-Wide Bandwidth (UWB) devices configured to perform ranging, third-party devices that interact with mobile applications executing on a mobile device (e.g., a scanning device associated with a toll booth that scans an E-Z pass tag, an electronic payment device in a store that scans information presented on the mobile device, etc.), and the like. -5-

[0019] As used herein, a “Precise Point Positioning (PPP) engine” refers to one or more components (e.g., software components or modules) that perform PPP techniques to determine location data of a mobile device. PPP generally uses a network of global base stations to determine Global Navigation Satellite System (GNSS) satellite orbit and clock corrections and transmit them to a “rover station” (e.g., a mobile device).

[0020] A PPP engine may use various Bayesian estimators to determine the one or more PPP positions of a mobile device. Examples of Bayesian estimators that may be used include a Kalman Filter, an Extended Kalman Filter, an Unscented Kalman Filter, a particle filter, or the like. It should be noted that, as used herein, “Kalman Filter” is intended to refer to various types of Kalman Filters, such as an Extended Kalman Filter, an Unscented Kalman Filter, or the like. In some embodiments, an estimator may be used to iteratively determine states which corresponded to a predicted device location over a series of time steps. Continuing with this example, the Bayesian estimator may be iteratively updated (e.g., states of the estimator may be iteratively updated) to identify a solution. The solution of the estimator may correspond to a PPP position of a mobile device at a time point at which the estimator has converged.

[0021] It should be noted that a PPP engine as used herein may be implemented as one or more modules. For example, in some embodiments, a PPP engine may be implemented as two or more modules. As a more particular example, in some embodiments, a first module may receive position information and perform various pre processing techniques on the position information. Continuing with this more particular example, in some embodiments, a second module may correspond to a Bayesian estimator that estimates one or more PPP positions based on the position information. Conversely, in some embodiments, a PPP engine may be implemented as one module. It should be understood that the methods, systems, apparatuses, media, and techniques described herein may be implemented using any suitable number of modules or engines.

[0022] As used herein, “Real Time Kinematics (RTK)” generally refers to another GNSS-based positioning technique that may be used to determine a location of a mobile device. In general, RTK uses carrier-based ranging by determining the number of carrier cycles between a satellite and mobile device (e.g., carrier phase measurements, including changes in phase and the number of cycles of the carrier signals). 6

[0023] Conventional PPP may generally use GNSS data to obtain PPP location data. Conventional PPP techniques may use a Kalman Filter or an Extended Kalman Filter that utilizes GNSS data to determine location data by iteratively updating a predicted location until it is determined that the Kalman Filter or the Extended Kalman Filter has converged. Conventional PPP techniques may require a relatively long time period to reach convergence, for example, on the order of 20-40 minutes to reach an accuracy of less than 10 centimeters.

[0024] The techniques described herein allow a PPP position to meet or be below a convergence threshold more rapidly than a PPP position identified using conventional PPP techniques. In particular, one or more PPP positions of a mobile device may be determined based on additional precise position information. In particular, a mobile device may receive position information from one or more position source devices. The position information may indicate an absolute location of the one or more position source devices and/or a relative position of the mobile device relative to the one or more position source devices. The position information may be GNSS-based (e.g., RTK data) or non- GNSS-based (e.g., from IoT devices, from position information determined by the mobile device itself, from a wireless base station, from wireless beacon devices, from RF sensing devices, from LIDAR devices, from RF sensing devices, from UWB devices capable of performing ranging, etc.). Examples of UWB devices include smart mobile phones, smart watches, smart keys or fobs, and the like.

[0025] By providing the position information to the mobile device for use in determining the one or more PPP positions, the mobile device may effectively benefit from access to additional location data or position data (e.g., additional relative to multi constellation, multi-band data traditionally utilized in PPP) that can be used to constrain a location of the mobile device during determination of the one or more PPP positions. By utilizing additional position information that constrains the location of the mobile device, the one or more PPP positions may be determined more rapidly than would be determined using conventional PPP techniques.

[0026] The techniques described herein may be used in a variety of applications. For example, in an instance in which PPP position data is desired for a vehicle, it may be difficult to determine PPP position data in certain environments, such as when a car exits a tunnel, due to poor GNSS coverage. In some embodiments, in such a scenario, position -7- information may be obtained by a mobile device associated with the vehicle. The position information may be obtained from various position source devices, wireless base stations (e.g., 4G/LTE wireless base stations, 5G wireless base stations, wireless base stations that provide RTK data, and the like), LIDAR devices, RF sensing devices, IoT devices, UWB devices, and/or one or more devices associated with a road the vehicle is traveling on and/or a toll booth the vehicle passes through. For example, position information may be obtained from a traffic camera or toll both camera that captures an image of a portion of the vehicle. As a more particular example, a device associated with the traffic camera or the toll booth camera may transmit a message to a mobile device associated with the vehicle indicating detection of the vehicle and/or any position information (e.g., an absolute location of the camera, a field of view of the camera, a relative position of the vehicle relative to the camera, etc.). As another example, position information may be obtained from a scanning device that scans an E-Z pass tag. As a more particular example, the scanning device may transmit a message to the mobile device (e.g., to a mobile application executing on the mobile device) that indicates that the E-Z pass tag has been scanned and/or any position information (e.g., a location of the scanning device).

[0027] As another example, it may be difficult to determine PPP position data in an instance in which a mobile device transitions from an indoor environment to an outdoor environment due to poor GNSS coverage in the indoor environment. In such cases, position information may be obtained by a mobile device based on one or more position source devices accessible in the indoor environment. Examples of such one or more position source devices may include various IoT devices positioned in the indoor environment, various wireless (e.g., Bluetooth®) beacons that broadcast messages that may be detected by the mobile device, various RF sensing devices, various UWB devices that perform ranging techniques, various WiFi APs, and the like. In some embodiments, one or more initial PPP positions of the mobile device may be determined using the position information from the one or more position source devices accessible in the indoor environment, thereby allowing the one or more PPP positions to be more rapidly determined once the mobile device enters the outdoor environment (and therefore, when better GNSS coverage is available).

[0028] In some embodiments, a determination of whether to use position information to determine one or more PPP positions of a mobile device may be made based on an uncertainty of the position information. For example, the position information may be 8 used in response to determining that an uncertainty of the position information meets or is below a threshold.

[0029] It should be noted that PPP may be enabled on a mobile device at an application level. Accordingly, determinations of whether to request position information to determine one or more PPP positions of a mobile device may be made by a particular application executing on the mobile device and/or based on user configuration settings associated with the particular application. For example, in some embodiments, a navigation application may be set, by default, to not use PPP positioning. Continuing with this example, in some embodiments, the navigation application may request position information to determine one or more PPP positions in response to user configuration settings associated with the navigation application indicating that PPP positioning is to be used. In some embodiments, the application may determine a desired accuracy level or threshold of position uncertainty associated with requested position information in order to use requested position information to determine the one or more PPP positions. For example, the threshold may be determined based on application type. Moreover, in some embodiments, the application may determine when position information is requested. For example, in some embodiments, in an instance in which the mobile device is determined to be in a vehicle or approaching a vehicle, the application may request position information as the mobile device is in the vehicle or approaching the vehicle and prior to the vehicle being in motion (e.g., so that accurate PPP positions are available in a navigation application prior to the vehicle being in motion). As another example, in some embodiments, in an instance in which the mobile device corresponds to a Virtual Reality (VR) or Augmented Reality (AR) headset, the application may request the position information in response to the headset being turned on or activated.

[0030] FIG. 1 is a simplified illustration of a positioning system 100 in which a mobile device 105, location server (LS) 160, and/or other components of the positioning system 100 can use the techniques provided herein for determining and estimated location of mobile device 105, according to an embodiment. The techniques described herein may be implemented by one or more components of the positioning system 100. The positioning system 100 can include a mobile device 105, one or more GNSS satellites 110 (also referred to as space vehicles (SVs)) for a GNSS such as the Global Positioning System (GPS), base stations 120, APs 130, LS 160, network 170, external client 180, and/or one or more IoT devices 190. Generally put, the positioning system 100 can -9- estimate a location of the mobile device 105 based on RF signals received by and/or sent from the mobile device 105 and known locations of other components (e.g., GNSS satellites 110, base stations 120, APs 130, and/or IoT devices 190) transmitting and/or receiving the RF signals..

[0031] It should be noted that FIG. 1 provides only a generalized illustration of various components, any or all of which may be utilized as appropriate, and each of which may be duplicated as necessary. Specifically, although only one mobile device 105 is illustrated, it will be understood that many mobile devices (e.g., hundreds, thousands, millions, etc.) may utilize the positioning system 100. Similarly, the positioning system 100 may include a larger or smaller number of base stations 120 and/or APs 130 than illustrated in FIG. 1. The illustrated connections that connect the various components in the positioning system 100 comprise data and signaling connections which may include additional (intermediary) components, direct or indirect physical and/or wireless connections, and/or additional networks. Furthermore, components may be rearranged, combined, separated, substituted, and/or omitted, depending on desired functionality. In some embodiments, for example, the external client 180 may be directly connected to LS 160. A person of ordinary skill in the art will recognize many modifications to the components illustrated.

[0032] Depending on desired functionality, the network 170 may comprise any of a variety of wireless and/or wireline networks. The network 170 can, for example, comprise any combination of public and/or private networks, local and/or wide-area networks, and the like. Furthermore, the network 170 may utilize one or more wired and/or wireless communication technologies. In some embodiments, the network 170 may comprise a cellular or other mobile network, a wireless local area network (WLAN), a wireless wide-area network (WWAN), and/or the Internet, for example. Examples of network 170 include an LTE wireless network, a 5G wireless network (also referred to as New Radio (NR) wireless network or 5G NR wireless network), a WiFi WLAN, and the Internet. LTE, 5G and NR are wireless technologies defined, or being defined, by the 3rd Generation Partnership Project (3GPP). Network 170 may also include more than one network and/or more than one type of network.

[0033] The base stations 120 and APs 130 are communicatively coupled to the network 170. In some embodiments, the base station 120s may be owned, maintained, 10 and/or operated by a cellular network provider, and may employ any of a variety of wireless technologies, as described herein below. Depending on the technology of the network 170, a base station 120 may comprise a node B, an Evolved Node B (eNodeB or eNB), a base transceiver station (BTS), a radio base station (RBS), an NR NodeB (gNB), a Next Generation eNB (ng-eNB), or the like. A base station 120 that is a gNB or ng-eNB may be part of a Next Generation Radio Access Network (NG-RAN) which may connect to a 5G Core Network (5GC) in the case that Network 170 is a 5G network. An AP 130 may comprise a WiFi AP or a Bluetooth® AP, for example. Thus, mobile device 105 can send and receive information with network-connected devices, such as LS 160 and/or IoT devices 190, by accessing the network 170 via a base station 120 using a first communication link 133. Additionally or alternatively, because APs 130 also may be communicatively coupled with the network 170, mobile device 105 may communicate with Internet-connected devices, including LS 160, using a second communication link 135. In some embodiments, mobile device 105 may communicate with IoT devices 190 using a third communication link 195.

[0034] As used herein, the term “base station” may generically refer to a single physical transmission point, or multiple co-located physical transmission points, which may be located at a base station 120. A Transmission Reception Point (TRP) (also known as transmit/receive point) corresponds to this type of transmission point, and the term “TRP” may be used interchangeably herein with the terms “gNB,” “ng-eNB,” and “base station.” Physical transmission points may comprise an array of antennas (e.g., as in a Multiple Input-Multiple Output (MIMO) system and/or where the base station employs beamforming) of the base station. The term “base station” may additionally refer to multiple non-co-located physical transmission points, the physical transmission points may be a Distributed Antenna System (DAS) (a network of spatially separated antennas connected to a common source via a transport medium) or a Remote Radio Head (RRH) (a remote base station connected to a serving base station). Alternatively, the non-co- located physical transmission points may be the serving base station receiving the measurement report from the mobile device 105 and a neighbor base station whose reference RF signals the mobile device 105 is measuring.

[0035] As used herein, the term “cell” may generically refer to a logical communication entity used for communication with a base station 120, and may be associated with an identifier for distinguishing neighboring cells (e.g., a Physical Cell 11

Identifier (PCID), a Virtual Cell Identifier (VCID)) operating via the same or a different carrier. In some examples, a carrier may support multiple cells, and different cells may be configured according to different protocol types (e.g., Machine-Type Communication (MTC), Narrowband Internet-of-Things (NB-IoT), Enhanced Mobile Broadband (eMBB), or others) that may provide access for different types of devices. In some cases, the term “cell” may refer to a portion of a geographic coverage area (e.g., a sector) over which the logical entity operates.

[0036] The LS 160 may comprise a server and/or other computing device configured to determine an estimated location of mobile device 105 and/or provide data (e.g., “assistance data”) to mobile device 105 to facilitate the location determination. According to some embodiments, LS 160 may comprise a Home Secure User Plane Location (SUPL) Location Platform (H-SLP), which may support the SUPL user plane (UP) location solution defined by the Open Mobile Alliance (OMA) and may support location services for mobile device 105 based on subscription information for mobile device 105 stored in LS 160. In some embodiments, the LS 160 may comprise, a Discovered SLP (D-SLP) or an Emergency SLP (E-SLP). The LS 160 may also comprise an Enhanced Serving Mobile Location Center (E-SMLC) that supports location of mobile device 105 using a control plane (CP) location solution for LTE radio access by mobile device 105. The LS 160 may further comprise a Location Management Function (LMF) that supports location of mobile device 105 using a control plane (CP) location solution for NR radio access by mobile device 105. In a CP location solution, signaling to control and manage the location of mobile device 105 may be exchanged between elements of network 170 and with mobile device 105 using existing network interfaces and protocols and as signaling from the perspective of network 170. In a UP location solution, signaling to control and manage the location of mobile device 105 may be exchanged between LS 160 and mobile device 105 as data (e.g. data transported using the Internet Protocol (IP) and/or Transmission Control Protocol (TCP)) from the perspective of network 170.

[0037] As previously noted (and discussed in more detail below), the estimated location of mobile device 105 may be based on measurements of RF signals sent from and/or received by the mobile device 105. In particular, these measurements can provide information regarding the relative distance and/or angle of the mobile device 105 from one or more components in the positioning system 100 (e.g., GNSS satellites 110, APs 130, base stations 120). The estimated location of the mobile device 105 can be estimated 12 geometrically (e.g., using multi angulation and/or multilateration), based on the distance and/or angle measurements, along with known position of the one or more components.

[0038] Although terrestrial components such as APs 130 and base stations 120 may be fixed, embodiments are not so limited. Mobile components may be used. Moreover, in some embodiments, location of the mobile device 105 estimated at least in part based on measurements of RF signals communicated between the mobile device 105 and one or more other mobile devices (not shown in FIG. 1). Direct communication between mobile devices in this manner may comprise sidelink and/or similar Device-to-Device (D2D) communication technologies. Sidelink, which is defined by 3GPP, is a form of D2D communication under the cellular-based LTE and NR standards.

[0039] An estimated location of mobile device 105 can be used in a variety of applications - e.g. to assist direction finding or navigation for a user of mobile device 105 or to assist another user (e.g. associated with external client 180) to locate mobile device 105. A “location” is also referred to herein as a “location estimate”, “estimated location”, “location”, “location data,” “position”, “position estimate”, “position fix”, “estimated position”, “location fix” or “fix”. A location of mobile device 105 may comprise an absolute location of mobile device 105 (e.g. a latitude and longitude and possibly altitude) or a relative location of mobile device 105 (e.g. a location expressed as distances north or south, east or west and possibly above or below some other known fixed location or some other location such as a location for mobile device 105 at some known previous time). A location may also be specified as a geodetic location (as a latitude and longitude) or as a civic location (e.g. in terms of a street address or using other location related names and labels). A location may further include an uncertainty or error indication, such as a horizontal and possibly vertical distance by which the location is expected to be in error or an indication of an area or volume (e.g. a circle or ellipse) within which mobile device 105 is expected to be located with some level of confidence (e.g. 95% confidence).

[0040] The external client 180 may be a web server or remote application that may have some association with mobile device 105 (e.g. may be accessed by a user of mobile device 105) or may be a server, application, or computer system providing a location service to some other user or users which may include obtaining and providing the location of mobile device 105 (e.g. to enable a service such as friend or relative finder, asset tracking or child or pet location). Additionally or alternatively, the external client -13-

180 may obtain and provide the location of mobile device 105 to an emergency services provider, government agency, etc.

[0041] IoT devices 190 may include various IoT devices, such as cameras (e.g., traffic cameras, security cameras, web cameras, etc.), communication-enabled tags, smoke detectors, sensors (e.g., proximity sensors, motion sensors, etc.), and the like. IoT devices 190 may include any suitable number of IoT devices (e.g., ten, one hundred, one thousand, one million, etc.). It should be noted that IoT devices in IoT devices 190 may be fixed or mobile (e.g., IoT devices associated with vehicles, robots, and the like).

[0042] FIG. 2 is a block diagram of a positioning system 200, according to an embodiment.

[0043] A PPP location can be provided by a PPP engine. The PPP engine may perform various steps or techniques to determine a PPP position 202 using PPP. PPP position 202 can indicate a current location or position of the mobile device. For example, the PPP engine may use a Kalman Filter, an Extended Kalman Filter, an Unscented Kalman Filter, a particle filter, or the like to iteratively converge to a solution that corresponds to the PPP position that is the location of the mobile device. Means for performing the functionality associated with the PPP engine may be performed by hardware and/or software components of a mobile device. Example components of a mobile device are illustrated in FIG. 7.

[0044] In some embodiments, the PPP engine can be in an initialized state, referred to herein as initialized PPP engine 204. Initialized PPP engine 204 may be initialized using multi-constellation, multi-band data 212.

[0045] Multi-constellation, multi-band data 212 may include, for example, GNSS data. GNSS data may include data such as carrier phase, a differential delay of GNSS signals of different frequencies, and the like. GNSS data can be obtained by one or more GNSS receivers of the mobile device. It should be noted that a single GNSS receiver may be capable of receiving GNSS data from multiple constellations and on multiple bands and/or frequencies.

[0046] In some embodiments, the PPP engine can be in an updated state, referred to herein as updated PPP engine 210. In some embodiments, the updated state may correspond to initialized PPP engine 204 that has received updated or additional position -14- information. For example, as shown in FIG. 2, initialized PPP engine 204 may be updated to generate updated PPP engine 210 based on receipt of position information 206.

[0047] Position information 206 may be received by the mobile device from one or more position source devices of position source devices 208. Position source devices 208 are external to the mobile device. Examples of position source devices 208 include: one or more wireless base stations (e.g., 4G/LTE wireless base stations, 5G wireless base stations, wireless base stations that provide RTK data, or the like), one or more sensors (e.g., motion sensors, image sensors such as cameras, etc.), one or more IoT devices (e.g., a smart traffic camera, a smart device associated with a toll booth, etc.), one or more UWB devices (e.g., one or more UWB devices that may be configured to perform ranging), one or more RF sensing devices, one or more WiFi APs, and the like. Example techniques for determining position information 206 based on information transmitted by position source devices 208 are described in more detail in connection with FIG. 3

[0048] It should be noted that although FIG. 2 shows a PPP engine initialized using multi-constellation, multi-band data and updated using position information obtained from one or more position source device, other techniques for initializing and updating a PPP engine are contemplated. For example, in some embodiments, a PPP engine may not be initialized using multi-constellation, multi-band data. Rather, in some embodiments, a PPP engine may be initialized with other position information or any other initial estimate of position that may serve as a seed for the PPP engine.

[0049] In some embodiments, a PPP engine may be updated using position information obtained from one or more position source devices (e.g., one position source device, two position source devices, five position sources devices). Additionally, it should be noted that, in some embodiments, the PPP engine may request the position information from the one or more position source devices. For example, in some embodiments, the PPP engine may request the position information based on a current uncertainty level of the PPP engine and/or based on a closeness of the PPP engine to convergence, as shown in and described below in connection with FIG. 3.

[0050] In some embodiments, a PPP engine may be iteratively updated multiple times using position information received at multiple times. For example, in some embodiments, a PPP engine may be updated at a first time using first position information from a first position source device, and may be updated at a second time using second -15- position information received from a second position source device. It should be understood that various combinations of sources of information for PPP engine initialization and/or PPP engine updates may be used.

[0051] FIG. 3 is a flow diagram of a method 300 of determining position information, according to an embodiment. Means for performing the functionality illustrated in one or more of the blocks shown in FIG. 3 may be performed by hardware and/or software components of a mobile device. Example components of a mobile device are illustrated in FIG. 7, which are described in more detail below.

[0052] At block 310, the functionality comprises obtaining multi-constellation, multi band data that indicates absolute position information of a mobile device. Means for performing the functionality at block 310 may comprise a GNSS receiver of a mobile device, a processing unit of a mobile device, and/or other components of a mobile device, as illustrated in FIG. 7.

[0053] The multi-constellation, multi-band data may be GNSS data that is based on data from one or more satellites. The multi-constellation, multi-band data may indicate absolute position information in latitude, longitude, and/or elevation.

[0054] It should be noted that, due to an environment the mobile device is located in, the multi-constellation, multi-band data may not be accurate to a desired accuracy level (e.g., within 10 centimeters, within 1 meter, within 5 meters, etc.). For example, multi constellation, multi-band data that comprises GNSS data may not be accurate within a desired accuracy level in an instance in which the mobile device is indoors, is exiting a tunnel, etc.

[0055] Additionally, it should be noted that, in some embodiments, block 310 can be omitted. For example, in some embodiments, one or more PPP positions of the mobile device can be determined using other blocks shown in FIG. 3 without obtaining multi constellation, multi-band data.

[0056] At block 320, the functionality comprises estimating one or more PPP positions of the mobile device and an uncertainty associated with the one or more PPP positions. Means for performing the functionality at block 320 may comprise a processing unit of a mobile device, and/or other components of a mobile device, as illustrated in FIG. 7. -16-

[0057] In some embodiments, the one or more PPP positions can be estimated by identifying one or more initial PPP positions. In some embodiments, the one or more initial PPP positions may correspond to an initial solution of an estimator that determines PPP positions. For example, in an instance in which the estimator includes a Kalman Filter, the estimated one or more PPP positions can correspond to initial states (e.g., initial position, velocity, and/or acceleration states) of the Kalman Filter. As another example, in an instance in which the estimator includes a particle filter, the estimated one or more PPP positions can correspond to one or more particles (e.g., one particle, five particles, ten particles, twenty particles, or the like) that have been selected based on an initial prior distribution. The initial prior distribution may be based on a grid that spans a region that includes an expected PPP position of the mobile device. In some embodiments, the one or more PPP positions may be estimated based on multi-constellation, multi-band data received at block 310. For example, in some embodiments, initial states of a Kalman Filter may be determined based on the multi-constellation, multi-band data. As another example, in some embodiments, initial states of particles of a particle filter may be selected based on the multi-constellation, multi-band data and/or uncertainty of the multi constellation, multi-band data.

[0058] One or more uncertainty levels (sometimes referred to herein as a “position uncertainty”) can be determined that are associated with the one or more PPP positions. In some embodiments, an uncertainty level may correspond to an uncertainty associated with an estimator used to determine the one or more PPP positions. For example, in an instance in which the estimator is a Kalman Filter, an uncertainty level may be based on a covariance matrix associated with the Kalman Filter. As another example, in an instance in which the estimator is a particle filter, an uncertainty level may be based on probabilities associated with particles of the particle filter.

[0059] It should be noted that, in some embodiments, an estimated time to convergence may be determined. An estimated time to convergence may indicate an estimated duration of time an estimator of PPP position will take to converge to a PPP position within a desired accuracy range (e.g., within 10 centimeters, between 10 - 20 centimeters, within 50 centimeters, or the like) or the reach a steady state status. In some embodiments, an estimated time to convergence may be determined based on an uncertainty level associated with the one or more PPP positions. For example, in some embodiments, an estimated time to convergence may be generally proportional to an -17- uncertainty level such that an estimated time to convergence is higher with corresponding higher levels of uncertainty.

[0060] At block 325, the functionality comprises determining, by the mobile device, whether to request position information. Means for performing the functionality at block 325 may comprise a processing unit of a mobile device, and/or other components of a mobile device, as illustrated in FIG. 7.

[0061] In some embodiments, a determination of whether to request position information may be made based on a current uncertainty associated with the one or more PPP positions estimated at block 320. For example, in some embodiments a determination to request position information may be made in response to determining that the uncertainty exceeds a predetermined uncertainty threshold. Conversely, a determination to not request position information may be made in response to determining that the uncertainty meets or is below the predetermined uncertainty threshold. As another example, in some embodiments, a determination to request position information may be made in response to determining that an estimated time to convergence exceeds a predetermined convergence time threshold. Conversely, a determination to not request position information may be made in response to determining that the estimated time to convergence meets or is below the predetermined convergence time threshold.

[0062] In some embodiments, a determination to request position information may be made based on a current status, environment, or activity associated with the mobile device. For example, in an instance in which the mobile device determines that the mobile device is in a vehicle or is approaching a vehicle, the mobile device may determine that the position information is to be requested prior to the vehicle being in motion. As another example, in an instance in which the mobile device corresponds to a Virtual Reality (VR) or Augmented Reality (AR) headset, the VR or AR headset may determine that the position information is to be requested (e.g., to quickly obtain PPP position information accurate to a cm-level). As yet another example, in some embodiments, a determination to request position information may be made based on a historical pattern of use of the mobile device. As a more particular example, the mobile device may determine that the position information is to be requested in response to determining that a particular application or application type (e.g., a navigation application, or the like) is frequently used at a current time of day and and/or when the mobile device is within proximity of a -18- particular geographical region (e.g., near a work place of a user of the mobile device, or the like).

[0063] If, at block 325, it is determined that position information is not to be requested (“no” at 325), method 300 can proceed to block 360 and determine whether convergence has been reached.

[0064] Conversely, if at block 325, it is determined that position information is to be requested, (“yes” at 325), method 300 can proceed to block 330 and can request and receive the position information.

[0065] At block 330, the functionality comprises requesting and receiving, by the mobile device, position information. Means for performing the functionality at block 330 may comprise a processing unit of a mobile device, and/or other components of a mobile device, as illustrated in FIG. 7.

[0066] In some embodiments, the position information can indicate a relative position of the mobile device to one or more position source devices. For example, the position source information can indicate that the mobile device is a particular distance (e.g., 10 centimeters, 50 centimeters, 1 meter, etc.) from a particular position source device. As another example, the position source information can indicate a direction of the mobile device to a particular position source device (e.g., to the North, to the Northwest, 30 degrees to the left, etc.). Additionally or alternatively, in some embodiments, the position information can indicate an absolute position of any of the one or more position source devices, for example, in latitude, longitude, and/or elevation.

[0067] In some embodiments, the mobile device can request the position information from one or more position source devices. In some embodiments, prior to requesting the position information, the mobile device can select a position source device from which to request the position information. Selection of the position source device may be based on various criteria or various combinations of criteria. The criteria may include a cost of the position information, computational resources required by the mobile device to determine the position information, an accuracy of the position information, information indicating that position information provided by the position source device meets or will meet a predetermined position uncertainty threshold, or any combination thereof. As a more particular example, a position source device may be selected for which a cost of position information received from the position source device is below a predetermined -19- cost threshold. As another more particular example, a position source device may be selected for which accuracy of position information received from the position source device is within a desired accuracy range (e.g., within a desired accuracy of the PPP position to be provided). As yet another more particular example, a position source device may be selected that provides position information at the lowest cost and for which the accuracy of the position information is within a desired accuracy range.

[0068] In some embodiments, the position information can be received in connection with communications received by the mobile device from one or more position source devices.

[0069] For example, in an instance in which the one or more position source devices includes a wireless base station (e.g., a 4G/LTE base station, a 5G base station, and the like), the communications can include carrier wave information. As a more particular example, the communications can include RTK position information that includes one or more epochs of RTK data. Continuing with this more particular example, in some embodiments, the position information can include an RTK position determined based on the one or more epochs of RTK data. As another more particular example, in an instance in which the one or more position source devices includes a wireless base station (e.g., an LTE cell or base station, a 5G cell or base station, and the like), the communications can include range information (e.g., communication round-trip time) and/or directional information (e.g., based on a phased-array pattern of 5G antennas). In some embodiments, the mobile device may determine the position information based on signals (e.g., Positioning Reference Signals (PRS)) transmitted by a 5G cell or base station. In some such embodiments, the 5G cell or base station may be configured to function as a positioning-only beacon which transmits the signals (e.g., PRS signals) and/or may broadcast assistance data to assist positioning of the mobile device. Position information based on signals may comprise positioning-related measurements such as Received Signal Strength Indicator (RSSI), Round Trip signal propagation Time (RTT), Reference Signal Received Power (RSRP), Reference Signal Received Quality (RSRQ), Reference Signal Time Difference (RSTD), Time of Arrival (TOA), Angle Of Arrival (AOA), Receive Time-Transmission Time Difference (Rx-Tx), Differential AOA (DAOA), Angle Of Departure (AOD), and/or Timing Advance (TA). Additionally or alternatively, similar measurements may be made of sidelink signals transmitted by other mobile devices. 20

[0070] As yet another example, in an instance in which the one or more position source devices include a device (e.g., an IoT device, a Bluetooth ® beacon device, and the like) that broadcasts beacons, the communications can include identifying information associated with the device that broadcasts the beacons (e.g., a name of the device, a location of the device, an identifier of a network the device is connected to, etc.).

[0071] As still another example, in an instance in which the one or more position source devices include a device that detects the mobile device in its proximity, the communications can include information associated with detection of the mobile device. Examples of such information can include a timestamp of detection of the mobile device, camera data associated with detection of the mobile device (e.g., camera data captured by a camera of the one or more position source devices that detected the mobile device), Time of Flight (TOF) information, and the like. Additionally or alternatively, the communications can include a location of the one or more position sources devices, such as latitude, longitude, and/or elevation data.

[0072] As still another example, the position information can be received based on communications received and/or transmitted between the mobile device and one or more position source devices capable of making Fine Time Measurements (FTM) or capable of performing ranging. Examples of such position source devices can include RF sensing devices, ETWB devices, WiFi Aps, and the like. For example, in some embodiments, the position information can be based on communications between the mobile device and one or more WiFi APs, where the position information includes an estimate of a distance between the mobile device and each of the one or more WiFi APs based on Round Trip Time (RTT) measurements associated with a round trip time for signal propagation between the mobile device and the WiFi AP. As another example, in some embodiments, the position information can be based on communications between the mobile device and a ETWB device. As a more particular example, in some embodiments, in response to being in proximity to each other, the mobile device and the UWB device can begin performing ranging. Continuing with this more particular example, position information can be calculated based on TOF information that indicates a distance between the mobile device and the UWB device. In some embodiments, the mobile device may determine the position information based on communications received from UWB devices, WiFi APs, or the like. For example, the mobile device may make one or more FTMs based on received communications to determine the position information. 21

[0073] As still another example, the position information can be received as part of a Vehicle-to-Everything (V2X) communication, such as from a vehicle or a mobile device in a vehicle in proximity to the mobile device. In some embodiments, the V2X communication may be received in response to a request from the mobile device. For example, the request may include a request for position information that meets or is below a position uncertainty threshold (e.g., an uncertainty of within 10-30 cm, an uncertainty of less than 10 cm, an uncertainty of less than 5 cm, or the like).

[0074] In some embodiments, the position information can be determined by the mobile device in response to a sensor of the mobile device (e.g., a camera, a LIDAR sensor, an RF sensor, etc.) detecting an external landmark and/or a physical feature of an external landmark. Continuing with this example, the position information can be determined based on a known absolute location of the external landmark or physical feature and a relative position of the mobile device to the external landmark or physical feature. More detailed techniques for determining position information based on sensor data are shown in and described below in connection with FIG. 5.

[0075] It should be noted that, in some embodiments, at block 330, the mobile device can additionally determine an uncertainty associated with the position information. In some embodiments, the uncertainty can indicate an error range associated with the position information, such as +/- 1 centimeter, +/- 5 centimeters, +/- 20 centimeters, and the like. In some embodiments, the uncertainty may be expressed as a Dilution of Precision (DOP). In some embodiments, the uncertainty may be expressed over various axes, such as a Horizontal Dilution of Precision (HDOP), a Vertical Dilution of Precision (VDOP), a Position (3D) Dilution of Precision (PDOP), or the like. In some embodiments, the type of uncertainty calculated may depend on a device type associated with the mobile device. For example, in some embodiments, an HDOP may be calculated for a mobile phone, a wearable computer, an automotive vehicle or the like. As another example, a PDOP may be calculated for an aerial vehicle, such as a manned or unmanned aerial vehicle.

[0076] The uncertainty can be based on various factors. For example, in an instance in which the position information is based on RTK position information and/or an RTK position, the uncertainty can be based on a number of epochs of RTK data received. As a more particular example, the uncertainty can be lower in an instance in which there are 22 relatively more epochs of RTK data than in an instance in which there are fewer epochs of RTK data.

[0077] As another example, in an instance in which the position information is determined based on camera data (e.g., camera data captured by a camera of a position source device as part of detecting the mobile device in proximity to the position source device and/or camera data captured by a camera of the mobile device that includes image data of one or more known physical landmarks), the uncertainty can be determined based on a quality of the camera data. As a more particular example, the uncertainty can be higher in an instance in which the camera data is of lower quality (e.g., blurry, dark, and the like) relative to an instance in which the camera data is of higher quality.

[0078] As yet another example, in an instance in which the position information is determined based on a ranging technique or an indoor positioning technique (e.g., based on RTT or TOF between the mobile device and one or more other devices, such as a WiFi AP and/or a UWB device), the uncertainty can be based on characteristics associated with measurement of a RTT or TOF. For example, in some embodiments, the uncertainty may be based on a duration of time over which ranging was performed, such that the uncertainty is lower when ranging is performed for a longer duration of time. As another example, in some embodiments, the uncertainty may be based on a magnitude of an RTT or a TOF. As a more particular example, in some embodiments, the uncertainty may be proportional to the RTT or the TOF such that the uncertainty is higher for further estimated distances between two devices. As yet another example, in some embodiments, the uncertainty may be based on a variance of a set of RTT or TOF measurements, such that the uncertainty is proportional to the variance.

[0079] At block 340, the functionality comprises determining, by the mobile device, whether to use the position information. Means for performing the functionality at block 340 may comprise a processing unit of a mobile device, and/or other components of a mobile device, as illustrate in FIG. 7.

[0080] In some embodiments, the mobile device can determine whether to use the position information based on the uncertainty associated with the position information. For example, in some embodiments, the mobile device can determine that the position information is to be used (“yes” ^at 340) in response to determining that the uncertainty meets or is below a threshold. -23-

[0081] The threshold may be based on various criteria. For example, in some embodiments, the threshold may be a predetermined threshold (e.g., < 5 centimeters, < 10 centimeters, < 20 centimeters, or the like). As another example, in some embodiments, the threshold may be based on a device type of the mobile device. As a more particular example, different thresholds may be used for different device types, such as a mobile phone, a wearable computer, a computing device associated with a vehicle, or the like. As another more particular example, different thresholds may be used for devices associated with different types of vehicles, such as a non-autonomous vehicle, an autonomous vehicle, an aerial vehicle, an unmanned aerial vehicle, or the like. As yet another example, in some embodiments, the threshold may be based on an application type of an application executing on the mobile device, such as an application requesting or using the one or more PPP positions of the mobile device. As a more particular example, in some embodiments, different thresholds may be used for different application types, such as a map application, an e-commerce application, a social media application, or the like. As still another example, in some embodiments, the threshold may be based on a requested or desired accuracy by the mobile device.

[0082] In some embodiments, the mobile device can determine whether to use the position information based whether the initial estimate of the PPP position(s) of the mobile device is associated with an uncertainty that exceeds the uncertainty of the position information. For example, in some embodiments, in an instance in which the uncertainty exceeds the uncertainty associated with the initial estimate of the PPP position(s) (e.g., as determined at block 320), the mobile device can determine that the position information is not to be used (“no” at block 340). Conversely, in some embodiments, in an instance in which the uncertainty does not exceed the uncertainty associated with the initial estimate of the PPP position(s) (e.g., as determined at block 320), the mobile device can determine that the position information is to be used (“yes” at block 340). That is, in some embodiments, the mobile device can determine that the position information is to be used if the position information is, by some metric, determined to be more accurate that the current estimated PPP position(s).

[0083] It should be noted that, in some embodiments, block 340 can be omitted. For example, in some embodiments, block 340 can be omitted in instances in which the position information is requested based on an accuracy of the one or more position source devices that provided the position information. As a more particular example, in an -24- instance in which the one or more position source devices are selected at block 330 due to a presumed accuracy of position information provided by the selected one or more position source devices, block 340 may be omitted.

[0084] If, at block 340, it is determined that the position information is not to be used (“no” at block 340), method 300 can proceed to block 360 and can determine whether convergence has been reached.

[0085] Conversely, if, at block 340, it is determined that the position information is to be used (“yes” at block 340), method 300 can proceed to block 350 and can use the position information to update the one or more PPP positions of the mobile device.

[0086] At block 350, the functionality comprises generating one or more updated PPP positions of the mobile device using the position information. Means for performing the functionality at block 350 may comprise a processing unit of a mobile device, and/or other components of a mobile device, as illustrated in FIG. 7.

[0087] In some embodiments, one or more updated PPP positions may be generated by constraining a covariance matrix of a Kalman Filter used to determine the one or more PPP positions. That is, in some embodiments, the position information may be provided as priors for the Kalman Filter that serve to constrain the covariance matrix. As another example, in some embodiments, the one or more updated PPP positions may be generated by resampling particles associated with a particle filter based on the position information to determine the one or more PPP positions. As a more particular example, in some embodiments, an importance weight associated with each particle may be updated based on the position information, and the particles may be resampled based on the importance weights.

[0088] At block 360, the functionality comprises determining convergence has been reached. Means for performing the functionality of block 360 may comprise a processing unit of a mobile device, and/or other components of a mobile device, as illustrated in FIG. 7.

[0089] In some embodiments, determination of whether convergence has been reached can be based on determining whether the one or more PPP positions meet or are below one or more convergence thresholds. -25-

[0090] In some embodiments, the one or more convergence thresholds may correspond to a requested or desired accuracy of the one or more PPP positions. For example, in some embodiments, a determination that convergence has been reached can be made in response to determining that an uncertainty of the one or more PPP positions meets or is less than a desired accuracy requested by the mobile device. Examples of desired accuracy may include 10-20 centimeters HDOP, less than 10 centimeters PDOP, less than 50 centimeters HDOP, or the like.

[0091] It should be noted that, in some embodiments, the requested accuracy may depend on a device type associated with the mobile device. For example, a device associated with an automotive vehicle may request a particular HDOP (e.g., between 10 - 20 centimeters, between 10 - 50 centimeters, or the like), whereas a device associated with an aerial vehicle may request a particular PDOP (e.g., less than 10 centimeters, less than 15 centimeters, or the like). In some embodiments, the requested accuracy may be based on an application executing on the mobile device. Additionally or alternatively, in some embodiments, the requested accuracy may be based on a task being performed by the mobile device. Examples of tasks may include updating or presenting a map, providing navigation results, identifying a location of another mobile device in proximity, or the like.

[0092] In some embodiments, determining whether the one or more PPP positions meet or are below the one or more convergence thresholds may include determining whether an estimator used to determine the one or more PPP positions has reached a steady state status. For example, in an instance in which the one or more PPP positions are determined using an Kalman Filter, a determination that a steady status has been reached can be made in response to determining that values of a covariance matrix associated with the Kalman Filter have changed by less than a predetermined threshold (e.g., less than 10%, less than 5%, or the like) over a time window (e.g, over the past one minute, over the past thirty seconds, over the past five seconds, or the like). As another example, in an instance in which the one or more PPP positions are determined using a particle filter, a determination that a steady state status has been reached can be made in response to determining that probabilities associated with one or more particles have not changed by more than a predetermined threshold (e.g., less than 10%, less than 5%, or the like) over a time window (e.g., over the past one minute, over the past thirty seconds, over the past five seconds, or the like).. -26-

[0093] It should be noted that, in some embodiments, by using position information at block 350 to generate the one or more updated PPP positions, an estimator (e.g., a Kalman Filter, a particle filter, or the like) may converge. In some such embodiments, block 360 may be omitted. For example, in an instance in which the position information has an accuracy within a desired accuracy range corresponding to the convergence threshold, the convergence threshold may be reached when the position information is used to constrain the estimator. As a more particular example, in an instance in which the desired accuracy is within 10 centimeters, and in which the accuracy of the position information is within 5 centimeters, by providing the position information to the estimator (e.g., at block 350), a predicted state by the estimator is constrained to within the desired accuracy of 10 centimeters.

[0094] If, at block 360, it is determined that convergence has not been reached (“no” at 360), method 300 can loop back to block 320 and can estimate updated PPP positions of the mobile device. For example, subsequent predictions at a next time step can be made based on the current estimated one or more PPP positions.

[0095] Conversely, if, at block 360, it is determined that convergence has been reached (“yes” at 360), method 300 can proceed to block 370.

[0096] At block 370, the functionality comprises providing at least one PPP position of the mobile device. Means for performing the functionality of block 370 may comprise a processing unit of a mobile device, a display of a mobile device (e.g., to display a map that indicate the at least one PPP position), and/or other components of the mobile device, as illustrated in FIG. 7.

[0097] For example, in some embodiments, the mobile device can present a map that indicates the at least one PPP position. As another example, the mobile device can transmit a message to another device (e.g., another mobile device, a server, etc.) that indicates the at least one PPP position.

[0098] FIG. 4 is an information flow diagram of a method 400 of determining position information, according to an embodiment. Means for performing the functionality illustrated in one or more of the blocks shown in FIG. 4 may be performed by hardware and/or software components of a mobile device and/or a position source device (e.g., an IoT device, a wireless beacon device, and the like). Example components of a mobile device are illustrated in FIG. 7, which are described in more detail below -27-

[0099] At block 410, the functionality comprises the position source device detecting the mobile device in proximity to the position source device. Means for performing the functionality of block 410 may comprise a processing unit of a position source device, one or more sensors (e.g., a camera, a motion sensor, etc.) of a position source device, and/or other components of the position source device, as illustrated in FIG. 7.

[0100] In some embodiments, the position source device can detect the mobile device based on a sensor, such as a camera associated with the position source device, a motion detection sensor associated with the position source device, etc.

[0101] For example, a position source device may capture or obtain camera data that includes one or more images that indicate a presence of the mobile device. As a more particular example, in an instance in which the mobile device is physically associated with (e.g., in or on) a vehicle, the position source device may capture camera data that includes at least a portion of the vehicle (e.g., a front portion of the vehicle, a license plate of the vehicle, a top portion of the vehicle, and the like). Examples of position source devices associated with a camera can include a traffic camera, a camera at a toll booth, a camera at an intersection or stoplight, a security camera, and the like.

[0102] As another example, a position source device may detect the mobile device based on a detection of a tag that has been paired with the mobile device. Examples of such position source devices may include a scanning device at a toll booth that detects E- Z pass toll tags, a scanning device associated with an electronic payment system, a proximity detector that can detect a tag that broadcasts identifying information, and the like.

[0103] It should be noted that, in some embodiments, block 410 can be omitted. For example, in some embodiments, a position source device may transmit messages to the mobile device (e.g., as described below in connection with block 420) without first detecting the mobile device. For example, in some embodiments, such a position source device may periodically broadcast messages rather than transmitting a message in response to a detection of a mobile device.

[0104] At block 420, the functionality comprises transmitting a message to the mobile device. Means for performing the functionality of block 420 can include a processing unit of a position source device, a wireless communication interface of a position source device, and/or other components of the position source device, as shown in FIG. 7. -28-

[0105] In some embodiments, the message transmitted to the mobile device can include location information associated with the position source device, such as latitude, longitude, or elevation information indicating a location of the position source device.

[0106] In some embodiments, in an instance in which the message is transmitted to the mobile device in response to the position source device detecting the mobile device (e.g., at block 410), the message can indicate information associated with the detection, such as a timestamp associated with a time at which the mobile device was detected, camera data associated with the detection, and the like.

[0107] In some embodiments, the message can indicate a relative position of the mobile device to the position source device. For example, in an instance in which the position source device detected the mobile device via captured camera data, the relative position of the mobile device to the position source device can be determined based on a field of view of the camera associated with the position source device. As a more particular example, in an instance in which the mobile device is associated with a vehicle, and in which the mobile device is detected based on camera data obtained by the position source device that includes at least a portion of the vehicle, the relative position of the mobile device to the position source device can be determined based on a position of the portion of the vehicle within the camera image data relative to the field of view of the camera.

[0108] At block 430, the functionality comprises receiving, by the mobile device, the message from the position source device. Means for performing the functionality of block 430 can include a processing unit of the mobile device, a wireless communication interface of the mobile device, and/or other components of the mobile device, as shown in FIG. 7.

[0109] It should be noted that, in some embodiments, the message may be received by an application executing on the mobile device. For example, in an instance in which the position source device is a scanning device associated with a toll booth, the message may be received by an application executing on the mobile device that is provided by an entity that operates the toll booth and/or that has been previously paired or associated with the scanning device or the toll booth. As another example, in an instance in which the position source device is a scanning device associated with an electronic payment system, -29- the message may be received by an application executing on the mobile device that is associated with the electronic payment system.

[0110] At block 440, the functionality comprises determining position information based on the received message. Means for performing the functionality of block 440 can include a processing unit of the mobile device, and/or other components of the mobile device, as shown in FIG. 7.

[0111] In some embodiments, the position information can be determined by extracting information included in the message received by the mobile device from the position source device.

[0112] Additionally or alternatively, in some embodiments, the mobile device can determine the position information by combining various pieces of information included in the message received from the position source device. For example, in an instance in which the message includes an absolute position or location of the position source device, and in which the message includes information indicating a relative position of the mobile device with respect to the position source device, the mobile device can determine an estimated absolute position of the mobile device by combining the relative position of the mobile device with respect to the position source device and the absolute position or location of the position source device.

[0113] At block 450, the functionality comprises determining an uncertainty associated with the determined position information. Means for performing the functionality of block 450 can include a processing unit of the mobile device, and/or other components of the mobile device, as shown in FIG. 7.

[0114] In some embodiments, the uncertainty can indicate an error range of the position information. The uncertainty may be expressed as a DOP value, such as an HDOP value, a VDOP value, a PDOP value, or the like. For example, the uncertainty can indicate that the position information is within about +/- 10 centimeters, within about +/- 50 centimeters, or the like.

[0115] In some embodiments, the uncertainty can be determined based on a quality of information included in the message received from the position source device at block 430. For example, in an instance in which the position information is determined based on camera data captured by a camera associated with the position source device, the -30- uncertainty can be based on a quality of the camera data. As a more particular example, the uncertainty can be based on whether the camera data is blurry, dark, etc.

[0116] As another example, in some embodiments, the uncertainty can be determined based on a device type associated with the position source device. For example, in some embodiments, lower uncertainty values can be assigned to particular device types relative to other device types. As a more particular example, an uncertainty value associated with position information received from a toll booth camera may be lower than an uncertainty value associated with position information received from a wireless beacon device.

[0117] Additional criteria associated with a determination of the uncertainty of the position information are described above in connection with block 330 of FIG. 3.

[0118] It should be noted that, in some embodiments, the uncertainty can be determined by the position source device. In some such embodiments, an uncertainty value may be received by the mobile device, for example, in the message received at block 430 from the position source device.

[0119] It should be noted that the position information determined at block 440 and/or the uncertainty determined at block 450 may be used to determine whether to use the position information to generate one or more PPP positions of the mobile device, as shown in and described above in connection with FIG. 3 and/or as shown in and described below in connection with FIG. 6.

[0120] FIG. 5 is a flow diagram of a method 500 of determining position information based on sensor data, according to an embodiment. Means for performing the functionality illustrated in one or more of the blocks shown in FIG. 5 may be performed by hardware and/or software components of a mobile device, and/or by hardware and/or software components of a server. Example components of a mobile device are illustrated in FIG. 7, which are described in more detail below.

[0121] At block 510, the functionality comprises obtaining, by a mobile device, sensor data. The sensor data can include camera data, RF sensing data, LIDAR data, or the like. In some embodiments, the sensor data can include any combination of camera data, RF sensing data, LIDAR data, or the like. Means for performing the functionality can include sensor(s) of a mobile device (e.g., one or more cameras of the mobile device, one or more LIDAR sensors associated with the mobile device, one or more RF sensing -31- devices associated with the mobile device, or the like), a processing unit of a mobile device, and/or other components of the mobile device, as shown in FIG. 7. In instances in which the mobile device is a vehicle, the means for performing the functionality can include cameras associated with the vehicle, LIDAR associated with the vehicle, RF sensing devices associated with the vehicle, and/or other sensors.

[0122] In some embodiments, the sensor data can be captured automatically. For example, in some embodiments, the sensor data may be captured regularly, such as at periodic intervals. Alternatively, in some embodiments, the sensor data may be captured in response to a trigger. In some embodiments, the trigger may include an explicit user instruction to capture the sensor data, a determination that position information has not been updated in more than a predetermined amount of time (e.g., in more than five minutes, in more than ten minutes, etc.), and the like.

[0123] At block 520, the functionality comprises identifying one or more physical features of one or more physical landmarks based on the sensor data. Means for performing the functionality can include a processing unit of a mobile device, and/or other components of a mobile device, as shown in FIG. 7. It should be noted that in instances in which the physical landmark is identified at a server, means for performing the functionality can include a processing unit of the server.

[0124] Examples of physical landmarks can include a statue, a particular building (e.g., an office building, a residential building, a school, a library, a landmark building, etc.), a street sign, a highway sign, and the like. Examples of physical features can include components of a building (a spire of a building, a roof of a building, a window of a building, a hallway or corridor of a building, or the like), components of a statue (e.g., a head of the statue, a torso of the statue, or the like), and/or any other suitable physical features.

[0125] The physical features may be identified using various image processing techniques or other processing techniques. For example, camera data may be processed using various image processing techniques (e.g., depth estimation, object segmentation, etc.). Continuing with this example, a physical feature present in camera data may be identified by, e.g., comparing portions of the image data to a database of known physical landmarks. As another example, LIDAR data may be processed to generate a 3-D representation of the LIDAR data. Continuing with this example, in some embodiments, -32- the physical features may be identified by using any suitable processing or analysis of the 3-D representation of the LIDAR data. As a more particular example, in some embodiments, portions of the 3-D representation may be segmented to identify objects in the 3-D representation. Continuing with this particular example, in some embodiments, physical features of particular physical landmarks may be identified by comparing the identified objects to a database of known physical landmarks.

[0126] It should be noted that, in some embodiments, various text processing techniques may be applied to camera data to, for example, identify text of signs associated with a physical landmark. The identified text can then be used to identify the physical landmark. For example, text of a highway sign that indicates an exit number associated with the highway sign may be identified. As another example, text of a sign associated with a building may be identified to determine an address of the building, a name of the building, etc. In some embodiments, identified text may be used to identify the physical landmark. For example, a specific building may be identified based on text included in the camera data that indicates an address of the specific building.

[0127] At block 530, the functionality comprises identifying a location of the physical landmark or of the physical features of the physical landmark. Means for performing the functionality can include a processing unit of the mobile device, and/or other components of a mobile device, as shown in FIG. 7. It should be noted that in instances in which the position information associated with the physical landmark is identified at a server, the means for performing the functionality can include a processing unit of the server.

[0128] In some embodiments, the location can indicate an absolute location of the physical landmark. In some embodiments, the absolute location of the physical landmark or of the physical feature of the physical landmark can be retrieved, for example, from a database that stores known locations of various physical landmarks. For example, in an instance in which the physical landmark corresponds to a building (e.g., a building having a particular shape or faqade that was identified based on the sensor data, a building having a particular address that was identified in text of the camera data, etc.), the absolute location of the building can be retrieved from a map database.

[0129] It should be noted that such a database may be stored on any suitable device. For example, the database may be stored in memory of the mobile device. As a more particular example, a database that includes physical landmarks frequently passed by the -33- mobile device may be stored in memory of the mobile device. As another more particular example, a database that includes physical landmarks that are waypoints on a planned trip may be stored in memory of the mobile device. It should be noted that such a database may be curated via explicit user input and/or curated via a machine learning algorithm that identifies commonly passed physical landmarks or the like. Additionally or alternatively, in some embodiments, such a database may be stored on a server, and the database may be queried by the mobile device and/or by a server to identify the position information of the physical landmark.

[0130] It should be noted that, in some embodiments, the physical landmark may be identified at a server rather than at the mobile device. In some such embodiments, the mobile device may transmit the image data to the server (e.g., via a wireless communication network) for processing at block 520. Similarly, in some embodiments, the position information associated with the physical landmark may be identified at a server rather than at the mobile device. In some such embodiments, the mobile device may receive the position information from the server (e.g., via a wireless communication network) at block 530.

[0131] At block 540, the functionality comprises determining position information of the mobile device based on the one or more locations of the one or more physical features and/or of the one or more physical landmarks. Means for performing the functionality can include a processing unit of a mobile device, and/or other components of the mobile device, as shown in FIG. 7.

[0132] In some embodiments, the position information of the mobile device may be determined by combining the location of the physical feature(s) or of the physical landmark(s) with information indicating a relative position of the mobile device to the physical feature(s) or to the physical landmark(s). For example, in some embodiments, the sensor data can indicate a distance of the mobile device to the physical feature(s) or to the physical landmark(s) and/or a direction of the mobile device from the physical feature(s) or to the physical landmark(s). Continuing with this example, the position information of the mobile device may be determined by calculating an absolute location of the mobile device based on the distance of the mobile device to the physical feature(s) or to the physical landmark(s) in the direction of the mobile device from the physical feature(s) or to the physical landmark(s). -34-

[0133] It should be noted that the position information determined at block 540 may be used to determine the one or more PPP positions of the mobile device, as shown in and described above in connection with FIG. 3.

[0134] FIG. 6 is a flow diagram of a method 600 of determining position information, according to an embodiment. Means for performing the functionality illustrated in one or more of the blocks shown in FIG. 6 may be performed by hardware and/or software components of a mobile device. Example components of a mobile device are illustrated in FIG. 7, which are described in more detail below.

[0135] At block 610, the functionality comprises obtaining one or more GNSS signals. Means for performing the functionality at block 610 may comprise a GNSS receiver of a mobile device, a processing unit of a mobile device, and/or other components of a mobile device, as illustrated in FIG. 7.

[0136] The one or more GNSS signals may correspond to one or more multi constellation, multi-band signals. The one or more multi-constellation, multi-band signals may be GNSS data that is based on data from one or more satellites. The one or more multi-constellation, multi-band signals may be used to provide absolute position information of latitude, longitude, and/or elevation.

[0137] At block 620, the functionality comprises obtaining, by the mobile device, position information based on one or more position sources, where the position information is indicative of a location of the mobile device. Means for performing the functionality include a processing unit of a mobile device, and/or other components of a mobile device, as shown in FIG. 7.

[0138] As described above in connection with FIGS. 2-5, the position information may include position information received from one or more position source devices (e.g., wireless cellular network base stations, wireless base stations that provide RTK data, IoT devices, wireless beacon devices, UWB devices that are configured to perform ranging, RF sensing devices, WiFi APs, etc.). Additionally or alternatively, in some embodiments, the position information may include position information obtained by one or more sensors of the mobile device, as shown in and described above in connection with FIG. 5. -35-

[0139] At block 630, the functionality comprises determining one or more PPP positions of the mobile device based on the position information and the one or more GNSS signals, wherein a position uncertainty of the position information meets or is below an uncertainty threshold. Means for performing the functionality include a processing unit of a mobile device, and/or other components of the mobile device, as shown in FIG. 7.

[0140] As described above in connection with FIGS. 2 and 3, the one or more PPP positions may be determined using an estimator (e.g., a Kalman Filter, an Extended Kalman Filter, an Unscented Kalman Filter, a particle filter, or the like) to iteratively update predicted states that correspond to the one or more PPP positions. In some embodiments, the position information may be used to determine the one or more PPP positions by constraining a covariance matrix associated with a Kalman Filter, by resampling particles of a particle filter based on the position information, or the like.

[0141] At block 640, the functionality comprises determining whether at least one of the one or more PPP positions meet or are below one or more convergence threshold(s). Means for performing the functionality include a processing unit of a mobile device, and/or other components of the mobile device, as shown in FIG. 7.

[0142] As described above in connection with FIG. 3, the one or more convergence thresholds may be based on a requested accuracy of the mobile device. For example, in some embodiments, it can be determined that at least one of the one or more PPP positions meet or is below the one or more convergence thresholds in response to determining that the at least one PPP position meets or is below the requested accuracy of the mobile device. As a more particular example, in an instance in which the mobile device is an automotive device that has requested an accuracy of 10-20 centimeters HDOP, it can be determined that the at least one PPP position meets or is below the one or more convergence thresholds in response to determining that the at least one PPP position has an uncertainty less than the requested 10-20 centimeters HDOP.

[0143] As another example, in some embodiments, it can be determined that the at least one PPP position of the one or more PPP positions meets or is below the one or more convergence thresholds in response to determining that an estimator used to determine the one or more PPP positions has reached a steady state status. As a more particular example, a steady state status may be identified based on a determination that a covariance -36- matrix associated with a Kalman Filter has changed by less than a predetermined threshold over a time window. As another more particular example, a steady state status may be identified based on a determination that probabilities of particles associated with a particle filter have changed by less than a predetermined threshold over a time window.

[0144] If, at block 640, it is determined that the at least one PPP position of the one or more PPP positions exceeds the one or more convergence thresholds (“no” at 640), method 600 can loop back to block 630 and can update the determination of the one or more PPP positions of the mobile device. It should be noted that, in some embodiments, the updated one or more PPP positions may be determined based on additional one or more GNSS signals and/or additional position information. That is, in some embodiments, method 600 can loop back to block 610 and/or block 620.

[0145] Conversely, if at block 640, it is determined that the at least one PPP position of the one or more PPP positions meets or is below the one or more convergence thresholds (“yes” at block 640), method 600 can proceed to block 650.

[0146] The functionality of block 650 comprises providing the at least one PPP position of the mobile device. Means for performing the functionality of block 650 include a processing unit of the mobile device, a display of the mobile device (e.g., for presenting a map that indicates the at least one PPP position of the mobile device), and/or other components of the mobile device, as shown in FIG. 7.

[0147] In some embodiments, the at least one PPP position can be provided via a map presented by the mobile device. As another example, in some embodiments, the at least one PPP position can be transmitted from the mobile device to another device (e.g., another mobile device, a server, etc.).

[0148] FIG. 7 illustrates an embodiment of a mobile device 105, which can be utilized as described herein above (e.g., in association with FIGS. 1-6). For example, the mobile device 105 can perform one or more of the functions of the methods shown in FIGS. 3, 4, 5, and/or 6. It should be noted that FIG. 7 is meant only to provide a generalized illustration of various components, any or all of which may be utilized as appropriate. It can be noted that, in some instances, components illustrated by FIG. 7 can be localized to a single physical device and/or distributed among various networked devices, which may be disposed at different physical locations. Furthermore, as previously noted, the functionality of the mobile discussed in the previously described -37- embodiments may be executed by one or more of the hardware and/or software components illustrated in FIG. 7.

[0149] The mobile device 105 is shown comprising hardware elements that can be electrically coupled via a bus 705 (or may otherwise be in communication, as appropriate). The hardware elements may include a processing unit(s) 710 which can include without limitation one or more general-purpose processors, one or more special- purpose processors (such as digital signal processor (DSP) chips, graphics acceleration processors, application specific integrated circuits (ASICs), and/or the like), and/or other processing structures or means. As shown in FIG. 7, some embodiments may have a separate DSP 720, depending on desired functionality. Location determination and/or other determinations based on wireless communication may be provided in the processing unit(s) 710 and/or wireless communication interface 730 (discussed below). The mobile device 105 also can include one or more input devices 770, which can include without limitation one or more keyboards, touch screens, touch pads, microphones, buttons, dials, switches, and/or the like; and one or more output devices 715, which can include without limitation one or more displays (e.g., touch screens), light emitting diodes (LEDs), speakers, and/or the like.

[0150] The mobile device 105 may also include a wireless communication interface 730, which may comprise without limitation a modem, a network card, an infrared communication device, a wireless communication device, and/or a chipset (such as a Bluetooth® device, an IEEE 802.11 device, an IEEE 802.15.4 device, a WiFi device, a WiMAX device, a WAN device, and/or various cellular devices, etc.), and/or the like, which may enable the mobile device 105 to communicate with other devices as described in the embodiments above. The wireless communication interface 730 may permit data and signaling to be communicated (e.g., transmitted and received) with TRPs of a network, for example, via eNBs, gNBs, ng-eNBs, access points, various base stations and/or other access node types, and/or other network components, computer systems, and/or any other electronic devices communicatively coupled with TRPs, as described herein. The communication can be carried out via one or more wireless communication antenna(s) 732 that send and/or receive wireless signals 734. According to some embodiments, the wireless communication antenna(s) 732 may comprise a plurality of discrete antennas, antenna arrays, or any combination thereof. The antenna(s) 732 may be capable of transmitting and receiving wireless signals using beams (e.g., Tx beams and -38-

Rx beams). Beam formation may be performed using digital and/or analog beam formation techniques, with respective digital and/or analog circuitry. The wireless communication interface 730 may include such circuitry.

[0151] Depending on desired functionality, the wireless communication interface 730 may comprise a separate receiver and transmitter, or any combination of transceivers, transmitters, and/or receivers to communicate with base stations (e.g., ng-eNBs and gNBs) and other terrestrial transceivers, such as wireless devices and access points. The mobile device 105 may communicate with different data networks that may comprise various network types. For example, a Wireless Wide Area Network (WWAN) may be a CDMA network, a Time Division Multiple Access (TDMA) network, a Frequency Division Multiple Access (FDMA) network, an Orthogonal Frequency Division Multiple Access (OFDMA) network, a Single-Carrier Frequency Division Multiple Access (SC- FDMA) network, a WiMAX (IEEE 802.16) network, and so on. A CDMA network may implement one or more RATs such as CDMA2000, WCDMA, and so on. CDMA2000 includes IS-95, IS-2000 and/or IS-856 standards. A TDMA network may implement GSM, Digital Advanced Mobile Phone System (D-AMPS), or some other RAT. An OFDMA network may employ LTE, LTE Advanced, 5G NR, and so on. 5G NR, LTE, LTE Advanced, GSM, and WCDMA are described in documents from 3GPP. CDMA2000 is described in documents from a consortium named “3rd Generation Partnership Project X3” (3GPP2). 3GPP and 3GPP2 documents are publicly available. A wireless local area network (WLAN) may also be an IEEE 802.1 lx network, and a wireless personal area network (WPAN) may be a Bluetooth ® network, an IEEE 802.15x, or some other type of network. The techniques described herein may also be used for any combination of WWAN, WLAN and/or WPAN.

[0152] The mobile device 105 can further include sensor(s) 740. Sensors 740 may comprise, without limitation, one or more inertial sensors and/or other sensors (e.g., accelerometer(s), gyroscope(s), camera(s), magnetometer(s), altimeter(s), microphone(s), proximity sensor(s), light sensor(s), barometer(s), and the like), some of which may be used to obtain position-related measurements and/or other information.

[0153] Embodiments of the mobile device 105 may also include a GNSS receiver 780 capable of receiving signals 784 from one or more GNSS satellites using an antenna 782 (which could be the same as antenna 732). Positioning based on GNSS signal -39- measurement can be utilized to complement and/or incorporate the techniques described herein. The GNSS receiver 780 can extract a position of the mobile device 105, using conventional techniques, from GNSS satellites 110 of a GNSS system, such as GPS, Galileo, GLONASS, Quasi-Zenith Satellite System (QZSS) over Japan, Indian Regional Navigational Satellite System (IRNSS) over India, BeiDou Navigation Satellite System (BDS) over China, and/or the like. Moreover, the GNSS receiver 780 can be used with various augmentation systems (e.g., a Satellite Based Augmentation System (SB AS)) that may be associated with or otherwise enabled for use with one or more global and/or regional navigation satellite systems, such as, e.g., Wide Area Augmentation System (WAAS), European Geostationary Navigation Overlay Service (EGNOS), Multi functional Satellite Augmentation System (MSAS), and Geo Augmented Navigation system (GAGAN), and/or the like.

[0154] It can be noted that, although GNSS receiver 780 is illustrated in FIG. 7 as a distinct component, embodiments are not so limited. As used herein, the term “GNSS receiver” may comprise hardware and/or software components configured to obtain GNSS measurements (measurements from GNSS satellites). In some embodiments, therefore, the GNSS receiver may comprise a measurement engine executed (as software) by one or more processing units, such as processing unit(s) 710, DSP 720, and/or a processing unit within the wireless communication interface 730 (e.g., in a modem). A GNSS receiver may optionally also include a positioning engine, which can use GNSS measurements from the measurement engine to determine a position of the GNSS receiver using an Extended Kalman Filter (EKF), Weighted Least Squares (WLS), a hatch filter, particle filter, or the like. The positioning engine may also be executed by one or more processing units, such as processing unit(s) 710 or DSP 720.

[0155] The mobile device 105 may further include and/or be in communication with a memory 760. The memory 760 can include, without limitation, local and/or network accessible storage, a disk drive, a drive array, an optical storage device, a solid-state storage device, such as a random access memory (RAM), and/or a read-only memory (ROM), which can be programmable, flash-updateable, and/or the like. Such storage devices may be configured to implement any appropriate data stores, including without limitation, various file systems, database structures, and/or the like. -40-

[0156] The memory 760 of the mobile device 105 also can comprise software elements (not shown in FIG. 7), including an operating system, device drivers, executable libraries, and/or other code, such as one or more application programs, which may comprise computer programs provided by various embodiments, and/or may be designed to implement methods, and/or configure systems, provided by other embodiments, as described herein. Merely by way of example, one or more procedures described with respect to the method(s) discussed above may be implemented as code and/or instructions in memory 760 that are executable by the mobile device 105 (and/or processing unit(s) 710 or DSP 720 within mobile device 105). In an aspect, then such code and/or instructions can be used to configure and/or adapt a general-purpose computer (or other device) to perform one or more operations in accordance with the described methods.

[0157] With reference to the appended figures, components that can include memory can include non-transitory machine-readable media. The term “machine-readable medium” and “computer-readable medium” as used herein, refer to any storage medium that participates in providing data that causes a machine to operate in a specific fashion. In embodiments provided hereinabove, various machine-readable media might be involved in providing instructions/code to processing units and/or other device(s) for execution. Additionally or alternatively, the machine-readable media might be used to store and/or carry such instructions/code. In many implementations, a computer-readable medium is a physical and/or tangible storage medium. Such a medium may take many forms, including but not limited to, non-volatile media and volatile media. Common forms of computer-readable media include, for example, magnetic and/or optical media, any other physical medium with patterns of holes, a RAM, a programmable ROM (PROM), erasable PROM (EPROM), a FLASH-EPROM, any other memory chip or cartridge, or any other medium from which a computer can read instructions and/or code.

[0158] The methods, systems, and devices discussed herein are examples. Various embodiments may omit, substitute, or add various procedures or components as appropriate. For instance, features described with respect to certain embodiments may be combined in various other embodiments. Different aspects and elements of the embodiments may be combined in a similar manner. The various components of the figures provided herein can be embodied in hardware and/or software. Also, technology evolves and, thus many of the elements are examples that do not limit the scope of the disclosure to those specific examples. -41-

[0159] It has proven convenient at times, principally for reasons of common usage, to refer to such signals as bits, information, values, elements, symbols, characters, variables, terms, numbers, numerals, or the like. It should be understood, however, that all of these or similar terms are to be associated with appropriate physical quantities and are merely convenient labels. Unless specifically stated otherwise, as is apparent from the discussion above, it is appreciated that throughout this Specification discussion utilizing terms such as “processing,” “computing,” “calculating,” “determining,” “ascertaining,” “identifying,” “associating,” “measuring,” “performing,” or the like refer to actions or processes of a specific apparatus, such as a special purpose computer or a similar special purpose electronic computing device. In the context of this Specification, therefore, a special purpose computer or a similar special purpose electronic computing device is capable of manipulating or transforming signals, typically represented as physical electronic, electrical, or magnetic quantities within memories, registers, or other information storage devices, transmission devices, or display devices of the special purpose computer or similar special purpose electronic computing device.

[0160] Terms, “and” and “or” as used herein, may include a variety of meanings that also is expected to depend, at least in part, upon the context in which such terms are used. Typically, “or” if used to associate a list, such as A, B, or C, is intended to mean A, B, and C, here used in the inclusive sense, as well as A, B, or C, here used in the exclusive sense. In addition, the term “one or more” as used herein may be used to describe any feature, structure, or characteristic in the singular or may be used to describe some combination of features, structures, or characteristics. However, it should be noted that this is merely an illustrative example and claimed subject matter is not limited to this example. Furthermore, the term “at least one of’ if used to associate a list, such as A, B, or C, can be interpreted to mean any combination of A, B, and/or C, such as A, AB, AA, AAB, AABBCCC, etc.

[0161] Having described several embodiments, various modifications, alternative constructions, and equivalents may be used without departing from the scope of the disclosure. For example, the above elements may merely be a component of a larger system, wherein other rules may take precedence over or otherwise modify the application of the various embodiments. Also, a number of steps may be undertaken before, during, or after the above elements are considered. Accordingly, the above description does not limit the scope of the disclosure. -42-

[0162] In view of this description embodiments may include different combinations of features. Implementation examples are described in the following numbered clauses:

Clause 1: A method of determining a Precise Point Positioning (PPP) position, comprising: obtaining, by a mobile device, one or more Global Navigation Satellite System (GNSS) signals; obtaining, by the mobile device, position information based on one or more position sources, wherein the position information is indicative of a location of the mobile device; determining one or more Precise Point Positioning (PPP) positions of the mobile device based on the position information and the one or more GNSS signals, wherein a position uncertainty of the position information meets or is below an uncertainty threshold; determining whether at least one PPP position meets or is below one or more convergence thresholds; and in response to determining that at least one PPP position meets or is below the one or more convergence thresholds, providing the at least one PPP position.

Clause 2: The method of clause 1, wherein the one or more position sources comprise one or more of: a wireless base station, a wireless Access Point (AP), an Ultra Wide Bandwidth (UWB) device, a Radio Frequency (RF) sensing device, a LIDAR device, or an Internet of Things (IoT) device.

Clause 3: The method of clause 2, wherein the wireless base station provides Real

Time Kinematics (RTK) position information.

Clause 4: The method of clause 3, further comprising determining an RTK position based on the RTK position information.

Clause 5: The method of any of clauses 1-4, wherein obtaining the position information comprises determining, by the mobile device, the position information using: Fifth Generation (5G) signals, UWB signals, WiFi signals, Fine Timing Measurements (FTM) or any combination thereof.

Clause 6: The method of any of clauses 1-5, wherein the position information is received by the mobile device in a Vehicle to Everything (V2X) message.

Clause 7: The method of any of clauses 1-6, wherein the one or more GNSS signals are multi-constellation and multi-band signals. -43-

Clause 8: The method of any of clauses 1-7, wherein the uncertainty threshold is based on: a device type of the mobile device, an application type of an application executing on the mobile device, a requested accuracy by the mobile device, a requested accuracy by an application executing on the mobile device, a predetermined threshold, or any combination thereof.

Clause 9: The method of any of clauses 1-8, wherein the uncertainty threshold is between 10 and 30 centimeters.

Clause 10: The method of any of clauses 1-8, wherein the uncertainty threshold is between 30 and 50 centimeters.

Clause 11: The method of any of clauses 1-10, wherein determining the one or more PPP positions of the mobile device comprises constraining a covariance matrix associated with a Kalman filter.

Clause 12: The method of clause 11, wherein determining whether the at least one PPP position meets or is below the one or more convergence thresholds comprises determining whether values of the covariance matrix have changed over a time window.

Clause 13: The method of any of clauses 1-12, wherein determining the one or more PPP positions of the mobile device comprises using the position information to resample particles used by a particle filter.

Clause 14: The method of any of clauses 1-13, wherein determining the position information comprises: obtaining, by the mobile device, sensor data, wherein the sensor data comprises camera data, RF sensing data, LIDAR data or any combination thereof; identifying one or more physical features of one or more landmarks based on the sensor data; and determining the position information based on one or more locations of the one or more physical features.

Clause 15: The method of any of clauses 1-14, wherein determining the position information comprises: receiving a message from a position source device, wherein the message is transmitted by the position source device in response to detection of the mobile device; and determining the position information based on the message. -44-

Clause 16: The method of clause 15, wherein determining the position information comprises retrieving a stored location of the position source device from a memory of the mobile device.

Clause 17: The method of clause 15 or 16, wherein the message indicates an identifier of the position source device.

Clause 18: The method of any of clauses 1-17, wherein obtaining the position information comprises: determining whether to request the position information from one or more position source devices; and in response to determining that the position information is to be requested, requesting the position information.

Clause 19: The method of clause 18, wherein determining whether to request the position information from the one or more position sources devices comprises selecting at least one position source device based on: an accuracy of position information provided by the at least one position source device, information that indicates that the position uncertainty of position information provided by the at least one position source device meets or is below the uncertainty threshold, a cost of position information provided by the at least one position source device, or any combination thereof.

Clause 20: The method of clause 18 or 19, wherein requesting the position information comprises requesting position information such that the position uncertainty of the position information meets or is below the uncertainty threshold.

Clause 21: A mobile device for determining a Precise Point Positioning (PPP) position, comprising: a GNSS receiver; a memory; and one or more processing units communicatively coupled with the GNSS receiver and the memory, the one or more processing units configured to: obtain, via the GNSS receiver, one or more Global Navigation Satellite System (GNSS) signals; obtain position information based on one or more position sources, wherein the position information is indicative of a location of the mobile device; determine one or more Precise Point Positioning (PPP) positions of the mobile device based on the position information and the one or more GNSS signals, wherein a position uncertainty of the position information meets or is below an uncertainty -45- threshold; determine whether at least one PPP position meets or is below one or more convergence thresholds; and in response to determining that at least one PPP position meets or is below the one or more convergence thresholds, provide the at least one PPP position.

Clause 22: The mobile device of clause 21, wherein the one or more position sources comprise one or more of: a wireless base station, a wireless Access Point (AP), an Ultra Wide Bandwidth (UWB) device, a Radio Frequency (RF) sensing device, a LIDAR device, or an Internet of Things (IoT) device.

Clause 23: The mobile device of clause 22, wherein the wireless base station provides Real Time Kinematics (RTK) position information.

Clause 24: The mobile device of clause 23, where the one or more processing units are further configured to determine an RTK position based on the RTK position information.

Clause 25: The mobile device of any of clauses 21-24, wherein obtaining the position information comprises determining, by the mobile device, the position information using: Fifth Generation (5G) signals, UWB signals, WiFi signals, Fine Timing Measurements (FTM) or any combination thereof.

Clause 26: The mobile device of any of clauses 21-25, wherein the position information is received by the mobile device in a Vehicle to Everything (V2X) message.

Clause 27: The mobile device of any of clauses 21-26, wherein the one or more GNSS signals are multi-constellation and multi-band signals.

Clause 28: The mobile device of any of clauses 21-27, wherein the uncertainty threshold is based on: a device type of the mobile device, an application type of an application executing on the mobile device, a requested accuracy by the mobile device, a requested accuracy by an application executing on the mobile device, a predetermined threshold, or any combination thereof.

Clause 29: The mobile device of any of clauses 21-28, wherein the uncertainty threshold is between 10 and 30 centimeters. -46-

Clause 30: The mobile device of any of clauses 21-28, wherein the uncertainty threshold is between 30 and 50 centimeters.

Clause 31: The mobile device of any of clauses 21-30, wherein determining the one or more PPP positions of the mobile device comprises constraining a covariance matrix associated with a Kalman filter.

Clause 32: The mobile device of clause 31, wherein to determine whether the at least one PPP position meets or is below the one or more convergence thresholds, the one or more processing units are configured to determine whether values of the covariance matrix have changed over a time window.

Clause 33: The mobile device of any of clauses 21-32, wherein to determine the one or more PPP positions of the mobile device, the one or more processing units are configured to use the position information to resample particles used by a particle filter.

Clause 34: The mobile device of any of clauses 21-33, wherein to determine the position information, the one or more processing units are configured to: obtain, by the mobile device, sensor data, wherein the sensor data comprises camera data, RF sensing data, LIDAR data or any combination thereof; identify one or more physical features of one or more landmarks based on the sensor data; and determine the position information based on one or more locations of the one or more physical features.

Clause 35: The mobile device of any of clauses 21-34, wherein to determine the position information, the one or more processing units are configured to: receive a message from a position source device, wherein the message is transmitted by the position source device in response to detection of the mobile device; and determine the position information based on the message.

Clause 36: The mobile device of clause 35, wherein to determine the position information, the one or more processing units are configured to retrieve a stored location of the position source device from a memory of the mobile device.

Clause 37: The mobile device of clauses 35 or 36, wherein the message indicates an identifier of the position source device. -47-

Clause 38: The mobile device of any of clauses 21-37, wherein to obtain the position information, the one or more processing units are configured to: determine whether to request the position information from one or more position source devices; and in response to determining that the position information is to be requested, request the position information.

Clause 39: The mobile device of clause 38, wherein to determine whether to request the position information from the one or more position sources devices, the one or more processing units are configured to select at least one position source device based on: an accuracy of position information provided by the at least one position source device, information that indicates that the position uncertainty of position information provided by the at least one position source device meets or is below the uncertainty threshold, a cost of position information provided by the at least one position source device, or any combination thereof.

Clause 40: The mobile device of clauses 38 or 39, wherein requesting the position information comprises requesting position information such that the position uncertainty of the position information meets or is below the uncertainty threshold.

Clause 41: A mobile device for determining a Precise Point Positioning (PPP) position, comprising: means for obtaining one or more Global Navigation Satellite System (GNSS) signals; means for obtaining position information based on one or more position sources, wherein the position information is indicative of a location of the mobile device; means for determining one or more Precise Point Positioning (PPP) positions of the mobile device based on the position information and the one or more GNSS signals, wherein a position uncertainty of the position information meets or is below an uncertainty threshold; means for determining whether at least one PPP position meets or is below one or more convergence thresholds; and means for providing the at least one PPP position in response to determining that at least one PPP position meets or is below the one or more convergence thresholds.

Clause 42: The mobile device of clause 41, wherein the one or more position sources comprise one or more of: a wireless base station, a wireless Access Point -48-

(AP), an Ultra Wide Bandwidth (UWB) device, a Radio Frequency (RF) sensing device, a LIDAR device, or an Internet of Things (IoT) device.

Clause 43: The mobile device of clause 42, wherein the wireless base station provides Real Time Kinematics (RTK) position information.

Clause 44: The mobile device of clause 43, further comprising means for determining an RTK position based on the RTK position information.

Clause 45: The mobile device of any of clauses 41-44, wherein the means for obtaining the position information comprise means for determining, by the mobile device, the position information using: Fifth Generation (5G) signals, UWB signals, WiFi signals, Fine Timing Measurements (FTM) or any combination thereof.

Clause 46: The mobile device of any of clauses 41-45, wherein the position information is received by the mobile device in a Vehicle to Everything (V2X) message.

Clause 47: The mobile device of any of clauses 41-46, wherein the one or more GNSS signals are multi-constellation and multi-band signals.

Clause 48: The mobile device of any of clauses 41-47, wherein the uncertainty threshold is based on: a device type of the mobile device, an application type of an application executing on the mobile device, a requested accuracy by the mobile device, a requested accuracy by an application executing on the mobile device, a predetermined threshold, or any combination thereof.

Clause 49: The mobile device of any of clauses 41-48, wherein the uncertainty threshold is between 10 and 30 centimeters.

Clause 50: The mobile device of any of clauses 41-48, wherein the uncertainty threshold is between 30 and 50 centimeters.

Clause 51: The mobile device of any of clauses 41-50, wherein the means for determining the one or more PPP positions of the mobile device comprises means for constraining a covariance matrix associated with a Kalman filter. -49-

Clause 52: The mobile device of clause 51, wherein the means for determining whether the at least one PPP position meets or is below the one or more convergence thresholds comprises means for determining whether values of the covariance matrix have changed over a time window.

Clause 53: The mobile device of any of clauses 41-52, wherein the means for determining the one or more PPP positions of the mobile device comprises means for using the position information to resample particles used by a particle filter.

Clause 54: The mobile device of any of clauses 41-53, wherein the means for determining the position information comprises: means for obtaining, by the mobile device, sensor data, wherein the sensor data comprises camera data, RF sensing data, LIDAR data or any combination thereof; means for identifying one or more physical features of one or more landmarks based on the sensor data; and means for determining the position information based on one or more locations of the one or more physical features.

Clause 55: The mobile device of any of clauses 41-54, wherein the means for determining the position information comprises: means for receiving a message from a position source device, wherein the message is transmitted by the position source device in response to detection of the mobile device; and means for determining the position information based on the message.

Clause 56: The mobile device of clause 55, wherein the means for determining the position information comprises means for retrieving a stored location of the position source device from a memory of the mobile device.

Clause 57: The mobile device of clause 55 or 56, wherein the message indicates an identifier of the position source device.

Clause 58: The mobile device of any of clauses 41-57, wherein the means for obtaining the position information comprises: means for determining whether to request the position information from one or more position source devices; and means for requesting the position information in response to determining that the position information is to be requested. -50-

Clause 59: The mobile device of clause 58, wherein the means for determining whether to request the position information from the one or more position sources devices comprises means for selecting at least one position source device based on: an accuracy of position information provided by the at least one position source device, information that indicates that the position uncertainty of position information provided by the at least one position source device meets or is below the uncertainty threshold, a cost of position information provided by the at least one position source device, or any combination thereof.

Clause 60: The mobile device of clause 58 or 59, wherein requesting the position information comprises requesting position information such that the position uncertainty of the position information meets or is below the uncertainty threshold.

Clause 61: A non-transitory computer-readable medium storing instructions for determining a Precise Point Positioning (PPP) position, the instructions comprising code for: obtaining one or more Global Navigation Satellite System (GNSS) signals; obtaining position information based on one or more position sources, wherein the position information is indicative of a location of a mobile device; determining one or more Precise Point Positioning (PPP) positions of the mobile device based on the position information and the one or more GNSS signals, wherein a position uncertainty of the position information meets or is below an uncertainty threshold; determining whether at least one PPP position meets or is below one or more convergence thresholds; and in response to determining that at least one PPP position meets or is below the one or more convergence thresholds, providing the at least one PPP position.

Clause 62: The computer-readable medium of clause 61, wherein the one or more position sources comprise one or more of: a wireless base station, a wireless Access Point (AP), an Ultra Wide Bandwidth (UWB) device, a Radio Frequency (RF) sensing device, a LIDAR device, or an Internet of Things (IoT) device.

Clause 63: The computer-readable medium of clause 62, wherein the wireless base station provides Real Time Kinematics (RTK) position information. -51-

Clause 64: The computer-readable medium of clause 63, wherein the instructions further comprise code for determining an RTK position based on the RTK position information.

Clause 65: The computer-readable medium of any of clauses 61-64, wherein obtaining the position information comprises determining, by the mobile device, the position information using: Fifth Generation (5G) signals, UWB signals, WiFi signals, Fine Timing Measurements (FTM) or any combination thereof.

Clause 66: The computer-readable medium of any of clauses 61-65, wherein the position information is received by the mobile device in a Vehicle to Everything (V2X) message.

Clause 67: The computer-readable medium of any of clauses 61-66, wherein the one or more GNSS signals are multi-constellation and multi-band signals.

Clause 68: The computer-readable medium of any of clauses 61-67, wherein the uncertainty threshold is based on: a device type of the mobile device, an application type of an application executing on the mobile device, a requested accuracy by the mobile device, a requested accuracy by an application executing on the mobile device, a predetermined threshold, or any combination thereof.

Clause 69: The computer-readable medium of any of clauses 61-68, wherein the uncertainty threshold is between 10 and 30 centimeters.

Clause 70: The computer-readable medium of any of clauses 61-68, wherein the uncertainty threshold is between 30 and 50 centimeters.

Clause 71: The computer-readable medium of any of clauses 61-70, wherein determining the one or more PPP positions of the mobile device comprises constraining a covariance matrix associated with a Kalman filter.

Clause 72: The computer-readable medium of clause 71, wherein determining whether the at least one PPP position meets or is below the one or more convergence thresholds comprises determining whether values of the covariance matrix have changed over a time window. -52-

Clause 73: The computer-readable medium of any of clauses 61-72, wherein determining the one or more PPP positions of the mobile device comprises using the position information to resample particles used by a particle filter.

Clause 74: The computer-readable medium of any of clauses 61-73, wherein determining the position information comprises: obtaining, by the mobile device, sensor data, wherein the sensor data comprises camera data, RF sensing data, LIDAR data or any combination thereof; identifying one or more physical features of one or more landmarks based on the sensor data; and determining the position information based on one or more locations of the one or more physical features.

Clause 75: The computer-readable medium of any of clauses 61-74, wherein determining the position information comprises: receiving a message from a position source device, wherein the message is transmitted by the position source device in response to detection of the mobile device; and determining the position information based on the message.

Clause 76: The computer-readable medium of clause 75, wherein determining the position information comprises retrieving a stored location of the position source device from a memory of the mobile device.

Clause 77: The computer-readable medium of clause 75 or 76, wherein the message indicates an identifier of the position source device.

Clause 78: The computer-readable medium of any of clauses 61-77, wherein obtaining the position information comprises: determining whether to request the position information from one or more position source devices; and in response to determining that the position information is to be requested, requesting the position information.

Clause 79: The computer-readable medium of clause 78, wherein determining whether to request the position information from the one or more position sources devices comprises selecting at least one position source device based on: an accuracy of position information provided by the at least one position source device, information that indicates that the position uncertainty of position -53- information provided by the at least one position source device meets or is below the uncertainty threshold, a cost of position information provided by the at least one position source device, or any combination thereof.

Clause 80: The computer-readable medium of clause 78 or 79, wherein requesting the position information comprises requesting position information such that the position uncertainty of the position information meets or is below the uncertainty threshold.